Benno Senoner wrote on Mon, 23-Feb-2004:
There is no
guaranteed relative timing between two notes in GSt or LS.
If you send two simultaneous MIDI events to GSt they will start when
they start, just like playing two keys on the piano. They are close to
each other, but they do not begin at exactly the same time.
In Ardour, you can take the same two wave files as samples and place
them in a track such that their relative timing is known exactly. You
could, for example, play one wave file and then play the next one such
that it sounded exactly right. When the first wave file finishes the
second wave file will start. You will have a sample played on every
clock cycle.
LS and GSt will not do this. They are MIDI based and certainly there is
jitter and no timing info in MIDI so you just cannot accomplish this
level of control.
Not true Mark :)
LS does not have this limitation: although the current implementation
for now allows only
ALSA MIDI input, Christian added a time stamped event system which was
planned anyway
for accuracy reasons and because it will allow LS to be turned into a
VSTi or AU plugin.
If some VSTi like standard and sequencers will arise under Linux, LS can
support such features
without needing many modifications to the engine.
In addition, work is being done on midi-over-JACK which will provide
sample accurate timestamped midi events via a new jack port type. Programs
that use this interface will get all the benefits of sample-synced
realtime performance from their sampler/synth, plus the ability
to render accurately non-realtime when JACK is in "freewheel" mode.
jlc