[Charlie Austin]

[Jeff Markgraf] “like to come up and pontificate on how unsuitable X is for professional work. Not that they’ve used it. They just know.”

This is exactly the attitude I’m encountering… The way I see it is:

If someone learns X, really learns it, and just doesn’t like it… fine
If someone has a workflow requirement X isn’t suited for… fine
If someone messes with X, doesn’t bother to learn how it really works, and then proclaims it unsuitable and backs their opinion up with anecdotal opinions from other people who don’t use it… I get all pissy. 😉

In my very specific case, X could conceivably give us an edge on our competition. We could make changes faster with the client looking over our shoulders, the GFX guy wouldn’t have to waste time constantly making revisions to titles and other temp GFX stuff, lots of little things like that add up. Many things that are of course do-able in other NLE’s, but they really do take longer and/or look worse.

But no… nobody uses X, the end. :-/

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Jeff Markgraf] “I mean, Charlie is entertaining and all, but no one quite has your way with words.”

Hey! 🙂 I’m an Amurican, I can’t compete with A’s mastery of the mother tongue. lol

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Jeff Markgraf] “It’s unfortunate that so much discussion of X is overlaid with the need to defend it against the “it’s not professional” meme. What a waste of time. So much more interesting to focus on HOW X can be integrated into a professional workflow”

+1 or something.. 🙂

[Jeff Markgraf] ” Interchange of media and sequences between NLEs is a manufacturer-created and curated nightmare. “

Yeah, can we got this sorted out please? MC is kind of an island unto itself… EDL?!?! Pr can send a nice sequence to FCP 7, but bringing things into Pr using old fcp 7 XML is an audio mess. Using IA’s tools, going from X to 7 or 7 to X works really well, but X to Pr still uses the fcp 7 xml, so we’re back to messy. Be nice if there was a standard. hahahahahah 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] “You know you are still using inertia in a negative way right? 😉 Associating it with people clinging to something. There are certainly people like that, but there are also places where the investment in time, resources and money was so heavy in the old FCP”

Point taken, I guess I was editorializing. 🙂 “Still using” would have been more balanced… lol And I am talking about people like that, I get that there are situations like you point out..

[Andrew Kimery] “How do you bridge the gap between the thousands of FCP 7 projects sitting in archive and the new projects? Many times I would pull an old FCP project from the archive and repurpose those assets in a new project.”

Honestly, that’s really not a big deal any more. Old FCP projects run through 7 to X open up just fine. In way it’s less of a headache going from 7 to Pr due to the dual mono vs’ interleaved audio thing. But point taken..

[Andrew Kimery] “Find a seasoned editor in LA that knows PPro or X? Eh… not so easy. That’s inertia.”

True, but seasoned editors can easily learn either of those NLE’s if they choose to. And if I were a seasoned editor I would certainly think that doing so would be good thing. Oh… wait.. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “his response was that X “keeps you in the zone” when you are editing. I completely agree with that and see it myself when using X. I’m not sure that’s exactly the same thing as meaning that you can stay in X to do mixing or color correction, but you can’t in other NLEs. “

I concur, with both Jan’s statement and your last sentence. As to the first, I’ve been working in Both X and Pr side by side lately. Literally CMD TAB-ing between the two cutting different spots for the same movie. It’s subjective, but there is a huge difference in “feel”. And while you can of course accomplish the same tasks in both, for me, X just gets you as good or better results (effects, audio adjustments and other clip manipulation, not “editing”) faster, with way less fiddling around. Not to say the opposite isn’t sometimes true… it is. But in general, for what I do, my focus (see what I did there?) remains on the cut more in X than in Pr. (or 7 for that matter). I think that’s where some of the intangible “faster in X” mindset comes from…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Aindreas Gallagher] “it’s maybe best to nest”

Don’t you mean use a Compound Clip? :-p

But you’re right, in some cases that’s a better fit. I’m talking about a very basic use though… Our sources are all cut features or dailies with burn in’s in the cropped area. If you resize or reposition clips you want the crop to be consistent over the whole cut, including masking out the burn in shots that haven’t been transformed. Adjustment layer is the way to go.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Aindreas Gallagher] “As long as proponents don’t come out with ridiculous language like the stuff that was in the article we’re all good.”

Well, sure. But all proponents of anything sometimes come out with ridiculous language. Marketing baby! 🙂

[Aindreas Gallagher] “it’s right on the tip of my tongue. ah yes.

“I feel like I’m describing how the microwave works to my Grandpa.””

Oh, I remember it well. 😉 Thing is, I feel that way when trying to explain to people why they should at least move from 7 to Pr FFS, let alone X. When, for example, people think it’s better to crop every single clip in a cut, rather than use an adjustment layer, It kind of boggles my mind… Hell I’ve had an “adjustment layer” crop (.png with an alpha cutout) in FCP Old for years. They still won’t use it. It’s not what they’re used to.

Inertia. Fear. 🙂

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Aindreas Gallagher] “[Jeff Markgraf] “Now they use Premiere out of a combination of fear and inertia”

This is the weird self aggrandising myth making of the X user. If you reverse that sentence the FCPX adoptee is thrusting, forward moving with courage and insight.
“

I think you (and Tim) might be misinterpreting Jeff’s meaning when he uses the word “inertia”. I don’t interpret it in the the way you do at all. Here’s an example of inertia. People clinging to FCP 7, resisting learning Premiere, X, or anything. I live in this world.

Veering off topic but… For the love of Jeebus, let it go. It’s dead. You don’t have to use FCP X, but start using MC or Pr or fracking anything.

Especially because I can run these other NLE’s at he same time as FCP X. This makes my life a lot easier. 🙂

[Aindreas Gallagher] “It’s really funny is all. Funny and a little, little bit sad. And really ripe for a p*ss take”

And… there it is. Classic. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Tim Wilson] “Saddle up, son. LOL The longer and angrier the better. LOL
“

Well played sir, well played… 🙂

[Tim Wilson] “This has been my issue with the whole concept of Luddites, Dinosaurs, “stuck in the old ways,” or, worst of all “just doesn’t get it.” It fails to take into account the absence of EXTERNAL FORCES compelling change, or the absence of INTERNAL FORCES compelling change, not always, but sometimes purely for its own sake. “

Despite my occasional outbursts, I totally agree with you here. As you and Jeff point out, there most certainly are valid reasons not to use X, or any bit of software. Glens’ “don’t like it, don’t use it” comment is dead on. One – problem in my little world – is that even when presented with real, objective evidence that FCP X is in many ways a better choice given our workflow, people refuse to even consider it due to some weird herd mentality. Additionally, many people who don’t like X feel compelled to try to tell the people that do like it how foolish they are. To be fair, the compulsion to deride peoples choices comes from the X side as well. Mac vs. PC, iOS vs. Android etc. etc. My bone(s) of contention has always been with people that:

-Don’t use X because other people don’t use X
-Haven’t cut more than 1 or 2 simple things in X and are suddenly experts in all the things you can’t do, particularly when they are things you *can* do, just differently.
-Love to crap on any positive reviews, news etc about FCP X for no apperent reason.

Conversely, it drives me nuts when people who use X, but have very little experience in other NLE’s are suddenly experts in all the the shortcomings of the NLE’s they don’t use. Examples of all these things are contained in this thread. 🙂

IMO, the most valuable, honest opinions come from people who have actual working experience in all the NLE’s we blabber about. If you don’t use X, or Pr, or MC, what on earth makes you think you are qualified to tell anyone anything about X or Pr or MC? If you poke around here at the cow and elsewhere, the most reasonable posts come from people who fit that bill.

Well, except for me, I meet the qualifications, but I just like to hear myself talk. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Glenn Ficarra] “If you don’t like it, don’t use it.”

lol Welcome to the thunderdome Glen. 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~