I am having a Devil of a time understanding why a certain type of OSC message is not working.
I am trying to trigger a cue in Qlab. I have two machines and I use one as a master and one as a slave. When I press a go button in my TD network, it reads the current cue from the master and sends a go cue to the master.
The problem has to do with sending the cue to the slave.
If I send the command explicitly, op('oscout2').sendOSC('/go',['4'])
, it works perfectly. However, when I get the current cue from the master and try to send the command to the slave in any other way, as in, op('oscout2').sendOSC('/go',[cueNumber])
, nothing happens. cueNumber
is a string I pull from a select like this, cueNumber = op('select1').text
.
I can print this to the console and I know I am getting the right cue number. I have tried a number of things like cueNumber = "'"+op('select1').text+"'"
to get a string with literal quotes. No matter how I format the string, Qlab will not respond when the cue number is anything other than a string literal in the list.
Is there something I’m missing? I mean, there must be. I cannot see how you couldn’t use a string variable rather than a string literal.