On Thu, Sep 04, 2014 at 07:33:58PM +0200, Ralf Mardorf wrote:
> 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.
Ciao,
-- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow) _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Fri Sep 5 00:15:03 2014
This archive was generated by hypermail 2.1.8 : Fri Sep 05 2014 - 00:15:03 EEST