John Heagy
Forum Replies Created
-
Further testing reveals that Premiere Pro has the same issue with the same files. QT Player, FCP7 or FCPX all read the TC fine.
I’ll contact Squarebox support to try and resolve the issue.
Thanks
John -
The Key is com.apple.proapps.reel
-
There’s a FCPX Reel? So once the app copies the Arri Reel to the FCPX reel in the .mov, FCPX reads this on import and populates the standard “Reel” field in FCPX?
This means there is an extended QT metadata Key that FCPX maps to the standard Reel field. Certainly news to me.
John
-
[Kevin Reiner] “So should I just start with a 30p sequence and edit the 24 footage into it?”
No, edit in 24p and then add 3:2 to the finished 24p master. This is the only way to create an unbroken 3:2 cadence across edits.
[Kevin Reiner] “My videographer insists on shooting 24p even though I argue for 30p to make my life easier. (filmic shmilmic)
“The “Cult of 24” is strong.
Hoping the 48fps Hobbit is able to deprogram those who suffer from it.
John
-
30p to 24p is really worse case as far as frame rate conversion goes. You will be dropping significant chunks of time and it will appear “jumpy”. Underwater footage may lend itself to optical flow frame creation which is enabled by the highest quality frame rate setting in Compressor.
If you can doing a conform from 30 to 24 will be cleanest but will slow the footage.
The reason you need 24p is all the other footage is 24p?
John
-
Is it possible you captured them as .dv and not .mov?
-
Just yesterday we had an iMac attached to our San via a Promise SanLink that suffered chronic kernel panics. After eliminating the San Link as a cause, it’s looking like the Thunderbolt cable was the culprit. Not too surprising considering it’s got a chip in the connector.
John
-
We are using SAN Link to mount Xsan volumes on 4 iMacs. No issues to report and never had to unplug them.
-
[Bret Williams] “A reference movie has one gotcha. Everything it references has to be the same codec, same frame rate.”
That is not true. A QT ref can contain mixed codecs and frame rates. It’s FCP7 that will not accept or produce such a ref .mov.
[Bret Williams] “In FCP X it all mixes as long as its the same frame rate, without any render required”
That’s only a temporary condition in FCPX. If you want to export anything FCPX will render to a single codec. Would you want an export containing mixed codecs and frame sizes? The point of any export, including ref.mov, is to represent the finished timeline not the project file.
John
-
[Craig Seeman] “I think Apple will take a different route depending on the progress with the use of the underlying database and FCPX media. I don’t think it’s as simple as you think only because you’re implying a direction Apple probably doesn’t want to take.”
Yes, quite possibly. I’m just expressing the feature I want, and the easiest way to get there knowing what I know today. Heaven forbid Apple keep/update something as old as QT ref if there’s a new more involved way that currently no third party apps support.
Setting aside how/if Apple would replicate ref .mov in another form… how many would want the ability to send a tiny file that represents the finished timeline to third party apps (not just other Apple apps) the way ref movie does today? This has to be the finished timeline including renders, not like xml today.
John