-
When source media crosses midnight
Came upon this issue on recent project.
When checking the session in the conform tab I noticed that there was an issue with one of the shots. I checked the offline edit in FCP and made sure that the correct media file was loaded in the media pool but still it didn’t link. After some investigating, I noticed that the “problem” media crossed the midnight point going from 23:59:59:23 to 00:00:00:00, however the EDL and thus Resolve were looking for media with TC starting 24:00:00:00.
I fixed the problem by manually cutting in the correct shot, but I was wondering if anyone else has experienced this problem and if there are any better solutions.
Thanks,
Roman -
12 Replies
-
In general I think it is best to avoid the 24:00:00:00 timecode issue by setting timecode at 1:00:00:00 for each reel. That way each named reel has a TC reference and you will never have the TC rollover issue. For example I have a feature right now with 97 flats of film even with fractional timecode (i.e. 30min TC breaks) there is no way to make a 24hr timecode work. Each film flat is punched at the first A frame and given a 1:00:00:00 TC and the edl works fine.
-Rob-
Robert Houllahan
Director / Colorist
Cinelab Inc.
http://www.cinelab.comMAHC-PRO 6-Core 3X GTX285 20Tb SAS Wave Panel Panny 11UK SDI Plasma.
-
I hear you but you don’t always have control over the timecode of the media you’re getting. It’s a common practice to shoot with time-of-day TC or to start each shoot day’s TC with a different hour (ie. day one is 01:00:00:00, day two is 02:00:00:00).
The question is when it happens, what do you do?
Roman -
Yeah I know should have added to that… I suppose separate the media by reel names.. Charge extra for fixing a F’ed up EDL? is the project from Final Cut or Avid? get the editor to give you a working EDL like they should have in the first place… I know none of this is helpful… V8.0 has better editorial tools… Change the TC in the quicktime so it works, edit it QuickTime Pro(V7) player for .mov or fix it in MC for Avid…
-Rob-
Robert Houllahan
Director / Colorist
Cinelab Inc.
http://www.cinelab.comMAHC-PRO 6-Core 3X GTX285 20Tb SAS Wave Panel Panny 11UK SDI Plasma.
-
The project I experienced it on was an FCP project. I don’t know what AVID would have done on EDL export. The weird thing is that this is an issue with EDL creation, not FCP nor Resolve. Why doesn’t the EDL record that the TC switches to 00 hour?
Good thing is that these situations don’t happen too often so it’s not a big deal to manually deal with.
Roman -
I think EDL export from Final Cut is much less robust than from Avid…
-Rob-
Robert Houllahan
Director / Colorist
Cinelab Inc.
http://www.cinelab.comMAHC-PRO 6-Core 3X GTX285 20Tb SAS Wave Panel Panny 11UK SDI Plasma.
-
I spend most of my time on a DS, and am having the same problem with items shot by an outside company. Offlined in Avid MC, but online in DS. Have to manually capture the shot.
When we have control, and know a multicam shoot is taking place in the evening, we routinely ask the crew to take a 10 min break around midnight.
Glenn
-
[Robert Houllahan] “I think EDL export from Final Cut is much less robust than from Avid…”
This isn’t a problem with the EDL, though, as far as I can tell. The EDL in these instances is accurate. This is, as far as I can tell, a Resolve bug. The algorithm it uses for checking whether a given timecode range is contained within another timecode range doesn’t seem to understand clips that cross the midnight barrier. So if it’s looking for media from reel A001 starting at 00:00:01:00 and going through 00:00:10:00, it doesn’t understand that it if there’s a reel A001 clip that runs from 23:59:58:00 to 00:01:10:00 it should look for it there.
It’s easy to see why. In all other cases, if you’re looking for a clip that encompasses a given timecode range, that clip’s start timecode will be less than the start timecode of the range, and its end timecode will be greater. In this case, the former isn’t true, and the code wasn’t written with that edge case in mind.
(Vaguely-related rant: I don’t understand why the industry hasn’t added day, month, year, and camera identifiers to TC/reel information by now, to give every frame ever captured by every camera a globally unique code. That would solve a lot of annoying post problems.)
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read Does FCP X make project files obsolete? on our blog.
-
Happened twice, fixed manually. Never happens when conformed with edgecode.
-
Yeah, ran into this problem as well. Its definitely a bug in Davinci. I’ve seen it on R3D files pulled through an EDL. Going through an AAF or XML in the future (v8) will probably solve that problem as the clips will have UUID’s to link from instead. Of course I logged this with them months ago, so I wouldn’t be surprised if the core issue has already been solved in v8.
-
Just had to deal with this last week for the first time. Funny, if I hadn’t seen this thread I wouldn’t have IDed the problem this quickly. Thanks y’all!
It’s funny, when people ask me how long the conform will take on their project I now reply “well it depends on whether we start after DaVinci 8 is out or not.” I hope it’s not delayed!
Reply to this Discussion! Login or Sign Up