Understanding an "in the box" dubbing workflow

[koo_koo_bonkers]

I held off on upgrading so long I went directly from v7 to v12. Well I dabbled in v9 a bit on my laptop...

A hold over from v7HD cards I used to have my stems setup so they would cascade through audio tracks that were input enabled and fed my master bus. I could monitor as I worked and then print as required.

Earlier this year I setup v12.7HD Native (no avid hardware) with stems and master bus in the same old way as v7HD cards only to realise that there was a "known issue" where the stems would print a frame or two late if setup cascaded.

I'm trying to understand the issues better and I'm looking through the "Whats new" docs for versions 12.7 and up. Is this what "Blue mode" referrers to ? Is everyone just using the track commit feature for stems now ?

Currently I'm setup to use aux sends to feed my stems as a colleague recommended. I have also experimented with using track commit from my source busses which is a great new feature.

Any advice would be amazing ...

Thanks

[Dan Smith]

This is exactly what blue mode is for, which is for HDX systems. However I follow the same procedure on my HD Native system and haven't found any delay on my printed masters. And it has been that way since before they released "blue mode." With delay comp turned off on those tracks I don't have any delay. All my print tracks are being fed by master auxes for each stem. I monitor through the input on my printmaster track. Track commit and offline bounce to multiple busses at once is really great but normally I'm printing and punching in, in real time.