![]() ![]() While Pro Tools latency and ADC is a buggy mess, it is usually possible to get stuff working OK if you avoid the known problems.ĭo you have "extra buffering" disabled in the the UAD console? Make sure ignore errors is not checked in Pro Tools.Note: The latency methodology described in this article applies to all keyboards on Test Bench 1.2 and earlier. There are also a known bug with H/W inserts that can cause very large (2K or 4K or so samples) false incorrect ADC corrections if they are used with Low Latency Monitoring. Or I should say "should correct for recording latency" since there is the known bug where checking "ignore errors" causes incorrect time line placement of recordings (with or without "ADC" being enabled). they correct according to the latency reported by the CoreAudio or ASIO interface when using non-DigiLink interfaces. Pro Tools Ultimate/Standard/Studio/Artist/Intro. that will be corrected by Pro Tools regardless of the ADC setting.Īll versions of Pro Tools correct for recording latencies. There will always be convertor delays adding some latencies. (edit April 2023: ouch deleted incorrect info that has been sitting here for years)ĪDC corrects plugin latencies, it should not affect anything you are seeing where there are no plugins. What is "SF" in "UA Apollo Duo SF" Mk I or II? Firewire? Thunderbolt? This is driving me crazy, as there is nothing i can think of anymore to get rid of that problem.ĭo you guys maybe have an idea what it could be? i am thankful for every tip:) I also tried all the above with low latency monitoring off and on, the outcome was the same. the problem occurs everytime, a restart or anything like that doesn't change the behavior of pt. there were also no plugins in the apollo console open. pt has to take the buffer size into account, right? there are no other audio tracks in the whole session than these, there is no busses and no plugins. ![]() So: what is the problem here? pt would have to behave just like ableton, right?įirst off, the buffer size shouldn't make any difference to where pt is recording the audio to. ![]() i put those tracks into the pt session for the screenshot, too. i did it with a 128 buffer and with a 1024 buffer, and both times it was perfectly on the grid. I then did the same thing with ableton, recorded the internal ableton click there (also going out of apollo's line output and recording the line input). putting it to 'short' or 'medium' made it even worse, as you can see in the attached screenshot. I also fiddled around with the internal delay compensation of the apollo, which was initially set to 'off'. This was all done with delay compensation enganged (although this also should make no difference because looking at the mixer there is a green zero on each channel, so no day comp needed.) i set the buffer size to 1024 and the outcome was even worse (around 1200 samples late). with a buffer size of 128 there was already a noticeable delay in the recording (it recorded around 240 samples late). Then i routed that same click track out of a line input of my apollo, which i connected to a line input of my apollo and recorded that. both times the recorded click was perfectly on the grid. i recorded it with a buffer size set to 128 and then set to 1024. now i did, and the outcome is this: (all of the stuff written below you can also see in the attached screenshot)įirst i created a click track and routed it to an internal pro tools bus. i mainly track vocals in pro tools and always had the feeling that it's a little off, but never got around to really check. i found out, that my protools is recording late. I have an odd situation that i need your help with. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |