Open captions have been extremely buggy in all of the most recent Premiere Pro updates for some time now. There NEEDS to be a fix to open captions not exporting consistently. In the past, I've had to nest my captions, pre-render in-to-out, and then export in Premiere, rather than Media Encoder, and it MAYBE works. This is unacceptable in the day and age when Facebook video is king, and captions are becoming a necessity for effective marketing. Premiere is making it consistently difficult to do my job efficiently and on-time.

Premiere Pro becomes less and less stable to work with. 2019 has seen the worst versions so far. It's already a running joke with EVERY single filmmaker I meet.

It's buggy, lagging and keeps crashing and wasting the time I should spend working for my client rather than trying to fix all kinds of things with crazy work-around solutions other Adobe customers come up with.

I'm dreaming of the day Premiere Pro is as stable as Photoshop but I guess I will have switched to DaVinci Resolve before that happens.

I've been at work for about an hour and fifteen minutes today, and Premiere has crashed three times so far. I'm not asking a lot of the program, I'm just doing the workflow I've been doing for the last month. This is now worse than Final Cut Pro was when I switched to Premiere a decade ago. What am I gonna do now, switch to Vegas?

Of course, if you are still encountering specific crashes, feel free to report them with specific steps on how to reproduce them. Posts that say the app crashes aren’t actionable by the team especially when the thread describes multiple scenarios.

Crash logs are helpful especially in combination with reproducible steps and system information.

I haven't had this many issues with Premiere since CS6. This update is simply awful and needs fixing fast!

The font issue. Invalid fonts? Should have been fixed with the first complaints months ago.

Rendering stalls out and you need to force quit. Re-open and render again - no problem. This shouldn't happen.

When opening sequences, sometimes the track are all muted (even though the mute button isn't on). The only fix for this is to solo a track and then un-solo it and it works. But if you open a sequence and export it while tracks are invisibly muted, no sound is exported and you need to start again.

Please fix this Adobe or at least recognize that these are serious issue which affect people who use your software to make a living.

I haven't had this many issues with Premiere since CS6. This update is simply awful and needs fixing fast!

The font issue. Invalid fonts? Should have been fixed with the first complaints months ago.

Rendering stalls out and you need to force quit. Re-open and render again - no problem. This shouldn't happen.

When opening sequences, sometimes the track are all muted (even though the mute button isn't on). The only fix for this is to solo a track and then un-solo it and it works. But if you open a sequence and export it while tracks are invisibly muted,…

Adobe needs to implement a roll back feature that simplifies rolling back when an update goes wrong like the new one just rolled out. I'm dead in the water, have hours of video to edit, but PP is useless at this point even though I'm paying for something I can not use. At this point I've lost 5 hours or more of editing time that I will never get back and never get paid for and I have no clue as to when Adobe will fix the problems. This is absolutely unacceptable!

As other commenters have pointed out, it’s possible to roll back using Creative Cloud desktop.

Not sure how that file got damaged; If you can reproduce the problem in current builds of PPro, please contact Support and provide step-by-step instructions on how to reproduce it; we’d be happy to help.

Who cares if this is not "actionable." Adobe, do you see how many requests you're getting to make Premiere stable? Even Philip Bloom called you out. It crashes constantly and for no apparent reason. Either stop charging us money for your bad programming or use our money to make your program better

We continue to address issues reported here on User Voice, and as that’s the only way to keep the conversation productive, I will indeed have to close this general statement as non-actionable. I’d like to encourage you to report on issues that you run into and enter single, actionable items instead.

This is a general statement for general purpose work – the higher you go on resolution, the more you use mixed input formats and not a dedicated format for ingest or proxies, the more you’ll benefit from using a machine that is using what’s recommended vs. minimum.

For those reporting general slowness: I suggest to start a new thread on that topic. This might be more of a workflow conversation than anything else, but let’s treat that as a separate item. Sometimes it’s good to take a closer look at input formats (something like 10 bit HEVC 422 isn’t great for playback, ProRes 422 on the other hand is fast and smooth – just an example). Sometimes it’s best to double check that GPU acceleration is indeed enabled and all the latest drivers are in place.

Cheers,
Patrick

We continue to address issues reported here on User Voice, and as that’s the only way to keep the conversation productive, I will indeed have to close this general statement as non-actionable. I’d like to encourage you to report on issues that you run into and enter single, actionable items instead.

i just had contact with support regarding super slow rendering times – they referred me here.
i convert an h264 to a cropped png sequence, no effects applied (except the cropping).
if i do this in premiere or ae, it takes at least 2 hours and only utilises a fraction of my cpu. if i do the very same operation via ffmpeg (cli), it's done in less then 7 minutes. attached you'll find screenshots of the two procedures, note the render times (as said, same task, same machine, same result).

is this expected behaviour (because cc simply does not work on more then one core/thread) or a bug (and something can be done about it)?

i just had contact with support regarding super slow rendering times – they referred me here.
i convert an h264 to a cropped png sequence, no effects applied (except the cropping).
if i do this in premiere or ae, it takes at least 2 hours and only utilises a fraction of my cpu. if i do the very same operation via ffmpeg (cli), it's done in less then 7 minutes. attached you'll find screenshots of the two procedures, note the render times (as said, same task, same machine, same result).

SO sick of Premiere crashing. It is seemingly random so I cannot give any specific reasons.
Sometimes I haven't touched anything and the whole thing just closes (doesn't freeze, just disappears as if the program isn't open).
Sometimes it freezes while just hitting the space bar, sometimes when I save it crashes ie. it doesn't save and I lose everything!

As of the last update it hasn't been saving properly either (I have autosave set to 10mins but also manually do it constantly) so I have lost hours of work and a whole head of hair. It's doing my head in.

I'm on version 12.1.0 (build 186) and using macOS High Sierra 10.13.3 on one of the top spec/latest iMacs.

SO sick of Premiere crashing. It is seemingly random so I cannot give any specific reasons.
Sometimes I haven't touched anything and the whole thing just closes (doesn't freeze, just disappears as if the program isn't open).
Sometimes it freezes while just hitting the space bar, sometimes when I save it crashes ie. it doesn't save and I lose everything!

As of the last update it hasn't been saving properly either (I have autosave set to 10mins but also manually do it constantly) so I have lost hours of work and a whole head of hair. It's doing my head…

After updating to the newest version (13.0.1) it happens once a while, that Premiere Pro shuts off without warning, error message or anything similar. It happens at any time (like playback), it is NOT connected to any heavy processing. It is very annoying. Maybe it happens when it wants to do auto-save but I am not sure about it (but I am sure, that when it happens my last auto save is very long time ago...)