|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#81
|
|||
|
|||
Re: Tracking with Buffersize 32?
Ya all talking about hardware inserts or separate track outputs and inputs.
And the fun of doing these measurements is you might find at least two known latency bugs in Pro Tools. I mean why should anybody expect Pro Tools to get basic stuff like time and phase alignment correct.... for fun start by toggling on and off ignore errors and see if that messes up things. Oh no I posted to the perpetual monitoring latency thread, I'll be trapped here forever... |
#82
|
|||
|
|||
Re: Tracking with Buffersize 32?
Quote:
I'm not sure I understand what you mean by this statement? And is there anyway possible that Protools would still compensate for the new recording with auto delay comp turned off? Sync up the original and the new with ADC off?
__________________
. System info https://duc.avid.com/member.php?u=57185 "please stop OVER-complicating simple things" |
#83
|
||||
|
||||
Re: Tracking with Buffersize 32?
PT delay compensates hardware insert DA/AD but does not compensate for normal output hardwired to normal input.
__________________
Janne What we do in life, echoes in eternity. |
#84
|
||||
|
||||
Re: Tracking with Buffersize 32?
Maybe you bite the next reindeer
__________________
Janne What we do in life, echoes in eternity. |
#85
|
|||
|
|||
Re: Tracking with Buffersize 32?
Quote:
Yes, and with ADC turned off Protools will not/should not compensate for either audio path correct? That's has been my understanding for several years now. Quote:
I've attached a screenshot of the test path. ADC is off and the hardware output and input are connected with analog cables. The two audio files should show some type of latency correct? Then measure the distance in samples and convert that to milliseconds based on the session sample rate. Playback engine set to 64, cache at 8GB, and no other options checked.
__________________
. System info https://duc.avid.com/member.php?u=57185 "please stop OVER-complicating simple things" |
#86
|
|||
|
|||
Re: Tracking with Buffersize 32?
Quote:
What has ADC got to do with this? ADC compensates for insert latency, the internal reported latency from plugins, and when using hardware inserts the interface output and input latency reported via its driver (for CoreAudio or ASIO interfaces) or seemingly hardcoded into Pro Tools for Digidesign interfaces. That is all it does. (And because it's a persistent point of confusion: The Setup>IO>Insert page lets you add correction for additional latency introduce by the external H/W insert device. So it can't reduce what Pro Tools thinks the insert latency is if the driver reported latencies are not correct (and they are expected to be wrong if you have mixed digital and analog paths in an interface, like using ADAT mic/line inputs)... to do that you use the +/- track delay compensation. And yes Pro Tools needs to be cleaned up here, including have a ping function like modern DAWs.). Normal input and output interface latencies are corrected by Pro Tools independent of ADC, again using latency reported via the interface driver (for CoreAudio or ASIO interfaces) or seemingly hardcoded into Pro Tools for Digidesign interfaces. If a DAW did not do this you would have hell of a time getting basic stuff to work. To me the fastest way of measuring hardware RTL is with a hardware insert with ADC turned off. Take a click track, record it to an audio track, bung a H/W insert on that track and then record that track output to another. Measure the offset in the two audio tracks. Last edited by Darryl Ramm; 09-08-2023 at 01:44 PM. |
#87
|
|||
|
|||
Re: Tracking with Buffersize 32?
Ya never told me the girls have antlers.
|
#88
|
|||
|
|||
Re: Tracking with Buffersize 32?
Quote:
If you are configuring the offset values in the I/O menu, there is a section in the manual that explains the measurement procedure. IIRC, it has slightly changed in recent releases, but it might just be the wording rather than the procedure itself. If you are just interested in knowing total system latency, RTL tool by Oblique Audio is great if you have a second system for measurement. For example, Pro Tools DAW RTL = Total RTL - Measurement system RTL. By using a second system, you can stack plugins or change routings or test Avid DSP hardware in Pro Tools and get some very accurate results of how it affects the overall latency. The measurement ‘system’ doesn’t need to be anything fancy. It could just be an extra USB audio interface or the internal sound card running on your Pro Tools machine that gets used exclusively by the RTL tool. It just needs to have stable latency on repeated tests, then you can connect it to any other system to measure its latency.
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. |
#89
|
|||
|
|||
Re: Tracking with Buffersize 32?
I'm not actually sure what any of this is about. What latency are we trying to measure and why? And what has this got to do with this nonsense thread?
|
#90
|
|||
|
|||
Re: Tracking with Buffersize 32?
Quote:
First off Can you please stop with your consistent internet arrogance! It gets old pretty quickly! lol I asked these questions in the way I did for a specific reason. I've also done round trip latency measurements many times over the years using a few different ways including the one you mentioned(Take a click track, record it to an audio track.....). I ran the tests recently and a was only getting 1 sample of latency at 48k and thought it was very strange. I could not figure it out and didn't have time in between sessions to re-read through tech docs or search through forums like I wanted to. My gut feeling was that Protools might still be compensating for the I/O recording pass even with auto delay compensation uncheck/turned off. When you mentioned the "ignore errors" feature which I never ever use in Protools I thought it was worth a try. I exactly saw that mentioned in the Youtube video comment a while ago but totally forget about it so thank you. I turned it on(checked the boxes), ran the RTL test, and got 66 samples of latency which converts to 1.375ms at 48k or 0.69ms at 96k with a hardware buffer setting of 64. Seems better than what the interface manual mentioned but I'll take it. So all and all, I was conducting the tests correctly and now guess I understand why I was only get 1 sample of latency. When I got more time I'll look up more info. out!
__________________
. System info https://duc.avid.com/member.php?u=57185 "please stop OVER-complicating simple things" |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to get the low H/W buffersize of 32 | Dutchmountain | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 7 | 12-18-2009 10:34 AM |
How do i change the I/O Buffersize? | One-i | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 1 | 01-15-2006 09:26 AM |
Buffersize vs RAM | soebx | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 06-01-2005 02:27 PM |
H/W Buffersize and Rewire | am.syn | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 09-23-2004 03:03 AM |
buffersize PT 6.4 ?? | hoijandee | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 05-05-2004 01:01 AM |