Alexa timecodes come up 00:00:00:00

Hi all,

Going from FCP 7 to OSX Resolve 8.2.2 (also tested 9B1) I'm running into a problem I've never seen before. About half of the Alexa ProRes 4444 files show up in the browser as having no embedded reel name and timecode that starts at 00:00:00:00. Even more strange, these files are intermixed with the Alexa footage that works - coming up with the correct reel and has timecode starting at a normal time-of-day timecode. So, on a given mag, takes 1 3 and 7 might work, and takes 2, 4, 5, 6 might not.

I can't think of any workaround to conform these since the timecode is being read incorrectly. In final cut, the reels and media start values are correct (so I think the project XML is also correct).

Any thoughts?

KC

Prehistoric Digital

Thanks Anish, sent that along. Just to be clear- this configuration has worked and still works with all other Alexa footage, and I haven't seen this problem with any other footage from any camera...

My workaround was (ugh) to read the "media start" on the transcoded dailies and use "change timecode" to specify the media start on the camera originals. Many hundred of times. While doing that, we noticed some oddities in the camera original footage. Occasionally the camera recorded exactly 9-second takes of green frames...it's unclear if the camera rolled or if it was writing these clips to the cards without rolling. On those clips, the time resets to 00:00:00:00.

There's definitely something wrong with the clips from the camera, but in the end we seem to be able to get the picture in by manually putting in the timecode and extracting reel numbers from file path...

KC

Prehistoric Digital

Hi Stacy,

I did not and I never heard a resolution from BMD. Definitely e-mail them at davincihelp at blackmagicdesign dot com.

I blame Arri.

Cheers,

KC

Prehistoric Digital