Re: [QLab] Linking multiple QLabs

[Mike P]

Hey Mitch,

Several of us do this on a regular basis. The answer is typically using MIDI for your network. QLab speaks all sorts of MIDI and can send and be programmed to receive any of it. The particular topology of the network can be either a classic MIDI arrangement or via MIDI over Ethernet. Classic MIDI can be done using various interfaces such as the MOTU Fastpath or one that's built into many of the popular audio interfaces used with QLab. MIDI over Ethernet can be done several ways, the most popular seeming to be the ipMIDI driver from this website:

http://www.nerds.de/en/ipmidi.html

Either way works well with a little tinkering. I generally prefer the classic arrangement since most of the devices I work with (lighting consoles, audio effects processors) already speak this natively. I use Fastpaths for the QLab machines. Then it's just a matter of assigning MIDI IDs and building the appropriate cues in QLab. One handy device for this arrangement is a MIDI 'fanout' such as the MIDI Solutions Quadra Thru to make your topology more of a star instead of a daisy chain. In some cases, it's a necessity since not all devices provide a Thru port.

One last note is if you want to go down this road, QLab will have to be licensed for MIDI on all the machines you want to use it on. The license is included in the Bundle or you can license it separately with the usual cost/rental options.

Hope this helps!

Mike Post
(601) 307-8657
mdp...@mac.com
http://mdpostdesign.com

On Nov 4, 2012, at 1:38 AM, Mitchell Smith wrote:

> Hey folks,
> I was wondering if anyone had any experience doing some sort of networking with QLab so that one computer could run a master q-list of several other slave computers. I've seen other programs out there that do it really well, like Watchout, but I am QLab faithful and want to see if I can make it work. Basically, I want one master computer that can fire cue lists on 3 slave computers that each have a projector hooked to them. What's your opinion on how this would work?
>
> Cheers,
> Mitch
>
> --
> Change your preferences or unsubscribe here:
> http://groups.google.com/group/qlab
>
> Follow Figure 53 on Twitter: http://twitter.com/Figure53

[Mitchell Smith]

Great!  Thank you very much.  As of right now there is no way to do it without MIDI though right?  Even if you do an ipMIDI, it's still using MIDI?

Cheers,

Mitch

[Mike P]

I wouldn't say that, but it is a very convenient way. Others may have different approaches.

Mike Post
(601) 307-8657
mdp...@mac.com
http://mdpostdesign.com

[Jeremy Lee]

Basically true. You could likely do some very convoluted system in which you send something like a telnet command to the QLab computer and translate that into an AppleScript command that fires your cues. But that's not probably the best route... 

Jeremy Lee

- A thumb is a terrible speller. Please forgive my trespasses.

[Mick Ritchie]

Does the easy midi license midiIP approach to this mean adding midi cues on the main Qlab for
every Go command so the computer keyboard can be used?

Ive never done the above but I could suggest a skin of the teeth alternative using midiIP and a
little freebie app called midistroke along with a cheap midi controller. midistroke will convert midi
into keystrokes ie spacebar. Ive set up 2 machines like this so 3 should be no problem - midistroke
and midiIP has to be set up on each machine to turn the incoming midi message from a usb controller into
a space bar and off you Go - make sure you have some reset cues on hot keys to save you resetting
each machine manually. The controller is essential without a midi license as you cant send midi out
thru the main qlab directly.

Its possible midistroke is so old it wont run on the Lions and Id think of having at least one midi license
for your main machine and you could always license multiple qlab for peace of mind as I set this up
as a poor musicians alternative for on stage control

best

mick ritchie

[Mick Ritchie]

Just done my own test and mdistroke still works on Lion so it isnt a rosetta sware. As an addendum I just found another bit of software that allows the main Qlab to be run from keys rather than a controller - called "midipress" this works in the background and will send off the Go command aas midi so only remote macs need midistroke.

Take it as read this is the cheap and cheerful approach and would need severe testing

mick

[Jeremy Lee]

IMO, if you can afford 3 machines, you can afford the MIDI license (or at least rent it) and skip the MIDIStroke complexity.

Jeremy Lee
Sound Designer, NYC - USA 829
http://www.jjlee.com

[ra byn taylor]

On Mon, Nov 5, 2012 at 6:38 AM, Jeremy Lee <jerem...@jjlee.com> wrote:

IMO, if you can afford 3 machines, you can afford the MIDI license (or at least rent it) and skip the MIDIStroke complexity.

And after running 3 machines for 2+ years now, you need to make the system as absolutely simple for the operator to understand even if it requires more hardware on the backside.

I've gotten in the habit of running "failure modes" when there is spare time so the operator actually "truly" understands what to do if X Y or Z happens. 

Otherwise having a backup or 2 can create a whole new set of unforseen issues that could ultimately be worse than a single failure. It's happened to me...

But at the end of the day, a backup of any sort is better than no backup at all when the main machine dies completely.  Headphone out on a mac book, backup CD' player that is actually patched & tested, SFX backup, Itunes backup, Ipod, etc... Anything to avoid a refund.

ra byn (robin)