Qlab 3 and Yamaha LS9

[Dave Franklin]

Novice trying to connect a Yamaha LS9 to Qlab3. The LS9 is connected to my Macbook via Ethernet (direct connection), I asum the connection/communication between both is working/good because Studio Manager 2 works flawlessly. (midi port set to Ch1 for Tx/Rx)

Initially all I want to be able to do is switch channels on/of via Qlab. I believe I need to use 'Control Change' messages on the LS9 so have set this to Tx/Rx ON and 'table'. Is this correct? How to I set up Qlab to over the ethernet connection?

[Tyler]

You'll need a midi interface to get into the 5pin DIN midi on Yamahas. Yamaha network midi allows their software to communicate over ether but I have yet to find a way to access that. As far as exact settings for control change I'd have to be in front of a console. Absolutely possible to do what you're wanting though

[Vinny Osborne]

You will need a USB to Midi interface, The Ethernet port is only for Studio Manager.

Alesis make a very simple one with a USB on one end of a cable & a Midi in & out plug on the other.

I have only got Qlab to trigger scene changes.  Basic tip is that if you want to cue Scene 10, send midi control change number 9! and so on, because the LS9 has a Scene 000 on it.

If you want the LS9 to control Qlab functions, sent the midi RX to NPRN, but be careful.  It can be unpredictable. 

[Dave Franklin]

Thanks Chaps for your wise words, best I go shopping for a MIDI/USB interface to start with then see how far I get from there. Cheers

[Sam Kusnetz]

Vinny Osborne wrote:
> Alesis make a very simple one with a USB on one end of a cable & a
> Midi in & out plug on the other.

With respect,

I do not recommend this interface, or in fact any interface with
permanently attached cables. Generally speaking they're probably OK, but
a damaged cable is easier and faster to replace than an interface and
cable damage happens all the time.

Also, in general, budget MIDI interfaces have smaller buffers which can
easily handle regular "musical" MIDI messages, but sometimes balk at MSC
or SysEx messages which can contain rather more data. Even if you don't
intend to use those message types right now, you may in the future.

Here at Figure 53, we like: iConnectivity iConnectMIDI2+ and
iConnectMIDI4+; the MOTU FastLane, Micro Express, and micro lite; and
the assorted ESI MIDI boxes (not the MIDIMATE).

Cheerio,
Sam

--
Sam Kusnetz | Figure 53 Field Operative
s...@figure53.com

[Dave Franklin]

Hi Sam, yes I tend to agree on that. Currently doing some web research buy I am inclined to go along the route of separate box/cabling.

Cheers

Dave

[Vinny Osborne]

Hi Sam,

Disagree.

Just finished a run of 2 shows a day for the past 2 months, controlling LS9 with Qlab via Alesis Midi, not one error to report.  

[Sam Kusnetz]

Vinny Osborne wrote:
> Disagree.
> Just finished a run of 2 shows a day for the past 2 months,
> controlling LS9 with Qlab via Alesis Midi, not one error to report.

That's great news! And in the grand scheme, not a huge amount of data to
decide one way or another. But nevertheless good news.

What kind of MIDI messages were you using? In particular, were you using
either MSC or MIDI Timecode?

Cheerio

[Vinny Osborne]

MSC to Change LS9 Scenes & MTC to Zero 88 desk to time code music with LX