-
Why we will be choosing PremierePro over FCPX
-
[Bill Davis] “Everyone fits in one camp or the other.”
Bill,
I think Walter was specifically commenting on philosophies behind software design, and I’d be very surprised if he had just two in mind – there seems to be at least a handful of approaches continually discussed here.
When it comes to editors and their workflows, needs, approaches, and theory, there are significantly more than a handful to count. This forum is (or should be) a constant reminder of that.
Franz.
-
[Morten Ranmar] “Adobe hides away everything in menus that look completely alike, and generally takes too many mouse clicks to work with”
We have striven to minimize mouse clicks over the past few versions and I think the next release is the most significant one to date. Only you will be able to determine if it meets your needs.
One other big thing to understand with Adobe’s philosophy in UI is that we are strong believers in contextual menus for certain things, so a right click can often save you a bunch of hunting in the menus.
Dennis – Adobe guy
-
[Chris Kenny] “Those ‘updates’ have brought many very significant features. Apple hasn’t really gotten much credit for this, because most of those features were willing in functionality that people believe should have been present in the first version. But now that many of those gaps are filled, if Apple continues to push out updates of similar scale every 3-4 months (which appears to be the plan), this seems vastly preferable to Apple holding back features for a big release every 12-24 months.”
Hi Chris,
I tend to agree with the sentiment that you stated – a lot of these are add back features, but important ones for developing the FCP X user base transitioning from FCP 7 and others. In my opinion, the more important features were already baked in at 10.0, namely things like compound clips, skimming, magnetic timeline, etc. Though I haven’t used it personally, I have heard that the multi-cam is unique and preferred by some, so you could consider that a new feature as well.
For those who care – Here’s the wikipedia entry on FCP X which details its enhancements by version number
One of the potential upsides of Adobe’s Creative Cloud model is that it allows Adobe to release new features on a regular basis as well. We have already demonstrated that with Photoshop and Illustrator in the CS6 cycle along with other products like Muse. We’ll start to do the same with the video products as well which will be good news for Adobe users of any video product.
And in the interest of fairness and history, here’s the wikipedia article on Premiere Pro
Dennis – Adobe guy
-
[Bill Davis] “The two pholosophies are simple.
A – I need to keep working the way I always have because my investment in process is too deep to jettison.
(which is an extremely defensible contention, by the way)or
B – I’m willing to explore new ways to work in order to potentially benefit from some new ideas and thinking.
Everyone fits in one camp or the other. “
Hey guess what Bill!? News Flash! –
– I am in camps A and B. Guess I must just love Premiere Pro.
Alex Hawkins
Canberra, Australia -
[Bill Davis] “A – I need to keep working the way I always have because my investment in process is too deep to jettison.
(which is an extremely defensible contention, by the way)or
B – I’m willing to explore new ways to work in order to potentially benefit from some new ideas and thinking.
Everyone fits in one camp or the other.
“Just NOT true, Bill. It isn’t one or the other however hard you try to make it so. Or how many times you say it. I’m not working the way I always have when I’m working on an Avid. My methodology is quite different. In some respects, working in X might even be closer.
There are some things X does really well. There are some things it doesn’t do well. There are even some things it does badly. If most of what you do fits into group one, than X is probably for you. If a sizable chunk of what you do fits into group three–like a lot of what I do does–than it will probably be a long while before you want to use X.
-
I’ve been strictly an Avid user for non-linear since moving from an A/B BetaSP setup in the mid 90’s. Premiere and FCP, while both very capable, never had enough differentiation to make me seriously consider switching. With FCPX and Premiere CStheNext (combined with Avid’s inability to advance their software in the areas I need them to), I really see the possibility of using two or possibly even three editing applications – and playing each to their own strengths.
The really great thing is that I bought the MC7 upgrade (from v6.0) for $299, FCPX for $299 and a Cloud subscription for $360+tax (for this year at least…) That’s $1k for three really great applications for a maybe a year’s time. I added a decklink card for FCPX and Premiere output as well as Resolve (the free version for now).
Like many people here, I’ve had a love/hate relationship with the three A’s, but really it’s a pretty amazing and economical time to be involved in post.
Now whether the economical part of it is a good thing or not is another topic entirely… 🙂
-
[Ievgenii Larin] “I agree with everything except your point about Motion 5. Motion 5 is awesome inexpensive piece of software that allows very flexible manipulations with titles and effects in FCPX.”
I happen to agree with you about Motion.
-
Hi Morten,
just some answers to some of your complaints:
“Missing ability to work with Shared Storage in a simple way”
Well, situation could very much be better, but we work with Shared Storage and FCPX, although, never people working on the same projects at the same time. Just a Mac Mini Server connected to Pegasus RAIDS, Atto Thunderbolt to 10GB Ethernet, to a switch. Every Retina connected to that trough Ethernet. We just load in the footage in FCPX, all have our own events. The only thing we do is copy the Events and Projects that we need before the editing to the SSD we are working on. This is only like a couple of hundred megabytes in total for our projects, works great. But could be better.
It’s more or less the same as with FCP7 and Premiere Pro in my knowledge, so… (not talking about the Adobe Anywhere project)“Lack of possibility to easily save a version”
Okay, but you can just make a duplicate of a sequence and name it version 1 or whatever, and work further on version 2. Also check Digital Rebellions ProVersioner tool.“Colorgrades cannot be key framed”
No, that’s true. I do hope that Apple goes a lot further in developing much more old Color tecnology back into FCPX. But, the Color Boards is fast, renders very fast and you have to learn a bit. That being said, I still prefer color wheels. Do you know SliceX? You can do some wonders with that in combination with the Color Board. Still. Could be better!“The color board becomes cluttered and looses overview ”
Well, I sent feedback to Apple about the ability to name grades. I’m not really of the opinion that it really becomes clutter, but I can get where you are coming from.“No Media Management for saving with trimmed Media”
Does Premiere Pro allow this? You can save media with FCPX, or even only the used clips you have in your timeline. But no handles. I’m pretty sure that’s coming in an update.“Loading of all projects slows down workflow”
Buy Event Manager X. Seriously. It’s a 4 dollar app.“Locked project settings, no custom sizing”
True and not true. Yes, I would like to have Apple set custom resolutions in a project, I hope they add this (I’m pretty sure they will). But there is a perfectly working work-around for this, described here on Creative Cow. Search Google for Creative Cow Custom Resolutions or something. It works perfectly.“Custom Titles need to use cumbersome Motion engine”
Performance used to be bad in FCPX at times, sometimes it still is. Other times I find it much better and much easier then the old FCP. You have a lot more visual feedback, much more flexibility, …” Lack of partial export from Timeline”
Not true. that was added in an update, 10.0.6.“Missing possibility to inspect clip from timeline in event viewer”
You can always just click the clip and use the shortcut SHIFT+F (if I’m not mistaken). Reveals it in the Event Browser…“Re-importing from archive does not maintain timing”
Can’t comment on that, I don’t use the archive function, and I don’t really get your comment either, but can’t commend either way. -
Yes I know there are workarounds for many of the issues.
But it is like pushing my car as a workaround to get it to start, when the battery is dead…
– No Parking Production –
2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial
-
[Morten Ranmar] “But it is like pushing my car as a workaround to get it to start, when the battery is dead…”
Perfect analogy!
Reply to this Discussion! Login or Sign Up