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.
They made sure you can't do that, as soon as you want to stop paying them, they will only take more money off your card.
One thing they do know is how to take our money.
I think we have to stop paying them untill they provide a vision of their plan toward a solution to our problems!
It doesn't matter how easy it is to reproduce the bug, because Adobe doesn't care! They shut down their "support" (well, it's theoretically "currently experiencing long wait times", yet you don't have an option to wait at all) and will not accept complaints filed in any other way. So basically they are telling us to bugger off with out problems, they don't care.
But do they care about taking our money? YES!!! Do you want to cancel your subscription now, since you can't use the software? Pay Adobe half the yearly plan and you can cancel it. I feel like I should be the one getting money back for all the time I kept paying for a software that doesn't work, but who cares what I think, certainly not Adobe!
Clayton Cupples commented
I have a brand new HP computer and a fresh install of Premiere Pro. I have not been able to do the simplest edit so far without this error. FIX IT!!! Adobe has just made a deal with the education department in Victoria Australia and many kids in 'lockdown' are going to be downloading and trying to use this software only to go insane with this bug! Expect this issue to persist until you FIX IT!
Jessica Lamont commented
Hey folks. It seems like it's getting to a point where people are expressing their concerns over Adobes effort into this issue. I don't use Premiere Pro for work myself, but I'm not happy about how this issue is being handled either. Yesterday I tweeted Adobe about the issue with a link to this forum post included, and so far I got a much quicker response than from this. If anyone would also like to air their concerns about this bug with Adobe, Twitter or other social media seems to be the best bet.
Lauren Pushkin commented
My quick fix, after reading this thread, is to take out the titles. It's definitely a problem with legacy tool. When exporting with titles, my 6 min sequence took 60 mins and then was unreadable. It became a 24.98 fps sequence. Once I took the titles out (I only had them in as placement titles - so created final ones is AE and replaced them) the seq took 6 mins to export and was fine. Obviously this is a ridiculous workaround, but am pleased I can pinpoint where the issue is coming from.
This is unbeleavable, can you see the list of people experiencing problems? And you are still asking for evidence of it!!!!
My GPU acceleration is still not working, what do you need more? You want me to stop paying you and use a competitor software?
I cannot beleave that ADOBE is doing this way.
Mats Blixt commented
Still nothing! This is just sad and embarrassing! Ever since Adobe started with their software subscriptions, I have felt like a "beta tester"! And I am sick and tired of it!
Adam Kortepeter commented
Here's a quick rundown on how to reproduce the issue:
My System info:
HP Z840 Workstation
1 TB SSD (OS), 1 TB secondary SSD
128 GB RAM
Dual-Xeon CPU ES-2620 v3
NVIDIA M6000 GPU w/ 24GB GDDR5 dedicated video memory
(3072 CUDA cores, Nvidia driver version 442.92, Video BIOS version 84.400.4C.00.02, PCI Express x16 gen 3 slot)
Windows 10 Professional 10.0.18363 Build 18363
Step 1: Create a new Project
Step 2: Make new Legacy Title. Standard HD 1920x1080 is fine.
Step 3: Type any text into title area and close dialog.
Step 4: Drag legacy Title to timeline in any track
Error appears immediately as soon as you drag Title 01 to the timeline:
"A low-level Exception Occurred in: Adobe Player (Player 6)"
Error repeats as many times as you attempt to play the timeline, or add another title to the timeline.
Does that about sum it up for everyone? Are there any other ways to get this error I haven't accounted for?
LEE MCEACHERN Jr commented
Adobe, I don't know how to do software engineering; I know how to make a video. And I've been making video with the help of your software for this long: You hired me to produce the first marketing video ever made for Premiere. Very first version. It was hard because I had to get out of my videotape editing suite and learn what we then called nonlinear editing to do it. I was editing in your basement and your software crashed constantly. I had to spend as much time writing up crash reports as I did editing and I had to find a way through that in order to deliver a video to you on time. All of that didn’t make me angry; I understood. Creating an ambitious new product like Premiere is extremely challenging and bugs are going to be a part of it. Many year later I still rely on Premiere (Pro CC) as a mature and mostly rock-solid editing system that has been a big part of my career. But today, Adobe, I feel like you just don't care enough about the users of your product. If you really cared you would be proactive and so concerned about the people who continue to pay your monthly fees that you wouldn't post something that says, basically, "This isn’t a problem we’re going to worry too much about because we haven't seen it here. We haven’t heard enough. So, we're going to wait until one of you complainers sends us something better to work with." But you know, Adobe, I see reports of this bug going back to November. Many, many consistent reports since then. Certainly in my studio, too. I'm shut down. This is serious, Adobe. It's having severe effects on your customers. Loyal customers. How about showing some loyalty in return? With enough effort, I know you could run this to ground. You are the software engineers; you know this stuff so much better than we do. I guess this bug might be hard to fix. OK, sometimes I have some really hard problems that take me a long time to figure out, with minimal information to work on. But my income depends on how well I perform. My career depends on it. I have to do it.
You have to do it.
Adam Kortepeter commented
I have been working on and off with Adobe products over 20 years now, and I must say that they have never been particularly strong on user documentation. It has always been "go to the forum and maybe you'll get lucky and some user who has wasted more time trying to figure this out might be able to help you." The problem with that notion is (A) it means a bunch of people who are not Adobe employees are all wracking their brains trying to come up with a workaround, but (B) nobody on the forums can actually fix the code.
If it's really a bug, all you see is a multitude of unanswered posts about the same problem. The forum is ultimately useless for finding a real fix, but that is always the first thing Adobe tells you to do regardless. Only Adobe can fix a bug. They are responsible for it, and they should be the ones to fix it.
This is a huge weakness - a major failing in the product/service philosophy, in my humble opinion. With the change to a subscription model, I feel like the focus has shifted to pushing out the next release, and not so much ensuring that it ACTUALLY WORKS. They should be beta testing before they make the rest of us use it. If it's not ready, it shouldn't be released. CUDA is a component of the software we all depend on to get things done. It should not be an option for this to fail in the way that it has. I would be more forgiving if the new features were more buggy than if the old ones I rely on to do my job suddenly stop functioning. My boss just doesn't understand when I can't get something done with the same software that worked fine a week ago.
As with any machine - the more moving parts it has, the higher the likelihood that one of them will break. We should not be "beta testing" unstable releases when we have projects that need to get out the door on a deadline. It should be stable before it gets rolled out to all subscribers. I'm inclined to recommend to my employer that we don't install any updates from adobe for at least 6 months, but honestly I shouldn't have to. Adobe should be more careful. Just my thoughts.
ROBIN MCCAIN commented
Unfortunately, "Legacy Title" really does seem to mean something leftover from long ago that users do not want to let go of... The new titling tools do not meet users needs in many ways, so Adobe has been forced to retain it. What this probably means is that the programmer who created it and knew "the recipe" left the company long ago and no one currently working at Adobe knows how to fix it.
So, until one of the programmers is assigned the task of either comprehensively updating the tool or throwing it out and creating a new replacement, fixes will continue to be "band-aids" that break easily.
And how exactly are we supposed to "contact support" when support is unavailable since weeks (I have reported this too, but nobody seems to care)? All I get is "Our support center is currently experiencing long wait times. Skip the queues and reach us in the Community." - how are we to "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."
It's so easy to blame someone else...
Somehow I get this problem with clips shot on a Sony AX53 camcorder, Samsung Galaxy S10 smartphone and recorded by Skype (through their Android app), yet the whole team at the gigantic (money hog) Adobe has not been able to find one clip that reproduces the issue. Have you even tried???
Paolo Citrini commented
Si apre il progetto..ma continua a fermarsi...su un motion graphics
Such incompetence! Or maybe just hiding laziness behind incompetence and drinking margaritas on a beach, all paid by the users' money?
The problem is easily reproducible when putting any legacy title on a track above a video file. After so many users complained about this problem being generated by legacy titles, have you tried using one?? What the **** are we paying you for every month?
Hervé SIFFERLIN commented
Bug Premier Pro
"A low-level exception occurred in : Adobe Player ( Player:6)"
"A low-level exception occurred in : Adobe Player ( Player:79)"
"A low-level exception occurred in : Adobe Player ( Player:83)"
Nom du modèle : iMac
Identifiant du modèle : iMac19,1
Nom du processeur : 8-Core Intel Core i9
Vitesse du processeur : 3,6 GHz
Nombre de processeurs : 1
Nombre total de cœurs : 8
Cache de niveau 2 (par cœur) : 256 Ko
Cache de niveau 3 : 16 Mo
Technologie Hyper-Threading : Activé
Mémoire : 40 Go
DuVerne Rutherford commented
Create a new project. Create a legacy title through File>New>Legacy Title. Add the new title to your timeline. Make an mp4 with your cell phone and drop it in your timeline. This is the recipe. I downgraded to version 14.0.1 (Build71) and the problems are gone. Whatever is wrong was introduced after this version. Sorry I cannot provide more help but I had to start over three times and I no longer have the offending .prproj files.
I have the same problem since weeks! I DO NOT SEE ANY FEED BACK FROM ADOBE! We cannot accept this behavior from them
Dennis St. John commented
Regina, I have been monitoring this thread for a while now and it is very apparent to me that Adobe does not monitor this forum. The only thing I would recommend is downgrading (or actually upgrading, if you will) to PP 2019. That solved my issues entirely!
Regina Rivard commented
Everyone that did this upgrade at my work is having problems with this. We have screaming fast machines and this bug isn't letting us utilize them. What can we do as users to help get this problem the attention it needs to get fixed? Is there someone else we should be reaching out to?