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.

Cursor Frame Behavior (Affecting In Out, Ripple Edits).

Ok team, I know you had some guy complain about how the Cursor works in the timeline, and now you changed how it works, which completely screwed over the Ripple Trim to Previous Edit.

What WORKED before yesterday was if you were on the front of a clip in the timeline, and you hit the Ripple Trim to Previous Edit, it would remove the first frame and obviously move the entire timeline up a frame to compensate.

THIS WAS INSANELY HANDY because if you're trimming a clip, you could just hit that button a few times and make it work right.

Now, because you guys changed how the cursor works, I have to hit Right on my keypad, and then hit the Ripple edit button, and it'll remove that first frame.

Guys, you seriously screwed over an entire generation of editos who know how editing works. I know some people complain about how the cursor works, but this sucks.

Why not just create a preference option where you can make the Cursor act like FILM or act like it is now. All NLEs were based on film editing, which lots of people expect and relied upon. Now, I have to hit an extra keystroke all the time which is massively time consuming.

Can you please just put in a preference option to revert back or not? That would solve this issue for everyone instead of bowing to people that don't understand NLE history.

Request for Essential Graphics Text Tool
It is wonderful to be able to gradation the color of letters!
Thank you very much! !! Very glad! !! All Japanese users are happy!

As a request for further creative creation ...
・ We want a gradation function for the border.
・ We also want a gradation function for shadows.
-Multiple boundaries can be used. We want you to be able to use multiple shadows as well.

Especially in the Japanese video industry, multiple boundaries and their gradations are really used a lot. Hopefully at this time, we hope for further evolution!
Thank you!

エッセンシャルグラフィックステキストツールのリクエスト
文字の色をグラデーションできるようになったことはとても素晴らしい！
本当にありがとう！！とてもうれしい！！日本のユーザーはみんな喜んでいます！

さらなるクリエイティブの創造のためのリクエストとして・・・
・境界線にもグラデーション機能が欲しい。
・シャドウにもグラデーション機能が欲しい。
・境界線は複数使用することができる。同じようにシャドウも複数使用できるようになって欲しい。

特に日本の映像業界では、複数の境界線、それらのグラデーションは本当に多く使われています。できればこのタイミングで、さらなる進化を望みます！
よろしくお願いします！

When exporting a video sequence premiere randomly leaves out part of the audio. Those part were not muted, but in the same channel and of the same kind of other parts exported fine, not even cut: so for instance you have a talker that randomly get the voice silent.
This is a big reliability issue, because there is no correspondence of what you have on timeline and what you are going to have on final export. This happens on different machines and happened also with previous versions of Premiere different from this one at moment of writing 15.4.1 (build 4).
The only reliably working workaround has been export only the single audio channels in wave files and then import it back into the timeline, that is time consuming and unacceptable for a professional software.

When I hit the "L" key to fast-forward while playing on the timeline, and hit about 4x speed, the audio stops scrubbing (I think this is normal), followed by Premiere Pro locking up. There's no way to halt the playback at this point, and eventually Premiere Pro locks the entire system - even the mouse cursor won't move. If I shutdown/restart fast enough (after Premiere locks, but before the entire system locks), I can get a reboot to happen. Otherwise it's the reset switch.

It is very similar to the problem described here, except I'm running Premiere Pro 2022 on Windows 10, and the video format is XAVC S HD:

https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-cc-2020-crashes-on-fast-forward...

If I edit AVCHD footage, the problem doesn't seem to occur. I've tried turning off hardware accelerated encoding/decoding in the Media preferences, with no effect on this. I'm guessing it's a Premiere bug - suggestions?

The fact that Pr always defaults to the last export location, regardless of which project is exported from, is completely illogical. Why would a user ever want to export Project B's sequence into the last used export folder if that folder belongs to Project A, for example? (see illustration 1)

There are already about a half dozen FRs that ask for this to be fixed, however since they only offer half baked solutions, I'm posting a new FR, offering a full fledged solution.

The solution is simple:
Provide a new 'Export' tab in the Preferences window that allows users to define the default location they want all of their projects to export to (both from Export Settings and Quick Export). (see illustration 2)

A 'Relative path' checkbox would allow users to make the export path relative to each project. In the illustration's example, the location is set to .\Exports. This means exports from Project A will automatically appear inside a folder named 'Exports' next to project 'Project A.prproj', and exports from Project B will appear in Project B's 'Export' folder, and so forth. If an export folder doesn't exist, Pr would automatically create it upon export.

Should a user wish to automatically export to the same location regardless of which project is exported from, setting this up would be as easy as browsing to one's preferred export location (for example, a "Pr Exports" folder on the Desktop), and unchecking 'Relative path'.

Note that these options would only set each project's DEFAULT export location. If a user chooses to export to a different location from a certain project, then that (and only that) project's default export location would be automatically set to this new location.

Example:
Project A: User exports to Desktop = New default export location for Project A set to Desktop

Project B: Default export location continues to be 'Export' folder (next to Project B.prproj)

This workflow would address the needs of all editors: those who want exports saved in locations relative to each individual project, as well as those who want exports from all projects to appear in the same place!

The current exporting behavior makes zero sense and is incredibly frustrating, especially for editors who work on more than one project at a time. Please fix this already! Thank you!

When you are "seeking," (which means QUICKLY looking through a long video by clicking and dragging the playhead with the cursor,) there is sometimes very high "prefetch latency," meaning that frames will load slowly, resulting in very few frames being shown. This can make it very difficult to find what you're looking for.

But when seeking, perfect frame accuracy is not nearly as important as seeing what you're doing. Therefore, to reduce the "prefetch latency," I suggest that the nearest I-frame is loaded and displayed FIRST, (because I-frames are always the fastest to load) while the exact B or P frame is still being slowly decoded. As soon as it's decoded, it can be displayed, replacing the displayed I-frame.

If the user is seeking quickly, there might not be enough time to load the P and B frames before the user has already moved the playhead nearer to another I-frame. This is fine! The I-frames should always take priority.

In VLC, there is a similar feature called "fast seek."

Combined with my "ghost playhead" feature suggestion, it would be made clear to the user exactly what is going on. (Linked below)

However, it would probably be important for fast seeking to be optional, and perhaps even off by default, as it may confuse some users.

NOTE: This works best if only ONE video source is visible. With more than one video on the timeline, the I-frames will probably not be in the same spots. Nevertheless, it COULD still work, but there would have to be multiple ghost playheads. This might be too difficult to code, and confusing and frustrating for users, who won't understand why premiere is showing video frames out of lockstep, especially in cases where one video has high prefetch latency, and the other is low.

LINK TO FULL EXPLANATORY VIDEO: https://youtu.be/XeFezzmG22c

LINK TO GHOST PLAYHEAD USERVOICE ENTRY: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/42186274-a-ghost-playhead-which-always-marks-the-timeline

ProRes Raw files are seeming unable to be played back on AMD GPUs using the latest PP 22.x + ProRes RAW 1.3 on Latest Windows 10 & 11.

See: https://community.adobe.com/t5/premiere-pro-discussions/issues-decoding-prores-raw/m-p/12648595

There seems to be a bug that prevents the rendering of frames using GPU Acceleration using OpenCL that produces a console Error and results in audio playing but only a black screen for video:

<12112> <Assert> <0> Debug Assert failed!
Expression: dvacore::ResultSucceeded(result)
Process: Adobe Premiere Pro.exe
Process ID: 9652
Thread ID: 12112
Thread Name: Display Thread
File: ....\Src\RenderRequest.cpp
Line: 228
Function: AdobePlayer::RenderRequest::ProduceFrame
Last Error: 6
Assert Dialog Show:false
Callstack:
xRendererEntry
xRendererEntry
dvacore::threads::CreateAsyncThreadedExecutor
dvacore::threads::GetThreadName
dvacore::threads::GetThreadName
boost::detail::win32::handle_manager::swap
configthreadlocale
BaseThreadInitThunk
RtlUserThreadStart

I've worked with these files fine in Premiere v15.4.1 and did not have this issue but since updating earlier this month to v22.1.2 I've had several issues with Premiere errors while editing and random crashes without warning or pinwheel of death.

Most common error is "Unable to access resource "SErrorXlND@2x'(type svg)" Attached screen shot below. Once this error occurs I almost always have to completely restart Premiere.

It also has made it nearly impossible to export a finished project from both Premiere and Media Encoder. When doing so it will hang up at some point in the export and create an Accelerated Renderer Error - Unable to produce frame.

The only way I'm able to export is by changing the render settings from GPU to mercury playback engine software only. That work around works for now but isn't great.

The issue is difficult to replicate. I've provided my computer specifications below.

Mac Pro 2019
BigSur 11.6
3.2 GHz 16 Core Xeon W
128 GB Ram
AMD Radeon Pro Vega II 32 gb

We are, in NRK (Norwegian Broadcasting company), working on several big documentary-projects, where transcripting interviews is key to keep an overview of all the interviews and quotes. PreLude, which is a discontinued application, had a good workflow in using the playback-features on an interview while writing the transcript. In Premiere Pro, this is more complicated because we have to stop the video, open the "Comment Marker"-window, write, close the window and play the video again, as in PreLude you could do all this at the same time. If this function was available in Premiere Pro as well, we too could put down the use of a discontinued program such as PreLude.