I will have to do more testing with this. I can't do that at the moment though but thanks for your help. Hopefully I will figure this out yet, and it seems like it can be done from what you're saying.
On Sat, Jan 2, 2016 at 9:48 PM, J. Liles <[email protected]> wrote: > The JACK IO delay values are all or nothing. You cannot have a separate > delay for some channels on a multichannel device, which is what it sounds > like you're trying to do. > > However, if you run the signal through a strip in Non Mixer with the > LADSPA "artificial latency plugin" on it with the correct value entered, > you may be able to get the compensation you want. > > No software can reach outside the computer and guess what's going on in > your studio wiring... > > > On Sat, Jan 2, 2016 at 1:42 PM, PJ Aileanach <[email protected]> > wrote: > >> I just did some tests trying this, with JACK set up to account for the >> I/O delay. I can confirm this is working with jack_delay after the >> adjustment. >> >> I tested 2 aligned snares tracks in non timeline (Playback Latency >> Compensation enabled), one going straight to non mixer and then playback, >> the other first going to bypassed outboard gear, then playback. The two are >> out of sync unfortunately. >> >> On Sat, Jan 2, 2016 at 8:58 PM, J. Liles <[email protected]> wrote: >> >>> If you manually use the jack latency tools to measure and inform JACK >>> of the input and output latency of your outboard gear (with the -I and -O >>> options), then Non Timeline will use this information when calculating its >>> adjustment. >>> >>> Latency compensation isn't magic. It is basically a lot of complicated >>> bookkeeping resulting in a value for an offset to the playback (the reverse >>> of a delay) of individual tracks in the timeline. It will only work >>> properly if all of the information that goes into this calculation is >>> accurate. Sometimes plugins lie about their actual latency, and so you may >>> have to compensate for things like that. It is very complicated in practice >>> and I can't tell you if a given situation would work without knowing all >>> the specifics. >>> >>> >>> >>> >>> >>> On Sat, Jan 2, 2016 at 12:49 PM, PJ Aileanach <[email protected]> >>> wrote: >>> >>>> Thank you for the quick reply. When you say compatible signal routing, >>>> what does that mean? Does this only refer to software latency compensation? >>>> Or is there a way that it would work when including outboard gear in a set >>>> up? >>>> >>>> On Sat, Jan 2, 2016 at 8:43 PM, J. Liles <[email protected]> wrote: >>>> >>>>> Non Timeline and Non Mixer work together to perform latency >>>>> compensation (when you enable the Playback Latency Compensation option in >>>>> Non Timeline). >>>>> >>>>> There are limitations to the way this works, though, and it depends on >>>>> having a compatible signal routing in JACK. For corner cases, there is a >>>>> ladspa plugin that sets a fake latency value to allow you to trim that and >>>>> of course there are plenty of delay plugins too. >>>>> >>>>> >>>>> On Sat, Jan 2, 2016 at 11:54 AM, PJ Aileanach <[email protected]> >>>>> wrote: >>>>> >>>>>> I've recently been learning how to use the Non suite of software and >>>>>> i'm very close to being 100% satisfied for my purposes. The last piece of >>>>>> the puzzle is latency compensation. I don't believe that Non itself has >>>>>> any >>>>>> way of working with this itself (?) but maybe someone knows of a LADSPA >>>>>> plugin, or other hack, that will allow me to achieve this. I use some >>>>>> outboard gear and this is my reason for needing this. Anyone have any >>>>>> suggestions? >>>>>> >>>>>> Cheers, >>>>>> PJ >>>>>> >>>>> >>>>> >>>> >>> >> >
