Hello folks 5-year logic user, 1-st time poster here with a problem: On occasion when recording audio, it plays back (and shows up in the arrange window) a good 100ms or so late. It's incredibly frustrating as I then have to manually move the take to where I think it was probably performed. I know it's NOT the following: - bad performance. The whole take is consistently late - accidental movement of the region. I have "limit dragging to one direction in arrange" checked, and it does it even when I haven't moved the region. My guess is that it has something to do with my interface. I'm using an Edirol FA101 Firewire interface, and it can be quirky sometimes. This delay-problem doesn't go away when quitting and restarting Logic, but does usually go away with a restart. Anyone else have this problem? Any solutions? Thanks! - Dylan MacPro Quad Xeon 2.0/2GB RAM Logic Pro 7.2.3 Edirol FA-101 Audio interface

> On occasion when recording audio, it plays back (and shows up in the > arrange window) a > good 100ms or so late. It's incredibly frustrating as I then have to > manually move the take > to where I think it was probably performed. Do you have a latency-inducing plugin in a bus or output object, and bus latency compensation switched off? Maurits.

Dylan wrote: On occasion when recording audio, it plays back (and shows up in the arrange window) a good 100ms or so late. It's incredibly frustrating as I then have to manually move the take to where I think it was probably performed. You have probably set the plugin compensation to "all".

On 08/05/2007, at 4:00 AM, Maurits van de Kamp wrote: > Do you have a latency-inducing plugin in a bus or output object, and > bus latency compensation switched off? I'll bet that's it, it gets me too everytime... ;) michael

--- In logic-users@yahoogroups.com, "HKC" <hkc@...> wrote: > > Dylan wrote: On occasion when recording audio, it plays back (and shows up in the arrange window) a > good 100ms or so late. It's incredibly frustrating as I then have to manually move the take > to where I think it was probably performed. > > > You have probably set the plugin compensation to "all". > Hi folks Thanks for all your suggestions. I took a look at the driver settings... and noticed that the "recording delay" setting had been messed with (set to a 2000 sample delay!). That seems to do it... if not, I'll be back! - Dylan

On May 7, 2007, at 7:14 PM, Michael Scheurer wrote: > > On 08/05/2007, at 4:00 AM, Maurits van de Kamp wrote: > >> Do you have a latency-inducing plugin in a bus or output object, and >> bus latency compensation switched off? > > I'll bet that's it, it gets me too everytime... ;) Question: is there any reason *not* to select "all", so that latency compensation is in effect for busses + inst + audio? Shouldn't you just set that to "all" and leave it, or does mess up something else?

> >> Do you have a latency-inducing plugin in a bus or output object, > and > >> bus latency compensation switched off? > > > > I'll bet that's it, it gets me too everytime... ;) > > Question: is there any reason *not* to select "all", so that latency > compensation is in effect for busses + inst + audio? Shouldn't you > just set that to "all" and leave it, or does mess up something else? I second your question Andrew. And besides van somebody explain to me, when to use all these latency settings and sample delay things? Maybe I'm a bit naive about these things but so far I haven't cared about latency at all .... should I? And if so, when exactly? Is there something in general to say about it?

>> Question: is there any reason *not* to select "all", so that latency >> compensation is in effect for busses + inst + audio? Shouldn't you >> just set that to "all" and leave it, or does mess up something else? As far as I know there's no reason, except if you have old songs where you solved the latency problems with sample delays etc and don't want to break it. That's probably the only reason why it's configurable at all (and why the default is NO bus compensation), namely that Logic tries to behave backwards-compatible by default. > And besides van somebody explain to me, when to use all these latency > settings and sample delay things? I'm not sure what you mean by latency settings, but extra plugins for compensation are always useful when there is a latency that Logic is not aware of. This can be the case when you insert outboard effect equipment, or when you have microphones at different distances recording the same sound. The sample delay can delay a track by a few samples. There is also a latency compensator plugin (not in Logic itself but free for download, somewhere..) that makes a track a few samples *early*. It does this by reporting a latency to Logic that it doesn't actually have, thus compensating for other latencies by outboard equipment for example. > Maybe I'm a bit naive about these things but so far I haven't cared > about latency at all .... should I? And if so, when exactly? Whenever you have a plugin that takes more than one buffer cycle to process audio, you will have latency. Logic compensates this so you don't need to worry about this. (Just set the latency compensation to "full" in case you have such a plugin in one of your busses). If you ever introduce latency that Logic doesn't know of (like when you use the I/O-plugin to introduce outboard equipment in your mix), you'll need latency compensation. > Is there something in general to say about it? Apart from the above: You'll notice when you need it. :o) Maurits.