-
FCP-X and misrepresentation
-
Evan,
One of the main topics of discussion on this Debate forum is the growth and viability of FCPX in major facilities handling high end productions – features, broadcast, commercials. Examples of such use are still relatively rare and when examples are produced they are big news here, in this little pasture of the Cow. Radical Media is one of the main examples of this high end acceptance because of the very public statements you have made about it and because you are featured prominently in Apple’s marketing of X.
The fact that Radical Media has not been using FCPX for over a year is therefore big news in this environment. It is a surprise, to say the least. The fact that you so publicly chose to champion your use of FCPX and then so privately decided it was really not ready for use in your facility is a reasonable subject for conversation. The fact that this conversation is public and not private was dictated by your choices.
[Evan Schechtman] “In the future if you have a question you can email me or call me like many strangers who read the article or who saw me speak do. I do not seek publicity- I do not sell products or even consumer services- I have no way to benefit by pulling the wool over anyones eyes.”
How can you say you do not seek publicity – did Apple hold a gun to your head? Did the guys at Tekserve drag you to their store by force? What you obviously don’t seek is bad publicity – but sorry to tell you that is part of the price for all the good Pub you’ve gotten from that Apple article. I realize you make nothing for your demo’s, that they are in effect a public service, and I know that Apple doesn’t pay you a penny for your testimonials, but that does not mean you do not benefit by them. You do, anybody in your position does.
I believe that you are honest and sincere with your opinions, I do not believe you set out to deceive anyone with your statements, and I have no reason to doubt that you will be switching your facility over to X in a few months time. But for the past year you have knowingly allowed Apple to mislead people by using your example. It must be embarrassing to be put in that position and for that position to then be made public. But don’t shoot the messenger.
[Evan Schechtman] “You are essentially asking me to publish a retraction of an article that was written, not by me.”
I wasn’t asking you to do anything, but if I were to advise you I would say you have three reasonable choices:
You could ask Apple to pull the article until such time as you have switched back to FCPX.
You could write a piece about why you stopped using X at the time you did, even though you fully intend to switch back. The details of what worked and what didn’t would be very informative and helpful to editors and facilities who are still exploring making these kind of changes.
You can do nothing and go about your business knowing this tiny tempest will blow over before your next cup of coffee.
(Personally I would prefer number two.)
But what is not reasonable is to come on here all hurt and upset that someone actually noticed that what you had been doing did not match what you had, very publicly, been saying.
[Evan Schechtman] “I wrote a response telling the entire story. If that doesn’t satisfy you and get you to drop it, then thats your damage at this point.”
Looking back through the first series of postings I will admit to being more than a bit snarky and for that I apologize. But for the tone, not for the content.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
[Jeremy Garchow] ”
No. Apple doesn’t make nice things anymore, ‘member?!
“touché.
-
What does seem to be telling in this discussion, is that over two years after FCP X was released and four years after FCP 7, no NLE sufficiently checks all the boxes to serve as an adequate replacement for FCP 7 for many shops. And that has nothing to do with preference or resistance to change. Although I edit mainly in X, I find that I consistently need most of the pieces in the FCP 7/FC Studio package.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Although I edit mainly in X, I find that I consistently need most of the pieces in the FCP 7/FC Studio package.”
And is that because you have those pieces and haven’t bought the equivalent pieces on the AppStore, or because FCS3 really “does more” than FCPX and free/paid counterparts?
-
[Jeremy Garchow] “And is that because you have those pieces and haven’t bought the equivalent pieces on the AppStore, or because FCS3 really “does more” than FCPX and free/paid counterparts?”
The latter. I have all the App Store pieces and they are not equivalent. When you play by the FCP X rules and everyone else does, then X (plus the add-ons) is sufficient. But that’s not the real world, because there are a myriad of workflows.
Three simple examples. 1) OMF to a ProTools guy. 2) Relinking non-matching media files after color correction without a new XML. 3) A more detailed authoring job on a DVD. These are three areas where I need FCS.
I also have clients who bring in projects cut on FCP 7 and need to be compatible.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “When you play by the FCP X rules and everyone else does, then X (plus the add-ons) is sufficient. But that’s not the real world, because there are a myriad of workflows.”
But of course. There are a myriad of workflows. Let us count the ways.
[Oliver Peters] “Three simple examples. 1) OMF to a ProTools guy. 2) Relinking non-matching media files after color correction without a new XML. 3) A more detailed authoring job on a DVD. These are three areas where I need FCS.”
1) If the ProTools guys (and one girl!) that I have worked with, I have asked them, “Hey, I know we usually do OMF and that works, but what if I have you an AAF this time?”. So far, 100% success rate.
2) Yep. Relinking without the corresponding FCPXML is a consideration. Advantage goes to anti-FCPX (unless you can convince the people giving you the material to export an FCPXML out of DaVinci, or you use the free Davinci to get the FCPXML you need).
3) True. There is no AppStore replacement for DVD Studio Pro (not an NLE). I think, even Adobe, has life supported Encore/DVD (as well as BluRay):
“Is the Encore CS6 version the final release of this product?
Yes. The trend in the video and broadcast industry is moving away from physical media distribution. The
future is in cloud and streaming content. Therefore we are focusing more on products that deliver to
streaming services. For example, Adobe Media Encoder and Adobe Premiere Pro CC include a new
feature allowing users to create iPad-ready video with QuickTime chapter markers. The Encore CS6
version will be the final release of this product.”So, yeah, if you need to author DVDs, FCPX (an NLE) sucks, but so does nearly everything else on Mac, so it’s a bit of a wash. But, if you DO need to export very simple DVDs, FCPX actually does it, and you can even add chapters.
4) If people still bring things on FCP7, then of course, you are going to need FCP7. That won’t last much longer. If someone brought you a Media100 project you’d still need Media100. Or Avid. Or Combustion. Or whatever. If someone brought you an FCPX project and you didn’t have it, guess what you would need?
5) Sony XAVC (recorded by the fairly popular Sony F5x lines) can’t even work with FCP7 very easily without buying some plugins, and if they are above 1080, you can pretty much forget it. So, are they wrong when someone brings me XAVC footage and I can’t deal with it?
-
[Jeremy Garchow] “…FCP7. That won’t last much longer.”
Ha ha ha ha ha !
But, to be clear, I’m talking about FCS to augment my needs, not its continued, long-term, exclusive use. At least not by me. Right now – on and off – I work in 4 NLEs (7, X, PProCC and MC). There’s also Smoke, but in my market, people have dabbled, but no one has adopted.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “[Jeremy Garchow] “…FCP7. That won’t last much longer.”
Ha ha ha ha ha !”
It won’t.
There will be an archive of old projects that have the potential to be resurrected. I have nearly 98 TBs wrapped up in them (ninety eight terrabytes). Believe me, I understand the implications.
It’s going to be fun.
What I was reacting to you was your quote:
[Oliver Peters] “What does seem to be telling in this discussion, is that over two years after FCP X was released and four years after FCP 7, no NLE sufficiently checks all the boxes to serve as an adequate replacement for FCP 7 for many shops.”
If comparing FCPX and it’s AppStore parts, and FCP7 (not FCS3) to it’s parts, are we really that far off?
-
[Jeremy Garchow] “If comparing FCPX and it’s AppStore parts, and FCP7 (not FCS3) to it’s parts, are we really that far off?”
In my opinion, yes. And I’m not limiting that to X. I include Premiere Pro CC as well in that opinion.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “In my opinion, yes.”
In parts 1,2,3 of your earlier analysis,
1) is outdated
2) is overcome with an updated workflow (isn’t this what Evan and Liz have alluded to in this post, workflow?)
3) Doesn’t apply to FCP7, and actually, FCPX does it better.
Reply to this Discussion! Login or Sign Up