4 Sep
2014
4 Sep
'14
7:58 p.m.
On Thu, 2014-09-04 at 19:57 +0200, Ralf Mardorf wrote:
On Thu, 2014-09-04 at 17:42 +0000, Fons Adriaensen
wrote:
^ not ;)
On Thu, Sep 04, 2014 at 07:33:58PM +0200, Ralf
Mardorf wrote:
You got me wrong! I only pointed out that "NSM (Non session management)
support." - http://qtractor.sourceforge.net/qtractor-index.html Could
cause issues, for those who understand it word by word. And who aren't
aware that "An Audio/MIDI multi-track sequencer" -
http://qtractor.sourceforge.net/qtractor-index.html has to be understand
word by word. Audio tracks are just a bonus that isn't part of the
complete concept.
I never claimed that NSM is bad, I just pointed out that Qtractor offers
features that aren't restored, by this session manager. Users should be
warned! I don't need a warning, I'm using scripts! I don't lamment! I
just want to help, that users once will be upset, because they If jackd is started with settings that cause
another latency, than the
latency that was used, when an audio recording was done with Qtractor,
then audio and MIDI tracks get out of sync. So jackd has to be started
with the same latency. If the session manager shouldn't start jackd, the
latency settings could be incorrect.
And that is a design error in Qtractor and has *nothing* to do with NSM.
If latency compensation is implemented correctly (which is easy) there
no need to remember any latency values in the session file. Which implies
that a change of latency doesn't matter, see also my previous post.
So please stop whining about this. misunderstood Qtractors NSM support.
Ok?
Regards,
Ralf