Analogue-sequencer

>> I'm working on adding midi remote control to P3. Obvious TBIs are
bank select or program change messages to change P3 bank, CCs for
mute/unmute tracks, maybe also CCs for edit track 1 - 8, pattern
select, note input for PXPos, that sort of thing. Seems like a good
idea to discuss it before I implement stuff no-one wants...<<

ah. ah-hah. so.... stuff that takes more than one button push would go
on my list... like dropping in & out of record, & selecting the track
to record into... is that what you meant by "cc's for edit"?

what about.... mapping some program changes onto a bunch of
user-defined macros? given that nothing's more than a few button
pushes away anyway, you wouldn't have to store very much. 

you'd put the p3 into "learn" on power-up, by holding down the tempo
knob & blowing in a southerly direction. paul does this anyway. then
push a step key to select a macro to edit. the display would say
something like: "whatever buttons you push now, I'm going to push the
same buttons in the same order when I receive the PC corresponding to
step whatever, on the global channel". with scope in there somehow for
a PC followed by a CC so you could do things like change the length or
timebase of a pattern.....
yikes.
could it stand that much switching on & off?

(I deleted a load of thinking-out-loud, you'll be glad to know...)

d/r.m.i.