Here's an example patch

The first Scene is your "preshow" scene. In this Scene you'll just press spacebar to start the cycling Scenes going in their loop.

The next three Scenes (Cycling Scenes 1-3) are identical. They have example content in them, and an Enter Scene Trigger connected to a Trigger Delay (15 secs) that will trigger a jump to the next scene after the delay. There's also a Gate (controlled by a Keyboard Watcher) between the Trigger Delay actor and the Jump actor so that if you need to program something in the Scene, you can press "a" to temporarily disable the automatic jump.

The Final Scene is an example of what to do if you want the Scenes to continue looping forever. It's essentially identical to the previous three cycling Scenes, but instead of jumping to the next Scene (because there isn't a next Scene) it jumps to the first cycling Scene, which starts the loop again.

Hope that's helpful :)

Best wishes,

Woland

@notdoc

...and part of the problem is that i fail to read to the end of the tutorial where some important scene-control stuff gets explained... a lesson for the future :-)

hi , 

sorry my bad, it was the nano control 2 macro that is all wired with comparators that was trigger all envelopes... I have to clean my version of it regarding my use...
maybe you can delete this post now !
debeug controller.izz

@woland thanks for posting this - i have so much to catch up with in isadora 3 !

...we ask because in the manual there are only four options in the drop down?

"

Isadora Manual96DirectionThe Direction drop-down menu determines which action you wish to set up with a Go Trigger. There are fouroptions.Next Scene. When the specified key or input is received, Isadora transitions from the active scene to the succeeding scene in the scene list. As before, this will create a crossfade transition between scenes if a Fade Out time has been specified for the current scene, orif a Fade In time has been specified for the following scene.Previous scene. When the specified key or input is received, Isadora transitions from the active scene to the preceding scene in the scene list. This will create a crossfade transition between scenes if a Fade Out time has been specified for the current scene.Go Forward. When triggered, sends a trigger to the Go Forward actors in the active scene.Go Backward. Sends a trigger to the Go Backward actors in the active scene.By default, only the ‘Next Scene’ direction is enabled. You can enable any of the others by specifying what activates each Go Trigger direction: Keyboard, MIDI, or HID.

"

thx

r.h.

@nickdesigner84 said:

virtual stages - I was wondering what they could be used for...

 You can use them like this to group a bunch of overlapping content and then easily manipulate its location and scaling as a whole. (I used a Virtual Stage for all the shapes that make up the penguin's head.)

Penguin.izz

@michel

Off course! How could I forget. Thanks a lot Michael ;o)

Our event in Rome in the press.

https://www.biancoscuro.it/sit...

https://www.lineadarte-officin...

https://www.sordionline.com/te...

http://www.datedarte.it/events...

https://www.arte.go.it/event/w...

@d1gits

If it is an AV foundation codec (we are not familiar enough with current offerings to know if this is the case) it may be possible to have it become available in the future.

However, it will not be back as a Quicktime only codec.
At this time the website, seems to only mention QuickTime (https://resolume.com/software/...)

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.

@mclefferson

You are correct. It appears some inputs are no longer available.
I have logged a ticket, to have this inconsistency looked into.
thank-you for the feedback.

@malibu

If you're willing to post your patch I can take a look. It may be that your approach is not optimal.

Best wishes,

Woland

@HelenDeneb 

look at this post to see how it works: https://support.troikatronix.c...

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.

@tgtmedia
I am also going to suggest using Nodered to bridge the gap. Isadora doesn't use NodeJS, so some package may not be possible to use a js libs in Isadora (some can, with slight modification).
NodeRed is a great option to run side by side with Isadora for this purpose.

I've also run into this: https://community.troikatronix...

@Michel 

Thanks, Michel. Always good to see the simple things I think I know but don't : 0

please open a support ticket and include your isadorable file that is causing the  trouble. 

The support link is in my signature.

There should not be a limit (definitely not at that number) so it would be helpful to take a look at the file.

Thanks

@Salimelo 

I've had huge success sending MIDI Show Control (MSC) from QLab and ETC Ion/Nomad lighting consoles to trigger Isadora (via MIDI Show Control Watcher actors paired with comparators), in conjunction with using @dbengali (Mac) and @djinoui 's (Windows) JumpByName custom Isadora plugins and then prefacing Scene names with MSC cue #'s.

JumpByName.izzyplug.zip (Mac)

Best wishes,

Woland

Yeah, I've been using jumpbyname for years. It's been awesome. I usually disable the midi while editing.