[QLab] MIDI Program Change Query

[David]

Hi!

 

I am very new to QLab and am in the process of setting up my first show with it – and enjoying the experience very much. But I can’t seem to find any reference to a problem that I am having either in the manual or in the archives, so I am hoping that someone can point me in the right direction.

 

I am having an issue with sending MIDI Program Changes to a Yamaha O1V96. For example, when I send a Program Change from QLab with Program Number #1, the O1V96 changes to Scene #2 (while in the O1V96, the Program Assign setup is 1 to 1 i.e. Program Change #1 maps to Scene #1 etc etc) In other words, if I want to recall Scene #(x) on the O1V96, I have to send the Program Change #(x-1) from QLab.

 

However, when I use Cricket to send Program Changes to the console, the Program Change number does “correctly” correspond with the Scene number.

 

I have noted the MIDI messages transmitted using MIDI Monitor and receive the following reports:

 

From QLab

When sending Program Change #1

Source: To MIDI Port

Message: Program

Chan: 1

Data: 1

Results in the O1V96 recalling Scene #2

 

From Cricket

When sending Program Change #1

Source: To MIDI Port

Message: Program

Chan: 1

Data: 0

Results in the O1V96 recalling Scene #1

 

I guess the question is whether there a control panel somewhere that I haven’t found yet that will allow me to send Program Changes 1 to 128 as Program Changes 0 to 127?

 

With many thanks,

 

David

 

David Longmuir

Stage Designer, Canberra

 

MacBook Pro, OS X 10.5.8, MOTU 828 Mk3 (latest drivers), Yamaha O1V96 ver 2.4

 

 

 

[raymond soly]

Hi David , 

actually both Qlab's and Cricket's implementation of the midi protocol are correct,  o-127 or 1 -128 are accepted manufacturers implementation of the midi protocol,  sending a midi program change message from one would read a message change of 1 to 1 and the other of 0 to 1, it is not unusual for  the receiving device to have a  mapping implementation that "maps" to the incoming signals to the preferred protocol......ie.0=1 or 1=1 so perhaps the 01V96 has such preferences.....

Ray

________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED.  Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com

[Richard B. Ingraham]

The small Yamaha digitals are a bit odd in their MIDI Program Change implementation.  They have a Scene called Scene Zero, but that is a factory default that cannot be recalled via a Program Change Command.  So if you send a 01V96 a program change of zero in hex (the hex codes being on the 0 to 127 scale) it will recall Scene 01 in the 01V96.  Send it 01 in Hex and you’ll get Scene 2, etc…   

 

It’s very common to have to offset things by 1 when dealing with program changes.  You have to know ahead of time if it’s dealing with a 0-127 scale or 1-128 scale.  Either way the hex code sent to it will be 0-127.

 

 

Richard B. Ingraham

RBI Computers and Audio

http://www.rbicompaudio.20m.com

[Jeremy Lee]

It's a matter of semantics and interpretation of the MIDI spec.  The spec gives the option for Prog Changes from 0-127, but many manufacturers translate that into 1-128 because they don't want a program number "0".  It's completely linear once you know what devices respond starting with 0 or 1.

Just wait until you have to recall scenes on an H8000 or something- now that starts to get tricky.

Jeremy

On Feb 25, 2010, at 7:49 PM, David wrote:

I am having an issue with sending MIDI Program Changes to a Yamaha O1V96. For example, when I send a Program Change from QLab with Program Number #1, the O1V96 changes to Scene #2 (while in the O1V96, the Program Assign setup is 1 to 1 i.e. Program Change #1 maps to Scene #1 etc etc) In other words, if I want to recall Scene #(x) on the O1V96, I have to send the Program Change #(x-1) from QLab.

-- 

Jeremy Lee

    Sound Designer, NYC - USA 829

        http://www.jjlee.com

[raymond soly]

Roland and some others had an even more "confusing" octal system, where 128 was divided in a series of banks of 8 which were then subdivided into a further 8 scenes..so 1 would read sc1-bank1..... 2 = sc2 bank1 and 9 would read sc1bank2 and so on .....now that was fun.

Ray

[David]

Ray, Richard and Jeremy, thank you all very much for the enlightening and informative replies to my question.

 

To keep life as simple as possible for the technical rehearsals, I will now re-map the Program Change Numbers to Scene Numbers in the O1V96’s Program Change Assign Tables as Ray  suggested. This should then ensure that Program Change #1 sent from QLab will now correspond to the O1V96’s Scene #1 – and so on. Or at least I hope so!

 

Thanking you all once again,

[raymond soly]

David, in chapter 18 of the yamaha 01V96 pdf you will find the Assigning Scenes to Program Changes for Remote Recall  chapter,  you will find what you need there...........it will do what you want....

Ray

[David]

Thank you Ray!