Pro Tools is often criticised for not being as customisable as other DAWs. The Pro Tools Preferences offer a surprising number of ways to configure operation to your tastes. The only delay which I have measured is a system ( CPU ) delay and AD/DA of HD Omni which altogether results at the value of 57 samples in the 44,1 kHz session which triggers in total 1,21 milliseconds of delay no matter of the buffer size set.Organising plug-ins by manufacturer can help you find what you want more quickly. Delay compensation is working fine as there is no difference while using buffer size 32,64,128 or 1024. I have made a reproduction of your issue in our Audio Lab using Pro Tools 2018.12 Ultimate with HD Native and HD Omni with the click track using your specific workflow. The question of why it was working with specific older versions of Pro Tools is a question for the UAD what they have changed in the driver. UAD driver is not providing the correct delay value to Pro Tools to let it compensate in time. Apollo 16 Thunderbolt 2 is not supported with Pro Tools 2018.12. UAD is a third-party company for Avid which is not cooperating with us regarding driver communication between the unit and Pro Tools. The issue is because of the driver for UAD. Hey Everyone, Here is the official response from Avid: Irrespective this is a clear bug one way or the other, and I hope that UAD and Avid can figure a way to fix it soon!!! So it may be something to do with a recent version UAD software as much as anything else. I am still not sure if this is an Avid or a UAD bug, as I can't believe that no-one would have clocked it as a problem until now. I have gone back to Avid to ask for an early version of 12 to see if the issue has always existed. If I however go all the way back the version 11, then the issue completely disappears. Interestingly the issue still exists within this version 12. I have raised a ticket with Avid, and asked for a copy of 12.8.3 to try and rectify the issue. This does not help or solve the bigger issues that Pro Tools is screwing up the syncing of recorded audio however. This has the effect of changing the amount that the audio is out of sync by, until such time as you change the pro tools buffer again. I suspect that you have changed the IDC in Apollo whilst Pro Tools is still open. non digital desk - so that I can monitor latency free).Ĭlick to expand.Hey Matt, I'm not sure if you have seen my replies on the other thread - but I may have an explanation for why your audio sync issues are inconstant. Latest version of Console (though I can't find a version number on this)Ģ x Apollo 16 connected via Thunderbolt 2 I notice that Console has a concept of virtual tracks - is this something I should be utilising? If so how. The amount of delay shown on the external track almost exactly matches the amount of buffer size set in Pro Tools.Ĭlearly I have set something up wrong. I then looked to see how aligned the 2 click tracks were. I then set up 2 tracks, "internal" and "external" and recorded the bus on the internal and the ran the click through my desk and back into pro tools and recorded this on the external track. In order to prove the point, I have set up a session, where I send a click both out of the Apollo and out of an internal bus. The delay is correlated with buffer size in Pro Tools, however I have only experienced this issue whilst using UAD Apollo 16. Looking into it a little bit further, it seems that a latency is being introduced into the recording chain somewhere. I noticed the other day that performance that had been recorded was a bit out of time - even though it clearly hadn't been at the time of performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |