| Subject: | Re: [LCtalk] Cues and MIDI Program change |
| From: | Van Curtis |
| Date: | Wed, 30 Jun 2004 20:44:13 +0200 |
Hey Flo,
> I found out that I will have to trigger the cues by midi control
> messages or by note velocity or whatever might be possible.
> [...]
So after answering your email, I thought I'd take a
hack at triggering cues with MIDI notes as well. As
I'm new to the LCX (and LD in general!), there may be
some better ways to do things that I'm still figuring
out. However, this will hopefully give you a concrete
way to get started. I'll try to give you a step by
step procedure, followed by an example, OK?
PROCEDURE:
#1. Select Loop (or "show control cue"): You need to
have the select loop as given in the tutorial and
previous emails. The logic behind it is:
- check to see if a certain MIDI note is being held
down. if it is not, then go to the next condition
check. (see #2 below)
- otherwise do whatever cue IN A LOWER PRIORITY ENGINE
(see #3 below). Then go to the next check.
#2. Condition Check: Follows the format
go <cuestep in this cue> if channel <MIDI note #>
within <low vel> - <high vel>
e.g.
001: go 003 if channel 64 within 0 - 50
The trick is that the instruction you want to do if 64
is pressed down harder than very softly is at step
002. So the condition check says, "If I don't have
this key pressed down, skip doing this and go on to
the next condition to see if I have that one
pressed..."
#3 go <cuelist.step> in layer <?>
Hopefully you'll have created the actual cues you want
to run, and can run them successfully from LCEdit+.
What you'll want to do is go to those in a layer with
a lower priority from the control layer. They will run
by themselves, and the control layer will continue to
check your main loop for MIDI note presses.
SETUP NOTES:
* Make sure that your control layer is setup to
receive MIDI, and that your controller is transmitting
on that channel.
* Make sure that you are not using a sustain pedal or
sustain command in the LCX on your control layer. This
will mess up your control loop checking.
* Make sure that something else (like your sequencer)
isn't sending messages on the control channel which
might interfere with your note on commands and the
control loop. You don't want your control cue list to
change right from under you!
EXAMPLE: For a simple example, let's say that when I
press MIDI note #60, I want my lights to turn red.
Pressing #62, they will turn green, and #64 they will
turn blue. Note: I want these to fire when the
velocity is higher than 50%, so pressing softly won't
work. The cues that it takes to do this are in
cuelist 101, and the cues start at 10, 20, and 30
respectively. (What actually happens in those cues
will depend on your equipment.) I'm going to run those
color cues in layer C, which has a lower priority than
layer A, which is where I will run the control cue --
cuelist 100.
Because it looks kind of weird when you cut and paste
an example, I'm just going to type it in as it would
look in the cuelist editor:
CUELIST 100 (running in engine A, higher priority than
engine C)
01. -- MAIN
02. -- NOT 60
03. go .7 if channel 60 within 0 - 50
04. -- IF 60
05. go 101.10 in layer C
06. -- NOT 62
07. go .11 if channel 62 within 0 - 50
08. -- IF 62
09. go 101.20 in layer C
10. -- NOT 64
11. go .15 if channel 62 within 0 - 50
12. -- IF 64
13. go 101.30 in layer C
14. -- loop
15. go .3
-------------------------------
CUELIST 101 (ruunning in engine C)
10. ...(whatever turns your lights red)...
20. ...(whatever turns your lights green)...
30. ...(whatever turns your lights blue)...
------------------------------
So yes you do need to setup control loops -- perhaps
many of them -- but it's not too bad cutting and
pasting. Hope this helps.
take care,
van.
- Re: [LCtalk] Cues and MIDI Program change, (continued)
|
