[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon Aug 26 07:06:01 2002
Here is my sequencer vision..
A sequencer type has a specific data format and an API for access and
manipulation of its elements (such as notes). The data is converted into
events at playtime. So the sequencers are event generators.
The editors are separate plugins but they use the APIs of the particular
sequencers. Because of the GUI code, the editors are platform dependent
while the sequencers are not. One type of sequencer data could be edited
with any editor supporting it. Most editors are probably
sequencer-specific, but nothing says that an editor couldn't support
several sequencer types. I don't know..
There is also a "container" sequencer type which allows placement of data
segments (what do you call them generally, patterns, blocks?) of all kinds
of sequencer types, and perhaps simple samples. They can even be nested
recursively! If there is a "main sequencer" it could be of this kind.
Niklas Wallen <=