Logic Pro X sudden latency apogee duet

Thank you for your thoughtful reply. Nice that someone is willing to take time to respond to a stranger for nothing in return. I don't think this particular advice is going to address the issue i've been dealing with. My buffer size is set at 64. And with low latency mode, Logic effectively bypasses all channel inserts/effects during recording so what you hear while monitoring audio recording through headphones is the dry signal correct? I understand that results in a lower latency. As most vocalists and producers would likely agree with, at the very least, a touch of reverb is almost necessary for performace quality. That aside though, I would definitely happily clear the channel strip while recording if the effects i use while recording audio caused a distracting amount of latency. They don't though. almost every vocal take i record has one or two effects on the way in just to give me a flattering signal through the monitors so the take will hopefullly come out better resulting from the confidence of liking what i'm hearing. It's only at random moments, sometimes just recording an acoustic guitar through a DI with the channel strip of every track completely empty, not even the armed eq and compressor logic throws in automatically. I'll hear a distorted kind of buzzing phasy sound for a second or two followed by the same noise level prior. its just after that odd sound, i might see a message that logic couldn't process the midi information and there was some kind of overload (this happens when no tracks are software instrument or drummer tracks or contain anything related to MIDI) and then, if i pluck a note on the guitar, i'll hear it in my headphone monitors like two seconds later. So much later it'd be impossible to record anything remotely in time. Maybe I'm the only one and it's some isolated thing. But I don't think effects in channel strips are inducing the sudden onslaught of latency from perhaps 7 miliseconds to 2.5 seconds. I sincerely do appreciate the response. Thanks

Thank you for replying Pancenter.

Yes the Duet connects via a USB cable. I am inclined to think the problem/ issue is not caused by the duet. My rationale being, and this just occurred to me because it just happened while using both a line out of an acoustic guitar and a condenser mic as inputs on two separate audio tracks in logic. the same old thing happened where it went from negligible latency, to an odd digitally kind of distorted unmusical sound to the same noise level produced prior to the odd sound. and immediately afterwards, latency was north of two seconds. i do however, use a tuner app for my guitar that uses the line from my guitar through the duet to tune the guitar. this problem happens regardless if the app is in use. but just looking at the meters on the duet and the tuning app. no latency was introduced suddenly except in logic. and if i close logic and reopen it, the problem goes away for anywhere from 15 minutes to 3 hours.

I tend to use the headphone port on the macbook air to monitor instead of the duet 2. now realistically, i understand this might add a couple miliseconds of latancy, but i just get a better feed from the macbook headphone jack. perhaps because i use a converter for the quarter inch output to an eighth inch output to monitor directly from the duet. who knows what the deal is. It's not the end of the world. just an annoyance really. thank you very much. Quick question. Are both USB ports on a macbook air "created equal?" one USB does seem to fit more snuggly than the other. Doubt it's the issue though. Thanks again.

charlie

I will definitely give it a try. I actually don't use an aggregate device, well ocassionally, but that's when i use two audio interfaces simultatiously...which is very rare. Both logic and the Duet are set to 44.1 kHz sample rates. The duet maestro software, which i recently updated (i think two weeks ago, so unless they've come up with an update since, that shouldn't be it.) actually says for the "clock source," "internal." Perhaps sample rate and digital clock settings aren't synced? don't worry about being overly technical. I need to learn. The audio coming out of the duet output isn't as good for some reason, probably subpar signal through converter from quarter inch studio headphones to my expensive, but not professionally designed for monitoring or mixing and with the smaller cable input. but it's workable for monitoring. I'll see if the issue pops up again trying that approach.

Thank you again. I'm either naive, ignorant, or just jaded cause it's so suprising to get thoughtful help for nothing in return except appreciation. Thanks again. If it doesn't work, Turning off Logic and turning it back on isn't going to ruin a track for me. Regards, Charlie

Interesting. so 44.1 does not equal 44.1 depending on the device. seems counterintuitive especially as this is within the digital realm. I was monitoring my acousitc guitar with a metronome yesterday (still monitoring via the mac's output) and when this issue occured, i just turned off the monitoring option on the track i was recording and continued playing and did three additional takes. Upon replaying while listening and looking at the wave forms, the take i recorded prior to the sudden latency was nicely on the grid. On the subsequent three takes, all were delayed by what appears to be an identical time (tought to tell because no one's timing is consistantly perfect, especially mine haha) but the integrity of the recording wasn't affected so i just manually dragged the track back in time to where it was played in reality. maybe ryhthm guitar is one instrument in particular that, even with isolating/noise cancelling head phones, can be performed well without need to hear exactly what your playing. It can also be performed badly this way. I was hoping to capture the audio of the sound that occurs prior to the latency as I'm sure it actually does record it when using a mic, but it happened in between takes. Don't have any records of it at the moment because i trashed them earlier.

What you wrote makes sense to me and clears some things up for sure. Thank you. Last question if you'd like to offer your knowledge/thoughts. This same things has occured recording piano via MIDI on a software instrument track. In these cases, however, if i wait for five or so seconds, non of the latency issues are present when recording or playing post interuption and pop up message (the message pops up on average one in four times while recording audio) that says the machine cannot process all the midi information in time (the wording is different in the acutal pop up). Am i correct to assume that the frame rate is irrelevant when recording midi? And if not, I wonder why the latency thing wouldn't occur after that notoriously disturbing three-ish second sound that precedes the latency problem. Think if I continued to montior audio recording via one head phone off or by feel, there would be additional, subsequent events and the latency would double to like ten seconds? Sorry. That's a lot. By no means feel obliged to take the time to respond. You've been more than helpful already and i sincerely appreciate. Best regards, Charlie

well maybe the 44.1 thing does make sense actually. as even atomic clocks need to be adjusted every few hundred years by a couple seconds. i'm pretty sure the apogee and the mac arent using atomic clocks either. what do they put in these devices? little pieces of quartz?