4 Sep
2014
4 Sep
'14
7:48 p.m.
On Thu, 2014-09-04 at 23:24 +0545, Kazakore wrote:
On 04/09/14 23:18, Ralf Mardorf wrote:
I start a script and my session is started as it is needed.
$ ./start-script-song-foo
jackd is started with the latency that is needed to get Qtractor's audio
and MIDI tracks in sync.
Assumed a session manager, e.g. NSM shouldn't restore the jackd latency,
then the session isn't restored. If tracks aren't in sync, it's not a
restored session.
A simple question, is it possible to restore a Qtractor session using
NSM, IOW is it guaranteed that jackd doesn't run with a wrong latency?
On Thu, 2014-09-04 at 23:09 +0545, Kazakore
wrote:
And that has WHAT to do with NSM support? On 04/09/14 20:34, 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.
_______________________________________________
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.