There is a bug in version 2.2.5 of Adrenaline which causes BWF files recorded
at 29.97 FPS to import with incorrect timecodes. We discovered this bug while
working on the feature Journey 3-D. Our files were recorded on the Cantar using
the B Mode, which was recommended to us by Aaton. During the course of
troubleshooting, we did a little bit of testing with files recorded in the C
Mode. The timecodes of the C Mode files were closer when imported into MCA
2.2.5, but still off.
Version 2.5.3 or Adrenaline has the same issue plus a few other bugs:
- BWF files get truncated upon import. The duration of the file is incorrect
(short) and upon playback, the clips generate "PMM_INSUFFICIENT_MEDIA" error
- BWF files import using the Quicktime engine and come in with a generic
01:00:00:00 timecode. When this happens, the Avid actually thinks itıs importing
a Quicktime file. If you look at the progress bar while the file is importing it
will say "importing media from Quicktime."
We also experienced a different permutation of issue #2 on an Xpress Pro 4.8.4
system in which files imported with an incorrect drop frame timecode. The Avid
said "importing media from Quicktime" while importing these files.
Xpress Pro 4.8.4 is supposed to be immune to the BWF import bugs and has been
touted as a workaround for people stuck on MCA 2.5.3. I have reported this issue
to Avid, but have been unable to confirm if they have recreated it or if anyone
else has experienced this issue.
Adrenaline version 2.6.2 has been out for a few weeks. It is supposed to have
fixed the BWF import issues. I have not had a chance to test it out yet and I
have heard conflicting feedback about this. Matt Schneider at PostWorks, New
York says that 2.6.2 has fixed the issues. I trust his expertise, but remain a
bit skeptical. Hopefully, I will have an opportunity to test it myself.