First of all, thanks very much to everyone who answered, that's what I love about this forum.
Special thanks to @Woland for your long and specific answer.
I've been doing some testing on these things, I post what I found in case somebody else finds it useful:
- The error in 2.6.1 was indeed caused by my 3D models, but not by the file itself, rather than the path. For some reason, if I put the 3D files in my desktop, Isadora has no trouble, but whenever the files are inside any folder, the error window pops up.
- The mouse watcher error only happens with an imported 2.6.1 patch. The mouse watcher works as expected in Izzy 3 if you make a new patch, but it doesn't if you open an old file. Maybe if I was able to save it (updating it in the process) it would behave correctly afterwards, but I have no way of knowing this... yet.
- As for the Blur taking up a lot of CPU usage, I found out that a missing FreeFrame plugin could be the actual problem. After I installed the FFMotionBlur (which was in the 32-bit plugins folder but not in the 64-bit one) the scene runs in Izzy 3 more or less the same way than in Izzy 2.
Thanks again everybody. I think I will be updating to Isadora 3 very soon, since it's clearer now than the problems were more closely related to using Izzy 2 in Mojave and I really want to try some of the new features (like Blind Mode and such). Cheers.
Even though you say you are running Isadora v3, this error. would indicate otherwise.
Instead, it seems that you are attempting to run Isadora v2 on Catalina, which is not possible because it is a Isadora v2 is 32 bit app and Catalina will only run 64 bit apps. (macOS Mojave and older ran both 32 and 64 bit apps.)
This error is described on this page from Apple where it says "When you attempt to open a 32-bit app, you will see an alert that the app needs to be updated to work with this version of macOS, or that the app is not optimized for your Mac and needs to be updated." It shows the same dialog you attached above.
@dillthekraut I wanted to have the movie loop at the position it is playing at a particular moment. the patch repeat2.izz I posted above archieves that, I guess now there are two solutions for the same problem.
The spout error is related to internal video card settings, and is something that should be dealt with. Although Spout is included with Isadora, the official package will provide 2 executables, a sender and reciever. It might be useful to run these and see if you get the same error. This error is often related to video card switching, so it may be required to into the nVidia control panel, to the 3D section, and define that isadora.exe only use the dedicated graphics card. A step further is what Fred recommended, and disabling the onboard video card in the bios. This is not always required, so first test after setting isadora.exe to use only the high performance/dedicated card.
I manipulate many text for show and the best way, for me, is a special Quartz Composer patch able to open and parse an XML text. With that I can have a very precise control on what Is screened. The only problem is you have to make your text in QC (size, place etc.) and send image to Isadora. It's possible to send text, but accent (like in french) are very badly interpreted between QC and Isadora.
Mark, a data array with text? :-)
or a XML paser?
here is a sample of a QC patche, and an XML. I use it for a performance with multilingual subtitles
Hope that help
I was running for the evil clowns the last couple of days, but I am back and managed to grap the file. I just tried it again and now it seems to work. I didn't change a thing in my project. But anyway, here is the file I used to test it. I can imagine that it makes finding the problem a bit difficult. Thanks!