Activity › Forums › Creative Community Conversations › Long time editor’s frustration with FCPX
-
Long time editor’s frustration with FCPX
Tim Wilson replied 10 years, 7 months ago 41 Members · 140 Replies
-
Oliver Peters
April 17, 2015 at 4:08 pmI use all of these tools and don’t have any particular problem with the FCP X or PPro interfaces. For those of you complaining about the PPro interface, you do know that you can open and close any of the tabs and save custom workspace layouts (not possible in X), right? So you can make it as cluttered or uncluttered as you like. Plus you can create optimized workspaces for doing effects, editing, mixing, etc.
Another beauty of the PPro interface is that it has huge advantages for developers, because custom panels can be created that are integrated right into the UI – also not possible with X, that we know of. This was evident at NAB, where a number of MAM companies showed integration with windows right inside PPro. This has also been true in AE, if you look at how tools like Type Monkey and Layer Monkey have been implemented.
I do agree that Apple’s changing of the terminology was a poor move. Trying to use their language in discussions and training around X and editing are very confusing to old and new users alike. If you work in a bubble and only use Apple software, then it’s fine, I guess. But if you have to work with other users and other applications, it’s an issue, through not a deal-breaker.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Jeremy Garchow
April 17, 2015 at 4:21 pm[Oliver Peters] “I do agree that Apple’s changing of the terminology was a poor move. Trying to use their language in discussions and training around X and editing are very confusing to old and new users alike. If you work in a bubble and only use Apple software, then it’s fine, I guess. But if you have to work with other users and other applications, it’s an issue, through not a deal-breaker.”
I often think that these types of statements aren’t thought through enough.
People rely on the old terms because they are familiar with them, which is completely understandable. If you start to use fcpx like it supposed to be used, and use it for it’s strengths, the Event/Project/Library terms make a ton of sense.
“Event” is the only one that could be a little misconstrued, but If you have a Library for a client, and in that Library you have several different jobs (or events) and in those Events, you could have multiple Projects. It makes perfect sense to me, and I use them a lot. Before, with 7 or Pr, I have a traditional projects, and if I had different (but related) projects that I was working on for that client, I would sometimes make a new project file, which means I have multiple files to track. This is alleviated with FCPX. I also barely duplicate timelines anymore, I simply snapshot the current timeline, and version up the number on the current timeline (the snapshot retains the previous version number). It’s easier and faster.
More so than anything else, if I work in other NLE’s I miss X’s organization tools when I don’t have them. I can work around timeline issues in any program, but the Library/Event/Project system, and now that Smart Collections can used across all Events in one Library, is something I think Apple got very right, even if it’s not perfectly named.
-
Steve Connor
April 17, 2015 at 4:38 pm[Oliver Peters] “For those of you complaining about the PPro interface, you do know that you can open and close any of the tabs and save custom workspace layouts (not possible in X), right? “
Very true, PPro’s interface is MUCH better than it used to be, it is possible to keep it much simpler and call on layouts when you need them. I wish FCPX had more options for this
-
Scott Witthaus
April 17, 2015 at 5:13 pm[Oliver Peters] “For those of you complaining about the PPro interface, you do know that you can open and close any of the tabs and save custom workspace layouts (not possible in X), right? So you can make it as cluttered or uncluttered as you like.”
Can I change the looks of the icons so it’s not like trying to read some ancient language off a stone tablet?
😉
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
David Lawrence
April 17, 2015 at 6:23 pm[Jeremy Garchow] “”Event” is the only one that could be a little misconstrued, but If you have a Library for a client, and in that Library you have several different jobs (or events) and in those Events, you could have multiple Projects.”
I don’t have any problem with “Events” but I think renaming sequences “Projects” was a colossal blunder.
“Sequence” and “Project” are terms that have very specific, commonly understood, technical meaning throughout the entire industry for decades.
From a UI design perspective, a label switch this profound isn’t just confusing, it’s wrong; because it breaks a decades long mental model and it goes against all other uses of the terms.
Apple could easily have called “Projects” “Sequences”. By choosing to reinvent the basic nomenclature of NLEs, they appear arrogant, out-of-touch, and have made industry acceptance of FCPX that much harder.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
https://lnkd.in/Cfz92F
facebook.com/dlawrence
twitter.com/dhl
vimeo.com/dlawrence/albums -
Aindreas Gallagher
April 17, 2015 at 8:07 pmactually yes – it’s possible to directly access many of the interface tool and button icons in PPro and adjust them (as in adjust/remake them in PS). Quite a few people did around CS6 Ppro time when the contextual slip slide roll tools were felt a little overbearing. When the adobe team heard about the modifications they published a blog linking to the designed files. Nevermind the ability for third parties to create entire custom interface segments. ITV is running custom PPro panels for asset and meta data management.
See? It’s a hotrod where you can pop the hood. your one looks quite pleasing (arguably) but it’s a big old lump of aluminium without any screws..
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
Scott Witthaus
April 17, 2015 at 8:22 pmThanks Aindreas. The standard interface sucks, but it’s good to know it can get less sucky.
Seriously I have this gig and then another 11 days on Pr CC in May so I am hoping I will see the strengths and differences of each. I am putting together a list! Either way, as alot of us say, it’s good to know all three A’s.
[Aindreas Gallagher] “It’s a hotrod “
Hardly, when compared to X, but I will give it a fair shake!
😉
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Jeremy Garchow
April 17, 2015 at 8:44 pm[David Lawrence] “I don’t have any problem with “Events” but I think renaming sequences “Projects” was a colossal blunder.”
We will agree to disagree. Colossal blunder?
[David Lawrence] “From a UI design perspective, a label switch this profound isn’t just confusing, it’s wrong; because it breaks a decades long mental model and it goes against all other uses of the terms.”
But of course. You don’t think that’s on purpose? You don’t think by changing the terms, you might have people change their frame of reference? Isn’t it OK to have a look at what the relationship of media to sequence to container may be? If you read the FCPX manual, timeline is listed all over it. If it’s really that confusing, and someone opens the manual, they will figure out rather quickly what a Project might mean.
[David Lawrence] “Apple could easily have called “Projects” “Sequences”. By choosing to reinvent the basic nomenclature of NLEs, they appear arrogant, out-of-touch, and have made industry acceptance of FCPX that much harder.
“I think that Apple has a much bigger hill to climb than Project vs Sequence terminology and if we, as professionals, can’t figure the difference between those two terms, we shouldn’t be here. I would assume that Apple thinks an FCPX user, can figure out what a Project, what an Event, and what a Library can do and how they work. Cameras have all different kinds of terminology for the same thing. Cam Ops get over it and get to work and none of them are all wrong or all right.
Some people might not know what lift and gain means, but they could tell you what shadows and highlights are. Are they wrong, or is it just a different frame of reference? If I asked someone to lift the gamma, they might not know what that means as there might not be a control in their device that says “gamma” or if there is, it might not do what they want it to do, but I might be able to say, please raise the midtones and they would know exactly what I was talking about.
-
Aindreas Gallagher
April 17, 2015 at 8:50 pm[Scott Witthaus] “it’s good to know all three A’s.”
I’m only trying, in my small way, to push for a situation where, as the song goes, three become one, and then Andy doesn’t actually have to bother his ass. Andy is surprisingly lazy.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
Timothy Auld
April 17, 2015 at 10:38 pmIf your are attacked on this forum it is usually because you are asking the right question.
Tim
Reply to this Discussion! Login or Sign Up