👋 MAKE THIS MORE STABLE.
Is this a professional software or what is this? I am just a little private youtuber. However, editing my little 7 Minute video, premiere has crashed 3! times and my video is not even done yet!
How are people supposed to create full cinema movies with constant crashes?
I am sorry, I know this is not actionable. But I am one more voice amongst many others complaining about stability. So please, do something about this :)
As noted in my last post, please submit specific issues about instability you may be encountering on separate threads. Please be specific.
Include steps, machine configuration including drivers (and/or 3rd party plugins, etc).
We appreciate you taking the time to engage with us.
Sorry, it would be much more efficient and reasonable for me to fly to where you are with my 16TB project and show you, than have me spend hours documenting details of my PC and project for you in the unlikely event that many of these bugs are related to code outside of Premiere.
I've reported bugs before and they disappear into your bug database and I never hear about them again. It's a very unsatisifying experience. 3 years ago I somehow got in contact with Wes directly and he helped me troubleshoot and solve a horrendous bug in Premiere that I had at the time, which was greatly appreciated. But it took a lot of my time and still took months to fix. I just don't have the time and patience to be an eternal beta tester for Adobe software. I need to finish this film, not troubleshoot Adobe software.
Is it too much to ask for your QA department to use large projects to test on? I'm positive that many of my problems could be easily recreated on a similarly large project. Is it expected that 2000 cut/20 track projects refresh at one frame per second on i7 5960X CPU with a GTX 1070?
I commented 3 issues I was having recently. Here's some more:
If I press m with nothing selected on a timeline, it creates a marker. When trying to turn the marker into a longer duration by pressing option+double click, sometimes it works, sometimes it doesn't. When it doesn't work, the cursor changes to a different tool icon when hovering over the marker when holding option on the keyboard, but sometimes it works fine and allows me to convert the marker into a longer duration style marker.. I know the work around is to double click, then change the duration there, but option+double click used to work great every time, now it doesn't.
Dropped support of older codecs, this isn't really a bug, more of an annoyance. If I install an older version of Premiere, all is good! Still works to export h.264 .MOV (Which some clients specifically ask for.) However, in the new version, can't export it anymore, I have to use a 3rd party app to get h.264 .MOV, why? It still works in older versions, so it must be just an Adobe decision to limit it's users. Why would I pay $900/year for professional video editing software, if I can't export a standard file type that my client's have requested? Have a read through forum posts online, there are literally hundreds of posts where people are annoyed about this. Another example of Adobe not listening to customers. For example, Storyblocks, a big stock website, doesn't accept .mp4 h.264 for 1080p footage, but they've always accepted .mov h.264, but I no longer can export .mov h.264 footage from Premiere, which means I can't submit footage to Storyblocks anymore, unless I do a workaround.
Warp stabilizer exported a clip the other day with a blue banner because it didn't analyze, but didn't warn me about it. Luckily I reviewed it and noticed. I seriously can't believe this happens. It's unbelievably unprofessional for a professional expensive editing program to not warn a user when they export a video, that there will be a giant blue banner across one of their clips. TRUST US, we will know if the clip hasn't been stabilized.. We were the one's that wanted it stabilized, so we'll be able to tell...
There are so many things overlooked, and I feel that focus is instead put on new features to get new customers, what about your existing customers and their needs?
The fact that I can't copy and paste audio plugins within the track mixer is crazy. Literally EVERY other program on the market can do this, it's a standard way of working with audio plugins.
Why is opacity defaulted to have a keyframe enabled? This has been an annoyance for many releases, as you'll see online from many different posts over the years.. Why hasn't this been changed? An example of not listening to customers.
Why is opacity defaulted on a clip in a timeline, instead of time remapping? How many times per editing session does your team when editing use opacity on a clip? I've NEVER used it; I do use time remapping in almost every editing timeline though. Isn't the point of efficient editing, to do a task in as few clicks as possible?
Why does Premiere Pro STILL interrupt your editing when it saves or autosaves? Why can't it be done in the background like other programs? If I'm watching the sequence, it would be great to simultaneously hit command+s and save the project in the background without interrupting playback..
If I nudge or move clips in a timeline while playing the sequence, Premiere stutters for a second, even though the area I'm playing was before the area that I made the changes on. Why does playback get interrupted? In other programs, playback isn't affected.
Reg Santo Tomas.... I appreciate your comments. However, you don't seem to understand the scope of pain that currently exists with many people using Premiere. NO NEW FEATURES should be added if you have thousands of reported problems in your bug database. I certainly understand that you have feature demands from your sales department and certainly lots of feature requests from users too..... but stability needs to be the paramount key feature. And it isn't right now..... not by a long shot. And yes, we understand that bugs cannot be solved without being able to recreate.... yet I feel that the QA team is failing you in this regard. Premiere needs to be tested on real-world large projects with 2 hour run times and 16TB of media. It needs to be tested on 2, 3 and 4 monitor setups. I don't feel that the complexity/sophistication of QA is sufficient right now. Last night alone (with the newest version). It took minutes to queue one render. Yes, like 2-3 minutes.... sometimes while getting NO visual feedback from AME that it hadn't crashed. Then, if I did get it queued, and started the render.... it would again go into a visual coma... again making me think that AME had crashed. Then, with a nearly identical project, on identical hardware, my render times for our film went from 60 minutes to 210 minutes. And both renders yesterday died at the 90 minute mark with 'unable to render frame' errors. I've now resorted to rendering out individual scenes and stitching them together after rendering an intermediate. I have a fast PC with 32gb of RAM. My media is on a 27TB local RAID 0 setup. Yet, even on sequences (that are not the whole film), Premiere still struggles to update the timeline on my screen. How can games render millions of polygons at 80fps with my GTX1070, yet Premiere struggles to maintain 3fps with a few thousand boxes and audio peak images? Like seriously WTF? It the code polling every single piece of media realtime for some kind of information? How inefficient is the timeline render algorithms? Premiere is so clunky right now, it screws up my ability to edit... using ALT to copy a media item doesn't work half the time because Premiere is chugging so slowly. Just look at how slowly Premiere takes to even close? I press the upper X and it takes an eternity in computer years before Premiere finally closes? ANd don't even get me started on workspaces. Premiere opens projects in seeminly random configurations on my 2 monitor setup. Sorry.... I'll stop ranting now..... I'd love to bring you my project and do a show and tell with all the engineers.... Let me know if Adobe is willing to cover the flight and hotel... I'll make the time. Or maybe Adobe would be willing to do a real-world feature film edit example on the big screen at NAB in Vegas?
A couple of points:
If you look at the last few releases, you may have noticed less features and more bug fixes and polish than in previous years. Even our major release at MAX contained hundreds of bug fixes including fixes to known crashes and other instability issues.
Now, of course, if we don't specifically address an issue you are encountering, that may not mean all that much. Understandably, this would be frustrating.
This is why we are asking for specific submissions. It isn't that we don't want to do our job. A lot of the issues reported have not been reproducible in-house. Reproduction is key in order for us to properly investigate and look in the code on what are the possible causes of instability or performance issues.
As Wes Howell on our team suggests, please engage with us.
While general threads about instability are important in making sure the team is aware that customers are running into issues - it is even more important that we fix those issues especially in cases where we don't have enough information for our engineers to properly investigate.
I would, however, push back on the notion that our team doesn't care about customer feedback.
We have implemented some of the requests and fixed issues specifically reported on this forum. No, we aren't going to be able to grant all the requests for obvious reasons, but we do listen and take your feedback very seriously
Premiere crashes, or freezes up all the time, at least once or twice during an editing session.
I'm looking for premiere not to crash! That's a feature we'd all love! Isn't that a great idea?
I'm on a brand new expensive high end PC. Premiere is extremely unstable. Checking this forum proves that Adobe doesn't care about customer feedback. There's SOOO many complaints about bugs and how Adobe focuses on new features instead of fixing what customers want; for Premiere to be STABLE.
PLEASE STOP ADDING NEW FEATURES AND INSTEAD WORK ON MAKING IT RUN SMOOTHLY. I don't need a new way to work with audio, or a new way to color correct. I DO NEED software that runs perfect, so my editing isn't interrupted.
The Premiere team loves to introduce new features and promote them, while simultaneously causing bugs with other stuff that used to work fine. Every release is like this. Something new that's got a cool name to it is introduced, and something old get's a bug, or Premiere freezes up.
This release for me, when I select audio and adjust audio gain, it won't let me press ok after adjusting a number. After a few moments, it works. Used to work fine, right away, now it doesn't!
Or when I have a lot of media in a timeline, if I use the select everything right tool and click and drag, then switch back to the regular tool, premiere freezes up for like 10-20 seconds sometimes. This used to not happen, now it does!
When I save a workspace, then adjust something and save again, when I restart, the workspace resets back to before I saved it.. Used to work fine, now it doesn't!
These 3 things I experienced today, there are others, and with each update it changes.
Please listen to your customers..... WE WANT A STABLE EDITING PROGRAM first, then new features.
At least 7x crashes today - running a 2018 MBP 6-core, firmware updated, everything updated specced out...
The bugs are hysterically bad ... plus the crashes, I have to re-start the program about once every half hour to avoid more crashes. I am starting to think I should go back to FCP or Avid ...
Nigel Jones commented
Regarding Wes Howell comments - it is good to know Adobe Quality team are listening - and yes, it is appropriate to collect specifics on why a crash occurred. But, but as other users comment below - this all takes our time and we are 'paying' monthly for this software as we speak. I would question why on new releases is Premiere Pro constantly stopping basic existing features from working ?.
As a side comment, I've also just had to post a basic problem on AME 2018 User Voice Forum which loads of other users have found. AME 2017 was fine.
Is this potentially a problem with lack of sufficient regression testing of new SW releases?. All these 'new features' might be nice, but you are not doing yourself any favours with your existing loyal customers by introducing a new release and causing mayhem. I would recommend senior Product Management for Adobe Premiere Pro stand back and say 'OK guys we are going to fix this for once and make it the most stable editing SW there is in the market ...' ....ok this might be unrealistic, but for goodness sake STOP trying to make your tick list of new features longer and longer just to make your glossy marketing brochure more impressive.
In the end this will catch up on Adobe and your reputation will be gone forever.
As a now retired R&D Director of Hardware and SW from the Telecomms sector, if we released new versions of code which screwed up existing working features our customers demanded fixes immediately and so we had 'total priority' on focusing on fixing those. Some issues may always slip through the door on a new release, but by seeing a better response from the Adobe team we will gain our confidence back in the Software and have more positive and pro-active comments on this forum about new features. I hope you get the message.
Thanks for the feedback, we are listening. We are actively working on addressing bugs and improving stability.
From an engineering perspective, detailed reports and projects that help us reproduce specific issues are one of the most effective ways to fast track fixes.
Do some of you have projects that crash often or have particular performance problems that you are willing to share? More specifically, any project that can be used to reproduce specific issues? I am willing to send hard drives to collect projects with media for internal testing purposes at Adobe.
I’m willing to investigate and follow up on specific issues and can also help with workflow and setup recommendations where applicable.
Real world user projects do contribute to fixes and improvements to Premiere Pro. If you have time and interest in participating in these efforts, please let me know.
Premiere Pro Quality Engineer
Kyle Schori commented
Crashing multiple times during rendering. Some of my error says the font isn't installed. I only use the ones listed on the menu. Go online and it's listed as synced. Worst software I've ever used. The older versions seemed to be fine.
Trevor Asquerthian I have a 'properly specced machine' and am editing a feature with Premiere. It's a pig. Incredibly slow with many issues that hurt productivity immensely. I'm speaking from direct experience. Premiere is not professional-grade in many ways. It could be if Adobe focused on stability and efficiency for a year instead of more features.
A million times, YES!!!! Reading the comments of this thread is soothing.... knowing that so many editors are suffering the same problems..... soloing audio tracks to get audio playback alive.... YES! I thought it was only me!
But isn't this disturbing to Adobe? We're all paying money every month and still Adobe seems to regard the feedback here as unimportant.... when it's quite critical actually.
I've demanding free months of Creative Cloud when hitting horrible bugs and I'm close to making that call again. Why am I even uncertain that it isn't deserved for all the users posting comments here? Where else would people willingly pay for a broken product month after month?
M L commented
I have 2 xeon workstations, Booth crash with regular intervals, throws render Error, wont Play Sound until random Channel is soloed and unsoloed.
I have had trickets opsende with adobe, aften support Remote logning in, they found nothing wrong software/hardwarewise. But That The crashes wire there. I have heard nothung since, Thisted Washington a year ago. I al switchimg to resolve.
I have used PP since 97... I have to strongly agree with it crashing. I have a more than required system with a great graphics card. I have to save my work every 10 minutes or so (by a new name) in order to get anything completed. Just today I worked for 10 minutes and decided I'd just do a save and not change the name... Boom crash... Couldn't save to the original name.
Now the one thing that may be causing this is the cloud.
I really don't want my work or need anything that is offered on the cloud.
So I have not signed up to set anything to use it.
If this is the problem, I would like someone to inform me...
+100, yes please.
Trevor Asquerthian commented
We need a more professional approach to this uservoice system.
Not sure how you'd be accredited but this kind of post is ridiculous.
Q: 'How are people supposed to create full cinema movies with constant crashes'
A: They don't. They have properly specced machines, properly maintained, with sensible workflows around media ingest & management.
Do they never get crashes? No, but lately it's been less than 1 per day for me and usually the app is back running where it was in a couple of minutes. Avid (with a chequered past in this regard) is even better than this these days. I'm not sure I can remember the last time Avid crashed on me.
Christopher Reynolds commented
Software crashes. I have been an editor for 33 years and before NLE the hardware crashed. VTR's stopped, edit controllers crashed. Avid crashes more than Premiere in my experience. Sure crashing is a pain but I suspect that your PC or mac may have something to do with it.
My mac pro system is very stable and I get a crash about every 10 hours or so and I would say that most often thats the mac running out of resources on a big project with lost of 4k layers, keying.
Blake Alley commented
You sure it isn't a problem with your specific hardware? Most editing machines are very stable with Premiere, but certain machines, either with outdated drivers or incorrect settings, will do what you are describing it as. My Hackintosh was extremely unstable until I changed the renderer to something else. Also see if there is other excess software hogging up your resources.
Please stop cluttering the list with useless entries like this
Definitely not normal. There are things I wish was more stable and efficient as well, but you definitely have either a driver conflict, failing hardware, or an errant plugin/preferences. For sure pursue the troubleshooting route.
For example: A few months ago I was having near constant export errors and program freezes -- turned out to be a dying video card.
WTF_ Common. And now after exporting my video my audio drops out at certain spots. This is not for real.