Massive Bug in DOP on N14 using WAV files with metadata

Hi everyone,

I’ve run into a serious and reproducible bug in Nuendo14 (N14) and Direct Offline Processing (DOP) when using WAV files contain extended metadata.

The problem: When I use DOP on files imported via “Field Recorder Audio Import”, everything works fine at first. But after reopening the project the next day, N14 reports that certain WAV files are missing - these are the files N14 created via DOP.
When I locate the files, N14 does find them, but the clips in timeline remain empty. Looking into the “Edit” folder shows that the files exist and have a size, but they can’t be played back (VLC fails). I ran a MediaInfo scan and got this error: Conformance errors: Element size 4756 is more than maximal permitted size 2388 (offset 0x384)
This suggests that the WAV files are not being written corectly during DOP.
This only happens with WAV files containing metadata like cue chunks or iXML. Files without metadata work fine with DOP. Also the plugin used doesn’t matter, I tried serival plugins. Furthermore the bug is platform-independent, I can reproduce it on both of my computers, Windows PC and MacBook Pro M1.
I don’t think it should be necessary to clean metadata from hundreds and thousands of WAV files from field recorders just to make DOP work correctly. This used to work fine in N13 and older. I think it is crucial for film & TV post workflows.
Anyone else experiencing this?

Thanks in advanced for help! And I hope the devs can look into this bug very soon!

Best regards
Sebastian

3 Likes

Hopefuly a simple a very quick fix.

Hi @ST-303 , that sounds very serious. I wasn’t able to reproduce it in a very quick test here. I’ll try more intense tests and investigate tomorrow.
Are you seeing this issue with files recorded from different field recorders? Which field recorder do you use? Or do you run into this problem with any file you import that way?
Would it be possible for you to share a (short) example file with me (a file from the field recorder as well as an edit file)? That would help me a lot
Cheers Dirk

is it a Fostex?

Hi @DSabath,
thank you for reply.

I’m using a TASCAM Portacapture X8. As I already mentioned, everything works perfectly in N13.
Here is a link to a Dropbox folder containing three files from the X8 and one corrupted file generated by DOP in N14:

Files were recorded in 32-bit float, 48k WAV.
Let me know if you need anything else.

Thanks,
Sebastian

Thank you! I’m on it.
Cheers Dirk

1 Like

I wonder if it also happens in 64bit mode.

Hi, just to give you a short update. Basically, the problem is caused by the list of markers stored in the field recorders wave file. It looks like the field recorder is storing a list of 100 marker placeholders with a position of -1, etc. N14 is now able to read and interpret these markers from the wave file, but these markers with their weird values cause confusion when the edit files are written, leading to the corrupt files with incorrect marker chunks.
I’m working on a fix which will be contained in the next maintenance update. Sorry for the inconvenience.

7 Likes

Hi @DSabath,

you’re welcome - and thank you so much for helping out and already working on a fix.
As someone who studied computer science years ago, I totally get it - one tiny thing changed, new unwanted “features” (bugs) created. (Refering to: it’s not a bug, it’s a feature) :wink:

Can you say when the maintenance update might drop?

Best regards,
Sebastian