On Tue, 19 Oct 2004 12:21:20 +0100, "Colin f" <colin@colinfraser.com>
wrote:
>In order to send a controller from the knobs using the aux events, you have
>to use two auxes, and set it up on every pattern.
Which is a drag to do.
>Also, the knob values will only be sent on each beat.
>With play mode controllers, a message would be sent whenever the knob is
>moved, and this would be independent of the pattern, so your auxes would be
>free for whatever else.
Free them Auxes! Let's print t-shirts!
>There would be enough space for per bank midi channels if the controller
>config was global - i.e. just one controller set up and not per bank. Maybe
>that would be a workable compromise...
It would be perfect for me. I'd never remember different assignments
in each bank anyway.
Having the ability to set MIDI channels freely per bank would be cool,
plus if the global knob assignments were routed to the channel of the
related tracks (for the 16 knobs above tracks) and the other 16 (above
parts) kept whatever channels were specified at definition, this could
make everyone happy?
The P3 being able to work as a controller is cool - but fist and
foremost it is a sequencer, and I'd say variable channels per bank
more logical to include. OK, I just bought a Remote 25 and, using the
P3 thru, can route any number of controllers from this decicated piece
of kit.
>Another option would be to add either an aux event or a new pattern config
>variable, that would over-ride the global midi channel per pattern. i.e.
>patterns would default to the global midi channel for that track, but you
>could set an alternative channel that woudl only apply to that pattern. An
>aux event would let you change the midi channel per step, but that would use
>up an aux.
Clever. I'd probably prefer the previous suggestion for simplicity of
use but that's only me.
Paul
---
Paul Nagle - SoftRoom Music - www.softroom.co.uk
Bogus Focus Records - www.BogusFocus.com