Copy and paste the problem of Jan Lucas since i have the same problem with the new version of premiere pro.

Bug Report: Premiere Pro 22.1.2 compatibility issues with Red Giant Universe 5.0.1 - Error Universe Runtime
Universe 5.0.1 seems to have an issue with the new Premiere Pro 22.1.1 Update. Premiere doesn't seem to be able to load the .aex-files. It massively slows down the startup of Premiere. You need to accept an error message ("Error connecting to Universe runtime. Please reinstall Universe.") for every Universe effect that is not loading, meaning 93 clicks are necessary to open up Premiere. The same problem occurs within a Premiere-Project, when trying to apply a Universe-effect; plus, in some cases, it causes Premiere or my PC to crash.
Reinstalling either Premiere Pro or Universe does not fix the problem. The only way to get Universe working again, is to downgrade back to Premiere 22.0.

Frame IO is not able to detect the file when using the Upload > Upload Active Sequence option. The file is in the correct place in my Creative Cloud folder when I navigate to it in Windows Explorer. This bug is happening to me on Windows 11, 10850k intel, Nvidia RTX3090, 32GB ram.

The workaround is Upload > File and pick my rendered sequence.

Not sure what category this bug falls under so I put it in 3rd Party Software since I think that's what Frame.IO. This may be a Premier bug though, not sure what category it would fall under in that case.

PFCHECKOUTPARAM no longer returns a valid image from PFCmdUSERPARAMCHANGED in Premiere Beta, as of 22.1.1 BETA build 41.
Occurs on Mac and Windows, every system, every time. PFCHECKOUTPARAM doesn't return an error but the effect world have bogus value, like very large width and rowbytes.
If we need to use another API that's fine, but PFCHECKOUTPARAM should at least return an error.
PrSDKSequenceRenderSuite seems to be the alternative, but I have not yet tried setting other parameters from the completion callback.

To reproduce this, download Beauty Box, apply and click on Analyze Frame (image content doesn't matter).
https://digitalanarchy.com/demos/psd_mac.html#d4
https://digitalanarchy.com/demos/psd_win.html#d4

As a Loupedeck user, I want to add tracks to timeline without causing Premiere to crash.

Steps to reproduce:
Open Premiere Pro 14.6 or 14.7 on Win or Mac (bug is not reproduced with older versions)
Add Loupedeck as control surface
Add a track (audio, submix or video) in the timeline sequence

Expected result:
The track is added, Premiere Pro application is running

Actual result:
The track is not added, Premiere Pro application hangs up

Note:
The behavior is the same when adding tracks with mouse through the UI of Premiere (with LD added as control surface)
Adding tracks works fine when LD is removed as control surface.

I also worked with a robot and with a person specialized in this field. He liked the person more. It was much clearer what he does and how he does it, and I could ask him questions if some details are not clear to me. For those interested in working with professionals, I could recommend the company that helped me from the beginning. https://wealthtender.com/firms/xy-planning-network/ worked intensively on my problems and gave me various tips. But when I switched to the robot, everything was dry and tiring. It already depends on what kind of person you are and how you like to work.

It'd be nice if Premiere and After Effects would have some way to let the user isolate and disable/delete plug-ins that cause the programs to crash on start-up (my biggest issue with new updates) or ideally even when it causes older project files not to work correctly. I hardly use plug-ins (for this reason) and even so a few times I've found myself scrutinizing the application load screen trying to catch exactly where the application crashes and then digging through the hard drive to find and delete the plug-in I think is crashing it. Maybe there's an easy way to do this that I don't know about but if not, I'd certainly appreciate one!

As a Loupedeck user, I want to add tracks to timeline without causing Premiere to crash.

Steps to reproduce:
Open Premiere Pro 14.6 or 14.7 on Win or Mac (bug is not reproduced with older versions)
Add Loupedeck as control surface
Add a track (audio, submix or video) in the timeline sequence

Expected result:
The track is added, Premiere Pro application is running

Actual result:
The track is not added, Premiere Pro application hangs up

Note:
The behavior is the same when adding tracks with mouse through the UI of Premiere (with LD added as control surface)
Adding tracks works fine when LD is removed as control surface.

Understandably, Adobe work on making integration between their various software packages within the Adobe family as smooth functioning as possible and it works fairly well to this end. However, Premiere can be a real nightmare to work with when your intention is to use 3rd party software for parts of your post production process, or when you want to collaborate and have other creatives working on different aspects of project, even if they themselves may use Adobe products.

There are many separate reasons why this is problematic, but my request is a little more general and overarching. Premiere has a collection of various functions some of which are designed to facilitate transfer of timelines and media from Premiere to someone or something else, and also some functions that aren't designed for that but can be co-opted for that. Examples include the AAF export tool for sending timelines out mostly to Avid products but also some others than can read AAFs too, or the media management tool that can be used to archive a project but as a side effect can theoretically be used as a means of sending projects or parts of projects out to other people/ software packages, render and replace can function similarly if you set it up so that conditions are as ideal as possible for it work, it also has XML and EDL export for sending timeline data around between packages without media, OMF too.

The issue is that these tools each have a LOT of problems and quirks, way more than you'd expect to the point where you need a book of workarounds to make them function as intended, also if you throw proxy files in to the mix then all bets are off because Adobe evidently didn't envisage that scenario when they designed those tools early on and didn't update them to accommodate the proxy feature after it was introduced.

All these tools, aside from their faults, are also, different, silo'd islands of functionality that all revolve around the same concept but which you have to know about separately to operate. They each seem designed for some theoretical, unlikely form of editing with little to no effects, one or as few as possible tracks, no proxies, no nesting, no multicamera, no merged clips etc, etc, etc. and the issues that affect one tool and require workarounds aren't the same for another. You have to invest a great deal of time trying to create this theoretical ideal circumstance to try and coax them in to doing what you need and even then it only really works about 50% of the time or less.

Aside from all the various glitches being fixed, I want there to be a single point of access for managing all the various scenarios you might encounter in the process of archiving a project or packaging elements of it up for use by other people/software -- what I call "interchange". Just as there is a single 'Export' window that you could use to create all possible forms of media that the Adobe Media Encoder engine can create, you'd use the interchange window to access all tools, features and settings related to this goal.

My idea is that in the file menu there'd be something called 'interchange/archive' and that this will open up a window that houses all those tools with an interface that makes the function of each very clear so that if you don't for example know what an AAF is, but do know you need to send your timeline to someone who uses Avid Media Composer, then this will be made clear to you. Additionally, this should hopefully integrate functions of existing tools that are often co-opted by Premiere users to approximate dedicated functions, in to something built for purpose. Thus, XML would be one of the options here in the interchange menu, but there'd be additional options such as transcoding the sequence media to a mezzanine codec packaged alongside the XML, not just exporting the timeline data, or consolidating the media in its current form so you can collect all the media associated just with the one sequence and send it off in its camera original form on a hard drive. Or consolidating in camera original codec, but also trimming with handles. These functions all theoretically exist in the media management tool, but for a start, they almost NEVER work but even if they did, it's not immediately obvious to someone who wants to send a timeline off to another package/person that they should use the archiving tool as a way of doing that, it's counterintuitive.

There's all kinds of ways I could suggest presenting this interface but really the important thing is that the options presented are all about different ways of delivering media and data about projects or parts of projects to different software and different people (who might even be using Adobe software but aren't on the same machine). With that end goal in mind, any single point of access to the different relevant settings would be an improvement. Same goes for archiving as well which has similar purposes in mind. Arguably Premiere has archiving sorted out in the form of the media management tool, but aside from the glitches, the tool is pretty rudimentary and could be folded in to this proposed single interchange tool which itself would hopefully have many levels of complexity to suit the level of control needed, much like exporting media does.

While development on this issue can help people to use tools other than Adobe tools, it's still in Adobe's interests since the 'Pro' part of Premiere Pro is always going to mean operating in circumstances that involve collaboration and that's going to mean different, facilities, different people, different storage, different machines let alone different software and the ability to manage that effectively drives a lot of the decision making on what editing software to use.