[SOLVED] Problems in Mojave with Isadora 2.6.1
-
Hello everybody. I'm having a rather new problem and haven't found the way to solve it.
I have a patch that was made in Isadora 2.6.1 running macOS Sierra and used to run with no problems. I was forced to upgrade to Mojave and the patch seemed to work OK for a while, until today, when I found I can not open the patch anymore, with Isadora giving an unexpected error message (ID=1852402768) which I assumed was caused by a corruption in the patch file.
First thing, I tried to open it with Isadora 3.0.7 (Demo mode) and, much to my surprise, it did open (so I assume the problem is not within the patch itself, right?) but then it doesn't work as expected in a couple of scenes.
I know Izzy 2 is not recommended with Mojave, and I was already thinking of upgrading to version 3, but I'm concerned with some subtle changes that make my patch behave different, so I'm asking for help to:
- Clarify whats the ID=1852402768 unexpected error so I can keep working with Izzy 2 (I can revert to an early save, but I'm afraid the problem comes back).or
- Help me understand what's up with the following things in Izzy 3:
- Gaussian Blur actor seems to take tons of CPU load. I use a gaussian blur with the amount parameter set to 50 in Izzy 2 with no problems, but in Izzy 3 I can't use it above 30 or so (even so, my frames drop drastically). And without the blur, or with a low amount, the visual effect is very different, it doesn't really work.
- The Mouse Watcher actor doesn't work if Isadora is not the top application. I'm playing all the audio in QLab and triggering Isadora via MIDI, but I use the Mouse at one point in the show to follow an actress. In Izzy 3, the Mouse Watcher doesn't respond without switching to Isadora, which is very inconvenient. Note that I don't want to use the Stage Mouse Watcher, I need my mouse pointer in my main screen.
- I changed the Target Frame Rate to 25 fps in the preferences, but Isadora keeps going for 30. I guess this is because of my inability to save the file in the demo mode, could someone confirm this?
- One scene which has a lot of Shapes actors rendering to a lot of 3D Projectors (all of which render to a single 3D Renderer) also runs very poorly sometimes. I guess I can work on my patch efficiency, but I'm surprised that this actually works quite well in Izzy 2 and not so in Izzy 3 (in the very same computer!) Are there any actors which for some reason are not quite updated to run in Izzy 3? Besides what I already mentioned, I use the Explode, Alpha Mask and Video Inverter actors in that scene. Or is there a different explanation for this?
Sorry for the long post, any feedback will be greatly appreciated. Cheers.
Using Mac OS 10.14.6 Mojave, 2.7 GHz Intel Core i5, 8 GB RAM, SSD.
-
Hi there,
If I'm not mistaking the error code is used for importing certain assets (like 3D models). But as an user we don't know this kind of error codes, to get the answer you really should create a new support ticket with the Izzy staff. They will know whats up and get the issues solved that you currently have. (https://support.troikatronix.c...)
Regarding the mouse watcher that works when the Window is not in the foreground. How would that even work ? Isadora needs to be on your screen to capture mouse input if I'm not mistaken. Or atleast on Windows I could not repro this, so perhaps this is a Mac only thingie ?
Anyhow; post a Technical Support ticket. They are able to help you out much faster then we can do and go in depth by looking into your patch.
Thanks !Isadora 3.1.1, Dell XPS 17 9710, Windows 10
Interactive Performance Designer, Freelance Artist, Scenographer, Lighting Designer, TroikaTronix Community moderator
Always in for chatting about interaction in space / performance design. Drop me an email at hello@juriaan.me -
@juriaan Hi there, thanks for your response.
Indeed, I will submit a ticket, it's probably the best thing regarding the error. It's just that I'm so used to post the problems in the forum since many times those problems have already been found (and solved) by someone else, and it's also a good place for other people to find out
As for the Mouse Watcher, up to Izzy 2, it did report the position of the pointer regardless of Isadora being the top application, at least in macOS. That's something that changed with Izzy 3. It would be good to know if that's just a bug which will eventually be solved or if this is the new Isadora behavior.Cheers.
-
@haradan said:
- I changed the Target Frame Rate to 25 fps in the preferences, but Isadora keeps going for 30. I guess this is because of my inability to save the file in the demo mode, could someone confirm this?
You can find the answer here: https://community.troikatronix...
Best Michel
-
@haradan said:
- The Mouse Watcher actor doesn't work if Isadora is not the top application. I'm playing all the audio in QLab and triggering Isadora via MIDI, but I use the Mouse at one point in the show to follow an actress. In Izzy 3, the Mouse Watcher doesn't respond without switching to Isadora, which is very inconvenient. Note that I don't want to use the Stage Mouse Watcher, I need my mouse pointer in my main screen.
I cannot reproduce this behaviour. On my Mac the Mouse Watcher actor runs in the same way with 2.6.1 and 3.0.7: As I write this post in Safari the Mouse Watcher actor follows my movements even though Safari is in the foreground and Isadora is in the background. System is Mojave
best
Jean-François
-
@haradan said:
I have a patch that was made in Isadora 2.6.1 running macOS Sierra and used to run with no problems. I was forced to upgrade to Mojave
As you said, Isadora 2.6.1 is not officially supported on macOS 10.14.x (Mojave), as outlined in the System Requirements for Isadora 2. Anything that works alright on Mojave with Isadora 2 is all well and good, but if something in Isadora 2 doesn't work on Mojave we may not be able to help you since you're running the software on an unsupported operating system.
@haradan said:
- Clarify whats the ID=1852402768 unexpected error so I can keep working with Izzy 2 (I can revert to an early save, but I'm afraid the problem comes back)
Please create a support ticket, though again, we may not be able to help you since you're running the software on an unsupported operating system.
@haradan said:
- Help me understand what's up with the following things in Izzy 3:
- Gaussian Blur actor seems to take tons of CPU load. I use a gaussian blur with the amount parameter set to 50 in Izzy 2 with no problems, but in Izzy 3 I can't use it above 30 or so (even so, my frames drop drastically). And without the blur, or with a low amount, the visual effect is very different, it doesn't really work.
The first thing to do is make sure that your video actors are using the "vid gpu" video type instead of "vid cpu". You can mutate existing actors from cpu to gpu by disconnecting an actor from any other video inputs and outputs, then connecting the vid cpu actor to a fresh Projector actor (or any actor that has the vid gpu data type). You cannot mutate an actor to vid gpu from vid cpu if it is still connected to any any other vid cpu actors, so make sure you disconnect it before you try to mutate it. As a rule, you should be using gpu instead of cpu whenever and wherever possible.
Try using Gaussian Blur or FFGLblur but in Isadora Preferences set your target framerate to 50. If your computer is struggling to hit the mark, putting your the target way above what you actually want can sometimes help in attaining the framerate you want.
@haradan said:
- The Mouse Watcher actor doesn't work if Isadora is not the top application. I'm playing all the audio in QLab and triggering Isadora via MIDI, but I use the Mouse at one point in the show to follow an actress. In Izzy 3, the Mouse Watcher doesn't respond without switching to Isadora, which is very inconvenient. Note that I don't want to use the Stage Mouse Watcher, I need my mouse pointer in my main screen.
I have no trouble getting this simple test patch to work in Isadora 2 nor in 3.0.7 regardless of whether Isadora is the front application or not.
@haradan said:
- I changed the Target Frame Rate to 25 fps in the preferences, but Isadora keeps going for 30. I guess this is because of my inability to save the file in the demo mode, could someone confirm this?
As @Michel said, see this thread: https://community.troikatronix.com/topic/6038/answered-isadora-3-framerate
@haradan said:
- One scene which has a lot of Shapes actors rendering to a lot of 3D Projectors (all of which render to a single 3D Renderer) also runs very poorly sometimes. I guess I can work on my patch efficiency, but I'm surprised that this actually works quite well in Izzy 2 and not so in Izzy 3 (in the very same computer!) Are there any actors which for some reason are not quite updated to run in Izzy 3? Besides what I already mentioned, I use the Explode, Alpha Mask and Video Inverter actors in that scene. Or is there a different explanation for this?
Send us your patch and 3d files in the ticket and I can take a look to see if I can make any suggestions to help with this. One thing to check is again to make sure that your video actors are using the "vid gpu" video type instead of "vid cpu".
Isadora 3 has a new, cross-platform licensing system with easy license-management in the program and via a new online License Portal. Isadora 3 is supported on Windows 10 (64-bit) and macOS 10.11.x (El Capitan) to macOS 10.15.x (Catalina), is fully 64-bit, contains a number of exciting new features like NDI support, depth camera skeleton tracking, a PJLink plugin, a screen/window capture plugin, more new plugins, and has new video tutorials so you may want to consider upgrading your license regardless.
Additionally, Isadora 2 and Isadora 3 can co-exist on the same computer without conflict, so if you upgrade you can still continue to use Isadora 2 without issue.
Best wishes,
Woland
-
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.
