I've been poking around trying to find a solution for this but haven't seen anything, so I am wondering if anyone else has had this happen:
A drive died on a documentary I've been working on, so we need to retransfer the 200+ 7D files that were on that drive back into ProResHQ, but they are coming up in Log and Transfer with the timecodes off by exactly one hour - all are one hour ahead of the previous transfer's timecodes. Anyone else ever have this? I can't figure out why this would have changed, and it's consistent across every batch of files I've put in so far.
Needless to say, the reconnect process is not working as easily as I'd thought/hoped it would. The only workaround I've been able to figure out is that I can alter the timecodes of the transferred files in FCP after the transfer is done and then reconnect those new files to the old clips, which does not feel like a wise decision, but seems to work. Anyone have this happen before? Is there a way to fix this? I'd love to hear that it's some setting that I am unaware of, particularly since it's so consistent. This is the first project I've worked on using files from this camera.
Download and try the free version of 5DtoRGB lite from the App store and convert to ProResHQ. See if this fixes the TC issue. If it does, look at the paid version of the App. It allows batch. I am just an end user of the product-- no financial connection to the company. I never use L&T. I find 5DtoRGB less problematic, faster as it is multi-core aware, and gives better looking results.