Analogue-sequencer

> in playlist-edit mode, with a playlist with a length of 1 step, if i
> select a different pattern than the one originally programmed and then
> hit "FUNC" to exit playlist-edit mode followed by "F3" to lose the
> changes i just made, i return to play-mode, but the changes made to
> the playlist aren't lost.

It's not that the changes aren't lost - the playlist data is restored, but
there's a flag that tells the sequence engine to refresh the current pattern
& transpose values, and it doesn't get raised in this case. This only
happens with a single step playlist because the flag gets raised every time
the playlist step advances anyway. Fixed in the next build.
That was a tricky one - I noticed something odd a couple of times myself...

> on another note, i have another request/suggestion for some 
> AUX-events.

Well the released build only has 6 slots free for events, but the current
build I'm working on has condensed all the swap and grab events into two
events, rather than 24, so there's some space set to appear.
The swap and grab events will change so that the value for each aux includes
both the target track number, and the type of data to be grabbed or swapped
(or pushed...) from the track, i.e. note, velo, leng, aux A etc.
The change to these events means that current pattterns using grab or swap
will need to have auxes remapped and values tweaked, but an imminent release
of P3Tools has a utility to do this for you.

> one is "grab all auxes trk N" which would effectively give you 7 auxes
> for a single track (the remaining 3 for the track you're working on +
> the 4 from track [N]). if at all possible i'd like the 4 "external
> AUXes", to be inserted before the "internal AUXes", the remaining
> AUXes for the track you're working on. this would probably mean this
> event could only be used on AUX A. (..?)

There's already the event 'auxes to trk n' - this redirects (pushes) auxes
from the current track to a following track.
Due to the way auxes are handled, it would be much more complex to have an
event that grabs events from another.
If you haven't tried 'auxes to trk n', give it a shot and see if it does
what you need.

> the other is "mute all other tracks", which would preferably send mute
> and unmute messages in the same way as the gates send note-on/note-off
> messages. maybe even a "mute all other tracks, Kn>N" event, which
> would give you realtime frontpanel control of the event and bypass the
> need to set up an additional "mask AUX[x], Kn>N" event?
> i think they'd be pretty useful.. to me at least. :-)

The TBI list for auxes can open up a bit after the next release.
I'll upload the current beta shortly if you want to try it.

Cheers,
Colin f