While I feel this forum can be helpful, I feel like the issue of implementing features and fixing bugs is not efficient enough. Not enough central communication. An example would be how some bugs take months to fix or even be addressed.

Email and forum post updates feel so robotic and disingenuous. Show us a human. Let us interact with them.

I feel a more efficient method would be to have a monthly live stream that editors can interact with and actually talk directly to the developers so fixes can be discussed. Maybe give updates on current fixes so users aren't kept in the dark, while hoping that a bug will be fixed in the next update. (Sometimes it isn't). I also feel this will allow the developers to understand how the user uses their programs. (a good example is the new export window. Not sure who approved that but no one likes it that i've talked to. Maybe the people approving these changes needs to be changed.)

I think some priorities might be skewed in directions most professional editors seem pointless. Like adding more features when priorities should be making Premiere stable and streamlined. Maybe I don't understand the behind-the-scenes development process, but I feel live communication with the community can clear this up. We are paying more money to use Adobe than most other Editing programs. I think that is why there are so many "passionate" comments in this forum.

Basically every time theres a new update, I feel the anxiety of something breaking and the program becoming even more challenging to use. And on top of that getting more frustrated knowing the bug may never be fixed or will take another 3 months to fix. When money and livelihoods are at risk, I feel this should be #1 priority over new features that aren't as important.

An example is now I can't use any of the transition add-ons I used to use in previous versions. They just don't show up in the M1 version of Premiere. And also I couldn't use most of Red Giant's presets either so I had to get rid of my subscription to them.

Please consider this! Thank you!

For as long as I have used a dual monitor setup (probably the past decade or so), there has been a bug that I have come to just live with, but is quite annoying. Whenever I have position or opacity keyframes on a clip, unchecking the stopwatch icon will cause Premiere to "encounter a serious problem" and close.

Having just gotten a Mac Studio, I held high hopes that this may finally be the machine/verison of Premiere that would no longer have this issue. But alas...

The only conclusion I can come to is that Premiere doesn't like how I have my windows set up in the dual monitor arrangement. This has happened on every machine and every version of Premiere I have ever used a two monitor workspace for. We're talking about 5 different machines, between at home and workplaces I have been employed.

And I'm not just reusing preferences from old versions. I usually start fresh every time I'm on a new machine, and rebuild it to my liking.

But I'd say 9 times out of 10, if I go to remove those keyframes by unchecking the stopwatch, this is the result. Out of habit, I have just started selecting them all, deleting them, THEN unchecking the stopwatch, which does not cause the problem. I've learned to live with it, but I find it a tad ridiculous this still exists, this many years later.

After adding a new Lumetri Color effect to a clip (I'm usually working with .mxf, but this happens on .mp4 and quicktime pro res as well), and going to the Input LUT drop down and selecting browse, premiere will either crash as soon as I hit browse, or after selecting the LUT. In some projects, this happens every single time and so I can no longer use LUTs. Sometimes the LUTs are exported from Resolve, sometimes they are presets from camera makers, some are creative. Seems to happen with any of them.

The footage and LUTs are stored on a shared internal server. This wasn't nearly as much of an issue about 6 months to a year ago so I don't think it's a problem with how or where we are storing footage or files as that hasn't changed, nor our created or exported LUTs as that hasn't changed either.

I'm currently using Premiere version 22.2, but have had this issue in all new versions and previous versions of 22. Have had to roll back continuously as newer bugs, and the new UI in the most recent versions have made premiere more unstable and unusable. Attached are my computer specs.

After posting and voting for several of these bug reports, I have to say Premiere has simply become a burden and unusable over the past year, and I don't say that lightly as a long term user who started on CS6. Maybe it works better on PC, but after using multiple iMac Pros and Mac Pros and weeks of Apple support discussions and tests, it seems to be a software issue. My whole team is having UI freezes and lagging, and constant crashes with Premiere to where we are forced to use another editing program a lot of the time. I'm adding this just to show the seriousness of the bugs, and I would love to see Premiere given the attention to make it workable again as I'd rather not migrate and retrain my whole team on a new piece of software. Currently though, this is what we are having to do.

All 22.3 and 22.4 Versions including this release are crashing without saving my current project if I don't take the time to open my sequences first in Source Monitor first. For example if I just double click a sequence on a timeline in order to open the sequence at that point then BOOM gone Premiere Pro app no longer open and any work since the last save is lost. This also happened in Premiere Pro 22.3.X

And today it is also crashing when I try and add a cut to a clip in my timeline.

Im excited about the new features but wish that the platform would not do these crashes because it is very frustrating.

I am on a 2020 fully loaded iMac 128gb Ram 16G Radeon Pro 5700 graphics card and i9 10-core processor.

When importing an image sequence, it would be incredibly convenient, if there was a tick box in the dialogue window, beside the "import as image sequence tick box labelled, "partial delayed import" or something along those lines which allows the user to import said file sequence in multiples of 100 images or at least importing 10 percent of what is needed to be imported and then pausing the processor thread managing the file import and then un-pausing after a constant period in time or at least until there is a drop in processor usage rather than waiting for an entire sequence to finish importing and potentially crashing ones computer in the process.

The default period of delay time could be measured based on averages of time measured when importing media in other projects such that an average period of time can be measured and then converted to Unix time such that this can be used as a constant time period relative to how fast
your own machine is. On Windows, as far as I’m concerned, there’s 2 ways of how this can be done

The first method is that rather than measuring time as it would normally be measured, C# delta-time is measured instead and then converted to Unix time for the sake of convenience and then the amount of “ticks” is the duration of time accounted for. One other way in which this could be better optimised, and could potentially cut out the need for having to even use C# in the first place would be to get the Unix time from the user’s Wi-Fi router as this would be connecting to an NTP server to begin with.

As of Macs, Unix time could be measured and then compared with what a Wi-Fi router is picking up from the NTP server it is initially connected to. Doing this would also make collaborative editing a whole lot less of a faff as if somebody is viewing footage in editor on one machine where the media has been pre-rendered, technically speaking this saves for the second user having to pre-render the footage on their own machine as the pre-rendered footage’s time-code can just be sent to any other machines therefore keeping everything in sync as in this specific context the video time-code substitutes the delta-time the other machine would be using e.g. one frame of time-code is synchronised with one network frame which is then synchronised with the current NTP pulse therefore, the incoming time-code embedded in the current network frame simply acts as a prompt for premiere pro to advance to the next frame

An advantage of my initial proposition would also be that less ram is used when importing media therefore allowing the user to not have to sit there awkwardly twiddling their thumbs while the file batch import finishes. Not only this but if this is done on multiple virtualised processor threads (this has been possible since C++11), this would also mean that the end user could do other stuff in the meantime while the media in question imports because the I/O related stuff is being done on separate virtualised threads on a separate physical processor thread therefore it doesn't need to be a case of the software having to have a "linear workflow".

Other than that, an option to directly import obj files would also make people’s lives a whole lot easier and would in some respects actually apply a bit more valid justification to the existence of the basic 3d tool as without this feature in question, despite it’s use for applying perspective to things so as to add a bit of depth or whatever, to say the least it does feel like a little bit of “half trick pony” so to say

Also ACES colour in adobe media encoder and 64 bit audio depth and being able to import footage directly from an SD card would be excellent.