TouchOSC & QLab Preview Standby

643 views
Skip to first unread message

Brendon Warner

unread,
Aug 13, 2016, 8:03:23 PM8/13/16
to QLab
Hi all!

I'm trying to build a very basic QLab remote in touchosc. I have gotten everything working that I need except I am trying to figure out a way to send touchosc the current cue on standby from qlab. Does anyone here know if this is possible? 

The current setup I have is iPad with TouchOSC -> OSCulator -> Qlab and then for now Qlab -> TouchOSC all on a closed network we have for our show control. 

Thank you!

Andy Lang

unread,
Aug 13, 2016, 9:54:07 PM8/13/16
to ql...@googlegroups.com

On Sat, Aug 13, 2016 at 8:03 PM Brendon Warner asa...@gmail.com wrote:

I'm trying to build a very basic QLab remote in touchosc. I have gotten everything working that I need except I am trying to figure out a way to send touchosc the current cue on standby from qlab. Does anyone here know if this is possible? 

It is not possible without some sort of custom translation utility in between, because QLab only transmits the cue details as a JSON array, which TouchOSC doesn’t know how to decode. We’re definitely interested in expanding how and what QLab can communicate over the network in the future, but for the time being, the only way to do this is to use QLab Remote, or to write your own program that can ask QLab for the current standby position’s cue name, and then parse the JSON to retrieve just the cue name part of it.

Don’t hesitate to reach out if we can help with anything else, and have an awesome Saturday night!

-Andy


Andy Lang
@SoundGuyAndy
sup...@figure53.com

micpool

unread,
Aug 14, 2016, 3:33:29 AM8/14/16
to QLab
However……..


If you are only going to be playing one cue at a time, read this thread:


 for a touch OSC project that will do this

The Touch OSC display will only update when you press buttons on the TouchOSC device, so it will not reflect any auto follows or activity on the host computer.

It works by using a set of cues which your buttons start, which in addition to controlling the QLab workspace send the names of the last played  and next cues to your TouchOSC device via OSC.

You can adapt this to send other text to TouchOSC from QLab.

It is possible to extend this method to continuously update the iOS device with the current standby cue in one of 2 ways.

1) Don't use TouchOSC but use LEMUR instead. This could trigger the cue in QLab  that sends the feedback to the iOS device every ½ second or so from a script in Lemur.

2) Use a loop in QLab to send the OSC to the label field in TouchOSC every ½ seconds or so.  The loop could be triggered when the workspace is opened automatically using the options.  in Settings General. The problem is the first time you panic the  workspace, using ESC to stop all running cues , your loop will stop as well, so you need to devise some method of restarting it. Or create your own panic cue on a hotkey that doesn't stop the loop.  This method is a bit impractical for general use, but for a fixed installation show just using the iOS device as the controller it works quite well.

Mic



On Sunday, August 14, 2016 at 2:54:07 AM UTC+1, Andy Lang wrote:

Lee, Jeremy (lee4jm)

unread,
Aug 25, 2016, 1:41:49 PM8/25/16
to ql...@googlegroups.com
Late to the party, but didn’t Wil Pickins just do this?

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/CACCWb6sCn9t67Y5H_gvzpvhPwZZrgFoTzxPzh6wafKcp92hViA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
Jeremy J Lee
Assistant Professor - Sound Design
College-Conservatory of Music
University of Cincinnati


Will Pickens

unread,
Aug 26, 2016, 10:15:27 PM8/26/16
to QLab
I wrote a beta program that runs in node in the background that translates the Json to OSC.

Here is the GitHub
https://github.com/willpickens/QLabOSCTranslate

And here is a YouTube video of how it works
http://youtu.be/oba4nL8g4lE

I haven't written a step by step, but if you have trouble setting this up contact me

I'd love to hear feedback from this.
Thanks

Juan Miguel Alcarria Herrera

unread,
Aug 29, 2016, 5:05:31 AM8/29/16
to QLab
¡Hi Will! 

¡Great work! Works for me very well :-)

I have seen a problem with the cue's name, if it's accentuated like many words in Spanish like "Camión", the node display this:

SyntaxError: Unexpected token  in JSON at position 44

    at Object.parse (native)

    at .<anonymous> (/Users/juanmi/Desktop/qlabosctarnslate.js:109:13)

    at emitTwo (events.js:106:13)

    at emit (events.js:191:7)

    at Socket.<anonymous> (/Users/juanmi/node_modules/node-osc/lib/Server.js:27:20)

    at emitTwo (events.js:106:13)

    at Socket.emit (events.js:191:7)

    at UDP.onMessage (dgram.js:550:8)


Thanks and sorry for my English ;-)


--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab

Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/1c7ba1ec-485c-48a4-896b-2741c969530b%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages