-
Is anyone rendering 23.976 footage transcoded or rewrapped with FCPX out of Color? Xto7 7toX
-
[Oliver Peters] “Right now all the PAL folks are rolling on the floor laughing at us ;-)”
No doubt!
[Oliver Peters] “I have also imported 23.98 files (from other exports) into FCP X and X sees them as needing rendering, while FCP 7 does not. No clue why, but I have more faith in Color and FCP 7 than I do in X.”
If you do an 7toX transfer of your (from Color) timeline, everything will show up as 23.98 in FCPX, timeline, compound, clip, etc.
But, if you import those clips to FCPX without an XML, they do show up as 24.0
There’s something wrong in Whoville.
-
[Jeremy Garchow] “But, if you import those clips to FCPX without an XML, they do show up as 24.0”
Yes. I just noticed, that Smoke sees the 24.0 file as in fact 24.0, because it throws up a mismatched frame rate warning. I presume in the Color-to-FCP7 return roundtrip it conforms the file based on the project frame rate of 23.98. The file itself is 24.0. But so far I have only hit that when I ingested (rewrapped) through FCP X and Sent to Color.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “But so far I have only hit that when I ingested (rewrapped) through FCP X and Sent to Color.”
Actually, I just now also directly imported the rewrapped C300 file into Color. This was straight from the Final Cut Events – Event – Original Media folder. This is only an ingest into X, which rewrapped the file as MOV. No other processes. Color ID’ed the file as 24.0 fps. That points back to the FCP X ingest process or the codec or a flaw in AV Foundation.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Yes. I just noticed, that Smoke sees the 24.0 file as in fact 24.0”
EDIT: My bad. I had the wrong file in Smoke. So far only Color is seeing the rewrapped FCP X file as 24.0.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “EDIT: My bad. I had the wrong file in Smoke. So far only Color is seeing the rewrapped FCP X file as 24.0.”
Yep.
Color is busted.
-
[Jeremy Garchow] “Color is busted.”
Sorry, that’s way too simplistic of an answer. Note the info below. Same C300 file imported into FCP X and FCP 7. Then those two QTs brought into Premiere. You’ll see two interesting issues. The start TC is wrong in the FCP X clip, although it’s right in FCP X. Also the expression of the video integer is different in the two. I believe that’s the core problem in both issues (Color and TC error).
Now, it’s quite possible that both are absolutely correct and it’s a change in how this info is written into QT files. In that case, Color might simply be wrong, because it hasn’t been updated to read a different variant of this expression. The FCP X reading is actually more accurate because it takes the decimals out farther. The FCP 7 version is rounded off to 23.976.
Imported into FCP X. Rewrapped to MOV. Note: start TC in Premiere is incorrect, but correct in FCP X.
QuickTime Details:
Movie contains 1 video track(s), 1 audio track(s) and 1 timecode track(s).Video:
There are 1068 frames with a duration of 1001/24000ths.Video track 1:
Duration is 0:00:44:13
Average frame rate is 23.98 fpsImported into FCP 7 via Log & Transfer. Rewrapped to MOV. Note: start TC in Premiere is correct.
QuickTime Details:
Movie contains 1 video track(s), 2 audio track(s) and 1 timecode track(s).Video:
There are 1068 frames with a duration of 125/2997ths.Video track 1:
Duration is 0:00:44:13
Average frame rate is 23.98 fps– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Sorry, that’s way too simplistic of an answer. “
Color not working with FCPX media is about is simple as it needs to be for me.
I don’t expect a fix.
David, on the other hand, shouldn’t have the same issues, yet he does, and from two different devices and it doesn’t involve FCPX at all.
Therefore, not using Color will solve all of these issues. 🙂
I am sure this has to do with 32bit QT vs 64 bit AVFoundation when it comes down to it.
Jeremy
-
[Jeremy Garchow] “David, on the other hand, shouldn’t have the same issues, yet he does, and from two different devices and it doesn’t involve FCPX at all.”
Because AE rendered files have the same math issues.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver]Right now all the PAL folks are rolling on the floor laughing at us 😉
Yes we do. 🙂The problem seems to be the TC (QT32,QT64 or AV foundation stuff)
FCPX doesn’t like TC and doesn’t handle it neither correctly nor flexible (like FCP mostly did using QT). Next problem is relinking — FCPX is very picky with that.Jeremy did send me some files.
The XMLs are okay.
The source is somehow correctly flagged as 23.976, but a bit different from the way it was done in the old QT days.
That might be the reason why Color does interpret/write the wrong TC track.Using Cinema Tools as test app, you can’t conform FCPX ingested files, while you can do that with files from Color or AE or whatever.
– Andreas
Spherico
https://www.spherico.com/filmtools“He who fights with monsters should be careful lest he thereby
become a monster. And if thou gaze long into an abyss, the abyss will
also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil -
[Andreas Kiel] “The problem seems to be the TC (QT32,QT64 or AV foundation stuff)
FCPX doesn’t like TC and doesn’t handle it neither correctly nor flexible (like FCP mostly did using QT). Next problem is relinking — FCPX is very picky with that.”I was thinking the same. Thanks.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up