i ve saw you have an answer but because , one question has often many answer , I would know if it could possible to use user actor ?
Build your user actor as you builded your first scene , then past that user actor in each scene that you need it . Then each time you need ( new show ?) Change the value in the user actor in the first scene and when close the user actor , select update all .
Hi @dusx the top comparator in the second row outputs "true" when there's a match but "true" and "false" when there isn't... as you say i think its a timing issue and its input is actually going from 1 to 0 very fast, hence causing true and false output
i've managed to create a work-around by increasing the first router's number of outputs from 9 to 10 and also the first table's number of inputs from 9 to 10 and then ignoring the first of each, as per this updated patch Step Sequencer (ver 25) workaround.izz which now achieves what i was after
I think you should be able to find a 'FFGL Tile' plugin that may replace the MultiVid actor, depending on your exact usage. Try the 'FFGL Tile' actor in the oficial FFGL bundle first: https://troikatronix.com/plugi...
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.