Home | News | Products | Support | Download | Sales | library | Guests | Contact | WebCam | Links
CDS Logo LanBox-Talk mail archive
 

By date: Prev | Next | Index By thread: Prev | Next | Index

SubjectRe: [LCtalk] Midi-controller
FromFokko van Duin
DateFri, 18 Jan 2008 01:05:51 +0100


At 00:30 +0100 18-01-2008, P. Koelman wrote:
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.

Preferred is the use of 21+53, and then 86 for the trigger + cue step.


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!

Maybe it's a problem that cc 20 (and also 21), so try with 21+53+86:

Hex "B0:15:01:SW:B0:35:5C:SW:END" I assume that 21, then 53, and then 86 is send.

Maybe the order is wrong, and better use the bank select + program change?


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?

Very strange, are you sure it sends out the bank select first and then the program change? A MIDI monitor is very handy in this case ;-)


By date: Prev | Next | Index By thread: Prev | Next | Index