[Robin S. kurz]

[Steve Connor] “still waiting for the iPad version though :)”

I believe that’s actually called “iMovie for iPad”, yes. 100% FCP X compatible, brilliant on an iPad Pro.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

So you didn’t get that actual point. That’s okay.

But yeah, there are in fact a LOT of people that want to able to do that, sorry to say. Be it e.g. for on-set dailies or actually editing, yes, with an external screen or not. In the latter case whether it’s a 2, 12, or even 17 inch whatever becomes completely irrelevant. Until recently my main machine was a MBP, too. Loved it and still love it as my secondary.

– RK

[Robin S. kurz]

[David Roth Weiss] “because you will NEVER find a single instance anywhere on this planet where I said “never” about anything relating to the future FCP X”

Yet you felt spoken to. Go figure.

[Robin S. kurz]

[Steve Connor] “It was a joke Robin, hence the smiley face”

Oh the irony.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

[Steve Connor] “Yep, those customisable UIs are for control freaks”

That, and for GUIs that are an unusable mess to begin with. 😛

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

[Oliver Peters] “One editor’s clutter is another’s useful visual information.”
No more or less information that I can think of. And I personally most certainly wouldn’t want that mess of interface juggling that others have, that so many people bizarrely consider “flexibility” either. I LOVE the fact that no matter when and where I open FCP X, I know exactly what I’m looking at and where to look for anything and everything else. ZERO surprises from someone that thought his jumbled version of the interface was somehow way mo’ better. I’m simply not that much of a control freak I guess.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

[Oliver Peters] “Sure, but again, that’s an extra step I don’t need with the other approach.”

Two, maybe three shortcuts (i.e. about 10 sec. of “work”) to avoid the continuous visual clutter. For me, worth it, yes.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

That’s what “Break Apart Clip Items” is for, yes.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

[Oliver Peters] “However, in a more concrete example, let’s say you cut a :60 commercial and from that you want to edit a :30 cut down version.”

Do it all the time. I just don’t see how the imho excessive visual clutter that all that brings with it aids me in that. Nor how that (due to the clutter) is any better or more helpful than e.g. simply copy pasting the 60 to the 30 project or making a compound of the 60 for quick and easy reference, which are two things that I would do. Stacking or “Pancaking” is great… if you have no other useful options and are accustomed to an overladen GUI to begin with. 😀

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Robin S. kurz]

[Shane Ross] “how quick it can do it…with the aid of third party applications. Stuff that Apple didn’t see fit in including. I am glad that there are many passionate people out there to make these apps to make for a smooth workflow.”

I’m confused as to what you’re arguing or suggesting with that. Using 3rd party apps to extend functionality is “cheating”? A bad thing? Laziness on Apple’s part? More expensive in the end?

Well, aside from others already pointing to the fact that there isn’t an NLE on the market that doesn’t require “external support” at some point or another, which cancels out the “cheating” part, I’m actually hella glad that e.g. the XML conversion was put in the hands of the most competent XML specialists, Intelligent Assistance. Because with that, the compatibility and functionality could be and WAS improved on probably 10:1 cycle compared to Apple’s own FCP updates. Same goes for various other mission critical add-ons that I have. If I had had to wait between 3-4 MONTHS for even smaller fixes to (maybe) come along with the next FCP update… wow. Not to mention that the communication with IA and others is actually possible, near immediate AND tangibly fruitful. 😉 So for me that cancels out any possible notion it could be a bad thing or disadvantage.

Apple’s “laziness” or disinterest (they don’t care about pros!)? I don’t believe so. I think they made an obvious choice to leave certain aspects up to others, quite possibly even for those exact reasons I mention. BECAUSE they cared that was done right (for the few that needed it)?

As far as cost is concerned, all I know is that in the exact same time period that I’ve had FCP X for a measly 300 bucks, CC would have cost me a whopping 2700€ and is going up by the month. With Avid and a monthly sub it would be even that much worse. With FCP X, as we know, it has been 300€… period. Obviously going down by the month (currently at 7.40€/month if you include Motion and Compressor).

So in comparison I could in fact buy every single 3rd party app or plugin that I know of for X and still have cash left over to go crazy on e.g. MotionVFX’s site… so cost clearly can’t be an argument either.

FWIW
– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!