[Phil Haslam]

I know the D5 doesn’t record vitc timecode that normally gets recorded into standard video camera’s. The D5, primarily a still camera that’s become used by the video community cause the quality of image is what every film-maker looks for. But longditudal timecode can be recorded to CH.1. Unfortunately FCP doesn’t/can’t read longditudal timecode. There’s software that can be bought to read it and then use it but I don’t see the point. Cannon introduced the EOS movie plugin-E1 for FCP to browse, log and import in, I believe in March this year

https://www.usa.canon.com/dlc/controller?act=GetArticleAct&articleID=3249

and made it possible to browse and select before importing into FCP. That way you can delete what you don’t want before importing and at same time it transcodes H264 into ProRess. The driver also builds timecode into the video based on the time and date stamp of the recording. All very useful. What I can’t work out is why, if that’s true my crew are bothering to record timecode into ch.1.

I just can’t cross check it all at the moment until I upgrade my mac to at least 6.06 and FCP to at least version 7.0.2 which is when the canon browser becomes operative in FCP.

That issue and the other issue of external sound I’d also like to understand. I guess the sound is something I’d like understand more than the timecode issue which I think I get. I just want to stop my crew bothering to record timecode but need to be sure before I do.

[Phil Haslam]

Thx Bob, I think what I’m trying to get my head around is how it deals with time code. For my understand Log and Browser in FCP builds it’s own time code based on the time and date stamp of each recording. My crew seem to be adding time code to audio CH.1 which for FCP is redundant. Is that right? Also if the audio is collected externally does the metadata on the clip account for it or do you have to import it seperately and not through Log and browser? thx