Jason Honeycutt
Well-known member
I've been doing some trial and error with an Avid to RCX test "online" to see if I can get my Avid sequence into RCX then use the source clips' 'one light' base color (since Avid refuses to see it until I export the RMD and apply it to each and every film, which wouldn't work since I have 600-some shots with varying looks). I exported a CMX edl and there was drift after I exported that. I thought the output from Avid was making it 24fps but then I test the same edl in DaVinci Resolve and it locked perfectly to the frames. I also tested an AAF (even easier) in DaVinci and that was perfect... I wish RCX could import that.
Anyway, so yeah, same EDL, different results... here's what it's doing in RCX. The "in" points are perfect but on the outs, there's an extra frame or two, not duplicated, but new... then the incoming next shot is accurate at the heads, but not at the tails. I thought it was maybe something to do with the export settings. I made sure on the DNX output, the AAF/MXF output and QT/DNxHD36... all had 23.98 set but they all still have this 'drift' happen... again, when DaVinci didn't. Someone else had this problem and they said they got it to work using ProRes, which is my last variable I haven't tried.
It seems like the sequence itself is somehow forcing itself to be 24fps or something. I don't know. Anyone have any ideas? Basically... is there a path to check/change a sequence's timecode from 24 to 23.98?
(Sorry for so many questions on this board lately.... so close to having this do what I'm looking for it to do.)
Anyway, so yeah, same EDL, different results... here's what it's doing in RCX. The "in" points are perfect but on the outs, there's an extra frame or two, not duplicated, but new... then the incoming next shot is accurate at the heads, but not at the tails. I thought it was maybe something to do with the export settings. I made sure on the DNX output, the AAF/MXF output and QT/DNxHD36... all had 23.98 set but they all still have this 'drift' happen... again, when DaVinci didn't. Someone else had this problem and they said they got it to work using ProRes, which is my last variable I haven't tried.
It seems like the sequence itself is somehow forcing itself to be 24fps or something. I don't know. Anyone have any ideas? Basically... is there a path to check/change a sequence's timecode from 24 to 23.98?
(Sorry for so many questions on this board lately.... so close to having this do what I'm looking for it to do.)