-
Trying new stuff
A few threads back, Lance Bachelder wrote –
“I left and built an uber PC just for CS6 and Vegas. I’m talking multiple SSD’s, nVidia GTX graphics etc…
After using Premiere on some paying gigs I can honestly say it’s the worst piece of crap I’ve ever seen – even simple things require so many extra clicks, windows, dialog boxes – just a horrible NLE.”
Having read this here, I worried about using PPro and possibly doing paid training work on it.
Well, I got paid by the BBC over the years to try out various NLEs (and a lot of other stuff) so I have some history in comparing systems and putting corporate money into buying them. And now – in my retirement (sort of) I’ve spent some time with Premiere Pro CS6.
It’s another editor – just another editor – it’s straightforward to learn and easy to use. Its logic follows that of FCP7, Edius, Avid etc etc. It runs fine with AVCHD rushes, which probably means it will work well with the general run of stuff. Half the world is likely to be ahead of me in this already, but I’m just reporting.
I’ve been doing cut-down work mostly so far, and discovered that the “ripple delete clip” keyboard shortcut – backspace in FCP, but shift-delete here – was a bit of a pain, so I changed it to “x”, giving me a run of keys x,c,v,b that did useful things without moving too much.
Just the usual stuff when changing systems. No “extra clicks” so far, though I’m happy to accept I’ve got a way to go yet. I doubt though, that I’m going to have any major problems.
I can’t see how Mr Bechelder could have such problems, given he’s just come from FCP7, as it’s almost identical in operation. Perhaps he could explain in more depth so that others can have a go at solving them.
B
-
54 Replies
-
I suspect Lance may have been extremely eager to report that he found PPro unsatisfactory. and that FCPX answers all his issues.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
My guess is that Mr. Batchelder didn’t take the time to learn Premiere, then got thrown to the wolves on the paying gigs because he didn’t know what he was doing yet. It’s really easy to hate something when you have to do it under pressure and you haven’t done your homework. That’s just my guess – I’ve been in that position before. Never throw stones at anything until you know it inside/out.
That said, any of the mainstream NLEs these days will do the job for you. All of the perceived shortcomings of any of them are usually based upon – the NLE they learned editing on – the NLE they loved, but is no longer around – the ideal NLE, which only exists in their mind’s eye. I’ve used Edit*, AVID, and Premiere Pro, in that order, and I loved and hated many things about all of them – it’s when you know them, and use them on a daily basis that you can put worth a real opinion.
Joe Bourke
Owner/Creative Director
Bourke Media
http://www.bourkemedia.com -
I truly think its a mistake to claim Pr works just like fcp7. It does a disservice to Adobe for all the hard work they’ve done, it sets false expectations, and while there are commonalities, they are really different and follow different logic especially when it comes to workflow.
It’s best to treat Pr as a new NLE otherwise you will never learn its true strengths and weaknesses and expect it to work just like fcp7, when it doesn’t.
-
[Jeremy Garchow] “I truly think its a mistake to claim Pr works just like fcp7. It does a disservice to Adobe for all the hard work they’ve done, it sets false expectations, and while there are commonalities, they are really different and follow different logic especially when it comes to workflow.”
What about the workflow is different? I used FCP7 extensively last year for the first 6 months, and then got Premiere CS6 when it came out. Of course there are differences in the details, but as far as a typical “workflow” goes, aside from the loss of the need to transcode in CS6, it’s very similar.
-
[Joseph W. Bourke] “because he didn’t know what he was doing yet. It’s really easy to hate something when you have to do it under pressure and you haven’t done your homework. That’s just my guess – I’ve been in that position before. Never throw stones at anything until you know it inside/out.
That said, any of the mainstream NLEs these days will do the job for you. All of the perceived shortcomings of any of them are usually based upon – the NLE they learned editing on – the NLE they loved, but is no longer around – the ideal NLE, which only exists in their mind’s eye. I’ve used Edit*, AVID, and Premiere Pro, in that order, and I loved and hated many things about all of them – it’s when you know them, and use them on a daily basis that you can put worth a real opinion.”
Heh.. can I just copy and paste this text into the next thread that pops up about how FCP X is inadequate? 😉
————————————————————-
~”It is a poor craftsman who blames his tools.”~
-
[Gary Huff] ” Of course there are differences in the details, but as far as a typical “workflow” goes, aside from the loss of the need to transcode in CS6, it’s very similar.”
I think it all stems from how it doesn’t need to transcode.
It’s completely different from FCP7 from import, render, export, and encode.
-
[Jeremy Garchow] “It’s best to treat Pr as a new NLE otherwise you will never learn its true strengths and weaknesses and expect it to work just like fcp7, when it doesn’t.”
Highly agree. The thing with Pr is that it is enough like FCP7 that, if you come from 7, you get lulled into thinking it is just like 7, and then, because it does some fundamental things differently, you can get trapped in a none-to-pretty way. With X or Avid, it is clear immediately that it is not the same beast, and that you have to relearn your approach. With Pr, you can just wander in and pretty much start working, without realizing that you didn’t understand, for instance, how to properly configure your timeline’s audio, and just assumed that you could easily monkey with the channel assignments down the road. Or you learn too late that you really SHOULD have set up a native timeline before you began cutting. I don’t know what happened with Lance, and I, certainly, have found the current version of Pr to be officially bitchin’, but when I do hear complaints about what a cluster fork Pr is, it usually has to do with people getting nailed by thinking they were in known territory and then finding that they were not.
-
Sure, Charlie – just don’t put my typo in – it should be “forth” in that last sentence, not “worth”.
Joe Bourke
Owner/Creative Director
Bourke Media
http://www.bourkemedia.com -
[Joseph W. Bourke] “Sure, Charlie – just don’t put my typo in – it should be “forth” in that last sentence, not “worth”.”
You got it! lol. 🙂
————————————————————-
~”It is a poor craftsman who blames his tools.”~
-
I probably should never post after a couple of glasses of Merlot – pretty harsh. That said, while I admit there is some lack of expertise with Premiere CS6 on my part, I have no lack of expertise as an Editor and don’t believe Premiere is a good NLE and nothing like FCP7. Not having something as simple as sync indicators is just the tip of the iceberg of the problems I see. Yeah I know there are no sync indicators in FCPX either…
As far as the extra clicks, the only way to show this would be to do a live side by side with other NLE’s to show just how clunky Premiere 6 is. This doesn’t mean it can’t be used for any type of show and for those who’ve never used another NLE day in and day out in a high-pressure, broadcast or feature film type environment, they’d never know what I’m talking about and never know there are issues.
Lance Bachelder
Writer, Editor, Director
Irvine, California
Reply to this Discussion! Login or Sign Up