Re: Session management with NSM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 04.09.2014 16:49, schrieb Ralf Mardorf:
Hi Rui :)

On Thu, 2014-09-04 at 15:34 +0100, Rui Nuno Capela wrote:
as said, automatic latency compensation in qtractors audio recording is
a one-time settlement--it gets settled at the time you take the
recording. nevermore it gets auto-adjusted later on, ie. the take offset
value, as read from jack_port_get_latency*(), won't ever change
thereafter. that means you're in charge to tweak it later if you please,
by summoning the clip properties dialog and changing the offset value as
you wish.
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.

______________________________

Your conclusions here are wrong. NSM didn't forward any jackd settings to the clients. So, how a client behave regarding the latency setting in jackd, have nothing to do with, if it support NSM or not. Also, your use of scripts didn't change that, so it isn't good or bad, it's simply just the way YOU do it.

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user




[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux