-
Is it Adobe or Premiere Pro?
-
[Oliver Peters] “Look at the owner of the page and video. It’s a color-correction online training resource.
“Doesn’t mean his points aren’t valid!
-
Perhaps this is only anecdotal, but, the guy in the suite next door runs Premiere pro on a recent MacPro tower and he’s experiencing a lot of crashes every day. Is five or six a lot? Seems like a lot to me. I run FCPX on a 6-year-old iMac pro and it’s very stable. Not that it -never- crashes, but I get a crash maybe once every three days, which recovers in about a minute, and he’s crashing hourly. He’s not doing anything super-complex or challenging either. A lot of his crashes also end up with corrupted files at some point. There’s too many variables involved to make a definitive judgement on his suite; it could be non-Adobe-related hardware issues, it could be he’s not using best practices, could be a lot of things.
I will agree with the argument that Adobe promised more innovative features were coming to Prem Pro as a “benefit” of the subscription model. You look at some of their annual development events, where they sow some of what their lab’s been working on, and they are demonstrating tools in the compositing and effects arena that are jaw-dropping. But I’ve been waiting to see some of those “almost ready for distro” features for like 2 years now, and maybe I missed the announcement, but they haven’t appeared in AE or PPRo yet.
I can’t afford to be too iconoclastic in this argument; I have to learn prem pro, as management policy decisions are forcing the shop to convert to it from FCPX, whether I like it or not. I will say from a personal perspective, I find Prem Pro more buggy, and more unnecessarily complex, and less “fun”, than my user experience with FCPX. I’m definitely having to waste more time thinking about the tool and how to drive it, than using it to do the job, and thinking about the creative decisions of the job.
-
[Mark Suszko] “Perhaps this is only anecdotal,”
Yes, it is and also very atypical. I work at a shop with 9 edit stations running Premiere Pro, as well as my own machines at home. Mixture of Mac models. Hardly any crashes over many years. I would say that in my experience FCPX, Premiere Pro, Resolve, and Media Composer all crash at about the same rate. It really depends on project specifics and media types.
– Oliver
Oliver Peters – oliverpeters.com
-
[Oliver Peters] “Yes, it is and also very atypical. I work at a shop with 9 edit stations running Premiere Pro,”
Doesn’t mean it’s “atypical” I only have one edit station but I had a few crashes on a recent PPro project I worked on and I REALLY missed FCPX’s save function when it did happen.
-
[Oliver Peters] ” I would say that in my experience FCPX, Premiere Pro, Resolve, and Media Composer all crash at about the same rate. It really depends on project specifics and media types.
“This is absolutely true. PC’s crash, Mac’s crash, FCPX crashes, Avid crashes, Premiere Pro crashes and Resolve crashes. I’ve gone through periods of time in which one program crashed less frequently but the truism is that computers crash.
Tallmanproductions.net | Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
Adobe CC 2019 13.0 | Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 x 2 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with Resilio -
[Steve Connor] “Doesn’t mean it’s “atypical” “
I don’t mean to minimize these issues. But I live and work in a market with multiple corporations, production companies, and broadcasters with multi-seat Premiere Pro installations on both Macs and PCs. Premiere is probably the single most installed NLE in town, with Media Composer/NewsCutter a second. I have freelanced at some of them and I know editors and managers at all of them. In general, no one has ever mentioned this level of instability. Occasional crashes? Sure. Multiple crashes every day? Nope. There’s clearly some issue causing this on that specific system or with those projects/media.
And for comparison, I’ve also recently had FCPX projects (libraries) where I couldn’t get through 10 minutes of editing without a crash. And auto-save didn’t necessarily catch everything. Certainly not the norm for me, but something about this one was causing issues.
– Oliver
Oliver Peters – oliverpeters.com
-
I’m sure you’re right, Oliver. And probably part of the success you see can be attributed to better practices and better setups. Our guys are all self-taught on Abobe, and our budgets, low. The gear is not cutting-edge. My observations of the crashes are anecdotal and not scientific. There are too many possible explanations for it and it’s unproductive for me to go chase down exactly what all the factors are, much less convince the guys to adopt any fixes.
Nevertheless, it’s a less than pleasant user experience from my POV. When or if I have fully migrated over to Prem Pro, I’ll be working to make my system as stable as possible, and adjust my own practices to suit. I’ll be looking for tips on that in days to come.
-
[Oliver Peters] “I don’t mean to minimize these issues. But I live and work in a market with multiple corporations, production companies, and broadcasters with multi-seat Premiere Pro installations on both Macs and PCs. Premiere is probably the single most installed NLE in town, with Media Composer/NewsCutter a second. I have freelanced at some of them and I know editors and managers at all of them. In general, no one has ever mentioned this level of instability. Occasional crashes? Sure. Multiple crashes every day? Nope. There’s clearly some issue causing this on that specific system or with those projects/media.
“I’m sure you’re right, I don’t have a lot of experience recently with PPro, it’s just my experience.
I also still find it’s an absolute dog with 4K XAVC material when using a laptop Mac, whereas FCPX and Resolve are much faster. But again I’m sure with a fast system that is optimised for PPro it’s much better.
-
[Mark Suszko] “I’m sure you’re right, Oliver. And probably part of the success you see can be attributed to better practices and better setups. Our guys are all self-taught on Abobe, and our budgets, low. The gear is not cutting-edge.”
I feel your pain. Although I see the same level of user familiarity around town. Often the biggest culprit is the crappy media formats that are rampant in our business. While Premiere generally does well with native media of mixed sizes, codecs, and frame rates, that’s often not the best or most reliable way to work. You might consider transcoding or using a proxy workflow for now and see if that helps.
– Oliver
Oliver Peters – oliverpeters.com
-
[Steve Connor] “I also still find it’s an absolute dog with 4K XAVC material when using a laptop Mac, whereas FCPX and Resolve are much faster. But again I’m sure with a fast system that is optimised for PPro it’s much better.”
Yes, I would agree with you there. It’s a horrible format, but FCPX certainly does better with it natively. Although I must say, you can’t use a laptop as a good measure of best performance. I cut on one, too, at home and on the road, but it’s not ideal.
– Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up