LS9 SERIOUS FLAW

222 views
Skip to first unread message

Vinny Osborne

unread,
Jul 24, 2013, 7:30:39 PM7/24/13
to ql...@googlegroups.com
Tonight I discovered a serious flaw, or my bad set up, which ever.
So I have mute group 8 on the Yamaha LS9 console set to user define key 2.
This is set to hit the GO button on Qlab ver3. It works perfectly

Until tonight, when I discovered that adjusting the Aux send 14, on channel 4 sends the go command also.

In the LS9' I have it set to NRPN mode. I tried setting it to TABLE mode, but it doesn't work with Qlab.

What have I done wrong, or has Yamaha doubled up on midi control change messages (codes).
According to the manual, they are completely different commands.

ANY HELP APPRECIATED.
VINNY.

Sean Dougall

unread,
Jul 24, 2013, 7:36:02 PM7/24/13
to ql...@googlegroups.com
I don't have any experience with the LS9, but one general troubleshooting step that might help with that type of issue is running MIDI Monitor (http://www.snoize.com/MIDIMonitor/) to see exactly what messages are getting received, and whether they actually are different messages.

-Sean

Rich Walsh

unread,
Jul 24, 2013, 7:54:28 PM7/24/13
to ql...@googlegroups.com
QLab is triggered by voice messages, ie: 3 byte messages. NRPN messages are made up of a number of these joined together. You are not actually using an NRPN message to trigger QLab; you are probably using just the first part, ie: CC99 @ some value (the MSB of the desired parameter). It is entirely plausible that many parameters on the LS9 share the same MSB - and hence will all appear to send a GO to QLab since it is only parsing 3 byte messages. Indeed, it may even be that your GO trigger is a 3 byte section later in the NRPN message, eg: the value of CC6 or CC38 (data entry).

Table mode should work fine - in fact, this is the mode QLab is expecting. You just need to tell whatever UDEF key 8 is triggering to actually send a CC value by editing the table. By default, master mutes won't do this.

What exactly is the MIDI Controls preference tab showing for the GO trigger?

Rich
> --
> --
> 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.
>
>

Vinny Osborne

unread,
Jul 24, 2013, 8:22:37 PM7/24/13
to ql...@googlegroups.com
What exactly is the MIDI Controls preference tab showing for the GO trigger?

GO: Byte 1 = 98 / Byte 2 = 97
LOAD: Byte 1 = 98 / Byte 2 = 96.

Thanks so Much.
Keep the info coming.  In fact my main worry is that another fader, encoder etc will send the GO command. 

Rich Walsh

unread,
Jul 24, 2013, 8:39:08 PM7/24/13
to ql...@googlegroups.com
On 25 Jul 2013, at 01:22, Vinny Osborne <the...@eircom.net> wrote:

What exactly is the MIDI Controls preference tab showing for the GO trigger?

GO: Byte 1 = 98 / Byte 2 = 97

Presumably it also says "Control Change"? The full NPRN string for MUTE MASTER 8 ON is probably something like CC99 @ 58 + CC98 @ 97 + CC6 @ 127 (not 100% sure on the last bit), so QLab has managed to capture the middle 3 bytes…

LOAD: Byte 1 = 98 / Byte 2 = 96.

Is this MUTE MASTER 7 by any chance?

I guess you get a GO whether turning the mute on or off too (ie: QLab is blissfully unaware of the actual value of "mute")?

Anything that has an LSB of 97 (61 in hex as per Yamaha's manual) will trigger your GO when sending NRPN. This includes INPUT4 send to MIX14 (CC99 @ 2 + CC98 @ 97 + CC6/CC38 @ the value) and probably MIX6 to MATRIX5 and many, many others (possibly even the MIX2 fader level!).

It's not going to work using NRPN mode. Use Table mode.

Rich

Vinny Osborne

unread,
Jul 24, 2013, 10:03:12 PM7/24/13
to ql...@googlegroups.com
First of All Rich.
Thanks so much for your Help.
Yes the Load Key is Mute Master 7.

So to set it up in table mode, I am guessing that I "Clear all" from the Table list & then ADD Mute 7 & Mute 8 to the List.
Now in the LS9 Main Midi page, I have the following Parameters (Page 178 of the manual)
MODE = Single or Multi
And Omni or Bank
And NRPN or Table (guess I select Table here too?)

Have you an idea of those settings above???

In The Midi Control Change Tab (Page 183)
I guess I set the following.

TX = Highlighted
Table = Highlighted
Control No. 0 = Bank Select NSB - Un-changeable
I then add 
Mute Group 7 (Load) to No 1 & 
Mute Group 8 (GO) to No 2.

Am I correct or do I have to add the Mute Groups to specific Control Numbers.
I presume I have to get Qlab ver 3 to re Capture these Midi Commands???

Again, I cannot thank you enough.

Chers, Vinny.

Rich Walsh

unread,
Jul 25, 2013, 9:12:56 AM7/25/13
to ql...@googlegroups.com
On 25 Jul 2013, at 03:03, Vinny Osborne <the...@eircom.net> wrote:

> So to set it up in table mode, I am guessing that I "Clear all" from the Table list & then ADD Mute 7 & Mute 8 to the List.
> Now in the LS9 Main Midi page, I have the following Parameters (Page 178 of the manual)
> MODE = Single or Multi
> And Omni or Bank
> And NRPN or Table (guess I select Table here too?)
>
> Have you an idea of those settings above???

From the manual, the whole MODE box only relates to PC not CC, so is irrelevant. You need CC TX on and TABLE on. You also need to select the correct PORT and CH; PORT will be unchanged from your half-working NRPN setup. The LS9 only handles CC on one MIDI channel; it doesn't matter which you choose as long as you choose the same one in QLab…

> In The Midi Control Change Tab (Page 183)
> I guess I set the following.
>
> TX = Highlighted
> Table = Highlighted
> Control No. 0 = Bank Select NSB - Un-changeable

CC0 and CC32 are not available for you to use as they are involved in bank select messages so that you can access more than 128 scene memories.

> I then add
> Mute Group 7 (Load) to No 1 &
> Mute Group 8 (GO) to No 2.
>
> Am I correct or do I have to add the Mute Groups to specific Control Numbers.

You can use CC1 & CC2; it doesn't matter.

> I presume I have to get Qlab ver 3 to re Capture these Midi Commands???

Sort of – you need to read https://groups.google.com/d/msg/qlab/8-_s50gCpBI/odxWiAgUfIwJ. You can program QLab directly rather than capturing; choose CC1@any and CC2@any.

Rich

Vinny Osborne

unread,
Jul 25, 2013, 10:16:13 AM7/25/13
to ql...@googlegroups.com
THANK YOU SO MUCH RICH.
Just a it lost as to where I enter the CC1@any commands?

Rich Walsh

unread,
Jul 25, 2013, 1:28:40 PM7/25/13
to ql...@googlegroups.com
On 25 Jul 2013, at 15:16, Vinny Osborne <the...@eircom.net> wrote:

Just a it lost as to where I enter the CC1@any commands?

MIDI Preferences – see attached.

Rich

Vinny Osborne

unread,
Jul 25, 2013, 2:41:00 PM7/25/13
to ql...@googlegroups.com
Yep all working fine
So hopefully ls9 is not sending any other midi commands.
Owe you big time.
Thank you.
Vin
Reply all
Reply to author
Forward
0 new messages