I'm pretty sure we were listening to "all types" so I figure that would include lighting commands. Do you know if Isadora's built in MSC control requires a go command? Maybe that's why one works, but not the other.

Thank you for your help.

Do you know of a situation where I would receive MSC through the built in Isadora MSC, and not with the internal scene actor? Does the MSC actor want a different message from lighting?

 Not that I can think of. Maybe the 'cmd format' input needed to be changed to lighting or maybe the lighting board wasn't sending "go" commands, which are the default that the MIDI Show Control Watcher actor looks for.

Communications > MIDI Setup?

 Unfortunately yesterday was my last day programming for that show, so I'm no longer near the system. 

Do you know of a situation where I would receive MSC through the built in Isadora MSC, and not with the internal scene actor? Does the MSC actor want a different message from lighting?

It should have no issue with it, it's what my whole system was based on. Can you post a screenshot of a MIDI Show Control Watcher actor in your patch as well as a screenshot of Communications > MIDI Setup?

If the lighting console were to send, cue 265.5, can the MSC watcher not read that?

You could also use my system for this: https://community.troikatronix.com/topic/5543/midi-show-control-scene-navigation-cueing-system?_=1717508857617

It pre-dates the built-in MSC Scene Jump feature but has a User Actor for cues internal to a Scene. You will need to be in the Scene that contains that internal cue before you can successfully trigger it.

Are you using a MIDI Show Control Watcher actor into a Text Comparator actor while the Scene containing the cue is already active?

Hi Juriaan

We are using decimals. Scene to scene these jump just fine. Is it a float vs integer thing?

How is your cue numbering in EOS?

1, 2, 3, 4

Or are those internal cues numbered 2.1, 3.2, 4.2 etc?