Analogue-sequencer

> 
> From: "Colin f" <colin@colinfraser.com>
> Reply-To: analogue-sequencer@yahoogroups.com
> Date: Sat, 29 May 2004 18:04:34 +0100
> To: <analogue-sequencer@yahoogroups.com>
> Subject: RE: [analogue-sequencer] anyone want to help a beginner?
> 
> 
>>> Well, this is a pretty basic question I guess, but I've only
>> had a few hours
>>> on my new P3, and I'm trying to figure out from the manual how to do
>>> something that should be pretty straightforward - how to change the
>>> controller number on a particular step of a pattern.
>> Changing the value sent
>>> out is easy - but I want to change the controller number.
>> 
>> You mean you want to send (for example) CC1 on step 1, CC2 on step 2,
>> CC10 on step 5 and so on? No can do - although obviously you can send
>> 4 controllers A-D and each can be the controller you want and active
>> on each step.
>> I reckon that's far from basic, personally dude.... 8-)
> 
> Each aux (A - D) can only be assigned one controller or event per
> pattern.
> This is to save space - if the controller number was settable for every
> step, I would need to store 32 bytes for each aux per pattern. By making
> the controller/event apply to the whole pattern, each aux only needs 17
> bytes.
> It would also be a bit of a pain having to configure the controller
> number for every step where you wanted the same controller on each.
> 
> What I could do though, is add an event that would temporarily re-assign
> the controller/event number for another of the auxes. By combining two
> auxes, you could then send a different controller numbers and values on
> each step.
> You might even use a further aux to randomise the controller or event
> number being assigned, although that could get somewhat chaotic !
> 

well, my confusion as to the setting of the cc # per step was based on a
faulty read of the manual, combined with ignorance as to what you meant by
the step key function switch. But what you suggest above sounds magnificent.
I'm also suppressing a desire to want send events on different MIDI channels
per step. I'm assuming that this also is not possible.

>> Function plus the bottom mode button (mine's red), then use Page to
>> toggle between Controllers and Aux events and the data entry to scroll
>> through the controllers/auxes available. If you do Function plus the
>> button (not a step button - that just peeks the value) repeatedly it
>> tabs between the four controllers.
>> Hey Colin, does that button have a name? Other than "the red one" that
>> is <g>?
> 
> I call it the 'step key function switch'.
> 

Is that actually stated in the manual anywhere?

> Cheers,
> Colin f
> 
> 



[Non-text portions of this message have been removed]