Robin S. kurz
Forum Replies Created
-
[Simon Ubsdell] “It is of course true of Premiere but not FCP 7.”
Ah! I stand corrected, yes. I must have let myself be confused by the visual differences i.e. differences in the handling. What can I say, it’s been at least four if not five years since I last used 7 for anything more than a quick check on something, comparison or simple export. My bad.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Walter Soyka] “Which specific stabilization controls should Adobe take out of their users’ hands? How much control must they remove before they meet your benchmark for simplicity?”
I’m sorry… are you suggesting that it all somehow hinges on just that one panel??! ???? Okay, so I may have been inadvertently hyperbolic as far as that one palette is concerned and remembered it wrong, but that does not change diddly about PPro’s GUI as a whole in comparison, which was my only and real underlaying point, so who cares?
Feel free to re-read my examples a couple of posts up as far as the direct overall comparison is concerned.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Oliver Peters] “I would add, that in a lot of the general post production world, knowing Photoshop and After Effects to at least a functional level is very important.”
More or less the exact logical fallacy I was talking about. For which NON-PPro editor is the need to “know AE at a functional level” of such dire importance?? And knowing GIMP, Affinity Photo etc. will not only give you that “functional knowledge” to work PS just the same, but you’ll be saving big $$$ in the process.
[Oliver Peters] “From there, Premiere isn’t that much of a difference.”
I love how you make it sound like that’s actually a good thing. ????
Learn the basic concept and logic of iTunes and you’ve acquired the most essential basic concepts of FCP X’s (organizational) logic. Ironically I personally find that much more impressive.
[Oliver Peters] “Then, if you compare that to Smoke, it’s a walk in the park.”
“Deal with it. It could be much worse!” ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Jeremy Garchow] “In Pr, it’s a bunch of clicks and tabs to move/repo/add stabilization/color/opacity/shutter fixes/crop/trim/zooms/compositing/spatial options.”
More is more! And therefore apparently much more is more “pro”? ????
[Jeremy Garchow] “In X, all those controls are exposed in the UI on every clip I select. I can see and manipulate audio and video as one in the Browser, in Pr, it’s a bunch of clicks and a few tabs.”
As I outlined further up with actual numbers, yes. But somehow, in some minds, having things split up into endless palettes-clicks-window-menu-things makes for a more user-friendly because “flexible” interface? Okay. Then will just have to agree to vehemently disagree. ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Walter Soyka] “Adobe UIs can be pretty hard to learn. “
Yes. And completely unnecessarily so imho. As shown by X’s interface in comparison imho.
Would I like the “web in your NLE”-thing option? Generally speaking, sure! At the cost of usability? Nope. But I suspect Apple will eventually make changes to either the FX Plug API or X itself to allow for more things in that direction. Only I suspect they’ll come up with a much better solution overall once and if they do. Or at least one that won’t mean the GUI has to explode into some convoluted mess for just that little bit more functionality.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Douglas K. Dempsey] ” Later, you find that you can take an item out of “Event A” and drag it in to “Event B.” It is no longer in A. It now reside in B.”
Assuming that both events are in the same library, yes. If not, that isn’t the case, nor is it even an option. But then having multiple “libraries” (i.e. projects) open at the same time isn’t even possible elsewhere to begin with, right? Certainly not with FCP 7 nor PPro. So, no comparison there either.
On the other hand, holding the ⌥ key will not move but rather copy the file to B. Is that possible with the classic “bin” you’re referring to? Nope. So again, different concept, even if there are seeming similarities at first glance.
I’d say that had they been named “bins” it would do nothing but simply shift the (imho rather nonsensical) nomenclature discussion elsewhere.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Steve Connor] “unless your clients supply you After Effects and Premiere Projects to work on or work with”
That of course not being the scenario I was referring to.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Scott Witthaus] “[Jeff Markgraf] “I find that what I may lose in extensibility/flexibility/customizability in FCPX (and many Apple products in general), I more than make up for in simplicity, ease of use, and the ability to focus on the work without other stuff in the way. ”
Exactly.”
+1
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Brett Sherman] “Yes. That’s why I changed the keyboard shortcut for the B-key from “Blade Tool” to “Blade”. Now it works as it should have from the beginning. Took me about 1 minute to figure it out.”
Simply holding the B-key (or any other tool’s shortcut for that matter), clicking, and then letting go would do the same btw, without having to change anything. ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Steve Connor] “What you think is “mindblowingly stupid” sadly is a necessity for an awful lot of other people’s workflows. Happy for you that you can CHOOSe not to use it”
Exactly. My personal opinion, nothing more. It’s an unacceptable concept for me, therefore I don’t buy into it. And again, it’s not Adobe exclusive either, which is the worst part if you ask me, more and more are jumping on that bandwagon. Adobe were just the obvious example in this context, but it applies to any and everyone with the same “service“.
Also, I don’t know of anything that Adobe offers that I can’t get elsewhere. Rarely very expensive (<$100, one time), often times even FREE. Even if a certain level of integration with each other is a strongpoint, sure. But everything is a give and take. I for one consider the “I have to have [insert Adobe app here] as a necessity!” a very common and way too easily accepted logical fallacy that clearly caters well to Adobe… good for them! But ultimately, to each his own, right? ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!