hoot
Junior Member
Posts: 68
|
Post by hoot on Feb 9, 2024 19:30:57 GMT -6
Hey all! I'm about to add converters of a different company than my current and would love to mitigate some PITA with regards to calculating delay compensation for multiple converter sets. The advent of Atmos is making me feel like most of my 44.1 sessions might as well get upsampled (and it wouldn't hurt for Sync either).
I've candidly never been sent a 88/96 kHz session, so I'm wondering if I'd be safe calculating my delay comp for 48 kHz, save that into the template, and calling that a day? This is simply based off of my assumption that the Interface itself is responsible for these HW Delay times with little CPU influence. Please correct me if i'm wrong and thanks!
|
|
|
|
Post by bgrotto on Feb 9, 2024 21:55:39 GMT -6
If you're in PT, manual delay comp calculations for HW inserts just flat out sucks. You're limited to ms values, which is basically fucking useless. It's been a while since I bothered trying to get it all working, so I may be misremembering this next bit, but, as I recall there's also some limitations when using AD/DA that is faster than that of Avid's. Like maybe you can only enter positive values in the HW insert latency tab or something? I can't remember for sure, but in any case, it's awful.
I'm actually ditching my studio's Burl Mothership and substituting my Avid IOs back in because of this very issue.
If you want my advice, for maximum ease of workflow, either stick with the Avid interfaces, or, find third party converters that have identical latency figures (some companies who make digilink-able boxes will offer this on a jumper, or even as standard)
|
|
|
|
Post by seawell on Feb 9, 2024 21:59:22 GMT -6
If you're in PT, manual delay comp calculations for HW inserts just flat out sucks. You're limited to ms values, which is basically fucking useless. It's been a while since I bothered trying to get it all working, so I may be misremembering this next bit, but, as I recall there's also some limitations when using AD/DA that is faster than that of Avid's. Like maybe you can only enter positive values in the HW insert latency tab or something? I can't remember for sure, but in any case, it's awful. I'm actually ditching my studio's Burl Mothership and substituting my Avid IOs back in because of this very issue. If you want my advice, for maximum ease of workflow, either stick with the Avid interfaces, or, find third party converters that have identical latency figures (some companies who make digilink-able boxes will offer this on a jumper, or even as standard) You're spot on Benny about some being faster. That's exactly why I could never get the Antelope interfaces working properly with Pro Tools. For no headaches, I'd go with Avid or Lynx interfaces for auto delay compensation, those are the two that have always worked flawlessly for me. |
|
