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,
We do monitor User Voice; we share your disappointment that we don’t have a reproducible case, for this issue.
If you can reliably reproduce the ‘low level exception’ problem, on your system, please contact Support and provide them with any files and source media required for that repro case, as well as (important!) step-by-step instructions on how you can reproduce the issue.
We’re eager to pursue the issue further.
I’ve been using Premiere since version 6 (yes I’m ancient). There have always been problems but often we could avoid this with cleanly managed systems (dedicated drives for OS, scratches, media, etc) , and keeping the OS updated and patched. But ever since a version or two ago, I too get Low Level Exception errors despite doing everything right with my machines. The error seems to occur randomly but i do notice that it’s especially more common when any Audio effects are applied. Often restarting Premiere fixes it but not always. It’s frustrating and only 1 issue we’re constantly dealing with.
Support is, to be frank, useless. Half the time it’s like talking to a bot. Language barriers and them simply not being able to reproduce the issue makes support kinda not helpful. And unless they happen to have the exact same computer system with the exact same hardware specs, drivers, etc, they often cannot reproduce a problem - which doesn’t mean the problem doesn’t exist, as evidenced by the numerous complaints on here.
Wagner Gonçalves de Oliveira Junior commented
this is unacceptable.
Jack Federman commented
Legacy Title is broken.
I get Low Level Exceptions on every project I work on in premiere.
Constant crashing, and lag due to adding one effect to a timeline.
Get your **** together Adobe, jesus christ.
Jim Granato commented
Rack one more (long time) user up there experiencing this problem. I first encountered it after updating to 14.1 a few months ago then quickly reverting back to 14.0 Well, the issue went away for awhile and now as I am just looking to perform simple cuts, voila, it's back! I'm not even using "legacy Title". I am just combing through h264 and prores video (combined) on my timeline.
I, too, can't believe its been this long (and with this many complaints) that this issue has not been resolved yet. One "quick fix" that has worked for some is to change the renderer (under Fle>Project Settings>General) to Mercury Playback Software Only. Well, the spinning color wheel went for a long time after selecting that. I had to force quit and restart twice. Here's to hoping I don't have to revert back to older versions again. Indeed, that is a drag when you have multiple project files in which I am presently working with. UGH.
iMac Retina 5k, 27in, 2019
3.7 GHz Intel Core i5
memory 32 gb 2667 MHz DDR4
Radeon Pro 580X 8 GB Graphics
It is probably a matter of this tool being so old that no one currently working at Adobe has a clue how it really works. That means they will need to hire someone specifically to rebuild it from the bottom up using current algorithms and interface specs for all platforms.
As for reproducing its behaviors, all you need to do is to open an existing title and see how the columns in the window move to the right. The columns must be manually moved to the left so you can see enough of the far right column to change the fonts, sizes, shadows, etc. This happens every time...
Sergiu Mihalache commented
Obviously, the more we pay, the less they will do; why do something if the money is coming in a constant stream (or, better said, river) anyway?
John Myers commented
Adobe is failing us again. How much money in subscriptions do we have to pay to continue beta testing for your products?
Yes, that is why it is called the LEGACY Titler. Unfortunately, it is still the best choice for many creative tasks. The new titler seems to be designed for closed captioning and does not have the features one would expect from a full service titler. Someone at Adobe seems to think that we should now design titles in After Effects. While this might be a good choice for really fancy high end projects, it does not meet the needs of people who need a quick & dirty titler.
Zheng Wang commented
I've been having this problem with older projects. Reliably, it's ALWAYS when there is an item on the timeline made with the old titler. If I delete those old titles from the timeline and restart Premiere, everything is fine.
Ziemowt Jaworski commented
In many different platforms, different OS the problem persist. I personally heard about at least 10. The easiest way to reproduce is to heavy scrub for a while (bac and forth with speed changes) on a H264 mp4 file. I bet it will crash after while on most of computers.
Robin McCain commented
Yeah, I had a problem exporting to h.264 and MPEG2 recently. Dissolves were not smooth but jerky. Turns out you need to check updates pending. Update the operating system, antivirus, graphics driver and Adobe stuff. Interactions between versions are so tricky that it is imperative that all the software versions are compatible.
T R commented
Sorry Adobe, this is unacceptable.
I am teaching an introductory class in video editing at university. I now have had several students complain that they cannot export h.264 anymore, which is one of the most central functions of any editing application.
TONS of people here seem to be unable to get rid of this problem, yet you claim you are not even able to reproduce it? Are you testing your software at all before you ship it?
It's 2020 and you charge money for an editing application that cannot reliably play back or export h.264 videos? Seriously?
Ursula Zach commented
Big problem with Export: It´s written: low level exception - can´t export with H.264. System stopps.
I switched back to version 2019 - now it works. That can´t be the solution!??
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!!!
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!