With the coming release of the new sequencer project. First of all, Iwould like to say… WOW !! to TK.
I intend to use this project for springboard for a 16 trk (more less?) sequencer. Those of you with like minded aspirations, lets collaborate on this thread.
TK had to say this:
16 track sequencer: everything is possible
BUT: only with some disadvantages, which
I don’t want to consider in my implementation.
With 16 tracks it wouldn’t be possible to store the whole
pattern in RAM. The sequencer core has to read the
pattern directly from EEPROM instead. This has no
timing disadvantages (remember that sending a
MIDI event takes 1 mS, an EEPROM value can be
read within 10 uS…), but it makes realtime editing
via MIDI impossible. Most parts of the control surface
handler would have to be changed, so that only
the select track is buffered in RAM. Features like
Morhphing wouldn’t be possible anymore, since this
requires a second data set of the layer values.
The whole SysEx store structure would have to be
changed to a new format, it wouldn’t be possible
to store 128 patches in a single BankStick, but only
32 or so… a second JSynth GUI would be required to
take the changed data structure into account (note:
realtime editing with JSynth wouldn’t be possible
anymore), and last but not least: a second documentation
would be required and somebody who answers the
questions to this different implementation.
Just take this into account…
And to repeat it for the guys who didn’t read my other
postings regarding the reason, why I only
need a 4 track sequencer: I’m using it as creativity
tool. Once a nice sequence “works”, I record it with
Logic, and the MBSEQ is free for the next track.
Sooner or later I’ve to rearrange and mixdown the
sequences anyhow, and for this an editor like Logic is
much more efficient (yes, in this situation I really like
to use a mouse).
If you really want to record, play, arrange, mix a whole
song with a standalone device, then you have to program
something which has been done by Emagic or Steinberg
15 years ago - on the Atari ST (a second-hand Atari costs
you less money and less effort)
Arumblack: for every CC’s you have to use a seperate
track. But see above, why more than this doesn’t make
sense. It is possible to chain multiple MBSEQs (synced
via MIDI clock), but it isn’t possible to control them from
a single control surface (it would have to save all
editable parameters in RAM anyhow)
So control surface handler would have to change as well as sysex format. Would it be possible to use a “processing core” to handle the ram buffer ?