HDX and ADC issues offline bounce

[jsvalmont]

Originally Posted by Peter Duemmler

Have you done a Null-test? I'm pretty sure native and HDX sound exactly the same, unless there's a bug. We've had this here quite a few times...

There can be a difference when bouncing offline vs real-time on an HDX system. I always bounce in real-time because it matches what I was hearing. My understanding is that when you do offline bounce all the plugins that were being processed on the HDX card get moved over to the CPU, but real-time bounce the HDX card gets used just like when you were mixing. DSP and Native versions of plugins often only null down to some variable number of DB depending on the plugin but rarely nulls entirely. This is because of the differences in architectures and some optimizations that need to be done for TI DSPs.

[reflexson]

Originally Posted by Guy McDude

Sorry for the upstream downstream confusion.

What I meant by that was, any contributing tracks, like your trigger track, that probably goes into a drum bus, then a mix bus, to a print track.
Each and every one of those tracks from start to finish of your signal flow, ( at least in my sessions) need to have subpaths assigned to them to solve the sync / delay compensation/flamming issue.


As an example, I had 50 different songs, that we’re all in the box, that all of the multi tracks were distributed to associated subgroups.

My hope was to off-line bounce or commit those sub groups, and quickly create stems.
I kept on getting these weird delay issues like you are experiencing with the trigger plug-in.

But once I assigned sub paths to all source and recipients tracks like my sub groups, all of those issues went away.

Hopefully that makes sense.

If not please drop me a line, and we could discuss it on the phone

Hang on....are you saying that you take all of your output assignments that would go to your mix bus supplying your converters and route them to a mix bus aux instead which, in turn, goes to your converter output fixes the issue? Im going to test this first thing tomorrow. Hope I read that right.

[Rich Breen]

Originally Posted by Guy McDude

...the addition of sub paths to any contributing ( upstream) sources, or any downstream recipients tracks solved the issue for me.

Avid said it was a known bug, and this “adding sub paths” would be a temporary fix until the bug is addressed in a future build.

Hope that helps.

I haven't run into this issue, but I'm curious about it and your workaround. It's not entirely clear to me what you're proposing as a fix; are you saying that adding mono subpaths to the stereo path in the I/O window is what fixes it for you?

[Rich Breen]

Originally Posted by Rich Breen

I haven't run into this issue, but I'm curious about it and your workaround. It's not entirely clear to me what you're proposing as a fix; are you saying that adding mono subpaths to the stereo path in the I/O window is what fixes it for you?

So, for what it's worth, it appears that this is fixed in 2018.7: "Fixed an issue where Offline Bounce could cause audio files to become out of sync when stereo bus paths have no subpaths."

[Guy McDude]

Originally Posted by reflexson

Hang on....are you saying that you take all of your output assignments that would go to your mix bus supplying your converters and route them to a mix bus aux instead which, in turn, goes to your converter output fixes the issue? Im going to test this first thing tomorrow. Hope I read that right.

Hi,
Here’s the scenario.
All ITB.
Drum tracks to drum sub, drum sub to mix bus, mix bus to print track.

Same goes for guitars, keys, horns, vocals etc.

Each grouping of tracks, go to a group sub, then that sub will go to the mix bus, then the print track.


If I tried to do an offline bounce for my mix, I’d get flamming/ things out of sync in the resulting bounce.

Same would happen if I did a commit on the subgroups in the hope to create stems quickly. I’d get a flamming out of sync artifact.

But....
When I added sub paths to any tracks along the signal flow, ( from source tracks down to print track),the artifacts went away, and all offline bounces or commits were fine and free of sync issues.


Hopefully that made sense.

And yes, as I originally posted, this issue would be (was) fixed in an upcoming release which just came out.

[brianjanthony]

I do hope this is fixed. I will download tonight. I just realized how pervasive this problem is. I open hundreds of sessions per week, from all over the world. Including my own studio, which has gone thru x billion IO Assignment versions over the years.

And working on two new records with vinyl pressing deadlines, and the labels have been really "Huh?" with the last round of bounces (ones done in HDX land vs my Native system). I do listen to the bounces quickly (many times I do off-line bounce bc they are daily, non final, "here's what they sang tonight" type things). But once I start A/Bing them... yikes. comb filtering. my bass disappears sometimes. drums smearing ever so slightly. But not on every song. Madness.

$3000 and all I got was a a headache. Tracking may feel better. But Mixing has been hell on earth. Starting to think I need 2 systems here. :-(.

I am downloading the latest greatest as I type this.