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,
enrico stocco
shared this idea
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.
242 comments
-
Chris Spiegl
commented
This is incredibly annoying. I am having this experience with my MacBook Pro 2017 with macOS Big Sur and it happens with and without my external monitor.
And in the realm of asking for a reproducible set of files: if I'd know I would simply not do what triggers the exception… but it's so random that it is completely unpredictable. I don't get it.
Please Adobe 🌸 fix this! As it actually has continued to happen even in PP2021!
-
Darren Manden
commented
I'm just curious how we are meant to contact "support"?
The old AE beta forums were amazing, as you could file proper bug reports that were definitely looked into by Adobe (crazy, I know!). But I'm not entirely sure how we are meant to do that with Premiere.
I know that there are definitely a lot of people on here who would happily file detailed bug reports if such support existed for Premiere.
User Voice is obviously a black hole of (absolutely warranted) user frustration, so having a place to file actual reports that don't just get flat out ignored would be great.
-
Mike Mc
commented
This original post ought to be closed if it's ben fixed, as this was many versions earlier, and last year.
Use OBS to screen record while working with Premiere. When something goes awry, upload to YouTube as Unlisted, and post a link to the video here, in the post.
-
T R
commented
@Wes Howell, you must be kidding, right?
This problem has been around for almost *a year* now. It is a huge issue *and* it affects a lot of users.For almost a year I cannot simply fast forward in my editing software. In 2020. This is just mind blowing. Not only can I not do it, no, it makes the software crash in a spectacular fashion.
Every ****** freeware editing tool is perfectly capable of fast forwarding my videos, your "premium" software for premium pricing is not.I am not the only one to have this issue. Lots of my students have this issue. No, I don't know what exact configuration is causing the problem and frankly, I don't see it as my job to figure that out for you. If so many users *still* have this issue, it's not caused by some obscure "niche configuration" that only some users will be affected by, it's appearing all over the place.
It's unbelievable that Adobe apparently cannot reproduce this problem. So unbelievable that in fact, I do not actually believe that Adobe has done any effort to reproduce it. There are so many people with this issue, I am sure if you would have tested it on just a few different systems, you would have come across this problem pretty soon.
Instead there is no communication for most of the time and if there is, it's just some "we are sorry, bla bla, working on it bla bla".
Last week we had to plan for the new semester at my university. Even though it means a lot of initial extra work for us, we decided to switch the university's entire editing workflow to DaVinci Resolve and abandon Adobe Premiere. Oh, excuse me, Adobe Premiere *Pro*. The Pro stands for "cannot fast forward".
This is *such* an unprofessional handling to such premium pricing that I just can't get over how bad it is. This should have been your number 1 priority to get fixed and it still hasn't happened for almost a year now and there is just no excuse for it, especially with such a huge company behind the product.
-
Sorry to hear that this issue is still affecting some of you. We are here and we'd like to help.
There are many different factors that could contribute to this issue. System, GPU, Hardware Decode settings and of course format is a big one. Have any of your been able to isolate the key factors here? As Reg mentioned, support is ready and available to assist. We have great people in support that will be more than happy to help troubleshoot any of these issues.
Can someone provide simple steps and possibly a small project that could be used to isolate and reproduce this on the Adobe side?
-
Ms M Anker
commented
Keep getting the same error here on an imac
-
Kay
commented
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.
Jim G.
iMac Retina 5k, 27in, 2019
3.7 GHz Intel Core i5
memory 32 gb 2667 MHz DDR4
Radeon Pro 580X 8 GB Graphics -
ROBIN MCCAIN
commented
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?
-
ROBIN MCCAIN
commented
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.
version: v14.2I 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.
