On 04/09/14 23:18, Ralf Mardorf wrote:
> On Thu, 2014-09-04 at 23:09 +0545, Kazakore wrote:
>> On 04/09/14 20:34, Ralf Mardorf wrote:
>>> IIUC NSM doesn't care about the jackd settings. When Qtractor also
>>> ignores the settings, expects that they are the same as when an audio
>>> track was recorded, then Qtractor _does not_ support NSM session
>>> management. I start my sessions by scripts and don't use a session
>>> manager and it seems that my decision to do so is good.
>> Do you honestly not see how much of a fallacy that statement is? If not
>> please mull it over for a moment, I'm sure it will come to you how two
>> programs, both not controlling/listening to a third programs settings
>> has absolutely nothing to do with their functioning together!
>>
>> Dale.
> 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 has WHAT to do with NSM support?
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Fri Sep 5 00:15:02 2014
This archive was generated by hypermail 2.1.8 : Fri Sep 05 2014 - 00:15:02 EEST