JRB,
It's fascinating to see people complaining about the devs pushing new versions/features rather than going after bugs/stability.
Most users clearly didn't actually look at the information for the 2020 version. The "new" features were ... auto-reframe. That's about it. Oh, and finally adding the full keyboard shortcuts from the old Titler to available with the EGP. That wasn't a lot of engineering time on new stuff.
So ... what was it? As noted in quite a few places ... the main purpose of the 14.x/2020 series was to go after stability and bugs. And in that process, announced they were limiting the older gear that they were coding for to simplify and update the code base, had fixed (for most scenarios at least) the largest batch of bugs/stability issues they've ever hit, and would be going after more as their main effort.
At Adobe MAX, the project sub-manager brought in to lead the rebuilding of the Pr engineering team to make bugs/stability a more native part of their entire process talked with a meeting of the ACPs. Ivo Manolov said that 1) they'd hit a ton of bugs which was the good news but 2) that backlog was massive and will take some time to work through ... as the bad news.
And for current users, also good news/bad news: as a percentage of the user base, more users are stable with the 14.x series than any previous series was the good news. The bad news ... the majority of the remaining bugs and stability issues were things they couldn't replicate with the in-house mix of Mac/PC gear and media. So getting at the remaining issues, which were HUGE for say some users with RED and Sony media types, some other things ... is darn difficult. What the engineers can't replicate, they can't fix.
Understand, Premeire runs on the widest range of gear/media/workflows of any major NLE. For years at NAB, aisle-talk has wondered if Premiere shouldn't back off on the gear/media it worked with in order to get wider stability. So I asked him about that, and he said that is why they cut back on some of the older gear and media types. Purely to simplify coding.
And further ... they made it clear they NEED the users with issues to file detailed reports on the UserVoice system. One of the engineers who read every report filed was there, and his chief complaint was that for so many reports, all he got was "X ain't working on my rig" ... and as he doesn't even know then what version they have or what gear they're running on, it's a useless report.
If you're having troubles, please go to the UserVoice system and search for similar reports, add on a comment with detailed information on your gear/media and what happens when you do whatever is leading to the problem. That way they can see better what is happening, start narrowing down on what gear/media, and contact those that give enough details so the engineers get a better look at the factors involved.
Also ... besides the engineers, all reports filed on the UserVoice system get collated and sent up to the upper managers who determine budgets ... Adobe lives by metrics, so ... let's give them metrics.
Oh ... and post back here a link to any UserVoice thread you create or vote on, so the rest of us can pop over there and upvote. Let's get some of these things fixed.
Neil
34
Replies
AdChoices