Re: [LCtalk] midi cue triggering

[Fokko van Duin]

At 00:29 -0500 28-01-2007, andrew wrote:
> i can get my lanbox (lcm) to load cues and at least transmit the 
> first step of one, but i can't for the life of me get it to actually 
> PLAY a cue.

Did you test it first in LCedit+?  The used layer must not be in edit 
mode, and it must be a locked layer. Before you start using MIDI 
triggers you should first test all cues and chases with LCedit+, as 
if you type g10a<return>, is the same as program change 10 on the 
MIDI channel who is mapped to layer A.


> sending  program change bank 127 program 1  makes the box sit and 
> stare at me like i'm trying to mind control it which also doesn't 
> work.

Bank 127 is special; program change 1, 2, 3, and 4 (or 0, 1, 2, 3) is 
next/previous step/cue.

Bank 0 + Program change 1-128 is Go cuelist 0-127
Bank 1 + Program change 1-128 is Go cuelist 128-255
etc


> someone previously mentioned having a headache from reading the docs 
> included and i'm also headed for the aspirin, to be honest the 
> manual is not very newbie friendly, not to mention for some reason 
> being spread out across 6 PDFs which makes it very difficult to 
> actually find anything easily.

Sorry we did not make a tutorial for MIDI triggering, but we assume 
that you first follow and learn usage of the box with LCedit+ and the 
tutorial. Once you understand how to create/edit/use 
cues/chases/shows in different layers, it's very easy to understand 
that a bank select + program change is the MIDI equivalent of a 
LCedi+ gxxx command.

Note: Bank select 0 + Program change 10 is a Go 10.1, but some MIDI 
devices uses a different convention, so that program changes are from 
1-128, instead of 0-127. It's just a naming, but be aware that you 
can have a difference of 1 :-)

--
Fokko van Duin,
CDS advanced technology bv,
http://www.lanbox.com/