OSC Listener does not always respond to Message from Ion
-
I am running a show file where, the ETC ion console is sending out an OSC message over the local network to isadora. I’m Isadora per cue, there is a OSC listener actor that it set to the specific cue number in the lighting console. I have setup the network to be local and input the correct syntax into isadora for OSC to work. The majority of scenes trigger fine when the ion cue is fired, but there are a few that don’t. I have looked at the monitor in both isadora and eos. Everything sends correctly, and receives correctly. I have checked my syntax in stream setup. And I can’t figure out why. When isadora does not trigger, even though the ion has sent the command. It’s not always in the same spot. Some night only a few don’t trigger and other night more don’t. I have gone through everything on the computer and on the network and nothing is out of the normal. Also the way in which I am triggering isadora is something I have done before. My only change right now is that I was running isadora on a Mac, now I’m on a windows 11 intel i5
-
Is this a completely private network dedicated solely to communication between the two devices, or is there other traffic on the network?
-
@woland, currently. Yes. The only items on the network is the lighting console and isadora computer and the network router. Originally it was also going to also control the projectors, but I had issues with that and decided to remove them entirely from the network.
-
Hey! We were talking about this in our internal channels.. Something that I would love if you could give it a shot is using a master scene.
The actor that I wrote called IzzyEos, which can be found here (https://community.troikatronix... ) has an example file to show you what I mean with a Master scene approach. It is basically a background scene that stays activated.
Let us know how that goes
