Participant

Answered

Premiere Pro 2020 won't playback and crashes

Forum|Forum|6 years ago
November 8, 2019
19 replies
11219 views

I recently updated to Premiere Pro 2020 and now all my projects won't work. While playing a sequence it will get stuck immediately and repeatedly display "A low-level exception occurred in Adobe Player (Player:6)" and will then freeze/crash and close itself sometime later after doing nothing. I recently updated my Macbook Pro to MacOS Catalina too. I've tried resetting preferences, uninstalling and reinstalling, ensuring my mac is fully up to date, restarting, etc. I need to work on projects urgently. Is anyone else having this problem?

Only other thing I can think of is when I updated to MacOS Catalina there were many old (pre Creative Cloud) Adobe apps that no longer worked so I deleted them. As far as I know I didnt delete anything backend that was required for the CC apps.

[Moved from generic Start/Help forum to the specific Program forum... Mod]
[To find a forum for your program please start at https://community.adobe.com/]

This topic has been closed for replies.

Correct answer David Arbor

It could definitely be format related. While I haven't gotten this error, I've been diving back into Premiere head first on a large project with over 500 GB of footage, most of it AVCHD UHD from a Sony a7R III and I haven't been thrilled with playback. I started using the native proxy workflow today and I'm so much happier: https://helpx.adobe.com/premiere-pro/kb/ingest-proxy-workflow-premiere-pro-cc-2015.html

I have a very beefy machine so I can get away with using the H.264 preset without lag, but I encourage you to look into that. You don't have to do anything other than right-click on a bunch of footage, choose Proxy > Create Proxies, then choose a preset and a location for your files. Premiere will transcode them in AME in the background and automatically start using proxies the moment they're transcoded. There is a button you can add to your Program monitor to toggle proxies on and off.

A few things to note (this is directly from the linked article):

• When you render Previews, Export Media or use certain Analysis effects (Warp Stabilizer, Rolling Shutter Repair, Morph Cut), Premiere Pro always uses and displays Full Res, regardless of the Toggle/Enable Proxies setting. The only exception is when you have Offline Full Res, but Proxy is Online, then Proxy is used.

So if you're using Warp Stabilizer or other effects your proxies won't be used. Also, if you're exporting you don't have to worry about disabling proxies—your full res media will always be used. This workflow has made me a much happier person today and Premiere is flying. Also, as a side note, I haven't experienced any instability or crashes in Pr 2020. The Premiere team has really made strides in the last year and it's showing.

J

jonnysix

Participant

Do we know what it is about the 2020 version that broke all of these things?

R Neil Haugen

Legend

In 2020 they removed a ton of older code, and also support for a lot of older gear. Both to work towards getting better stability on the gear it's currently designed to work with. Some of those changes have made difficulties for some users with older gear or media. Combined with Apple's Catalina giving a lot of apps headaches ... there's certainly been some issues.

And always ... when you rewrite a good share of a complex app, after releasing it you'll find there were some things with certain gear/media you didn't catch.

That said, most of us are working fine. Which doesn't help someone struggling.

If you are, create a new thread, list your gear, media, and general workflow steps and what's breaking for you. We'll try to help troubleshoot.

Neil

Everyone's mileage always varies ...

J

jonnysix

Participant

Thanks for the reasoned and helpful reply, sincerely. I posted in the heat of debugging after a couple of days of frustration and your reply was better than the comment deserved. I believe I tracked my issue to an out of date BIOS, but if it persists, I will follow your advice.

michaelf38377652

Participant

Solution for me : Change Audio Hardware from MME to ASIO

ramonw64294031

Participant

If i change to ASIO i cant playback the video. Do i need to change more settings? I have the same problem while play back a video in the edit screen adobe crashes!

S

Supernat10

Participating Frequently

Same here, only when using j, k, l to speed up/slow down playback. I am on a Mac with Mohave 10.14.6, so it is not a Catalina issue.

B

brianpf

Participant

My playback won't work at all. The app shows that it is playing, but it isn't, just sits there.

J

Javierlen

Participant

I just didn’t update and it keeps working. But if I update all hell brakes
lose. Figured will finish this project and then update

S

stephanieh96696927

Participant

I have the same error (low-level exception) and the player is stuck. mac os 10.13.6, no plugins. i reinstalled ppro 2019 to continue working, but now it appears i can´t open the project there, because it was saved in ppro 2020. any advice of how i can reproduce the project there? it´s already two days work ...

Joost van der Hoeven

Community Expert

A user posted a tool online that "will instantly convert (your project) to be openable in any older version of Premiere."

Use at your own risk, and make sure to create a back-up. This method is NOT supported by Adobe.

http://joshcluderay.com/downgrade-premiere-project-converter/

S

stephanieh96696927

Participant

super, this seems to work, thank you joost and josh!

A

aurelio pressplay

Participant

Same problem! Working on Premiere 2020, Mac OS Catalina and a Macbook Pro with 32 GB and i7.

It´s SO irritating!

What´s wrong with the new PPRO in combination with Catalina?

Hello, Adobe ?? I´m relying on this as i have clients waiting !!

R Neil Haugen

Legend

Catalina has been a major problem in and of itself. I routinely communicate with a number of colorists and participate on the LGG forum, also a colorist's haven. Many of them based in Resolve. And Catalina is not well liked by many of them. Sad to say. Apparently Catlina doesn't like Avid too much either.

So several took the painful step of rollling their OS back just to keep the shop working. But of course, others are getting along ok. OS changes can be a terrifying thing with deadlines. And I wish there was an obvious current fix.

Neil

Everyone's mileage always varies ...

D

daver51225565

Participating Frequently

I have now had this same problem occur while playing a Quicktime .mov file that originated from a completely different source (than from the JVC LS300 camera). Not syaing that .mov files are the deinite culprit, but it has not yet happened to me with any other file type.

Christian.Z

Community Expert

Here's an idea, uninstal everything adobe related using the Adobe Cleaner: https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

Let me know if this helps

D

daver51225565

Participating Frequently

Have started several new projects in Premiere 2020, have cleared cache, have reset preferences, and am not using any plugins at all... but still having the same problem upon playback of any footage from JVC LS300 (1080p60 .mov files). String of error messages appear: "A low-level exception occurred in: Adobe Player (Player:11)"

Playback of audio continues but video freezes and I am unable to continue to do anything in the app. The only option is to force quit - and a couple of times not even that has worked (I have had to hard reset my entire computer).

So I tried transcoding one of these clips from the JVC LS300 (originally shot: Quicktime 1920x1080, 60p, 50M XHQ format) to H.264 in Adobe Media Encoder. I then imported that clip and so far I have not encountered the errors yet... so possibly related to file formats..?

I'll keep experimenting and try recording some native AVCHD files in the same camera.

D

David ArborCorrect answer

Inspiring

It could definitely be format related. While I haven't gotten this error, I've been diving back into Premiere head first on a large project with over 500 GB of footage, most of it AVCHD UHD from a Sony a7R III and I haven't been thrilled with playback. I started using the native proxy workflow today and I'm so much happier: https://helpx.adobe.com/premiere-pro/kb/ingest-proxy-workflow-premiere-pro-cc-2015.html

I have a very beefy machine so I can get away with using the H.264 preset without lag, but I encourage you to look into that. You don't have to do anything other than right-click on a bunch of footage, choose Proxy > Create Proxies, then choose a preset and a location for your files. Premiere will transcode them in AME in the background and automatically start using proxies the moment they're transcoded. There is a button you can add to your Program monitor to toggle proxies on and off.

A few things to note (this is directly from the linked article):

• When you render Previews, Export Media or use certain Analysis effects (Warp Stabilizer, Rolling Shutter Repair, Morph Cut), Premiere Pro always uses and displays Full Res, regardless of the Toggle/Enable Proxies setting. The only exception is when you have Offline Full Res, but Proxy is Online, then Proxy is used.

So if you're using Warp Stabilizer or other effects your proxies won't be used. Also, if you're exporting you don't have to worry about disabling proxies—your full res media will always be used. This workflow has made me a much happier person today and Premiere is flying. Also, as a side note, I haven't experienced any instability or crashes in Pr 2020. The Premiere team has really made strides in the last year and it's showing.

D

daver51225565

Participating Frequently

Thanks for the tip - I think I knew this was an option but had never tried it. Will give it a shot and report back if I encounter same issue while using proxies or any other type of footage. So far only native .mov files from LS300 have triggered error. I've successfully edited footage from Panasonic GH3, GH5, and AC130 in same projects using Premiere 2020.

D

daver51225565

Participating Frequently

I have some 3rd party plug-ins (Magic Bullet) installed on my system, but no plug-ins are actually being used in any of my projects where the problem is occurring.

N

nicoemden

Participant

I had the same problem right after I re routed my plugins. I tried all (reseting preferences and cache, etc), but nothing worked. So I disabled all my plugins to see if those were causing this problem and BOOM! Came back to normal after that. Maybe it’s a 64-bit vs 32-bit compatibility issue. I ended up just enabeling the 2 plugins that I use the most and those didn't cause me any trouble. I imagine that the path to properly trouble shoot this would be to try every single one of your plugins and see which one is causing the issue. Maybe you can try big groups of them until some of those groups make Premiere fail, and then go more specific.
I hope this hepls 🙂

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded