bug premiere pro 2020
bug report on premiere pro 2020: playback stop while playing on timeline and then display message: "A low-level excerption occurred in: Adobe Player (Player:11)" - then Premiere crash, and i have to force quit from force quit application. i'm working on a MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports), 3,5 GHz Intel Core i7,
Corban Monger commented
I HAVE FOUND A WORKAROUND:
I only get this error when my Premiere project file is opened OVER THE NETWORK. I can add footage from my NAS and still edit with no problem but the *.prproj file must be on a LOCAL drive.
I would advise everyone with this issue try transferring their project to a local drive and open it from there and see if you still get this error.
潔霖 莊 commented
I can't open new project files in older version.....
hi there folks,
Just to let you know that the problem wasn´t in my Nvidia driver.
Premiere update to 14.1 was buggy.
Then I reverted to 14.0.4 through Adobe Cloud and everything is nice now (except for one day without editing).
Just go to 3 dots - other versions - click previous version and INSTALL.
When changing the option Acceleration from CUDA to OPEN CL the error switched from:
low-level exception ocurred in: Mercury GPU ... (accelerated renderer 2)
low-level exception occured in: Adobe player (player: 76)
When switching to software acceleration, the error stopped but the titles aren't working.
Will switch back my nvidia driver to the previous version.
It happen to me after I upgraded my video driver Nvidia 445.87 from apr-15-2020. I will try to switch back to my old driver and get back here (but will try the mercury software option by Robert Poissant).
Robert Poissant commented
UPDATE!!! A temporary solution for me is to switch the renderer from Mercury Playback GPU Acceleration Metal to Mercury Playback Engine Software...
Same error as all of the above, started happening upon the most recent update....working on MacBook Pro (15-inch, 2017), 2.8 GHz Quad-Core Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 555 2 GB Intel HD Graphics 630 1536 MB
Please help ASAP!!!
ROBIN MCCAIN commented
I remember sitting in a room at BAVC in early 2003 when the Adobe people told us that they were completely redesigning Premiere as a Windows only release. (This was because Adobe was upset with the Final Cut launch shortly before). At that time they tied the visuals to the Microsoft toolkit. That was 17 years ago, and there have been many changes to Microsoft's development tools. After a few years Adobe expanded the PP release to once again include the Mac OS and must have made some developer code changes at that time.
My guess is that Adobe has not really made too many changes at the back end since then, so much of the backbone video code is stuck somewhere around 2006 before GPUs were a major consideration. That is probably why we can turn off GPU acceleration and PP will then work (slowly).
Well - wake up Adobe - today it is a GPU world!
Tim Strube commented
"If you can reliably reproduce the ‘low level exception’ problem..." – same exact problem here and I'm blown away that Adobe can't seem to "reproduce" this or address it, or was somehow caught off-guard by it. It's happening to every (repeat: EVERY) editor I know who's currently remote and working on a Macbook, Mac Mini, or iMac.
Edit: I should add that this happened to me without any Legacy Titles. Just a standard Apple ProRes proxy, and a single music track (WAV). That's all it took.
JACQUES VILLIERES commented
ADOBE, when can we expect a solution?
Jake Tran commented
I had this problem when v14.0 came out, reverted back to v13 which is full of its own bugs and crashes, gave it many months then tried the new v14.1 today and still the same problem.
This is absolutely absurd that I pay so much for an app that I can't even use the latest version of.
No, turning off GPU acceleration isn't a viable option, Adobe. Stop recommending that "solution".
Windows 10 Pro
i7-6700k, not OC
GTX 1060 6gb
Ben Butt commented
Adobe - what an earth is going on. I am now in a position where I cannot backtrack. This is a terrible problem to have wth a major update. Really need to sort your **** out!!!
Adam Kortepeter commented
For those newcomers to this thread who are still experiencing this problem - The only successful resolution for this if you have legacy titles in your timeline is apparently to reinstall an older release of Premiere 2020. Rolling back to 14.0.1 seems to resolve this error and permit the use of GPU playback. I wish Adobe would have a better fix for this, but apparently they have not figured out how to reliably reproduce the problem. Alternatively, if you don't have many legacy titles, you could replace them with the new text tool or imported AfterEffects titles.
FYI Rolling back to an earlier version may break the dynamic link connection to other Adobe applications, such as Audition or AfterEffects, so you may need to also roll back to equivalent versions of those apps you link out to from within Premiere.
Hope this helps!
Mauro Silva commented
Having the same issue. It has become unbearable and unable to edit for days now. On macbook pro, 6 core Intel Core I9, 32GB Ram, Radeon Pro 560X 4GB
Xavier Miranda commented
I'm having the same problem. I can't edit anything anymore and I really really need it fixed.
Liam Richards commented
When will this be fixed? Only this month I am now having this problem and it’s on every single file, even when I don’t import anything into a project and just click create title, it doesn’t let me!
Tobias Schnepf commented
Bei mir gibt es keine Audiospur!
Nathan B commented
“ We’re eager to pursue the issue further.”
We’re eager for a fix. It’s great there’re workarounds — but we shouldn’t have to interrupt our work with troubleshooting.
My discovered fixes - roll back to 14.0.1 or beta test latest 2020 in CC
-alt click logo to wipe prefs
— either way necessitates using adobes basic font types. I’ve had to reposition and reset 70+ title plates due to legacy titler ERROR
DuVerne Rutherford commented
@Mats Blixt Thanks.
Mats Blixt commented
@DuVerne Rutherford 14.1 introduced the problem to me, immediately upon opening the first project after updating. Currently running 14.0.4, "works" for me... *knocks on lots of wood*
DuVerne Rutherford commented
Adobe Cloud Subscribers:
The easiest fix is to simply downgrade to version 14.0.1. To do this, open the Adobe Cloud application, navigate to Premier Pro and click on the small dots next to the Open or Upgrade button. You can remove the current version or keep it but, more importantly, you can select other versions. I installed version 14.0.1 and it is working fine. This got me back to a functional state while I wait for Adobe to find solutions. On that note, has anyone tried version 14.1? I noticed its availability today and wondered if it works or has the same problems. . .