[Confirmed] Timecode / AAF issues

TimoWildenhain · December 17, 2012, 4:35pm

Hugh:

Hello,
We are long-time Nuendo users with quite a few Nuendo workstations and building more. I recognize that Nuendo Live is designed to have a limited feature set, that’s what makes it so friendly. When chasing TC, which we ALWAYS do, the previously recorded files are shifted on the timeline to match the relative offset between the previous and new files. Example while chasing TC -
Record when TC reaches 01:00:00, stop when TC reaches 02:00:00.
Record when TC reaches 03:00:00, stop when TC reaches 04:00:00.
Result - the original files now start at 2 hours, not 1 hour as they were originally recorded.

I understand the reason for doing this, makes widely separated recordings easily navigated. However the AAF export puts the files at their NEW, incorrect position, not at their originally recorded timestamp position. I also understand why this would be useful - it makes the AAF match the Nuendo Live “timeline”. However there needs to be a checkbox in the AAF export dialog with two options -

Keeps files at Nuendo Live timeline positions, or

Puts files at their original timestamp positions.

Because we ALWAYS use TC the AAF export of Nuendo Live is useless because the files import into ProTools at the WRONG positions. It’s actually dangerous because once you import an AAF into PT, PT writes it’s own timestamp info into the file headers and it can be difficult to correct later. We MUST have them at the timestamp positions. We’re back to importing manually into ProTools, hoping they spot correctly when the timestamp option is easy to implement in Nuendo Live.

Thanks for considering,
Hugh

Hi Hugh,

thanks very much for the explanation and for making us aware of this. We will run a test on the issue you described!

Thanks,
Timo