-
Prem vs FCPX – Panels
-
Sorry to hear about your Dad Chris.
-
[Walter Soyka] “Adobe UIs can be pretty hard to learn. They’re close to the metal, so to speak, relatively thin wrappers over the underlying mechanics, with lots of options and controls exposed. “
So, let’s forget about the UI for a moment.
Why does Ae and Pr crash a lot? This isn’t just me taking, this is all of my colleagues. Perhaps all of our machines are broken, but nothing else crashes like this. Resolve, Fusion, all my third party interchange.
I have all the controls I need exposed, and if I need some speciality, I can go out and get it. And it’s stable.
Let’s remember the UI for a moment.
What exposed controls are you talking about? 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.
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.
What does Pr get me, what metal is more near my vicinity, that I need to know about?
-
[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! -
[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! -
[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] “Why does Ae and Pr crash a lot? This isn’t just me taking, this is all of my colleagues. Perhaps all of our machines are broken, but nothing else crashes like this. Resolve, Fusion, all my third party interchange. “
I know it’s not just you. And it sounds horrible. But at the same time, Ae and Pr are stable for us. I wish I understood what the difference is. Please submit bug reports when you have the time. These apps shouldn’t crash.
[Jeremy Garchow] “What does Pr get me, what metal is more near my vicinity, that I need to know about?”
I think you point out some good examples of Pr’s fiddliness above. But here’s an example of how philosophy differs between Apple and Adobe.
Apple curates the controls it exposes. FCPX stabilization:
Adobe shares lots of under-the-hood parameters with (at?) you. Pr stabilization:
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
[Robin S. Kurz] “Yes. And completely unnecessarily so imho. As shown by X’s interface in comparison imho.”
I’m curious. Please see my examples a couple of posts up. 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?
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
[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! -
[Robin S. Kurz] “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 plain does not change diddly about PPro’s GUI as a whole in comparison, which the only and real underlaying point.”
No. This screenshot has nothing to do with Ae’s Tracker panel; it’s the effect controls for Pr’s Warp Stabilizer effect.
I picked this as an example of Apple’s philosophy of simplicity versus Adobe’s philosophy of flexibility. Personally, I think both have value, but you seem to disagree. If Adobe exposes too many controls, let’s pick which ones to remove.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
[Robin S. Kurz] “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.”
If there wasn’t a need, there would be no Automatic Duck tools. Regarding GIMP, Affinity, etc – baloney. Because it doesn’t seem important in your neck of the woods, doesn’t make it so. But specifically, in the commercial and corporate editing world, it’s very important – even if only to integrate with graphic artists. For example, on one job, I was given a template for animated lower thirds that were done in Photoshop. These needed to be updated for each on-camera speaker in Photoshop. How does GIMP help me there?
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up