@tlaloc

There's also:

• Jump By Name (which is the basis for my MIDI Show Control template file that I use to make lighting consoles or QLab trigger jumps between Scenes, as well as cues internal to Scenes)
• Deactivate Scene (for use with the Activate Scene actor)
• Activate Scene Amount (usually best used with Envelope Generator, Ease In-Out, or Ease In-Out 2D actors)

Just to cover all the bases, here's this which shows all the options (and includes some User Actors of mine). --> FILE DOWNLOAD

Best wishes,

Woland

P.S. If you want to be able to set scene jump times across all your scenes globally, you can use Set/Get Global Values for that. My background scene activation User Actors on the bottom right there should be pretty helpful for this too.

@emullis said:

SmartSuit Pro II

 There are two flavors of Pro II. One is designed to be used with the Smart Gloves, and one isn't. Which flavor are you working with, and, if it's the gloves one, are you using the gloves or not?

@skuven

This isn't really my wheelhouse, but is it possible to send 9 parameters on port 1 to your destination and then the remaining 6 channels to it on port 2?

@DusX any thoughts about the Javascript approach?  Or maybe Pythoner can be used to send 15 parameters of Sys Ex messages?

@tlaloc in addition to @dbini great suggestions, you could also try Jump to Cue - useful if you want to jump forward or backward to a scene that has a specific cue number. This is useful if you are manually addressing scenes with a specific cue number.

Additionally, Activate Scene allows you to activate a secondary scene which runs in the background whilst in the current primary scene.

Best wishes, Simon

@tlaloc
Jump and Jump++ actors?

Is there a way to get the fade time into an actor. Example if the bext scene should fade in 16, can I get that value programaticaly in an actor?

Thanks! 

T

So the set and get global values do not work consistently with the trigger. Is the recommended actor for this broadcaster and listener?

Thanks in advance!!

Tláloc López-Watermann 

1. I'm using Isadora 4.1.3. I entered the wrong version in my original post.
2. I checked it with Legacy, and Izzy is not crashing with that version.
3. I'm working with the SmartSuit Pro II. The crash happens when I stream from the suit or from a mocap recording (e.g., no suit). Not sure if that matters. 

hi

i’m toying around with behringer xtouch mappings between different software. Utilising the sys ex send actor i can remap the text of the channel strips on the control surface. The problem is there are only 9 parameters max on that plugin but I want 15 or so. I was going to look at javascripting it somehow. Any solve?

thanks

@cacoos

It's a known cosmetic issue on newer versions of macOS with Isadora 4.1.3 and older.

This is fixed already for the release that's coming very soon.

In the meantime, you'll see that those areas are only blank when you do not have MIDI, OSC, Serial, or TCP/IP data going to or from Isadora. As soon as data is going in or out, the relevant section of the UI will update.

In its simplest form, you can do this to see what I mean:

Here's a slightly more complex example that demonstrates the same thing, but cycles through each of those four data types: DOWNLOAD

(NOTE: The MIDI won't work unless you use the settings shown in the screenshot for Communications > MIDI Setup > Port 1 > (Input and Output set to "Isadora Virtual Out")