-
FCP X Reels
-
[Oliver Peters] “The operative word is “standard”. Nothing about QuickTime is an actual standard. As odd as it may sound, moving this over to specific metadata fields is actually an effort to become standardized, if still not an actual “standard”.”
While it might cause confusion at first, I think that moving the NLE to camera metadata is a good thing.
THis means that any NLE, if they use each manufacturers suggestions, should have portable metadata with the footage.
If Resolve, FCPX, Pr, Avid, whatever, all use “ARRI Reel Name” for Alexa footage, then the metadata will travel to any system.
I know it’s more complicated to code at first, but it will at least offer some parity.
-
I should add, all Red metadata is completely fine.
Jeremy
-
[Shane Ross] “- Tape capture from non-firewire? Use the capture card software for that. Same for output to tape…third party”
Personally I think they’d have been nuts to devote resources to tape at this point. I know it’s still pretty widely used, but it’s on the way out. There will almost certainly never be another new professional video tape format. The future of SR, for instance, is solid state.
[Shane Ross] “- Import/export of standard XML? Third party”
FCP X’s XML format is no less of a ‘standard’ than FCP 7’s, it’s just newer and consequently not as widely supported. (Although really support is pretty widespread now.)
[Shane Ross] “- A NEW feature they tout in the 10.0.6 update…the ability to work with MXF files native! YES…via third party.”
I actually prefer the model of building in flexibility (which FCP X clearly has — it can natively work with media in non-MOV containers, which ‘classic’ FCP never could) and then leaving this sort of thing up to plug-ins. That way you’re not waiting on the NLE vendor when things change. Maybe this doesn’t matter that much with MXF, but it’s quite important with support for native camera formats that are sometimes updated (i.e. Red).
[Shane Ross] “- And now reading of reel numbers embedded in the metadata? Third party.”
This isn’t really ‘third party’ — FCP X doesn’t require a plug-in to read the Alexa-specific field in question. I’m not even sure there’s anything meaningfully ‘professional’ or ‘unprofessional’ about this decision. It’s just a bit odd that they’d require Arri to add this field when the relevant metadata was already present in a standard field, and that they’d adopt an approach that seems to leave no mechanism for attaching reels to arbitrary MOV files. There must be some logic behind this (it’s not like doing things this way is easier for them or anything) and I’m curious what it is.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Shane Ross] “Normally I would agree. But when they came out with FCX they flat out ignored most of the major needs of the higher end professionals, and relied on third parties to provide those solutions. “
Boo hoo.
Third party support isn’t a bad thing unless you want it to be.
You rely on plugins to enhance/supplement your NLE and edits, then third party workflow tools enhance your NLE and workflow.
Some people use them, some people don’t.
You buy what you need.
It makes perfect sense to me, although I used third party MXF and Alexa tools in FCP Legend, so I’m Ok with it.
I also think that this makes camera manufacturers pay attention and see how their footage and data will be used through the post process, in turn, making their products better.
Third parties make everything better in my opinion, as they work with the internal structures on a level that us users do not. Third parties usually have a more direct line to the major developers than general users do, therefore third parties can actually request features that make bigger differences in users day to day workflow.
Plus, if something is “broken” and you need to get actual support for a workflow enhancer, you can call and email people for a fix instead of waiting desperately for any major NLE patch. There’s an advantage to working with smaller companies for this type of support.
It’s a win win in my book. With 10.0.6, FCPXML has received some huge updates, and I expect will be seeing some major workflow enhancement fairly soon.
Jeremy
-
[Jeremy Garchow] “Boo hoo.”
Whatever. I’ve moved on. Just more of the “this used to do this stuff, now we no longer think you need it” things.
Like tape. Still using it…will be for a few more years. why not keep supporting it as long as the infrastructure does?
But…whatever. I don’t use FCX, no plans to. Dunno why I keep hanging out here.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Shane Ross] “Whatever. I’ve moved on. Just more of the “this used to do this stuff, now we no longer think you need it” things. “
I could talk about this for a long time.
Ultimately, I think the FCPX model has potential to be better, even if it is more confusing up front.
For instance, let’s look at AMA.
If AMA is “broken” or you want more capability, who do you have to wait for and for how long to get those fixes?
If an MXF workflow enhancer for FCPX is “broken” who do you have to wait for and for how long?
With tape capture, you will now rely on third party vendors. Every capture card manufacturer has their own capture software. Now with FCPXML v1.2, it seems there are more hooks than ever to be able to send data back and forth in and out of FCPX.
So, if I own an AJA card, and if they ever release their Control Room software, won’t I be able to add this capability right back in to my workflow?
Let’s say I am a user that doesn’t use tape, I am now expected to let Apple develop a robust tape capture system when I’d rather they fix and enhance other parts of the NLE?
Parting out certain workflows to third parties is NOT a bad thing in my book, but again, I am used to it and have been doing this type of workflow for years in FCP Legend. It doesn’t bother me one bit.
Jeremy
-
[Shane Ross] “Like tape. Still using it…will be for a few more years. why not keep supporting it as long as the infrastructure does? “
One more thing, let’s put it in to plug in terms.
Let’s say I do a ton of green screen, and the tools of my particular NLE are no good.
Do I get mad at my NLE company because their internal keyer sucks, or do I turn to a third party to help enhance that capability with my current NLE?
Same thing for interchange workflows.
Not everyone needs a keyer, not everyone needs native MXF support, not everyone needs EDL/OMF/AAF.
If you do, you go purchase that capability.
-
[Jeremy Garchow] “If Resolve, FCPX, Pr, Avid, whatever, all use “ARRI Reel Name” for Alexa footage, then the metadata will travel to any system.
I know it’s more complicated to code at first, but it will at least offer some parity.”
Third party software already could (and did) read the standard QuickTime metadata field, though, so this isn’t really an explanation for why Apple decided to go this way.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Jeremy Garchow] “The rental house we use is always up to date. The XML says the Sup is 6.0 when this footage was shot. It was an Alexa Plus, I don’t know if that has any bearing on the situation.”
Note sure why. My example was also a Plus. Could be that the your files weren’t a direct copy. Maybe handled through some on-set software or Resolve to add a LUT.
[Jeremy Garchow] “When you open the import window, do you have the choice of sorting by list view or filmstrip view? Or is it just list view?”
I see a list, a filmstrip and a viewer. The Import module functions differ depending on if it’s a file on a hard drive, a camera card or a mounted volume (disc image from card) or a camera archive. If it thinks it’s from a camera device/volume, you can import range selections – like FCP7 L&T – except multiple ranged. If it’s from a hard drive, you have to import the whole clip.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Jeremy Garchow] “Let’s say I do a ton of green screen, and the tools of my particular NLE are no good.”
Green Screen isn’t part of the main realm of the NLE. Editing is. And apps that ignore the basics of editing…reel numbers…capturing from a still industry standard format (even though it is fading, there is no argument there)…exporting files to other aspects of post production (audio, color grading machine). Those were all features of FCP. Gone in FCX.
But, I do know that that isn’t the market for the new FCX. We aren’t the market…so why do I keep hoping they will support our needs? Apple is aiming at a broader, more profitable market. I can’t blame them. So I see where they are going. It isn’t where I am.
Shane
Little Frog Post
Read my blog, Little Frog in High Def
Reply to this Discussion! Login or Sign Up