Skip nonexistent columns when using OSC /action/launchColumn?
Hi there,
I'm a big fan of this software and really enjoy using it.
I recently set up a show where I hoped to trigger columns via OSC via ETC EOS. I set up EOS to send a custom string every time a cue was fired. My Millumin cues are named to match the light cue numbers.
I hoped to use Millumin's /action/launchColumn , but found that when EOS fired a cue that did not have an accompanying video cue, Millumin would go black. It was as if we were launching the absence of a column because we were firing /action/launchColumn for a column that did not exist.
Is there a way to only apply launchColumn to existing columns? I resorted to a single custom OSC interaction for each cue but would love an easier way to do it.
Thanks!
Zach
Comments
Hello @zachwcohn,
Indeed, if you ask Millumin to launch a column that does not exist, it stops the current column : if you ask to launch the column at index -1 or 999 for example, or with a title that does not exist.
We will see if we can slightly adjust this behavior, so when a title does not exist, Millumin does nothing. But we do not want to change much in the behavior, as it has been like this for years.
Best. Philippe
Hi @zachwcohn I encountered this same issue. I ended up building a filtering javascript code snippet that parses what I set up as /lx/cue/M5 coming from EOS (with Media cue 5 = M5 and appended the "M" to the cue number in the lighting board). Then, it checks it against columns that exist in my Millumin file, and if it's there then it launches the OSC to trigger its launch, and if not it doesn't. If we could adjust this behavior in a future update of of course that be great! However, this is all documented in more detail here:
good luck!
Joseph
Hello @jamodei,
We prepare an improvement for next beta version (5.15.l), so if the index is after the last column of the dashboard, it does nothing.
Best. Philippe
Nice, thanks