Auto OSC control

[nickwi...@googlemail.com]

I tried have a Google around but didn't have much luck. I'm planning on running two Macs with the exact same workspaces on them, however I want one (the backup) to be triggered by the main computer. Is there a way that this can be done automatically (with software rather than hardware)? I know the slow way is to add OSC cues into the main computer that triggers the cues in the backup. 

Cheers

[Sam Kusnetz]

On February 17, 2014 at 2:41:43 PM, nickwi...@googlemail.com (nickwi...@googlemail.com) wrote:

I tried have a Google around but didn't have much luck. I'm planning on running two Macs with the exact same workspaces on them, however I want one (the backup) to be triggered by the main computer.

Hi Nick

The short answer is no, there’s not currently a way for QLab to automatically broadcast OSC commands that correspond with its operation, although we are thinking about things like that.

The longer answer is, this is not a good way to run a redundant setup anyway, and we advise against it. The reason for this is that you cannot have a redundant system where the backup relies on the primary, because there are too many way that the primary could fail and take out the backup with it.

Instead, we recommend using some external device to control both the primary and backup computers in parallel. That way, if the main Mac goes down, nothing else needs to change.

Cheerio

Sam

—

Sam Kusnetz
QLab Field Operative
s...@figure53.com

[nickwi...@googlemail.com]

Thanks for the reply Sam. Any suggestions on affordable hardware for triggering?

[mackerr]

On Monday, February 17, 2014 3:01:52 PM UTC-5, nickwi...@googlemail.com wrote:

Thanks for the reply Sam. Any suggestions on affordable hardware for triggering?

Define "affordable". A common solution is a Midi Solutions footswitch controller and momentary switch. A more elegant version is Andy LL's midi remote.

http://www.midisolutions.com/prodfsw.htm

http://ducksechosound.com 

Mac

[Ryan Joyner]

I have been playing with the Lemur app recently. It is only for iPad/iPhone but if you have one of those it could be very useful in your situation. If you are simply looking for a simultaneous "GO" button for your two machines/workspaces, that is a fairly simple task for Lemur. You would need to just create a button, set it to pad mode, then attach two script commands to that button that execute when variable x is increased (button gets pressed). One will direct an OSC go command to "Osc Target 0" which you will have setup to be your first machine's IP Address and Port 53000, the other will direct an OSC go command to "Osc Target 1" which you will have setup to be your second machine's IP Address and Port 53000. As long as they are all connected to the same wifi router, I would think this should work well for you. Let me know if you decide you want to go this route and I can attach a lemur file to get you started. The app is $50 but that is lower than the hardware being discussed so it is something to think about. Good luck!

Ryan

[Sam Kusnetz]

On February 17, 2014 at 11:19:14 PM, Ryan Joyner (ryanswi...@gmail.com) wrote:

I have been playing with the Lemur app recently. It is only for iPad/iPhone but if you have one of those it could be very useful in your situation.

<snip>

As long as they are all connected to the same wifi router, I would think this should work well for you. Let me know if you decide you want to go this route and I can attach a lemur file to get you started. The app is $50 but that is lower than the hardware being discussed so it is something to think about. Good luck!

Not to knock Lemur, which I think is awesome, but I cannot say that I recommend this particular plan.

WiFi is inherently problematic for live theater situations, because latency in a WiFi network is non-deterministic, meaning the delay between sending a message and receiving is is variable, and the WiFi spec permits this variability. In a non-show control setting, this matters not at all, or very very little, but as any good stage manager will tell you, having a variable amount of time between pressing GO and hearing or seeing the cue can really throw a show off the rails.

Again, I’m not trying to hate on Lemur, or on WiFi in general; QLab Remote uses WiFi! But it’s just not a technology that behaves predictably enough for me to use it for anything timing-specific.

[Ryan Joyner]

Fair enough point Sam!

[Nigel Hogg]

I use a USB remote from Widgeteering to control 2 Mac Mini's in the setup you describe. It works really well and is very reliable. (http://widgeteering.com/product/qwidget/)

Cheers,

[Neil Rose]

If you have the midi aspect of a Qlab license available, I've been using a Vestax Pad 1.  It's a 12 pad midi drum controller, but it has the benefit in this situation of have a Midi out, as well as connecting to a host computer via USB.  Other bonus is that the pads change colour when pressed (and also illuminate green, so easy to see in the dark!).  It doesn't give a tactile 'click' when pressed,which is the benefit of some of the dedicated remotes, but in addition to the usual GO/STOP/PREV/NEXT commands, I use it also as a shortcut controller, plus have some q lists on pads set up like a sampler, so I can fire instant spot FX.

  My setup was to have it connected to my Main machine via USB, and to my backup machine using the midi out.  As long as both machines are in sync at the beginning of the show, then it should all work fine.

  Programming of each pad is done on the unit itself.  Slightly more time consuming than hooking it up to a computer, and using a graphical interface (like the korg nano pads), but does have the benefit of being able to make changes, without loading up a separate editing program.  

  Obviously it draws it's power from the host computer, but an external 5vDC PSU can be purchased too.  My reasoning was that if Qlab crashes, the main machine should still have power.  If the main machine has lost power, then the backup will too, and that's a whole lot more serious situation than a missed sound cue.

  A quick google of the product should tell you how expensive it is in your part of the world.  I picked mine up for about £70 in the UK, via ebay.  Depending on your preference for tactile buttons, it may be a solution.

 Neil

[Janne Sivonen]

Or if you have a sound desk that has a midi function or a macro possibility, you could trigger the qlabs from a button on your mixer. I do this all the time with Digico's and Yamaha 01v96's.

Best,

Janne

--
--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
Janne Sivonen
Ljudtekniker /Soundengineer /Ääniteknikko
janne....@svenskateatern.fi
+358 50 5924362
(+358 50 3716443)

Svenska Teatern
Norra Esplanaden 2
00130 Helsingfors
vaihde (+358) 9616211

[nickwi...@googlemail.com]

OK, so I've realised that I can use my sound desk for doing this. I'll be using a Soundcraft Si Compact. It has a midi ouput, so I planning on purchasing one of these to get it over to USB:
http://www.amazon.co.uk/SODIAL-Cable-Converter-Keyboard-Window/dp/B008KGD6ZM/ref=sr_1_23?s=computers&ie=UTF8&qid=1392670120&sr=1-23

What's the best way to split the midi signal? Is there a better solution than that cable?

Cheers

[Fergus Mount]

Hi Nick, 

>OK, so I've realised that I can use my sound desk for doing this. I'll be using a Soundcraft Si Compact.

I have tried to do MIDI to Qlab from a Soundcraft Si Performer and I found the MIDI implementation to be pretty basic on the small Soundcraft desks. I believe you can only get the desk to send out MIDI program change when you move on to next scene, which is designed to changed patches on external processing. This does not really work for triggering Qlab. They might have updated the desk since I tried it, so it is worth checking with Soundcraft or getting your hands on the desk to try it yourself before it becomes an issue!

For splitting the MIDI signal, you can use any MIDI thru splitter. MIDI solutions and Kenton both make very good ones.

http://www.kentonuk.com/products/items/utilities/m-thru-5.shtml

http://www.midisolutions.com/prodqth.htm