-
Canon 5d EOS plugin is incorrectly naming ‘clip time’ attribute to one hour ahead
We finished a project and as part of our arrangement sent them all our media and project files, we didn’t send them the transcodes however because they were so large. They have our raw h264 media from the canon 5d mkII camera. We sent them a guide on how to transcode the footage so that it was exactly the same as ours and most importantly used exactly the same naming structure.
They just emailed us to say that the guide almost worked perfectly but that the log and transfer process naming convention that we sent him which included the ‘clip time’ attribute is transcoding the files so that their names include a time of day that is consistently one hour ahead of our version of the clips. If it makes any difference, they’re in America and we’re in the UK, but it shouldn’t make any difference since the time of day that the recording was done should be embedded in to the rushes and the time of day and location at transcoding should have no bearing.
Anyone know what would produce this kind of an error?
-
2 Replies
-
This was reported here just in the last week or two. Change the clock time in the computer to turn off daylight saving in the Mac.
https://forums.creativecow.net/readpost/8/1147044
-
To anyone who stumbles on this thread. It WAS daylight savings and Michael Gissing was right as was the poster of the similar thread that I’d not seen.
Set the clock back to before the last DST change and transcodes are named correctly.
Quite annoying that this is the solution because it was the first thing that occurred to me but I decided it couldn’t be it since the timecode would be an absolute value since the media’s already recorded and so why would the metadata change depending upon the conditions at the time of transcoding? Anyway, just goes to show you can’t always expect the answers to computer problems to be logical.
Reply to this Discussion! Login or Sign Up