Slower release schedule with more stable software
I would like to see a toned down release schedule with much fewer bugs going to release and much longer support for legacy project files (at least 3 years backwards compatibility) . It's very difficult to keep up in post production with so many buggy releases and project files becoming outdated so quickly.
I’m gonna close this request as it is neither a bug report nor a feature request, and therefore non-actionable for the product team.
As I’ve mentioned in the comments section, release schedule and stability are not linked in any way, but your point about quality concerns is well taken, and the same is true for version compatibility – which is potentially actionable for us, and you can vote for it here:
I'm going to have to disagree, Patrick. I think a blind man could see that if you spent more time on each version they would be far less buggy - otherwise what is your excuse for putting out such consistently sub par software? It's appalling, frankly. At this point I'm seriously considering my options for moving away from Adobe. You HAVE to improve the stability and address the bugs in this software.
Basic functionality is failing more than ever. I'm okay with an occasional crash or a glitch with a new feature but simple, basic functionality is no longer something I expect from Premiere Pro. It's been especially bad since late 2017.
Crashes (all kinds!) and bugs are now a constant presence on this software. I have several SSDs including an M.2 960 Pro and have tried every configuration. My machine has run this software well for years and years but in the last one or two, there's been a HUGE increase in annoying problems.
Adobe has gotten thousands and thousands of dollars from me and will get thousands and thousands more but only because switching to another NLE is difficult. If Adobe doesn't shift resources to stability and performance over the constant barrage of barely-working new features, I'm absolutely going to switch and I'm going to be a vocal advocate against this abusive, unethical business practice Adobe is engaging in by taking money from customers but not delivering a usable product. Shame on you, Adobe.
In my eyes,
There is only one thing that make Adobe feel, the same, that we feel, when we couldn't hold a deadline because of a new "feature", and our customer is not willing to pay.....
The difference is, we pay Adobe the money before we start the work.
We just have to find alternatives to there stuff...there are other companies that are on a good way..
Richard William commented
Release schedule and stability are not linked? We literally have to wait months after a new version comes out so we don't break our projects. Come on bro...
I know you're doing your job and I understand the business decision of declining our requests. You guys worry about bringing more users to your products, but you're on the top of the market right now because there's no one better, and if you guys continue taking this approach for every request we make, when we have a company that hears us we are going to jump out asap.
I mean, you still respond so that's that.
[Deleted User] commented
It's a tragedy
that you have to say to ADOBE,
so that the software runs more stable!
Honestly, it's better to
make less gimmigs
and more basic
and more power.
But the marketing-driven managers,
unfortunately do not understand what they do!
Otherwise, not so much of little Gimmigs & Ki would be spoiled.
If you see how deletantisch the QT7 conversion was operated,
you must make with the manager ....
Richard William commented
YES! Let's say this is a feature so they implement it! Agreed!
R H commented
Yes, pleaseeee do this! It's getting really frustrating every time a new version comes out one bug is fixed and two more crop up. I would be totally fine if you just went and fixed all the bugs and didn't add a single new feature for the next release.
Agree - so many bugs!
I've gone back to 2017 due to the latest version being unusable for me.
And yeah not being able to open old projects in the newer versions is annoying too!
I have been battling random crashes since v.12 rolled out. I've tried updating, rolling back, nothing helps. I suggest we all start calling the account and requesting credits to our membership. Maybe then they Adobe will start listening & fixing this inoperable software! Money talks.
It's 11:30am and I've already had 4 crashes this morning. Unfortunately, it's not just this machine. I've felt Premiere has been getting progressively less stable recently across both Mac and PC. It's incredibly disappointing.
I have been working on Avid and FCP for years and totally done with Premiere. Although it has great features, it is just too unreliable for any professional.
I wonder what would happen if everybody would stop paying their monthly fee to Adobe untill the crashes are solved.
(I am at the point that I am seriously considering this !)
this has been my enormous problem with Premiere from day one... the fact that i spend almost equal time fixing rendering errors, random crashes and other weird stuff is just beyond frustrating and makes me want to just play a flute or be a painter, with no uncontrollable hiccups constantly.
Didn't see Patrick's comment until just now. Then on that note. KEEP GOING. Keep squashing bugs and making the program not crash as often. It makes me want to move back to Avid MC8.
It's just non stop occasional performance hiccups, random crashes. Again, not that it's all the time and unusable, but just enough where I am conscious of it. It makes me want to go back CC 2017. I would be totally fine with more incremental updates that further enhance performance and stability, and less about features. Update the major features once a year. It's insane that a project can't not backtrack based on a single Build update.
Throwing in my support for an "Adobe Insider" beta-testing version before releasing the stable version to the general public. This allows you guys to get quality feedback from users who are interested in testing new features, while still making sure users who need mission-critical stability on each release are also taken care of.
I agree! While this is oversimplified there does need to be more focus on stability and legacy issues. My workflow has been greatly disturbed. These issues have added several hours of work to my week.
I don't understand how Adobe, being the large and successful company that it is, cannot release updates without disrupting the workflow and making previous files incompatible every single time. Sure, it makes sense that such a thing is necessary occasionally or with big changes, but every single update? Really? I don't think I have any other program that does that more than once a year, if that...it starts to seem like Adobe doesn't much care about its userbase's workflow or disk space.
Yeah we need to be able to open projects in, at the very least, the last version. A dialogue box that allows the user to open in the older version, stripping out any incompatible effects would be preferable, to being stuck with the new version (or having to use XMLs to downgrade)
Patrick, thank you for taking the time to respond.
In regards to software stabilty, bugs, release schedule and project file longevity being different issues please recategorize them in your mind as what they are to your users.
Instead think of all those "separate" issues as Premiere Pro's Trustworthiness. That is fundamentally why this is such an important issue.
I think Adobe has a certain responsibility to its customers to create a more trustworthy product release after release. Our confidence in the product has declined year over year and that's what needs to be addressed. Not just fewer bugs going to release, not just fewer crashes not just fewer broken features and not just project files that are outdated in between my daughter's 11th birthday and her half birthday. Premiere Pro must prove to its customers year after year that it is becoming not just more capable and feature rich but more trustworthy. And so far we just have not seen that.
A couple of general comments on the subject:
1) The Premiere Pro team has slowed down on new feature development. 12.1 has a lot less in the category of "new" and a lot more in the area of addressing legacy bugs or issues that occur because of changes to the infrastruture underneath us or around us.
We hear you.
A full list of bugs addressed in 12.1 is here:
2) Release schedule / frequency of release is not necessarily tied to stability. A lot of products and services release daily, and sometimes you wouldn't even notice. We currently do two feature bearing releases a year, with two stability and new formats releases between them. There's no perfect cadence, and we're very open to suggestions as to what's the ideal opportunity to take on new features. It used to be 2-3 years between two releases, and looking back at the introduction of Creative Cloud, we got very positive feedback on not holding on to new features but releasing them more frequently. There's Pros and Cons - looking forward to seeing more comments from you.
3) It would seem to me that a lot of the issues discussed here have to do with deployment and compatibility rather than frequency of the releases as such. It might be good to keep those separate, but once more: keep the feedback coming.