Having many issues with Premiere PRO

Eyenigma,

I can't think of anyone here who wouldn't understand a bit of cynicism ... all it takes is a functional brain, right?  😉

But Jason's right ... even their bean-counters move when they see metrics that "tell" them to. So we have to give them the metrics that some might say common sense should provide. Hmmm ... why would that invoke cynicism? lol

So file every stupid little issue on the UserVoice system. Give 'em enough metrics to choke on. It actually would do some good.

Neil

Eyenigma,

Love your idea that Adobe should give some sort of subscription credit for bug reports. That in fact would be a great UserVoice request to make ... keep in mind, Adobe is half the company that makes the apps we know of, Photoshop, Illustrator, Premiere et al ... and the other half is the software they create is for large companies to work with user experience metrics. Adobe runs on metrics. Let's give them some. (And yea, sometimes some common sense and experience should over-ride "metrics", don't you think?)

Go to the UserVoice system, and post a request for some system for rewarding users for posting bugs. Then post back here with a link. I certainly would be happy to jump over and up-vote that! Should be able to get some users posting on it in other forums also.

As to the 2019/2020 situation, from a group discussion at Adobe MAX with the program head and the man he brought in to get stability and performance improved, Ivo Manolov. There were three main differences between 2019 and 2020 ... first, some older formats/codec and hardware support were dropped to either comply with the requests of the owners of those "things" who are deprecating them or to simplify the code process moving forward for Premiere. (Nvidia and Apple among others wanted some things dropped.)

Second, they went through and hit a few hundred bugs, some of which required rewriting extensive sections of the program code.

Third, they worked on stability and performance especially with the "heavy" format/codecs such as RED, Arri, and others.

For most users, this has resulted in a better working process. But even with the way the changes improved things for many, for some ... they clearly caused issues. And you are clearly in that latter group. They are aware ... Ivo Manolov was pretty blunt that though the changes were in general a vast improvement, he's aware that for some users it really screwed things up. And that's what the engineers are working on now ... catching those things that got through.

Which is why they particularly need data from someone like you. What are the keys for why X worked well on the majority of systems, but on some, screwed the pooch? That's the information he needs.

And remember Adobe is a massive company. Premiere is one small part of the Whole, and the managers of any individual program and their teams are always in between their user base and the upper managers as a way of life. The Premiere developing staff aren't just dis-interested engineers. I've met a number over the years at NAB and MAX, and they all edit and do other motion-media stuff on their own. They're actually users of the software themselves.

But they work within the constraints placed upon them by the upper management. That upper group lives by metrics, as I noted above. Which is why it is so flipping crucial to give them metrics. And the UserVoice posts are read by the engineers, every flipping one of them. Past that ... and crucially ... they are collated and passed up the chain to the upper managers. Those UserVoice reports form a significant part of the metrics the upper management uses to, it seems, think.

We users need to give them a ton of metrics. My opinion? They need to enlarge the development team to both allow for better work at catching bad code and to fix some of the annoying long-term issues this app has. I don't know a user (including the engineers!) who can't point to several off the top of their heads. And then when those are handled, I can think of a few nice new things I'd like. AFTER they handle the bad & old stuff.

Chronicles ... to get to the UserVoice system just click on it. I've linked it.

Neil

Regarding your first main issue: the import of long-GOP formats, specially files that are pretty large in size, is a known issue with the latest Premiere.  It was reproduced internally by Adobe last month, so they know about it.  There's absolutely no word on its fix.

It's very intriguing how different this is running on various machines. In the main, fewer users (in percentage terms) are having major issues  ... which is good.

But there are clearly some for whom this is not performing properly. Which is awful especially if you're one of the select ones. Been there myself of course, yes it's a mess at that point.

They brought in a manager for rebuilding the team structure and practices for attacking bugs and performance issues a number of months back and he was at Adobe MAX to talk with users. Along with several engineers.

They aren't apparently working on features just going after bugs and stability primarily. And made it very clear they want EVERYONE with bugs or performance issues to please file full details on the UserVoice system. They want the data: what hardware, media,  plugins, effects and such are in use on the systems that are ragged.

They run a few hundred machines in-house of both Mac and PC plus do have a beta program and are trying to sort what combinations cause issues. As they can't replicate most of these in-house. What they can't experience nor get data on they can't fix of course.

And one of the engineers there was tasked with sorting the UserVoice posts. Yes, they do read every one of them. And for him, the biggest problem is a lack of enough details for them to even start trying to figure out a problem. So ... give them data. Tell them exactly where and when it's screwing up.

Neil

A fairly slow 6-core CPU on a laptop with only 16GB of RAM isn't an awful lot of oomph, to begin with. Not bad, but ... not high-powered by a long shot. So I'm not surprised that trying to load a massive clip over two hours in length makes it cough a bit. I don't think I've ever thrown a file like that at my desktop.

And laptop motherboards try to simplify everything, including the number of "lanes" involved. Which makes for logjams in data throughput. Dealing with massive single files like that, any throughput logjam will be magnified.

Of course, another massive issue when dealing with massive files is ... disc performance. Sustained read/write in "real world" on that computer right now terms. So ... how many drives of what type are you using, and what are the connections involved, and what sort of sustained read/write performance are you getting?

Neil