|
Post by Johnkenn on May 25, 2021 23:53:54 GMT -6
Yeah - I have completely NO IDEA why it's not working...found this thread where Drew @ UA explained...and even a video he sent. All my settings are correct. I can put the insert on the channel - I hear the playback with the HW on it - but I'm not getting any signal back onto the Pro Tools Channel. It's like I'm just monitoring it.
|
|
|
Post by Johnkenn on May 25, 2021 23:58:38 GMT -6
|
|
|
Post by Drew @ UA on May 26, 2021 5:32:23 GMT -6
Yeah - I have completely NO IDEA why it's not working...found this thread where Drew @ UA explained...and even a video he sent. All my settings are correct. I can put the insert on the channel - I hear the playback with the HW on it - but I'm not getting any signal back onto the Pro Tools Channel. It's like I'm just monitoring it. Be sure LLM is off.
|
|
|
Post by indiehouse on May 26, 2021 6:48:18 GMT -6
Yeah - I have completely NO IDEA why it's not working...found this thread where Drew @ UA explained...and even a video he sent. All my settings are correct. I can put the insert on the channel - I hear the playback with the HW on it - but I'm not getting any signal back onto the Pro Tools Channel. It's like I'm just monitoring it. I had my X6 hooked up last night and used HW insert to run a loop back. Had to go into Console Swttings and make sure it was set to Apollo X6 or something like that (preset). Also had to mute those channels in Console, because I was hearing it from there as well. Also, I was physically using channels 3-4, but the HW inserts were using 5-6. I think I need to rename PT’s I/O to account for the loss of 1-2, which is the main outs on the Apollo. Hope that gets you closer.
|
|
|
Post by Johnkenn on May 26, 2021 8:25:48 GMT -6
Yeah - I’m doing all of that. I’m just flummoxed.
|
|
|
Post by kcatthedog on May 26, 2021 8:27:36 GMT -6
What if you open a brand new session and just see if you can get inserts working ?
|
|
|
Post by Johnkenn on May 26, 2021 8:57:38 GMT -6
What if you open a brand new session and just see if you can get inserts working ? Tried that...ok - I'm starting completely over...reboot, etc.
|
|
|
Post by indiehouse on May 30, 2021 6:58:56 GMT -6
What if you open a brand new session and just see if you can get inserts working ? Tried that...ok - I'm starting completely over...reboot, etc. Here’s my setup with PT and X6 HW inserts.
|
|
|
Post by Johnkenn on May 30, 2021 14:43:55 GMT -6
Hey thanks for posting that! Yeah - mine's set up just like that and I think everything is kosher now...but why don't I have to add any delay calculations?
|
|
|
Post by indiehouse on May 30, 2021 18:10:37 GMT -6
Hey thanks for posting that! Yeah - mine's set up just like that and I think everything is kosher now...but why don't I have to add any delay calculations? I think you're technically supposed to. I don't know how PT calculates ADC, but I don't think it's technically accurate for non-Avid interfaces. You could always try the click test and see if it's accurate, or by how much it's off.
|
|
|
Post by Johnkenn on May 30, 2021 18:21:16 GMT -6
Hey thanks for posting that! Yeah - mine's set up just like that and I think everything is kosher now...but why don't I have to add any delay calculations? I think you're technically supposed to. I don't know how PT calculates ADC, but I don't think it's technically accurate for non-Avid interfaces. You could always try the click test and see if it's accurate, or by how much it's off. Yeah - the weird thing is (at least the last time I tried) it records it ahead of the source track. So weird.
|
|
|
Post by Blackdawg on May 31, 2021 2:02:53 GMT -6
Protools delay compensation is only guaranteed to work on avid converters. And really only hdx.
Non avid converters can do it via hdx but they can be off still or drift. All depends on the hardware and the firmware handshake it's doing to make it work. Because basically third parties have to trick protools into thinking it is using an avid hdx converter.
|
|
|
Post by thirdeye on May 31, 2021 12:31:27 GMT -6
Protools delay compensation is only guaranteed to work on avid converters. And really only hdx. Non avid converters can do it via hdx but they can be off still or drift. All depends on the hardware and the firmware handshake it's doing to make it work. Because basically third parties have to trick protools into thinking it is using an avid hdx converter. +1. The Lynx Auroras we use work perfectly. Lynx's LTHD card mimics Avid HD interface's latency spot on.
|
|
|
Post by gfunny72 on Dec 4, 2021 14:36:15 GMT -6
I think you're technically supposed to. I don't know how PT calculates ADC, but I don't think it's technically accurate for non-Avid interfaces. You could always try the click test and see if it's accurate, or by how much it's off. Yeah - the weird thing is (at least the last time I tried) it records it ahead of the source track. So weird. John I get the exact same thing on Pro Tools HDX with BurlB80 mothership - it is rendering the audio before the originating audio that feeds the hardware insert. Did you solve this problem? I have delay compensation on
|
|
|
Post by Johnkenn on Dec 4, 2021 14:47:28 GMT -6
Yeah - the weird thing is (at least the last time I tried) it records it ahead of the source track. So weird. John I get the exact same thing on Pro Tools HDX with BurlB80 mothership - it is rendering the audio before the originating audio that feeds the hardware insert. Did you solve this problem? I have delay compensation on I never figured it out.
|
|
|
Post by kcatthedog on Dec 4, 2021 15:49:21 GMT -6
Drag.
|
|
|
Post by ragan on Dec 4, 2021 16:05:53 GMT -6
Apologies for not reading the whole thread but did you manually calc the roundtrip latency (at the buffer you're working at, it changes with the buffer size) with like a printed audio click track and then enter that (in ms) in the hardware insert delay comp settings?
|
|
|
Post by drbill on Dec 4, 2021 16:07:36 GMT -6
Yeah - the weird thing is (at least the last time I tried) it records it ahead of the source track. So weird. John I get the exact same thing on Pro Tools HDX with BurlB80 mothership - it is rendering the audio before the originating audio that feeds the hardware insert. Did you solve this problem? I have delay compensation on I've only had that happen a couple of times. It was a Mac OS glitch, and a reboot fixed the problem. But I'm using AVID conversion, so there's that. It may be that the Burl's are not reporting the delay compensation correctly to PT.
|
|
|
Post by gfunny72 on Dec 4, 2021 18:35:01 GMT -6
The only way to correct it would be to enter negative ms in the hardware insert - which protools does not allow. The rendered audio is BEFORE the original audio not after Apologies for not reading the whole thread but did you manually calc the roundtrip latency (at the buffer you're working at, it changes with the buffer size) with like a printed audio click track and then enter that (in ms) in the hardware insert delay comp settings?
|
|
|
Post by gfunny72 on Dec 4, 2021 18:36:42 GMT -6
One of the reasons for going with hdx is the supposed bulletproof latency management, this is worse than studioone which I was using. I hope it’s some silly thing that I’m overlooking The only way to correct it would be to enter negative ms in the hardware insert - which protools does not allow. The rendered audio is BEFORE the original audio not after Apologies for not reading the whole thread but did you manually calc the roundtrip latency (at the buffer you're working at, it changes with the buffer size) with like a printed audio click track and then enter that (in ms) in the hardware insert delay comp settings?
|
|
|
Post by seawell on Dec 4, 2021 23:35:33 GMT -6
HDX + Avid or Lynx Interfaces have always been the most reliable for me as far as proper delay compensation goes. Antelope has been the worst for what it's worth.
|
|
|
Post by gravesnumber9 on Dec 4, 2021 23:36:45 GMT -6
One of the reasons for going with hdx is the supposed bulletproof latency management, this is worse than studioone which I was using. I hope it’s some silly thing that I’m overlooking The only way to correct it would be to enter negative ms in the hardware insert - which protools does not allow. The rendered audio is BEFORE the original audio not after Funny, I read this thread and was like… Studio One has this nailed. Latency management in Pipeline is one click and done.
|
|
|
Post by drbill on Dec 5, 2021 0:41:39 GMT -6
One of the reasons for going with hdx is the supposed bulletproof latency management, this is worse than studioone which I was using. I hope it’s some silly thing that I’m overlooking Funny, I read this thread and was like… Studio One has this nailed. Latency management in Pipeline is one click and done. PTHDX is the same. One click - done. Something is off here....
|
|
|
Post by jhsmastering on Dec 5, 2021 9:30:24 GMT -6
John I get the exact same thing on Pro Tools HDX with BurlB80 mothership - it is rendering the audio before the originating audio that feeds the hardware insert. Did you solve this problem? I have delay compensation on I've only had that happen a couple of times. It was a Mac OS glitch, and a reboot fixed the problem. But I'm using AVID conversion, so there's that. It may be that the Burl's are not reporting the delay compensation correctly to PT. You use Avid conversion and nothing else? Which interface exactly do you use?
|
|
|
Post by drbill on Dec 5, 2021 12:59:37 GMT -6
I've only had that happen a couple of times. It was a Mac OS glitch, and a reboot fixed the problem. But I'm using AVID conversion, so there's that. It may be that the Burl's are not reporting the delay compensation correctly to PT. You use Avid conversion and nothing else? Which interface exactly do you use? Yes. AVID only. HD I/o's.
|
|