Oh dear, we will switch to fcpx!

[Bret Williams]

let’s add z position as a push, and L/R would of course be “slider” not dolly. Can we get a jib position?

But really, in 20 years I’ve never see anything but XYZ. Suddenly we have tilt and pan.

[Shawn Miller]

[Bret Williams] “let’s add z position as a push, and L/R would of course be “slider” not dolly. Can we get a jib position?

But really, in 20 years I’ve never see anything but XYZ. Suddenly we have tilt and pan.”

I must be old then, in my day, we called L/R movements dolly, truck or crab… you kids and your fancy new sliders. 🙂 I tell you, it all went down hill when filmmakers stared caring about “crop factor”. 😛

Seriously though, I agree with you about the x,y thing… now, if we could just get the 3D folks to agree as well (some are “y up”, some are “z up”). 🙂

Shawn

[Shane Ross]

[Brett Sherman] “Sometimes I wonder if those who can’t handle the FCP X timeline have difficulty learning new things. Or they’re just impatient. It really was no problem for me.”

Some of us have no choice as to the NLE we use. The company has Avids, so we use Avid. Plus the “old way” works, and works well….why change? For change sake? Apple reinvented something that, IMHO, didn’t need to be reinvented. BUT, it turns out many MANY people like this reinvention…so I’m cool with it. I just don’t use it.

I know many people like and swear by FCX…love the way it is laid out. Fine…dandy, it works for them. Glad that they have that option. Others like things done another way…so for that we have alternate choices…Avid, Premiere Pro, Edius. It’s good to have options.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Andrew Kimery]

[Shane Ross] “I know many people like and swear by FCX…love the way it is laid out. Fine…dandy, it works for them. Glad that they have that option. Others like things done another way…so for that we have alternate choices…Avid, Premiere Pro, Edius. It’s good to have options.
“

It is good to have options, and when X dropped many X users were like, ‘What’s wrong with options? If you don’t like how X does things then use another NLE that better suits your style/needs’. Somewhere along the way though that attitude morphed from ‘having choices is good’ to ‘having choices is good, but if you don’t choose FCP X you’re an idiot’.

[Douglas K. dempsey]

Haha, I am looking forward to using Resolve 11, and I know RippleTraining is at work on a tutorial, anticipating its popularity. Thanks for the warning! This is typical, right? Even though there is no virtual camera that could conceivably, in 3D mode, perform a pan and tilt, someone has the half-baked idea, “Hey, in movies they call it Pan and Tilt, let’s do that!”

In writing the first lesson you learn is “parallel structure:” Like goes with like, to make things easy to follow. But in UI there are apparently no “grammatical” syntax, structural rules. So you get a mix of graphics app conventions, NLE features and movie language.

My observation of the traditional NLE as a wildly mixed-metaphor is: The Timeline is based on physical film editing, where you ran tracks of film and mag stock (audio) through a synchronizer while screening, selecting, editing. (Moviolas worked this way, and even flatbeds like the Steenbeck — although there, your tracks are turned on their sides). You could unlock the sync block and “slide” tracks out of sync … which is what you do when you shuffle clips around on NLE tracks. But the Source & Record windows (as Avid originally called them) are straight out of another era altogether, tape editing, in which you played a Source deck and watched on a Source Monitor, then dubbed your desired shots — via timecode — onto a Record deck, the result playing back on a Record Monitor. And finally, the “Browser/Bins” area leaps forward to yet another era, and is basically a Mac Finder or Windows desktop metaphor, with files hierarchal-organized into folders. The NLE mixed metaphor spans about 80 years of user interfaces!

With FCPX, Resolve, advances in metadata … we have a chance to become a bit more integrated and consistent in our interface rules and language. Maybe it will become important someday.

Doug D

[Charlie Austin]

[Andrew Kimery] “It is good to have options, and when X dropped many X users were like, ‘What’s wrong with options? If you don’t like how X does things then use another NLE that better suits your style/needs’. Somewhere along the way though that attitude morphed from ‘having choices is good’ to ‘having choices is good, but if you don’t choose FCP X you’re an idiot’.”

I don’t think that’s a fair assessment of “many” X users. Some for sure though and, as someone who prefers X over the other NLE’s (that I actually own/rent and use) I find that attitude just as annoying as you do. Just saying.

I gotta say though… I’ve been working in FCP 7 for a couple weeks and while it’s comfortable as an old shoe, I find myself cursing at it daily. Hourly… OK, every time I need to move a clip between tracks, or want to quickly see what the base layer of a composite is, or want to see scrub a single clip in the timeline, or see what’s in my clip beyond the cut point without leaving the timeline, or or or…

The trackless bit of X is not it’s only differentiation from other systems by a long shot. I do this 8-10 hrs a day every day of the week, and X is way more pleasant to cut in.

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

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

[Simon Ubsdell]

[Charlie Austin] “The trackless bit of X is not it’s only differentiation from other systems by a long shot. I do this 8-10 hrs a day every day of the week, and X is way more pleasant to cut in.”

I completely agree about the pleasure of cutting in X – though I’d have to say that every NLE has its “pleasure spot”, as it were, and they’re all different.

(And that means, believe it or not, that there are even some things I really enjoy about Media Composer that aren’t as well implemented elsewhere – though I can’t believe I just said that.)

The problem for me is that there are still two or three basic editing functions that are missing from X that mean I can’t really commit to using it because my job doesn’t allow me the time to juggle the workarounds.

(I don’t think that makes me a Luddite, or lazy, or stupid – though I may be all of the above and more.)

As to whether we will ever see these functions implemented, I’m starting to become doubtful.

Maybe there are more editors like me who are missing the, to them, essential functions that mean X is just not a plausible option at this point.

Simon Ubsdell
tokyo-uk.com

[Charlie Austin]

[Simon Ubsdell] “As to whether we will ever see these functions implemented, I’m starting to become doubtful.”

I’ve got actual playhead match replace on my short list of WTF? issues. Send to Motion/open in editor is another, but I don’t miss it all that much.

What’s on your list? I think a list of gripes from people who actually use FCP X would be interesting. 🙂

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

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

[Craig Alan]

Can you name the missing functions? It’s probably been talked to death but since we just had a new update I’m curious what for u is still missing.

I would really like to see them add custom layouts. Spend too. Much time opening and closing windows and resizing them.

Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.

[Charlie Austin]

[Craig Alan] “Can you name the missing functions?”

fcpx.tv has a pretty big list, though I don’t agree with all of ’em. Many of them are “would be nice” kinds of things. Also, the fact that “scrolling timeline” is his number one issue makes me take the rest less seriously. I can’t think of a future I would want less. 😉

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

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