On Tue, May 08, 2012 at 11:48:41PM -0400, S. Massy wrote: > On Tue, May 08, 2012 at 04:17:07PM -1000, Joel Roth wrote: > > On Tue, May 08, 2012 at 08:41:02PM -0400, S. Massy wrote: > > > Hello, > > > > > > Are we applying latency compensation yet, or are we just calculating it > > > for the time being? I have a project with latency offsets reported, but > > > can't find any evidence of eeither -etd or playat being used either in > > > the chainsetup file or in ecasound logs. So I'm wondering... > > > > Massy, > > > > I did a simple test right now with two tracks > > and a delay causing effect on one, and got an > > extra operator applied (visible with 'sh' on > > the other.) > > > > You don't see -etd in the chain setup file > > because Nama applies effects using IAM commands > > after loading the chain setup file. > I see the etd op using show_track. However, it doesn't show up in an ecs > created with cs-save-as, nor iin the ecasound log, nor in the nama log > with "-L ECI". Am I missing something? In fact, if I issue cop-list, I get all the ops on the track except the Delay op. Could nama somehow believe there is an op there but it never gets cop-add'ed to the chain? > > > On a related now, I'm thinking that LCR delay, or some other > > LADSPA delay effect would be interesting to use instead > > of -etd, because we could do a second calculation > > and watch the require latency offsets drop > > to zero. > The problem with LCR delay is that I'm afraid it does mid-side > conversion to have separate delay lines for left, right, and centre. I > only had a cursory look, still I couldn't find a plugin to simply delay > the signal by a given offset without mangling it. > > Cheers, > S.M. --