Try using your own software
I'm being serious. Using Premiere over the past few years makes it painfully obvious that not enough people at Adobe are using Premiere. It's so buggy now that I'm embarrassed to use it in front of other people.
Divert some engineers to actually make some videos with the product. Real videos, not simple vlog stuff. You'll see how miserable the experience has become. I don't believe you could release such unreliable software if you actually had to deal with using it.
I'm confident this thread will be taken down just like all the other people who have told you to focus on stability. But while you're taking this down, maybe think about why so many people are saying the same thing. I use Premiere every day and have never gone a full day without multiple major issues. I use more than one computer and I use both Windows and Mac, so this is not isolated to a specific system issue. This is a complete lack of commitment to testing your own product.
We do use our own software, thanks!
If you’d like help with those major issues, please contact Support and provide step-by-step instructions on how to reproduce it; we’d be happy to help.
clemens rehwald commented
honstly BRUCE , that was an extreme weak answer and reaction.
You , and every staff at adobe knows that you are working on stability improvements since the catastrophic cc18.
You claim yourself that the crashes have been significantly reduced since CC18.
You know that we still cannot playback simple 4K files without dropping frames .
You can read all the other threads about all the same issues related to mobile graphics / about Quadro-cards and so on.
Despite that ...your answer is..... we are using our own software .... if that would be true... you would be able to simply reproduce 90% of all reported issues easily ...but you where not...
I have spent now more then 2 years in desperate investigation to get this software to get to work in a high professional environment...and it still is impossible on 5 different machines , each of them 5-12K € . Only an IMacPro could come closer to a stable productionenvironment.
And I fully agree with a 2 year very successful experience in switching to DavinciResolve (no aggravating .. simply reproducable technical experience).
NO, Bruce, that was not a reaction worth regaining in a trusted relationship to adobe .
Evond Blake commented
You guys!!!! Please listen to me. Adobe doesn't care about us, they are making money. PLEASE take a day to learn Davinci Resolve 16 and SWITCH!!! It can do everything Premiere can do and so so much more. You will be leaving behind errors, crashes and slow performance. I did it and I'll never look back!!!
Marcus Koch commented
Bruce, maybe consider a bug hunting bounty. It is already frustrating to deal with issues and loose valuable work and life time. We pay a monthly fee just to open our old projects. So why shall we spend more time for free to write detailed bug reports. You don't work for free, so don't ask your customers to work for free. Either you do the work to reproduce an error on your own or you pay your customers for doing that work.
Also if a bug is not fixed within a reasonable time frame, teh effected customer should pay less for as long as the bug is fixed. This would lead to happy customers and better products for a little reduction of the revenue of stock holders. :-)
Alex Elkins commented
@Bruce (and anyone else from Adobe who has taken exception to this thread...)
Please take this seriously. I know it's been expressed in a negative way but people here aren't just talking about bugs that we can reproduce for you. It's all sorts of things that professional editors working on big projects expect that the folks at Adobe seem to have no idea about.
Here are some examples from my work today:
Syncing audio requires a shonky workaround (multicam) that puts a YELLOW BOX AROUND EVERY CLIP. ARE YOU GUYS SERIOUS!?
Audio clips don't display mic labels and there's no way to update synced clips with scene/take metadata. This is basic stuff for anyone used to cutting drama or commercials in Avid (or even Resolve now).
Subtitles are totally dysfunctional.
Video output via Blackmagic cards doesn't handle scaling properly (and Adobe keep passing the buck on this one despite it working perfectly in all other software).
Burn ins are amazingly limited. Let us add any piece of metadata into a burn-in.
This is what people mean when they tell you to try using your own software. Anybody using it in a serious way understands these limitations and finds them infuriating. The general impression people are forming about Adobe is that you guys have no idea how much you don't know. At least with Avid, for all its faults, we can trust that the people in charge are usually heading in the right direction. I desperately want to trust Adobe in the same way because it's a much nicer experience to work in Premiere! You need to hire some experienced editors and assistants to consult for you because it's very obvious that the people in charge have no idea about all of this stuff - if they did it'd all be sorted years ago.
paul wedel commented
So agree!! It's so obvious that we are all getting to pay for the privilege of testing their buggy AF software. They should be paying me $69AUD a month thanks. Noticed this thread is from 2018 and it's actually gotten worse in the last year.
13.1.4 is possibly the worst update they've ever released. It's actually unbelievable. Where are they on the list of Worst Companies in the World? But they don't read these threads or even care about their user base, so I can say whatever I want here hahahah fukyou hahah!
@Clement Batifoulier Now THAT would be quite the 'New' feature, wouldn't it?!!! ;) Fully agree!
If they add any new features, and I certainly think they should, these new features should be very small tweaks that help improve editing workflows, without the risk of breaking something else. For example, adding new keyboard shortcuts for adding any effect to a selected clip, as Taran has created hacks for, etc.
Clement Batifoulier commented
i think it obvious now that stapibility and bug fixies should be THE new features for 2019....
I just started watching the video you posted a link to (https://www.youtube.com/playlist?list=PLH1gH0v9E3rskenfQI-WQ99zwhA7IDj5r)
AMAZING work! If Adobe hired people like you and got rid of some of their nutty staff, PP would be so much better!
Well said! Amen to that!
Regarding what Reg Santo Tomas wrote, sounds like empty words IMHO. I was a beta tester on Sculy (PP CS5) years ago, and I was the tester who submitted the most quality FRs and BRs during that revision.
Years later, DOZENS of the things I reported on and Adobe marked as 'will be fixed' have yet to be fixed.
PLEASE STOP adding fancy new features so few people will ever use and focus on the cores of editing! Things such as fixing Time Remapping so it plays nice with keyframes from other effects, or giving new keyboard shortcuts so we can finally paste/insert paste clips to the HIGHEST active video track, etc. etc.
I'll actually believe Adobe cares about it's users the day they contact me for feedback on upcoming versions. During Scully, I was recognized as one of the top PP contributors world wide. So what happened next? Nothing. From several conversations I had with members of the programming team, it became clear that several team members were more concerned with protecting their ego than getting critical feedback from users like me that pointed out their programming mistakes.
If it's true you're working "with a broad set of clients", perhaps you're working with the wrong clients? How many of those clients asked Adobe to add a slew of new VR editing tools almost one needs vs fixing the current tools we use every single day?
Sorry to be blunt, but Adobe's priorities when is comes to what to add next to PP is FUBAR.
Naild it. I'm in the EXACT SAME position like the one starting this thread, though I'm not using MAC.
Marcus Koch commented
I can understand Micah's frustration. I have been working with Premiere for more than 15 years on a semi-professional level. We had been producing dancing videos and yearly DVDs for a festival. We stopped it due to the constant issues with Premier. Every year the delivery slipped for months due to major bugs in Premiere or Encore.
I just used Premier again after 1 year of absence trying to capture some of my old miniDV tapes. Premiere crashes after every capture.
On my last project I was not able to export any file, because Adobe crashed randomly (in between 1 and 15 mins) causing the graphics driver to crash. After 2 full months with multiple new installations of Premier, driver updates, endless talks to support engineers of Adobe, the graphics card manufacturer, the board manufacture, installing the OS completely new and an exchange of the graphics card, I found the source to be the autosave feature of Premiere that crashed the system.
I can go on and on with issues and error 0 messages. NLE is surly difficult, but if Premiere is not able to handle gracefully errors in subsystems or own modules, but crashes it is a general design, development, management, and quality control issue.
When bugs have been reported constantly on the forum, but on a support call the technicians have no idea of it, something is wrong.
First. Thanks for the feedback.
Second. We work with a broad set of clients on both our PreRelease program and also as direct engagements. We have sent our engineers on-site to directly debug and share our development versions with real customers that rely on our product day to day
Does that mean that the issues you are running into aren't real? Absolutely not. Clearly there is more work to do.
Share with us the specifics of your issues. Generalizations as well as huge buckets aren't helpful. As I think you will see over time, we will be releasing updates that directly address the issues that are being reported here.
You are right that words by themselves are meaningless. I am hoping we can prove that we are committed to improving the product as every release contains not only features but bug fixes for the specific issues that are reported here.
When threads are taken down, they are often non-actionable. We want to help and we do want to improve the product. So thank you in advance for taking any time to share any specific problems that we can address.
Reg Santo Tomas
Senior Engineering Manager
Brian Collins commented
I have to agree with Micah. I full respect that users have different hw / sw confgurations and if that is too challenging for the Adobe team, then tell us the drives, computers and ram to purchase that actually works. I have been a beta user for Autodesk on Flame and Smoke and their beta software is more stable than Adobe release software.
@Wes Howell, I'm happy that you edited a short documentary but that doesn't mean you run into the frustration that daily, in the weeds users do. Just in terms of logged and recognized bugs that we have all talked about, this software is embarrassing to use in client sessions. 10 premiere crashes a day is about the norm for me. Currently I'm on a project with a lot of footage that takes about 10 minutes to load. That's 100 minutes of downtime assuming everything is saved. I honestly would be ashamed to charge customers for that type performance.
I've been hearing some variant of "we're dedicated to improving Premiere" for years now, but the program is still missing several fundamental features, and still has several critical bugs.
You ask Micah to give you specifics, but I already did that... 3 years ago.
I know that several heads of development have seen these videos, and yet, most of the issues I point out are still unresolved. Some of them, such as adding shortcuts for features that already exist, would be incredibly easy to implement. I know, because I've done many of them with my own scripts.
I simply cannot believe anyone when they say "We're making Premiere better." I only believe actions, not words.
I'm a Quality Engineer on the Premiere team. I can assure you that we test the product and there is no shortage of work to be done. :) I'm also an editor and use the product for my own side projects on a semi-regular basis. I just completed a short documentary project with 2018.
Some configurations and environments can results in more problems than others (resolutions, formats, filters, hardware, etc) Of course we are committed to continuing to improve the quality and stability of Premiere. If we can get detailed information and we can reproduce any issues you're seeing on your side, we are more than willing to help resolve any issues.
Are there any specific bugs that your have logged that have not been addressed? Can you share detailed steps or even projects that we can use on our side to reproduce issues you're experiencing. If you have time to help break things down a bit more I'm willing to lend a hand.
Premiere Pro Quality Engineer
Trevor Asquerthian commented
And Micah maybe consider being a little bit more respectful of Adobe folks when posting. They are fellow human beings & have feelings. I realise there are frustrations when under pressure but EVERY piece of software more than a few lines long has bugs. And NLEs must be amongst the most complicated.
Trevor Asquerthian commented
Hmm maybe these kind of posts should be moved to comments in & add a vote to a single ‘focus on stability’ post.
Plus consider them a +1 to ‘make projects backwards compatible ‘ post
Best advice is to stay on a version that is stable (eg 2017 latest) and *wait* before jumping to 2018. Most places I work will most likely not move to 2018 until 2019 comes out - much the way 2017 became popular once 2018 was released.
BTW Avid have changed version numbering so 2018.5.4 is the 4th revision for May 2018. Which is useful when considering which version to be on (it is pretty stable too). Plus projects are always backwards compatible.
Let's see, you are a company with an ecosystem of powerful postproduction tools, you only need to improve in performance, stability and some other tools (for example the color workflow of Lumetri) to be really fantastic.