Qlab to trigger M7CL scenes

610 views
Skip to first unread message

ra byn (robin)

unread,
Apr 19, 2012, 9:36:34 PM4/19/12
to Qlab Google
I've got a show coming up where I'll have (2) Yamaha M7CL consoles. I'll
have one at FOH & another covering monitors. The band needs some very
specific monitor changes during the show & since they've had a terrible
time with the local monitor engineer getting it right, I'm thinking that I
might just trigger the changes from FOH.

Option A

Qlab @ FOH, midi to xlr / xlr to midi to M7CL console.

Option B
Use my Ipad & stage mix but that will rely on a wireless connection.

Option C
Use my Mac & Studio Manager to trigger the changes & run a CAT 5 cable
(might not have time)

I guess I could trigger the changes via Qlab & midi but keep an eye on
things via Stage Mix.

Anyone have a idiots guide to triggering presets on an M7CL or is it
pretty well documented in the various manuals?

Thoughts, tips & tricks appreciated!

ra byn


dan howarth

unread,
Apr 19, 2012, 9:48:59 PM4/19/12
to ql...@googlegroups.com
On Thu, Apr 19, 2012 at 6:36 PM, ra byn (robin) <ra...@rabyn.com> wrote:
I've got a show coming up where I'll have (2) Yamaha M7CL consoles. I'll
have one at FOH & another covering monitors. The band needs some very
specific monitor changes during the show & since they've had a terrible
time with the local monitor engineer getting it right, I'm thinking that I
might just trigger the changes from FOH.

Option A

Qlab @ FOH, midi to xlr / xlr to midi to M7CL console.

sure. 
 

Option B
Use my Ipad & stage mix but that will rely on a wireless connection.

i would still have option A available .. 

hopefully you have a healthy wifi box that includes a DHCP router -- the M7CL will
talk to that just fine on a short cat5, and then you're into ipad territory. i've seen 
this operated highly efficiently -- a tv shoot with 20 microphones around the table, 
basically walk around with the ipad and open each mic up and do eq and dynamics, etc. 
the M7CL is a good board .. i am excited to compare the DM / CL series with the new yamaha 
digital mixer series which apparently now includes a rupert neve preamp ?? 
 
Option C
Use my Mac & Studio Manager to trigger the changes & run a CAT 5 cable
(might not have time)

sounds like you're already running an xlr snake so option A is easiest eh ? if you're bringing 
an ipad then you're probably bringing your own wireless ... 
 
I guess I could trigger the changes via Qlab & midi but keep an eye on
things via Stage Mix.

definitely need some visual feedback to be sure things are happening with the monitor board. 
i'd probably run option A with the xlr / midi and then have the ipad running to see how the board 
is doing .. 
 
Anyone have a idiots guide to triggering presets on an M7CL or is it
pretty well documented in the various manuals?

yeah there's a few great youtube tutorials on this board -- just do a search and go for the long (20m ?) 
chapter / segment official looking video series ... 

Brendan Aanes

unread,
Apr 19, 2012, 11:06:14 PM4/19/12
to ql...@googlegroups.com
You can assign each scene memory on the M7 a program change message, so it recalls when that message is received. It's in one of the MIDI screens under setup, I believe. Not something I do regularly, but I do remember it being clearly documented in the manual.

Technically you're not advised to run MIDI over 100ft, but I've run it through some 350ft of snake before without any problems, and in that case it was a fairly complicated electronic instrument, sending a lot of messages vs. the very few you're sending. I think it depends on the details of the line amps in your MIDI hardware. Worth a test.

I haven't used the iPad with Stagemix (looking foward to it sometime, though), but I would not trust a WiFi connection during a show.

--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

Steve Lalonde

unread,
Apr 20, 2012, 12:14:36 AM4/20/12
to ql...@googlegroups.com
Did this many time with m7 and ls9, pretty easy to do. 

I'd also recommend option A. 

You can preprogram some program changes and the "tricky" part is always that the program change number isn't the same as the scene number as you have a scene 1 assigned to program change 0.  (or maybe it's only with the ls9) And when you're over scene 127 or 128 it can get messy quickly finding the right number if you haven't labeled your midi cues. 

Otherwise, you need to make sure that midi is configured correctly on the Midi Setup page. (Rx channel number, program change Rx is on and the mode to Table if memory is correct, echoed out if you trigger both consoles)

The rest is all in the manual around p.203 of the one I have here on hand. 

It's been very reliable and i even went as far as programming mutes and unmutes after some shows that have playback or backing tracks I'd launch from FOH through QLab, I found it very funny to be standing there and watching the console do half of my job. 

iPad and stagemix have been very reliable for me too with the exception that when recalling a scene, the iPad looses control for 10 to 20 seconds... so if something bad happens there, one has to wait before troubleshooting. 


Good luck with this, 


S

Charlie Richmond

unread,
Apr 20, 2012, 4:14:13 AM4/20/12
to ql...@googlegroups.com
On Thu, Apr 19, 2012 at 20:06, Brendan Aanes <baa...@gmail.com> wrote:

Technically you're not advised to run MIDI over 100ft, but I've run it through some 350ft of snake before without any problems, and in that case it was a fairly complicated electronic instrument, sending a lot of messages vs. the very few you're sending. I think it depends on the details of the line amps in your MIDI hardware. Worth a test.

This gets discussed on a regular basis and the consensus is always that MIDI line amps are usually more trouble than they are worth.  Here is our discussion on the subject: http://www.richmondsounddesign.com/faq.html#midilen

If you really want to be safe, as it says in the link, the MIDI Solutions Power Supply (working as a sender and receiver) is the best as far as we are concerned.

Good luck!

C-)

James Corner

unread,
Apr 20, 2012, 4:37:55 AM4/20/12
to ql...@googlegroups.com
Surely just finding another Monitor engineer is your answer, as Monitors and FOH on bigger gigs
are separate jobs in my experience with separate responsibilities, why give yourself twice the workload
to deal with.

Just a thought.

Regards

James.

> Date: Thu, 19 Apr 2012 20:36:34 -0500
> Subject: [QLab] Qlab to trigger M7CL scenes
> From: ra...@rabyn.com
> To: ql...@googlegroups.com

>
> I've got a show coming up where I'll have (2) Yamaha M7CL consoles. I'll
> have one at FOH & another covering monitors. The band needs some very
> specific monitor changes during the show & since they've had a terrible
> time with the local monitor engineer getting it right, I'm thinking that I
> might just trigger the changes from FOH.

> ra byn
>

ra byn (robin)

unread,
Apr 20, 2012, 8:26:05 AM4/20/12
to ql...@googlegroups.com
On Fri, April 20, 2012 3:37 am, James Corner wrote:
>
> Surely just finding another Monitor engineer is your answer, as Monitors
> and FOH on bigger gigs
> are separate jobs in my experience with separate responsibilities, why
> give yourself twice the workload
> to deal with.

Agreed!

I'll have to lean on the local anyway & from what I understand, the local
sound provider is top notch so I'll probably have a good engineer @
monitor world but I've done monitors on this gig myself up til now & had
another engineer @ FOH. I know what is involved & it's not something the
local can nail with the time available before doors. When I first did the
gig I got a 2 minute conversation that went like this...."I need such &
such on this & this & this song..." "Here is the set list".

I stopped them & started writing notes. Then I spent my dinner break
programming to be ready.

It was my hope that in the future I could just use my console file & hand
it to the locals but things never work out that way. Input lists change,
levels, etc...

I even asked the locals what they thought & right off the bat, I was told
some things that made me lean more toward the "do it manually" & avoid
"scenes" than to try to automate it all & just have the local press NEXT.

So while the local needs to be heavily involved even if there are scenes
(so they understand what is happening & can fix something if necessary), I
also can't expect them to get it all right for a 1 show day with 48
channels (24 band / 24 orchestra) & a few hours of rehearsal. Some of the
songs aren't even rehearsed because the orchestra doesn't play on them.

So the local monitor engineer won't get even 1 shot at much of it before
the show. I wouldn't want the gig without a lot of support from the band's
crew (me):)

Maybe I can just help the local monitor engineer understand what happens
when & they can step thru scenes but if I show up & they can't, I need a
fall back plan in place already. Qlab & midi with stage mix for a visual
check seems like a good one:)

Thanks for all the feedback folks!!! Very helpful.

ra byn

Reply all
Reply to author
Forward
0 new messages