Qlab Control Change Messages To Yamaha 01v96i --Novice

[kostis Pavlopoulos]

Hello,

I've perused Yamaha's ''midi control guide'' pdf. which is referred to M7CL.The problem is that I'm going to program a show and the mixer will be available on the last moment and I'm not familiar with Yamaha's digital desks in general but according to the budget it meshes perfect.

I would like to be able to automate mixer's parameters such as channel mutes , fader levels , pan ,etc. via qlab control change messages.

Could anyone give me a picture regarding 01v96i?Is there any tab where I'll be able to select the parameters that are needed to be automated?

Thanks in advance

[Rabyn]

Offline editor?

ra byn (robin)

[kostis Pavlopoulos]

Yes, offline editor but there I can only store scenes.

Am I right?I hope no ;)..

Because the play is going to be 6 hours long consisting of 4 parts the plan is to use 01v96i via Qlab..

Each part will be programmed in different 'Cue List' on Qlab so consequently I'll have 4 different Cue Lists for each part.

Each Cue List will be consisted of stored scenes according to the play and each scene will be consisted of some cc messages such as mutes pans effects parameters,etc.

Is this thinking right?It seems ok to me.

Can I do all this preparation through offline editor?

 

--
--
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 a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/7qcf1l0goMo/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[fishmonkey]

erm, how many days do you have the desk for before the show opens?

[kostis Pavlopoulos]

One week before I guess

[kostis Pavlopoulos]

and the problem is that I don't know that much regarding the cc messages to 01v.If there were only scenes to store yeah it would be much easier 

[Angus Turner]

Pretty sure you can recall scenes through cc messages. not 100% sure though. So you'd save each 'change' in the O1V as a new scene and then recall each scene though midi from QLab...

Thanks
Angus Turner
angus...@gmail.com

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.

[Angus Turner]

Let me know if this doesn't help/does help:

http://www.manualslib.com/manual/267128/Yamaha-01v.html?page=237

Thanks
Angus Turner
angus...@gmail.com

[Charles Coes]

Scenes in the yamaha desks, and many others, will also automate the pans, effects sends etc, and will fade some of the parameters.  It takes some work in the 'scene' sub menu to setup recall safes and fade times, but in the long run is a ton easier than the CC messages.  Yamaha publishes the full midi spec here:

http://www.yamahaproaudio.com/global/en/products/mixers/01v96i/downloads.jsp

bottom link.

 

You can also map assignments in the MIDI tab.

Programming the console this way is incredibly flexible, but a huge pain as every parameter has to be manually set by qlab and there is no easy way to have the console tell you the midi value of a control if you've adjusted it (i'm sure there is a way to monitor the midi it is sending and decipher it, but that seems like something that isn't easily doable in a tech).  

Finding a way to do what you need to with snapshots will likely be easier. and a week is likely enough time to figure it out if your hands aren't full with 6 hours of other things!

For complex shows I've had to reload show files at intermission (to get beyond the 100 scenes given in the older yamaha desks) from studio manager (with the 1k and O1V) or smartcards.

Good luck!

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.

[Angus Turner]

I'd recommend hiring out the desk for a day or two way before the show to play around and get a hang of setting everything up, especially if this is your first time *and* it's a 6 hour show. I know sometimes setting the midi up can be messy and it's nice to have plenty of time.

Thanks
Angus Turner
angus...@gmail.com

[Richard B. Ingraham]

Actually the M7 and LS9 have a much less flexible method for assigning
controls to MIDI CC messages. But they don't offer access even to full MIDI
channel's worth of MIDI CC messages. (128 MIDI CC parameters per MIDI
Channel) The most extensive Yamaha desks in this area were the DM Series
and one of the reasons I really liked them. They let you access 16 separate
MIDI channels worth of CC messages, so you could control a lot of stuff.

The M7 and LS9 prefer you to use the NRPN MIDI commands, which are nice in
the fact that they allow for greater resolution than the typical 128 steps
of a MIDI CC command. But it also means that for each control you end up
with 3 separate MIDI commands that all have to be sent to the console in
just the right order. Which makes moving multiple controls simultaneously
very difficult. Because if a messages or two gets out of order, then the
console doesn't know what to do and I can easily make an M7 or LS9 freak out
by trying to send them multiple streams of MIDI NRPN data. A poor choice on
Yamaha's part if you ask me.

Anyway, the 01V96 has a pretty decent MIDI implementation if memory serves.
In the past when I have worked with that desk, I use a combination of
internal scenes that get recalled via MIDI Program Change messages and then
when I only need to adjust a handful of parameter I use MIDI CC messages. I
find this method best because you don't have to spend as much time tinkering
with recall safes and the like for things you don't want to change. So I
use a scene when I want major changes and write CC MIDI commands when I want
to perhaps adjust two or three faders or something like that.

I recommend building up a library of MIDI commands of sorts. Put them in
their own dedicated cue list. Then you can select the commands you need on
a cue by cue basis and just copy and paste them to your main cue list. Or
you can use a Play command in QLab to fire off the ones you need. But that
saves having to make them by hand for every cue, every time.

Remember that just because you only have 100 scenes in the 01V that doesn't
mean you only get 100 cues. You don't have to recall them in order.
Although obviously that is a more intuitive way to work. You can have QLab
recall the same scene over and over again many times during a show. If you
have similar settings that you're using over and over again, I never saw the
point in programming multiple scenes that do the same thing over and over
again. I just create a library of scenes and I recall the correct one as
needed. But it does take more management and thought by the end user to
work this way.


Richard B. Ingraham
RBI Computers and Audio
www.rbicompaudio.20m.com



> -----Original Message-----
> From: ql...@googlegroups.com [mailto:ql...@googlegroups.com] On Behalf
> Of .
> Sent: April 19, 2013 8:02 AM
> To: ql...@googlegroups.com
> Subject: Re: [QLab] Re: Qlab Control Change Messages To Yamaha 01v96i --
> Novice
>
> I have an o1v none I. I have done what you are asking already. Program
> changes are the most fuctional way i found to recall scene. Most of the
cc
> stuff is the same on all the yamaha digital desk. The the o1v has the
Same
> midi perameter page that Allows you to assigns functions to cc that the
m7,
> ls9, o2r, andaybr the DM1/2k.It also has defeat settings too that are
close or
> the same as the m7. The manual I beleave list this if not i can pass you
any
> info you should need on Sunday when I am at work. Let me know

[Jeremy Lee]

All of the CC messages for the 01v are in the manual.  It's pretty comprehensive.  You may have to poke around in the MIDI settings on the desk to make it work, but it's pretty straight forward.

On Apr 19, 2013, at 6:02 AM, kostis Pavlopoulos <kpm...@gmail.com> wrote:

and the problem is that I don't know that much regarding the cc messages to 01v.If there were only scenes to store yeah it would be much easier 

On Fri, Apr 19, 2013 at 12:58 PM, kostis Pavlopoulos <kpm...@gmail.com> wrote:

One week before I guess

On Fri, Apr 19, 2013 at 12:55 PM, fishmonkey <fishmo...@gmail.com> wrote:

erm, how many days do you have the desk for before the show opens?

On Friday, April 19, 2013 10:00:03 AM UTC+10, kostis Pavlopoulos wrote:

the mixer will be available on the last moment and I'm not familiar with Yamaha's digital desks in general but according to the budget it meshes perfect.

--
-

-- 

Jeremy Lee

    Sound Designer, NYC - USA 829

        http://www.jjlee.com

[Andy Leviss]

On Fri, Apr 19, 2013 at 9:26 AM, Richard B. Ingraham
<rbing...@sbcglobal.net> wrote:
> The most extensive Yamaha desks in this area were the DM Series
> and one of the reasons I really liked them. They let you access 16 separate
> MIDI channels worth of CC messages, so you could control a lot of stuff.

--snip--

> Anyway, the 01V96 has a pretty decent MIDI implementation if memory serves.

Yup, for all intents and purposes, you can generally think of the
01V96 family as the baby of the DM line. I was never quite sure why
they branded it so differently from the DM1000 and DM2000, since they
share so much UI and functionality, and just differ on size and some
of the more advanced features. It's really more like a DM500!

-Andy

[kostis Pavlopoulos]

thank you so much for helping me.

--
--
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 a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/7qcf1l0goMo/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

[Craig k]

if you find that there is a midi message that you are having difficulty working out, QLab does have a capture function on the triggers tab of most cues. this way you could set QLab to capture and then make the move you want on the 01v. take the info from the capture and plug that into the show cue.

I've found direct control of Yamaha desks to be a very effective way of system programming - once you get the hang of it, its really quite easy and fast to get very detailed control - much more than just scene changes (although those are also helpful in many cases.

feel free to ask for specifics while you're programming

Craig

[kostis Pavlopoulos]

Thanks Craig k.

Is that also works on LS9 32?

Am I able to trigger Qlab via User Defined Keys? 

--

[Craig k]

yes you can trigger QLab from user defined keys on the LS9. just setup the key to send a midi note. Then goto QLab's preferences and on the Remote Control page turn on 'use midi commands', and click the capture button beside the 'GO' command.. then press the user defined key that you all ready set up as your 'GO' and it should fill in the commands for you in QLab. Click done in QLab prefs and you should be set.

Craig.

[kostis Pavlopoulos]

Thanks,you were very helpful

[cedricl]

The biggest issue with the 01V96 family (DM1000, DM2000) is setting up the midi section properly. Specify which midi/USB channels you're using for Studio Manager (their offline editor), usually channel 1, and then which one to use for sending and receiving midi. I use ch. 2 on my DM2000. Set your scenes in the mixer for the show, and then just use a midi program change message in QLab to call up the scene on the mixer. It's one number lower than the actual scene number (program change #8 calls up scene #9).

[kostis Pavlopoulos]

hello Craig!

I followed what you've written above on Yamaha DM200 and works flawlesslyI used 'capture' function and all cc messages works perfect except from audio cues.I'm not able to fire any audio cue,it just jumps to the next cue.It fires only the midi cues from user define keys but not the audio!

Could you help me?

[Craig k]

If I understand your post, you are able to use the user defined key to trigger everything BUT an audio cue in QLab? Do you have the UDK set up to trigger specifically targeted cues, or is it just a "GO" button to trigger the next cue in the sequence?

I might be easier to help you trouble shoot this if you send me your show file. (no media, just the .cues file)

Craig

[kostis Pavlopoulos]

Hello,

It is just a GO button to trigger the next cue in sequence.I cannot send anything because I didn't try to arrange any cue list since it didn't work last night.Sorry for my English,I will try to put it down better.

I would like to use Yamaha DM2000 to trigger the QLAB cues via midi while QLAB in turn effected scene changes on the console via midi, so I hooked my mac up to DM2000 (usb) then I defined a key from DM2000 (User Defined Keys)  to send a 'Note on' to QLAB and then  I used the capture function at the Remote Control tab for capturing ''GO BUTTON''.

All Qlab's cues that involve midi messages work flawlessly but when there's an audio cue in the cue list, it jumps to the next cue without firing the audio cue.

but today I did exactly the same thing and all the cue list worked perfect,I don't really know what happened,I will try it again tomorrow to see what is going to happen.

Thanks Craig

Appreciate your help

Kostis

To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/7qcf1l0goMo/unsubscribe.