Re: [LCtalk] Midi-controller

[P. Koelman]

> The Yamaha 01V will allow you to assign hex values to the faders (or 
> so it appears according to the users manual I found online), so you 
> can use those to send a "Note On" in a certain range.

Allright, I got most things working for me now.
The O1V accepts Hex input, so with some calculation I'm getting there.

I've got the ChannelSetData working
e.g. Hex "90:0F:FAD:END" is a fader controlling light-channel 15 in midi 
channel 1 which is set to layer A (FAD=O1V setting for fader controlling 
the value)
This way I can make "groups" aswell, e.g.
"90:01:FAD:02:FAD:03:FAD:END" for controlling light-channel 1 to 3 (up to 
max 7)

I also got the EngineSetTransparencyDepth working (allthough the fader 
works 'upside down')
e.g. Hex "B2:63:FAD" controls the transparency of midi-channel 3 which is 
set to layer P

But with GO-ing cues I got very confused with the MSB and LSB. The 
reference states:
*
The LanBox expects to receive the MSB (controller 20) first and will not Go 
the engine until the LSB (controller 52) is received. The MSB is remembered 
and used for any subsequent received LSBs.

For example to Go Cue List 200:
Controller 20 with a value of 1
Controller 52 with a value of 72 -> Triggers  go!
*
I cannot work out how to translate that to the input in the O1V.
I have tried:
Hex "B0:14:01:SW:B0:34:5C:SW:END" (SW is O1V switch)
B specifies that it is a controll change message.
"B0:14:01" is the 'coarse' MSB
"B0:34:5C" is the 'fine' LSB

It just doesn't work!


> > > For "Go" ing to cues you can use controller, as well as bank select + 
> > > program change messages, see page 30 of the LC+ Reference v2.0a1.pdf.

Then it stated in the reference:
*
For reasons of compatibility with the LanBox-LC II, it's also possible to 
start an engine with a Program change message. For example Sending a 
program change with value 30 on a MIDI channel assigned to engine A will 
start Cue List 30 in Engine A. As with the LanBox-LC II, a bank select 
controller (00) can be used to set a so called base number. This base value 
is multiplied with 128 and then added to the Program change value, so it 
becomes possible to start Cue List with a higher number than 127.
*

After a long search I found that C stands for Program change.
So: Hex "C0:52:SW" calls cuelist 82 in midi channel 1 (linked to Layer A)
Hex "C0:00:52:SW" calls cuelist 82 in midi channel 1 aswel, 00 being the bank.
BUT, "C0:01:52:SW" calls cuelist 310(??) instead of cuelist 210 according to 
my calculations, 128+52 is 210...

So... I'd like to be able to use the buttons (SW) to call cues. Can anyone 
give me a clue?

For the rest i am quite impressed with what I can do with a midi-controller!

Regards, Peter