Analogue-sequencer

> anyone care to guess, before I go home & try it for myself, what
> happens if you're running a playlist that consists of several
> patterns, some of which repeat during the course of the playlist, &
> you go into "track record"?

Track record writes the notes into the current step of whichever pattern is
playing.
It doesn't care what the playlist might be doing - the current pattern at
the time you play notes gets recorded into.
If the pattern is repeating, then obviously altered notes will sound in each
repeat.

Generally when I'm using track record, I set up a playlist with a number of
contiguous patterns without any repeats.
It's simpler that way...
But track record over an existing complicated playlist of patterns, with
judicious use of 'del' to clear a space then adding new notes in next time
round can be a very quick way to make changes.
 
While we're on the subject of real-time record, I've been doing a bit more
work on it of late, so I've uploaded a new beta to Yahoo files - v3.1.006
beta 25.

A limitation of the record mode up to now is that it only tracks the most
recent note played.
If a new note over-laps a previous one, then the first note is TIEd to the
second.
But if you hold one note, then play and release other notes over the top of
it, the held note is only be recorded until the first additional note.
After a new note is played, the held note is forgotten about.
The new record code now tracks multiple notes, so will capture that sort of
thing correctly.
And since it's tracking multiple notes, I'm looking at whether to optionally
record into any auxes assigned the 'aux note' events, for polyphonic
real-time recording.

There are a couple of other changes in the b25 build that are not final but
I'm looking for feedback on.
A number of people have commented that they find it easy to forget where
they are in the soft-key pages for play and edit modes.
The pages are arranged in two 'columns', where PAGE moves down each column,
and FUNC+PAGE switches to the other column.
In this build, FUNC+PAGE still switches to the other column, but also jumps
back to the top page in each.
Somehow I find this makes it easier to go to a certain page. Let me know
what you think...

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