Wasn't it a better choice to make it toggle all upon Ctrl+Click on the designated icon like it used to be discussed once? There are too many menus, and there are three places on the timeline where those menus are - the wrench icon, the 3 lines menu and the left side of the timeline. Ctrl+Clicking like it is in After Effects would be a better and more organic choice for this feature. Though I understand this idea of being able to turn on\mute\solo separate tracks and not all of them at once, a ctrl+ or even Alt+click to use this exact feature would be more prefferable than doing it through a menu ... View more

Ok, I'll make it a quarter update then, since no one's paying attention. Premiere Pro 25.1 (73), NV Studio Drivers 572.60. This bug is going nowhere, no matter what Drivers or Software versions I use. No matter what media it is. It just happens almost once every edit. I can fix it by ust changing the size of the Program monitor window. But it comes back in a while every time. Clean installs, windows reinstalls, Reddit guys having the same bug every other day... Everything here. ... View more

@tho_sch  A good thing to know. Unfortunately most of us here have this issue without any external plugins as well. I personally had one after I'd just cut the material, that is all. There were no audio filters used even Premiere Pro's own. I still think this issue is related to the audio compression issue ... View more

@RobShultz Why not make it in DavinciResolve? Why not in CapCut? Why not use Audition for lifting up the volume of each track? Why not use AI to add a text above the video? It's so convenient to jump from software to software for simple things ... View more

Yeah, I know all that. A simple "Turn off missing font warning" in the preferences would be much better ... View more

@Jarle Leirpoll  It's the same across languages other than english. ... View more

Changing the easy and convenient "zooming with scroll, panning with a middle mouse button" method was rather a bad idea... You should have changed the default global zoom method to the anchored one and that's it.  Also - I can see the vertical panning with the scroll, but there's no horizontal panning:   ... View more

Yeah, and in comparison to DR graphs built in right into the timeline, Premiere Pro just looks antique not to have it at all:       ... View more

1000 points is not "slightly", you know, it's the same result I get in v 25.0 with a cpu $100 cheaper. I guess in Premiere Pro 25.2 you'll get like 14k that way, me - even less. It's called ssergorp. ... View more

@JonesVid try resetting Premier's settings, cache and plugins cache via shift key pressed on its start. Mine 25.1 crashed too for the first time. 25.0 ran fine btw.  ... View more

And here goes the famous and most trustworthy PugetBench test from Puget systems: Premiere Pro 25.1: Premiere Pro 25.0:   The result is catastrophic...    14700K, RTX 4080, SSD (7600\7300 speed), 64 Gb of ram at 5600 Hz. ... View more

@JonesVid  Wow. I nearly dropped off my chair just now... So Premiere Pro 25.1 basically makes 13900K perform worse than 9900K which was released in 2019... Jesus Christ, Adobe... ... View more

@mayjain  https://www.intel.com/content/www/us/en/support/articles/000097123/graphics.html   ... View more

Worth checking if it's the decode or the 3d graph, because the 3d graph does not show the actual decoding but rather some job like the UI acceleration or some effects related tasks ... View more

Issue - Slow scrolling speed in Premiere Pro tabs while ideal in everything else, as given in the title. Adobe Premiere Pro version number: Premiere Pro 25.1, as given in the last paragraph. Operating system -Win 11 24h2 26100.2894 System Info: CPU, GPU, RAM, HD: CPU - Intel i7 14700K, latest BIOS firmware update GPU - Palit RTX 4080, as given in the last paragraph. GPU - driver Studio 566.36, as given in the last paragraph. RAM - 64 Gb, as given in the last paragraph. Hard Drive - 2x SSDs, 1 HDD. HDD is used for storage only. Video format: this is irrelevant, the bug is sowtware only. But if needed, h264 420 8 bit.  Workflow details: the while first message is about it with video illustrations. Steps to reproduce - (Very important!) 1) Open Premiere Pro. 2) Carefully and slowly hover your mouse pointer over the scrollbar of Premiere Pro tabs mentioned in the first message. Move your index finger over the mouse scroll wheel to make it rotate once, then do the same in the opposite direction. Feel the scrolling speed as opposed to your browser on OS windows scrollbars.  Expected result - the scroll speed in Premiere Pro ought to correspond to the scroll speed inside Windows OS or any programs inside of it. The nearest example is After Effects which has a correct scroll speed. Actual result -  The scroll speeds in Premiere Pro are 1,5-2 tomes slower than in the rest of the software in Windows.   @Kevin-Monahan is it enough? ... View more

I guess there will never be a fix for this one... ... View more

So this is the updated h264 you were talking about...   ... View more

Hi, @mayjain  I've got tired of this... Please, see this message: https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-25-1-igpu-stopped-decoding-my-footage/m-p/15110872#M550211 Premiere Pro 25.1 - zero iGPU load, PotPlayer - 50% iGPU load. With one and the same file.   Here: https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-25-1-igpu-stopped-decoding-my-footage/m-p/15023863#M542306 Premiere Pro 25.0 with h265 10 bit 422 120 fps - 50% CPU load with iGPU at 100%, (almost) no dropped frames. The same exact 4 files in Premiere Pro 25.1 - 100% CPU, the footage is unplayable and choppy as hell. Here's the file, try playing it back (make 4 physical copies): https://drive.google.com/file/d/1bkT6wP8kCbiKLp9CR8uU2TQhu_Ho0nQp/view?usp=sharing It's a 422 10bit HEVC at 280mbit. A huge bitrate and an Intel 11/12/13/14th Gen iGPU decoded format. Play it back then watch the video here and note how fluent the playback of 4 (FOUR!) of those files was in 25.0: https://youtu.be/phc1NhUayGM So what happened between 25.0 and 25.1 that made this flavor unplayable? And in 24.6 it was even better, you know Here's my current project scrubbed through fast and played back at maximum speed: https://youtu.be/-EusOAkgj4s It's HEVC 420 10 bit. Not h264 you "updated".  Also what happened with the Display color management? Why on earth with it on do I get half of the frames dropped when my video does play back on the iGPU? See here: https://youtu.be/ex2uOokHilc  I've had this checkbox ON since it was introduced versions ago and never had I had any framedrops, now it's a single file on an empty timeline and 500 dropped frames out of 900. On a 14700K. What is going on? Is there some DaVinchi resolve spy in your team who does everything to ruin your product?  Finally, you say you updated h264 and it's NVidia preoritized now. In my case I can see that 420 8 bit h264 files actually have started to be showing in the iGPU graph. So you actually did something which made h264 files seen in the iGPU graph. So it's all the other way around to what you are saying...   ... View more

I got an email from Intel too. So, Adobe, it's your call   Hello Andrew, Thank you for your patience. I've concluded the investigation of the issue that you've encountered with the Adobe Premiere Pro application. Intel can confirm that such issue exist in Adobe Premiere (Adobe Encoder also) but it's not related to Intel driver, screen or video setting involving Intel driver. Below is our test results: Note - Same tests conducted in Windows 11 23H2 and 24H2 Test env: 14900K Z-690 OS Windows 11 23H2 (22631.4751), 24H2 (26100.2894) both with latest patches igpu driver: 101.6458 dgpu driver: 566.36 Prepared ffmpeg (and Adobe Premiere, Adobe Encoder) winget install "FFmpeg (Essentials Build)" Also prepared GPU-Z (monitoring GPU usage) and, HWInfo as a secondary view I've used some sample video. Command using Intel Quick Sync encoder/decoder Default: ffmpeg -i [source] -c:v [h264/hevc/av1]_qsv -b:v [bitrate] -y [output] Testing encoding only, using h264 Command: ffmpeg -i d:\100630-video-2160_2.mp4 -c:v h264_qsv -b:v 30k -y d:\test2.mp4 Testing decoder and encoder - first -c is for decoder, second -c id for encoder Command: ffmpeg -c:v h264_qsv -i d:\100630-video-2160_2.mp4 -c:v hevc_qsv -y d:\test2.mp4 Command using Nvidia Encoder Default: ffmpeg -i [source] -c:v [h264/hevc/av1]_nvenc -b:v [bitrate] -y [output] Testing encoding only, using h264 Command: ffmpeg -i d:\100630-video-2160_2.mp4 -c:v h264_nvenc -b:v 30k -y d:\test2.mp4 Testing decoder and encoder - first -c is for decoder, second -c id for encoder Command: ffmpeg -c:v h264_cuvid -i d:\100630-video-2160_2.mp4 -c:v hevc_nvenc -y d:\test2.mp4 Summary: In all tests all was working fine, encoding or decoding and encoding charts were showing some activity. Which means that it's not related to driver. Second part of test was to use Adobe premiere. Used same sample file, imported to new project. Project was set to use OpenCL rendering method (not CUDA). Adobe premiere was set by default to use iGPU and dGPU when decoding and encoding videos under hardware accelerated mode. Next step is to start playing source video while looking on task manager charts. Also this short manual helps [https://www.pugetsystems.com/labs/articles/what-h-264-and-h-265-hardware-decoding-is-supported-in-premiere-pro-2120/#Run_this_Test_on_your_System_Windows] Especially hotkey Alt+Ctrl+F12 to open the Debug Monitor and expand “Importer.MPEG” to find which hardware was responsible for decoding. In all tests decoding was done by Nvidia, rendering looked like iGPU+dGPU. The only scenario when iGPU was used for decoding was when dGPU was de-selected from hardware acceleration. Summary: There were some situations when task manager didn't show any activity of iGPU or dGPU when used in Adobe premiere, while GPU-Z was presenting a real values in monitoring tab. It looks like a combination of OS + App issue but mostly, App related. Considering the situation and our findings, it would be in your best interest to directly consult with Adobe support and Microsoft Support regarding this error so that the application's behavior is corrected. I'll proceed to close this case now. Feel free to contact us if you have any concerns or clarifications Best regards, Ernesto C. Intel Customer Support Engineer     ... View more

The circle of suspects has narrowed. Thank you @JonesVid for the info. My Intel contacts have kept silent. At least we now know who's the one... ... View more

Another interesting behavior in Premiere Pro 25.1. Here is a fully software decoded HEVC 420 10 bit which should be hardware decoded: File info:       Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 1 min 44 s Bit rate : 50.4 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Original frame rate : 29.970 (29970/1000) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Bits/(Pixel*Frame) : 0.203 Stream size : 625 MiB (94%) Encoded date : 2000-03-21 18:26:12 UTC Tagged date : 2000-03-21 18:26:12 UTC Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : hvcC Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 1 min 44 s Bit rate mode : Constant Bit rate : 288 kb/s Channel(s) : 1 channel Channel layout : M Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 3.54 MiB (0%) Default : Yes Alternate group : 1 Encoded date : 2000-03-21 18:26:12 UTC Tagged date : 2000-03-21 18:26:12 UTC Other #1 ID : 3 Type : meta Format : djmd Codec ID : djmd Duration : 1 min 44 s Bit rate mode : Variable Title : DJI meta Default : No Alternate group : 5 Encoded date : 2000-03-21 18:26:12 UTC Tagged date : 2000-03-21 18:26:12 UTC Other #2 ID : 4 Type : meta Format : dbgi Codec ID : dbgi Duration : 1 min 44 s Bit rate mode : Variable Title : DJI dbgi Default : No Alternate group : 5 Encoded date : 2000-03-21 18:26:12 UTC Tagged date : 2000-03-21 18:26:12 UTC Other #3 ID : 6 Type : Time code Format : QuickTime TC Duration : 1 min 44 s Frame rate : 29.970 (30000/1001) FPS Time code of first frame : 18:26:05;04 Time code of last frame : 18:27:49;03 Time code, stripped : Yes Default : No Alternate group : 2 Encoded date : 2000-03-21 18:26:12 UTC Tagged date : 2000-03-21 18:26:12 UTC         And this is when I open the same file in PotPlayer:   As usual: 14700K, 4080, Win 11 24h2 up to date, latest iGPU and Nvidia studio drivers. In case you forget. ... View more

Hi, @Kevin-Monahan or the ones who watch this discussion from Adobe staff. Seems like this problem cannot be resolved. As far as I understand there IS some audio transcoding once the export starts and the only problem that all Premiere Pro users have with it is Premiere Pro showning 0% progress during this process. Media encoder on the other hand shows this progress fine. So cannot Adobe just make the progress bar work as it should - i.e. show the actual progress of the audio rendering?  I had a simple project yesterday. It was an hour long screencast in h264 recorded with NVidia overlay. So after I cut it in quite a lot of pieces I still had to wait for this audio files rendering to finish which showed 0% all the time. It had no effects, overlays, text layers, anything, just obe video clip with the sound:   I restarted the process several times thinking that my export just froze. In fact Premiere Pro was doing this audio rendering but in the background showing 0% till the process was over. Should the process have shown the actual progress, I'd have had no questions. So this 0% progress is the only thing that should be fixed. We - Premiere Pro users - can wait another 3-5 minutes if we actually see what is going on ... View more

About this. OpenCL is on the whole a renderer engine. It's old and not exactly optimized (correct me if I'm wrong here). It should be used when there's no NVidia alternative, like a no-GPU configuration or an AMD card. What we should look at is the checkboxes in the Prefetrences > Media. This is the acceleration of h264-265 decoding, even with the Cuda as the renderer. And as far as I know QSV is still faster for decoding than even 4xxx NVidia cards that is NVENC engine. The 5xxx cards may appear faster for decoding, but Intel is still avead with the current generation. My tests above show that once my iGPU stopped being used in the same project it used to be used for decoding, with NVidia decoding only the overall system load rose as well as I started noticing lags I had never seen before. NVidia encoders are faster, that's true. The decoder in Intel CPUs not only is fast, it offloads the CPU itself and the videocard for the rest of the tasks. So NVidia being faster is arguable at least untill the 5xxx series come out Oh yeah, in the videos below see the one with the OpenCL + Intal and NVidia. Despite the fact it's on OpenCL, both NVidia and Intel work ... View more

Hi, @Michael Scrip  Exporting with an iGPU is a different thing from what we are stuggling here (we deal with a realtime playback issue, i.e. decoding, not the encoding issue like in your case), but still yours is another manifestation of the problem and it should be considered too. ... View more

Hi, @jamieclarke  Don't know if speed refers to the same group of properties, but it cannot be transferred to any other layers via copy-pasting attributes too. Time remapping - can be. Speed - cannot. I know it's been always like that, but I think it's time to include speed to copyable properties too.  By the speed I mean the one that can be changed in the CTRL+R window       ... View more

Hi, @Annika Koenig  The problem I was referring to back in Oct 15, 2024 manifested itself with the the said footage (with the same resolution as of the sequence) more harshly than that small frame jump of yours. Please see my video attached in the first message. It may be the same case, but our footage differ in resolution ... View more