John Heagy
Forum Replies Created
-
[Chris Kenny] “Apple shouldn’t deliberately ignore that when it’s present merely because it might not always be present or because other container formats might not support it.
And, indeed, this seems to be what Apple is doing… with everything except reel names from QT files, for some reason. I”
Agreed! There’s never an excuse for not reading metadata, particularly one this easy for Apple to read.
If Apple has a problem mapping it to Reel, then don’t. Call it what is: tcsource and populate a tcsource metadata field in FCPX.
John
-
How did a Reel conversation get this long without me chiming in? That’s what I get for taking a few days off.
Interesting that FCPX sees what is apparently an Arri custom QT metadata key. CatDV is excellent at exposing these. I will have a look on Monday.
As far as the theory that Apple is treating each camera file’s Reel data separately, that’s all fine. All metadata should be read and the correct field populated. So what’s Apple’s excuse for ignoring QT tcsource aka: Reel, Tape Name, Tape ID and Source in QT files?
Why doesn’t Apple read tcsource and include a tcsource metadata field to populate?
That would work fine for me “A rose by any other name…”Anybody care to argue for not reading a file’s metadata?
Bottom line: If there’s metadata, and it can be read… READ IT!
John
-
[Oliver Peters] “As I said in another thread, I believe Apple has deferred this to the camera manufacturers via the camera import SDK. RED requires the RED importer plug-in and I believe that’s what takes care of adding the reel info. “
This is Apple’s file format with Apple’s metadata. No SDK required. I could care less what the camera puts in as reel in the field. We add reel as part of our post workflow. There’s little chance of prepping camera’s metadata ahead of time. Our cinematographers have too much to do, they can’t be expected to type in metadata. The only way of adding consistent metadata is after the fact by a small group of people. Reel for us is more GUID and it never comes straight from the camera. We assign reel to masters and element files not just camera files not to mention files captured from tape… yes tape… imagine that.
Reel is supported by Apple’s new AVFoundation API. Why support it in the creation of QT files and not read it!
Nothing could be simpler for Apple to do. They simply refuse to do because it’s “Old fashioned” in their minds.
Below is from the FCPX new features list. Ironic it mentions Reel soley yet Apple won’t read it in their own files. Where supposed to type it in manually!!
XML 1.2 with Metadata Import and Export
Enjoy richer integration when moving projects and media between applications. XML 1.2 includes new standard metadata fields such as Reel. And Final Cut Pro X XML now includes custom project and media metadata, so you can import from — and export to — third-party apps and media asset management systems.John
-
[Oliver Peters] “And BTW – embedded Reel numbers are read.”
Oops. Still not those embedded in QT files, like Alexa media.”
You have got to be kidding me! Apple’s reads Reel in Red R3D but they couldn’t be bothered to read it in their own GD file!
That’s just rubbing salt in the wound!
John
-
[Steve Connor] “Also the new Media Import window is VERY useful”
Steve, do you have QT file with an embedded Reel ID? If so can you tell me if FCPX 10.0.6 now populates the Reel field? Any file captured with FCP7 will do assuming Reel was entered prior to capture. Alexa files will do as well.
Fingers crossed…
John
-
I guess that’s No and No…
-
[Bill Davis] “But those with traditional workflows are arguing that EVERYONE needs reels such that software is somehow “crippled” if that field isn’t baked into the workflow…”
Nobody insisted EVERYONE use reel in their workflow. Just think of reel the same as you do all the other metadata fields in FCPX you don’t enter data in.
It’s clear reel is used to facilitate interchange and custom workflows. One man “bands” that don’t interchange with other processes or devise custom workflows have little need for reel. That’s all fine, nobody’s forcing you to use it.
Please don’t insist it’s useless because you don’t use it or understand how others do.
Apple clearly targeted FCPX, at least initially, to the one man bands and pajama editors of the world. I for one hope Apple wants to have FCPX used in high end professional “facilities” where “out of the box” workflows and hand holding just don’t cut it. Responding to the needs of pros who use time tested workflows will help FCPX make in roads into “pro facilities”.
John
-
[Jeremy Garchow] “I don’t understand it either”
Reading “Reel” in QT is really my “Canary in the coal mine” test for Apple that will tell me Apple has listened and responded by adding a seemingly super obvious and simple to implement ability that pros require.
Fingers crossed the Canary survives.
[Jeremy Garchow] “Or AVFoundation isn’t ready.”
Thankfully AVFoundation can create QT files with embedded “Reel” or as it’s called in the QT API “tcsource”. This opens up the ability to export movies with a user defined “Reel”, which I also requested. If Apple and people like Bill, are hung up on the original physical container Reel has traditionally meant, then refer to it as tcsource if that will help shake it’s legacy baggage.
[Jeremy Garchow] “I don’t understand it either. Even when using 7toX, “reel” is now put in the “notes” column.”
Unbelievably “Notes” is the only metadata field that is exported in a FCPX xml.
Apple may be concerned about “flooding” an xml export with all the metadata available in FCPX. Our recommendation to Apple was to include an option that only exports metadata in a specific Metadata view. Users could create custom metadata views and add metadata fields they what, much like columns, and then select that group to be exported in the xml.
John
-
[Jeremy Garchow] “This means that as long as an NLE understands P2 metadata (and Panasonic has recommendations on how to do this) it will travel with the clips anywhere they go.”
Yes, there needs to be an ID that travels with the file and identifies content whether it’s per clip or per group with unique TC.
So you only work with P2 files? If not, how do assign a Global ID to non P2 media? Does Adobe Media Encoder transcode to a P2 CONTENTS folder?
John
-
[Bill Davis] “And a Canon 5d does NOT mark a card as a REEL.”
Now’s it making sense… How can someone appreciate Reel if they don’t need TC from their camera.