hoot
Junior Member
Posts: 68
|
Post by hoot on Aug 3, 2024 22:51:10 GMT -6
Hey all!
When trying to calculate the H/W Latency delay of the studio I was working in today (running HDX), I ran into a situation where the “inserted” track would precede the original click track I had recorded as a base reference.
It was only a single sample off with the H/W Latency settings set to 0.00, but a sample in the wrong direction. I’d have to go negative if I wanted to get it “bang” on. What would cause this behavior from Pro Tools?
Thanks!
|
|
|
|
Post by Johnkenn on Aug 3, 2024 23:49:45 GMT -6
No idea, but I had something similar when trying to calculate delay comp in the past. Thank GOD they’ve got it working in PT now.
|
|
|
|
Post by guitfiddler on Aug 4, 2024 0:30:37 GMT -6
Geez, it took long enough! Do you mean you can actually use Protools Studio(Vanilla) with auto compensation with any interface running native? I got a Carbon because of this never ending failure with PT native to use my outboard.
|
|
|
|
Post by bgrotto on Aug 4, 2024 10:25:50 GMT -6
Hey all! When trying to calculate the H/W Latency delay of the studio I was working in today (running HDX), I ran into a situation where the “inserted” track would precede the original click track I had recorded as a base reference. It was only a single sample off with the H/W Latency settings set to 0.00, but a sample in the wrong direction. I’d have to go negative if I wanted to get it “bang” on. What would cause this behavior from Pro Tools? Thanks! If the interface wasn't Avid, the latency won't be correctly calculated. When we were running a Burl mothership at my place, we experienced this same problem (though the difference was larger than one sample). |
|
|
|
Post by Johnkenn on Aug 4, 2024 10:53:48 GMT -6
I’m not asking what god is being appeased, but all my HW lines up so I’m not futzing with anything.
|
|
|
|
Post by craigmorris74 on Aug 4, 2024 11:40:38 GMT -6
I don’t think entering a negative value would be a problem.
|
|
|
|
Post by Dan on Aug 4, 2024 12:19:24 GMT -6
i/o can be +/- 1 sample or only sample accurate
|
|
hoot
Junior Member
Posts: 68
|
Post by hoot on Aug 6, 2024 0:01:00 GMT -6
If the interface wasn't Avid, the latency won't be correctly calculated. When we were running a Burl mothership at my place, we experienced this same problem (though the difference was larger than one sample). They were using 192s, so I assumed things would be fail safe. I'm seeing from others that H/W delay can actually be negative, news to me! Anyways, this must've meant the HDX system was overcompensating and I should have thought to just try negative. |
|
|
|
Post by thirdeye on Aug 6, 2024 10:36:29 GMT -6
If the interface wasn't Avid, the latency won't be correctly calculated. When we were running a Burl mothership at my place, we experienced this same problem (though the difference was larger than one sample). They were using 192s, so I assumed things would be fail safe. I'm seeing from others that H/W delay can actually be negative, news to me! Anyways, this must've meant the HDX system was overcompensating and I should have thought to just try negative. Was there anything else inserted on track, perhaps another plugin? Pro Tools relies on the plugin to report the correct latency to it, which I've seen be wrong in the past. |
|
