Analogue-sequencer

Hi Gene, 

> I¹m sure that as soon as I ask this I¹ll figure out that I¹m 
> overlooking
> something simple, but I¹m puzzled right now.

You were overlooking something simple - a bug ;-)
Well, mostly.

When you use the push, swap or grab events, you need to remember two things
- the tracks are processed in numerical order, and push/swap/grab only
changes the values, not the aux assignments (though you maybe knew that
already)

So when you were pushing a value for aux B from track 6 to track 1, it was
already too late - track 1's events had been processed, so the change of
value made by the event on track 6 should have not had any effect.
The bug (which has probably been around for a long time...) is that the
change of value did have an effect - it fooled the CC generating code into
thinking there was a valid CC value in aux B on track 1.
There's an enable bit in the value for an aux on a given step that is
cleared when the event assigned to that aux is processed.
If the active bit is still set once event handling is complete, the value is
treated as a CC instead.
The 'push' of the value from a later track was making the value for the step
in track 1 active again after it had been cleared when the event was
processed, so it was treated as a CC.
Internally, 'xpose by track n' is event number 24, which is where CC #24
came from.
I'll look at fixing this, though it shouldn't really be a problem, since
pushing/grabbing/swapping from a higher track number does not have any
effect.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com