Hi @mayjain Thanks for the update. Sadly, having run some initial tests in v25.2, I'm still having the issue. In fact, it seems to be worse now. Main difference I noticed, was that after switching to Software Only (via startup menu), the render now takes roughly twice as long as in v24.6.4. The CUDA export (v25 default setting) on the other hand took the longest it ever has. These are the results of my initial export test, using my 17 minute reference timeline:   Default (CUDA) 10:30 min // 7:10 min // 27:30 min // 17:10 min   Software Only 8:30 min // 8:28 min (vs. 4:30 min in v24) I need to do some more tests to try and confirm what the new the baseline is, but if this is going to be the default going forward, it sounds like it's going to become a much bigger problem for me! ... View more

Thank you @Kevin-Monahan    And thanks for merging the two threads.  Fingers crossed something can be done to figure this out! ... View more

UPDATE - Bug Report merged with original discussion thread   Hi, I’m having an issue with very inconsistent export times, particularly when the Mercury Playback Engine is set to CUDA.   What's interesting is that when the Mercury Playback Engine is set to Software Only, my test timeline takes around 3:45-4:30 minutes to export. However, when CUDA is selected, the export can take up to 19 minutes.  That said, it can also take 7 minutes (typically right after I restart Premiere).   I originally made a post about this in the ‘Discussions’ section, as I wasn’t sure if there was something I was missing, or if the previous wisdom of 'if you have Nvidia, always enable CUDA'  had changed.  However, from what others have said, as well as the Adobe Support Chat person who remoted into my PC to troubleshoot, this seems to be a bug. I had some initial interest from some Adobe Staff on my previous post who said they were going to go off and do some testing, but I’ve not heard back for a couple of months.   I’m honestly just a bit sick and tired of being on a deadline and having to play the ‘should I cancel and restart the export’ game.  I would absolutely understand if CUDA wasn't any faster than Software based on whether or not the source/ export codec was able to benefit from hardware acceleration.  But for CUDA to be consistently slower just doesn't make sense.   Here’s a link to my original thread which has some more details. https://community.adobe.com/t5/premiere-pro-discussions/cuda-vs-software-only-render-engine-cuda-is-slower-than-software-only/m-p/15129466#M551316     The general overview is this:   Issue – With Mercury Playback Engine set to CUDA, export times are unpredictable and often take significantly longer than when Software Only is selected. Adobe Premiere Pro version number: v24.6.4 / v.25.2.0 (I use v24 daily, but have tested in v25) Operating system - Windows 11 Pro [23H2] System Info: CPU, GPU, RAM, HD: CPU - i9-13900K GPU - Nvidia 3070Ti GPU driver (Nvidia) - Studio (32.0.15.6590) / Studio (32.0.15.7216) iGPU driver (Intel) - 32.0.101.6557 RAM - 96 GB (48GB x2 - Corsair Vengeance DDR5 5600MHz CL40) Hard Drives C:Drive = Sabrent NVMe Gen4 SSD (2TB) Media Cache = Samsung 990 Pro NVMe SSD (2TB) Media = Samsung 990 Pro NVME SSD (4TB) Export = Samsung 850 Pro NVME SSD (256GB) PSU - EVGA 750w Video format: Mixed, based on different projects.  Normally I'll be editing using transcodes of the rushes, either DNxHD36 or ProRes422 Proxy.  However, I will frequently have projects where I pull in h.264 assets. Rushes themselves are typically XAVC based, ProRes, or H.264 Workflow details:  Mixed depending on the project.  Sometimes this will include Multicams, Essential Graphics, or Dynamic Linked AE comps.  However, the test export that I've been using is just footage, with no effects applied. Steps to reproduce - (Very important!) I wish I could give you some, but honestly I can't find a pattern.  In my test timeline, Software Only (Mercury Playback) is always faster (approx 4min).  But what I tend to find is that the CUDA (Mercury Playback) version will be fastest immediatley after I restart Premiere (7:30min).  This time then climbs with subsequent exports/ time.  Basically, it seems to be an issue that comes about after I've been using Premiere for a while. Expected result - Predictable export times Actual result -  Varied export times   FAQ Hardware decoding settings are set to both Intel and NVIDIA  Exporting to H.264 (with Hardware Acceleration enabled) Windows 11 Graphics Preferences (for Premiere/ After Effects/ Media Encoder) set to 'High Performance' Footage being used in test export is 4:2:0 (8 bit).  However, similar results have been seen with other codecs (for example XAVC 4:2:2 (10 bit)) I have tried reinstalling Nvidia driver (via DDU), rolling back to 556.12 and updating to latest GPU temp is around 45c during export (maxes out at 55c)     I'm sure there will have been bits that I've not mentioned, so any questions, feel free to ask!     ---UPDATE---   Funnily enough - I was writing this while I had an export going in the background.   That 18min timeline took 24min to export with CUDA (Mercury Playback) enabled, but after I switched to Software Only, it took 5:40min.   That's exactly the sort of thing I mean!     ... View more

Are there any moderators who are able to move this thread to 'Bugs' rather than 'Discussions'?     I'm hoping that it might stand a better chance of getting resolved that way! ... View more

Hey,   So I just got off with one of the Adobe customer service chat people who remoted into my computer and tried a few things. Sadly, I don't think we're much closer to a solution, but figured I'd update things here.   Main thing was rolling back my GPU driver to 556.12 (specifically the Game Ready version). Apparently there is an issue with the 560 series of drivers, so they recommended 556.12 as a stable option. I asked about Game vs Studio drivers and they said that Game was more optimised for now.   After Restarting Premiere and starting a quick test export of my baseline test, things looked like they were off to a promising start. But ultimately, it ended up taking about 8 minutes (for reference Software only does it in about 4 min). I then repeated the test immediately afterwards and the time climbed to 12 minutes, which is consistent with what I've found up until this point.   Sadly, the support rep didn't have a good answer for what was going on there. They were mainly focused on getting the GPU being utilised, which they were keen to point out was peaking at up to 100% "Utilisation" in task master during the export. Unfortunately, as I confirmed via a screenshot from last week where I was getting 98%, lack of 'Utilisation' doesn't seem to be an indicator of the problem.     One thing that they did suggest was that the reason for the fast Software vs CUDA export time was all down to the high amount of system RAM that I have (96GB). Essentially, what they were saying was that on simpler projects, where the RAM doesn't get filled, Software Only (i.e. CPU & RAM) will out perform the GPU. If the RAM get's overwhelmed, then the GPU would be a better option. So according to them, the answer to the question of "if I have an Nvidia GPU, should I set the Render Engine to CUDA", is... it depends. I didn't get a clear idea of how to recognise when one would be better than the other.  Which is obviously frustrating as it means I'm still stuck where I am, seconding guessing whether or not to cancel exports and restart them in the alternative renderer.   Ultimately, they said that they weren't sure what else they could do as it would be up to the development team to "analyse the algorithm". So, in short. There is apparently a known issue with the 560 series of GPU drivers, but rolling back didn't change anything for me. There also doesn't seem to be any sign that this issue is going away anytime soon. _____ For reference, I'm using: - Premiere Pro (v24.6.4) - Media Encoder (v24.6.4) ... View more

Scratch that.. Video Decode graph shows zero activity during CUDA export.  Not even any spikes...   Anybody have any ideas what this means?  Or more importantly, if anything can be done to solve it?     (I've edited my post above to avoid any confusion from my previous weird results)       ... View more

@MovieMutant   nice find - Premiere also wasn't in my list of apps.   I added and set the Graphics Preferences to 'High Performance'.  At first, I thought it had done the trick, because the render set off much faster. But sadly, it eventually slowed back down again and the CUDA export took 12 min (vs. 5min for software only).   For reference: I'm still using Pr 24.6.4 / Me 24.6.4     ... View more

@Alex367466572b5i did another test export, while keeping an eye on 'Video Decode'.   With the exception of some very occasional spikes of activity (which I couldn't really figure out a correlation to), there was pretty much no decoding activity going on.         ... View more

Things continue to be frustratingly inconsistent.    I've just done a test export with the exact sequence that I was referring to in my previous post and the CUDA version now exported in a time of 7:30, 10:45 and 11:45 minutes in repeated tests.  The Software export in contrast took 4:55min   Here's the export logs from today: 01/27/2025 10:49:55 AM : Queue Started - Source File: C:\Users\Jamie\AppData\Local\Temp\ProjectFile.prproj - Output File: E:\ProjectFile_(Software).mp4 - Preset Used: Screener_1080p_(w/Proxy+OutputTitle) - Video: 1920x1080 (1.0), 25 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:17:19:03 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 1.00 Mbps - Encoding Time: 00:04:53 01/27/2025 10:54:48 AM : File Successfully Encoded 01/27/2025 10:54:48 AM : Queue Stopped 01/27/2025 11:10:04 AM : Queue Started - Source File: C:\Users\Jamie\AppData\Local\Temp\ProjectFile.prproj - Output File: E:\ProjectFile_(CUDA).mp4 - Preset Used: Screener_1080p_(w/Proxy+OutputTitle) - Video: 1920x1080 (1.0), 25 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:17:19:03 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 1.00 Mbps - Encoding Time: 00:11:48 01/27/2025 11:21:53 AM : File Successfully Encoded 01/27/2025 11:21:53 AM : Queue Stopped       Here's the logs from last time, just to show how inconsistent things can be! 01/20/2025 11:45:33 AM : Queue Started - Source File: C:\Users\Jamie\AppData\Local\Temp\ProjectFile.prproj - Output File: E:\ProjectFile_(CUT01)_(SOFTWARE).mp4 - Preset Used: Screener_1080p_(w/Proxy+OutputTitle) - Video: 1920x1080 (1.0), 25 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:17:19:03 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 1.00 Mbps - Encoding Time: 00:03:56 01/20/2025 11:49:30 AM : File Successfully Encoded 01/20/2025 11:49:30 AM : Queue Stopped 01/20/2025 11:50:14 AM : Queue Started - Source File: C:\Users\Jamie\AppData\Local\Temp\ProjectFile.prproj - Output File: E:\ProjectFile_(CUT01)_(CUDA).mp4 - Preset Used: Screener_1080p_(w/Proxy+OutputTitle) - Video: 1920x1080 (1.0), 25 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:17:19:03 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 1.00 Mbps - Encoding Time: 00:18:54 01/20/2025 12:09:09 PM : File Successfully Encoded   Here's a screenshot of task manager during today's CUDA export   And here's the Software Only export         Thanks! ... View more

Hey there, I've not had any updates on this for a while and am still experiencing issues.   Just the other day, I waited 19 min for a simple 17 long video to export using CUDA.  This seemed crazy to me so I switched to Software Only and the export time dropped down to 4 min.   Not having a reliable idea of export times is quite frustrating and has already landed me in hot water on a few tight turnaround projects.   Given the responses so far, it seems like this isn't expected behaviour, so I'm guessing it would be a better to move this discussion to bugs.  Does anybody know if I can do this?  Or shall I just start a new thread over there and link to this one?   Thanks! ... View more

Chiming in to agree... but also add that an option to go 'BACK' to the previous bin level would be great.  It would make navigating clips in the project panel so much faster. ... View more

Thanks to everyone for the input and helping to clear up things up!  Glad to hear that there are others out there who agree that this would be a cool feature to add.   In the meantime, I thought I'd share the work around that I've gone with for any other Windows users who are interested. This is a script I put together using AutoHotKey v2 (it's my first time using it, so I am definitely not an expert). It's setup so that I just have to press 'F1' and it skips back 50 frames and then presses play.   AHK only works on Windows, but apparently you can do something similar on Mac using Keyboard Maestro.   It's a decent enough work around, but there are definitely some quirks.  Fingers crossed it get's implemented natively one day!     #HotIf WinActive("ahk_exe Adobe Premiere Pro.exe") F1:: { Send("{Escape}") Sleep(5) Send("{NumpadSub}") Sleep(5) Send("{Numpad5}") Sleep(5) Send("{Numpad0}") Sleep(5) Send("{NumpadEnter}") Sleep(5) Send("{Space}") } #HotIf ; Ends the context-specific hotkeys     ... View more

@DJP2014 A macro is a great idea for a halfway house, thanks for the suggestion.  Given how many custom things I've programmed onto my StreamDeck, I don't know why I didn't think of it before!   That said, would still be great to have it as a native shortcut with in Premiere.  Mainly, so that it's on my keyboard rather than via another peripheral (or requiring third party software like AutoHotKey).   For anybody who's interested, here's the StreamDeck macro that I created (via Multi Action button).  Happy for others to tell me that there's a better way of doing it!  Numpad -  Numpad 5 Numpad 0 Numpad Enter Spacebar     As I said, a good work around, but I would far rather see it natively! ... View more

  Thanks for the responses so far!   @R Neil Haugen – what you've described sounds like a great way to quickly work on a specific edit point, and it’s definitely something I’ll be adding to my toolkit. That said, it’s a bit different from what I was suggesting.   @DJP2014 seems to get where I'm coming from.   What I'm saying is that I want the ability to have playback, with pre-roll, while not being constrained by the post-roll point, whether it's looping or stopping.   Hopefully, my shoddy Illustrator work helps explain what I mean. The blue line represents what you’re describing, whereas the red line illustrates my suggestion.   ... View more

Assuming I’ve understood you correctly, I don’t think that would work the way I’m talking about.  That would link the playback to an outpoint. It would also require you to either set an IN and OUT point or enter a trim mode.   What I’m talking about is a playback shortcut that’s independent of IN/OUT points, Work Area, Trim Mode, etc.—just like the current Play-Stop Toggle (Spacebar). The only difference is that it would include a Preroll, so you could quickly review a section with some lead in.   Basically, I just want to be able to quickly press Play without having to worry about setting IN and OUT points first, or shuttling back a few seconds. ... View more

Good to know that I'm not going crazy and there's somebody else out there who's as confused as me!   FYI - @mayjain has gone off to do some testing at their end to see if they can give any insights. ... View more

Quick update for anyone coming across this in the future:   TL:DR - it seems to be sorted in v25.2 (Beta).     The issue was eventually identified as a GDI object leak that triggered every time I switched between sequence tabs. This was diagnosed by monitoring the 'GDI objects' column in Task Manager under the Details tab (you may need to right-click the header bar and add the column). When the GDI object count exceeds 10,000, Windows stops allocating new objects, causing the UI to become unresponsive.     By keeping an eye on the GDI figure while editing, I was able to figure out the interaction causing the number to spike. I was advised to try the v25.2 Beta, which seems to have resolved the issue (based on a quick test while monitoring the GDI objects count), athough I haven’t done extended testing. For now, I'm working in v24.6.3 while I wait for a stable release of v25.   Big thanks to @jamieclarke for all the help! ... View more

Yeah, I figured that might be the case.  Oh well, fingers crossed that Adobe updates the implentation in the not too distant future.  It would be really helpful.   Thanks for the responses! ... View more

Hi @mayjain - thanks for taking a look at it for me.  Do you have an email I can send things to?   ... View more

@mattchristensen Thanks for getting back to me. 1. No effects in this test sequence (except Timecode overlay) 2. Hardware decoding settings are set to both Intel and NVIDIA  3. Exporting to H.264 (with Hardware Acceleration enabled)   Although, (should have thought to try this earlier) exporting to ProRes 422 filps the results.  So CUDA exports in about 1 min, while Software only exports in 4 min.   So is this the answer then?  That you should change your render engine based on your export codec? ... View more

Sadly, uninstalling those two plugins hasn't helped.  I've just had another error.   At least this time the resulting Adobe UI x Glitch art was more interesting....   ... View more

Cool - I'll uninstall those and see how I get on.  I've also just emailed across the log files.  Thanks! ... View more

Hi Jamie - I'm not using the enhanced speech feature  (I don't tend to use anything in the Essential sound panel). I do use transcription quite a lot, however not in my current two projects, which have both been experiencing the same issues. The text panel is open on one of my tabs, but besides that, nothing.   I haven't got a massive number of effects on anything.  One of my current projects has a few Drop Shadows and Gausian Blurs, as well as Motion Graphic Templates and Dynamic Linked After Effect files.  But nothing too crazy.   On the other edit I'm working on (feature film, using Productions).  I have zero effects applied, and all of the footage is DNxHD36. That project has crashed over 8 times today (I've been saving log files after every crash - incase they're helpful?).   I have a decent number of markers (split so their duration spans the length of takes).  However, that's a very recent workflow change for me, and I've been having this issue for months before I started doing anything with markers.   I've found that anything to do with metadata (like search bins, or the metadata panel) can cause a series UI lag.  But can't say if that's related to crashing.  Just not used to relying so much on metadata in Premiere and I've discovered that it's very slow.     In terms of plugins, the only thing I'm aware of is an extension that I installed about a week ago.  It's called 'Timeline to Clip Marker Converter'  from EditingTools.io There hasn't been any noticeable change in performance or stability since installing it.   The only other relevant things I can think of are a couple of the outputs listed in Mercury Transmit.  Apparently I have 'Blackmagic Playback' and 'Nobe Omniscope Transmitter' installed.  However, they're both unchecked, as I use the one of the Adobe outputs instead.       I get a red popup error message in the bottom right hand corner of Premiere about 50% of the time.  The message tends to say something along the line of 'Unable to Create Image Buffer' (although not always). Premiere doesn't typically quit itself.  The UI glitches and the program becomes fully unusable.  But most of the time, I have to force quit myself.   I've attached some screenshots of some crashes from today.  Not the most impressive examples (they can get much crazier!), but they hopefully give a rough idea of what I'm seeing (obviously the lines covering things like file name aren't part of the glitch).     Let me know if there's any other info that could be helpful!  Cheers                       ... View more

Issue - Premiere will lock up several times a day, requiring a program restart to become functional again.   Adobe Premiere Pro version number: v24.6.3 Operating system - Windows 11 Pro [23H2] System Info: CPU, GPU, RAM, HD: CPU - i9-13900K GPU - Nvidia 3070Ti GPU driver (PC) - Studio (32.0.15.6590) RAM - 96 GB (48GB x2 - Corsair Vengeance DDR5 5600MHz CL40) Hard Drives C:Drive = Sabrent NVMe Gen4 SSD (2TB) Media Cache = Crucial P3 Plus Gen4 NVME SSD (500GB) Proxy = Samsung 990 Pro NVMe SSD (2TB) Media = SanDisk Extreme Portable SSD - USB-C (2TB)   Video format: Mixed, based on different projects.  Normally I'll be using transcodes of the rushes, either DNxHD36 or ProRes422 Proxy.  However, I will frequently have projects where I pull in h.264 assets. Workflow details: Again, mixed depending on project.  Sometimes this includes multicam sequences.  Most of the time I'm in a straight Premiere project, however I'm currently using Productions for the first time. Steps to reproduce - (Very important!) I can't reproduce it.  It seems to happen randomly.  But it consistently happens several times a day. Expected result - A stable platform Actual result -  Program lock up, often accompanied by error message (Error: Unable to create image buffer).     I am happy to attach any logs that might be helpful.  I have started to save them after a crash in the hopes that a pattern will emerge. For what it's worth, based on how things look when the issue occurs, it feels like it might be GPU related.     Happy to provide any more information I can  -thanks in advance for the help! ... View more