What you can also do is use a Enter Scene Trigger and a Trigger value to 0, connect that to all your Audio Players, that way when you enter the scene all active fields get a zero causing them to become OFF instead of ON. 🙂
You may also want to change the Direction on your Keyboard watcher to "Up" to prevent multiple triggers (since holding down the spacebar too long with the Keyboard Watcher set to "Down" can trigger the Keyboard watcher in the Scene your transitioning from AND the Scene you're transitioning into).
Adding a Multiblocker actor between the Keyboard Watcher and the Jump Actor is another way to prevent accidental activation of more than one Jump actor.
@woland Yes! I am working on this project again. I was waiting until V3 to dig in. I have a show in a month or so with FFoB and am working through refining and simplifying my patches. Excited about the speed increase and the fact that controls will run on a separate thread so I can use it to monitor audio inputs and routing to effects etc without taking a performance hit to the engine.
I would like to add an information: I have been able to correct similar issues with "spots" in Max/Jitter by forcing textures from "char" to "float32". Would there be a way to do something similar in Isadora?
i don't have isadora now with me to give it a try but maybe try to put the activate scene actor inside the scene you want to activate. So when you press the letter for the scene you want live, it will stay activated.
i got some problems starting Isadora. When i want to boot the program i get this error message:
it seems that he cant load the actors at all. when i look into the plugin folder, they are where they should be. i already tried reinstaling it and start it without any firewal, nothing works. I use an quite new windows 10 laptop and the newest version of isadora. do you have any ideas how i can solve this problem? Thanks a lot!
@michel it's odd - it was set at 1280 x 720. I'm still getting the aliasing when I set the shader to a low resolution. It's tough to find that balance of a clean dither and a lo-res look.
Hello together – first forum entry here. I'm currently using licenced Isadora 2.6 on a MacBook Pro running macOS High Sierra, 10.13.6.
As soon as I insert a Comment actor into the Scene Editor, I am not able to save either as regular save, backup, auto-save, run only or under another file name. If I remove the comment actor, saving is possible again. Does anybody observe the same? Any ideas?
Thanks for the usefulness of your patchwork. I have modified the patch again to make a control panel timer with a reset button. I used it for a show last night and thought to add to the shares here. It uses a Pulse Generator set to 1hz to 'count' seconds that then add-up to minutes and hours. The control panel 'monitor' is set to a 2 hz refresh rate.
2.6 did improve the ability to use these within user actors (as noted earlier), and there is currently no option for user built input lists like this.
My work around is to use an int input and associate an output to display the name of the selected item. You can limit the rang e of the Int to match the number of options and corresponding names/labels.
