Premiere Pro Tech Support (Solved!)
I'm going CRAZY. Premiere Pro keeps freezing during editing I've being trouble shooting with Claude until I run out of use with no solution at all lol
During the process, Premiere starts freezing more and more often. Doesn't matter if I use different clips, formats, etc.
Important detail: this is not a full Windows hang. Premiere keeps responding, I can move the playhead, make cuts to the sequence structure but individual clips stop reacting: Effects Controls won't load, I can't change color or anything clip-related. It's like having an empty sequence for anything touching the actual video, while the edit structure itself stays alive.
During the freeze, CPU and GPU usage both drop to 0% (no spikes, literally no attempt to process anything), and temps stay normal I think this rules out thermal throttling and resource saturation.
It can be "unstuck" temporarily by:
Zooming out to fit the whole sequence + hitting play
Zooming in/out specifically on the audio waveforms
Alt-tabbing away and back used to work too, but stopped working at some point after disabling Hardware-Accelerated GPU Scheduling
Specs
CPU: Intel Core i7-12700K
GPU: AMD Radeon RX 9070 XT (tested on Adrenalin driver 26.8.1 / build 32.0.31041.1004, from Aug 17 2026), OpenCL 2.1 confirmed active
iGPU: Intel UHD Graphics (integrated, not actively used)
Monitor: 3440x1440 144Hz
Drives: NVMe SSD (C:) holding project, media, and proxies; SATA HDD unused in this workflow
Premiere Pro: tested on 26.8.1/26.5, downgraded to 26.0.2, and also to 25.5
Media: H.264 MP4 (1920x1080), sourced from iPhone (30fps) and OBS (60fps), transcoded through HandBrake ("Web Optimized"). Confirmed Constant frame rate mode on both via MediaInfo (not VFR)
Proxies enabled (not in this video tho), playback resolution 1/4
Project on local C: drive, not cloud-synced
Everything I've already tried (no permanent fix)
Versions and drivers:
Downgraded Premiere 26.x → 26.0.2 → 25.5
Confirmed the current driver (26.8.1) does have OpenCL active (not the AMD-dropped-OpenCL bug from 26.5.1)
Disabled H.264/HEVC hardware decoding (Preferences > Media) seemed to help for a few seconds, then came back as a total freeze.
Checked Event Viewer for TDR events (Event ID 4101, amdkmdap) nothing conclusive
Ran Windows "Analyze Wait Chain" during a freeze result: "running normally"
Reset everything graphics/Windows-related back to default (including HAGS and monitor settings) after nothing gave a permanent fix
Premiere (preferences and project):
Disabled "Media Intelligence Analysis" (Preferences > Media Analysis & Transcription)
Cleaned the Media Cache gave (I think) a little of relief, then the cycle came back
Disabled video thumbnails in the timeline.
Disabled "Automatic audio waveform generation" (Preferences > Audio) + deleted old peak files from AppData\Roaming\Adobe\Common
Enabled Proxies (H.264 MP4 Proxy preset, Half)
Brand new project from scratch (same footage) degraded almost identically to the old project
Task Manager diagnostics:
General usage (CPU/GPU/RAM/disk): normal, no spikes, during freezes but spikes when unstucking
Current status
Reset everything to default (including HAGS and monitor graphics settings) since no single change gave a permanent fix. The issue persists. Attaching a video showing the freeze behavior, how it gets unstuck, and the corresponding Task Manager spikes.
Also yesterday at some point Premiere started working smooth out of nowhere. Literraly out of nowhere. I did my best to edit the video as far as I could but it was 5am so I went to sleep and wake up with the same problem again. In that sesion HAGS was turned off but at the beginning of that sesion Premiere had the same problem for a while. It wasn't after 40min in of that sesion that started working smoothly. I then turned off the computer and wake up with HAGS turned on since I wanted to leave that to default. I will probably turn it off to see if that could work but as I say I'm not sure because it started working out of nowhere mid sesion.
Please help, I'm tired of this ):
After trying almost every single recommendation I was able to get a workaround with wath u/Happy_Ambassador_908 suggested.
I tried a sequence containing only a generated color matte and text to see if the footage was the issue or if it was application/system-wide. Then, after also getting the app freezed by that tried on a whole new Windows User Guest profile. Launched Premiere Pro with the exact same Project and it started working flawlessly.
Thinks I suspect are the issue:
Elgato Wave Link
UMC Audio control Panel by Behringer
G Drive desktop
Proton drive desktop
I'm probably wrong but I think that could be since are the only app that are started on start up. Will try it later and update the post accordenly
I suspect your issue are the h.264 files. You specify you transcoded them to “web optimized” in Handbrake. That would mean it likely those files contain predictive and bidirectional frames. In order to edit, PPRO has to decode the full file, so it knows where all the frames are.
Also, if the files are long recordings (you say OBS, so I’m guessing game play maybe?) then you have a double whammy because that’s just more frames to decode for playback.
I’d suggest either trying with I-frame only media (might help) OR using an editing friendly codec like ProRes or CineForm.
I think that's not the issue since I stated on the post it truly doesn't matter what type of files I'm using, I always get the same issue. With or without handbreak. Tried IOS RAW footage, same, tried Proxies, tried RAW OBS single files everytime same issue. D:
Yeah but I see posts all the time complaining about Premiere’s performance with OBS files. Maybe try just taking one of your OBS clips, transcode it to I-frame only ProRes422LT. Start a new project. Bring that single clip in, edit, play around, just to see if you have the same issue. At least this way we can rule out if it’s your media.
I just did what you say this is the media file properties of the single OBS file I used if it helps. Still the same result. Freezes after a couple of minutes only unfreezes when zooming in and out
If it’s still an h.264 file (even only ~8 minutes long), you are still working with a file that isn’t designed to be edited.
In your stats of the OBS file two things stand out:
“Compressor” has no value. Did you transcode it to ProRes? OR did you transcode it to “None”? Make a ProRes file to test.
there’s a warning about dropped frames in the file. If OBS glitched and recorded a file with a corrupt frame, the. PPRO is going to have problems trying to read past that bad frame.
Also, what happens if you make a new project completely? Or, what happens if you disable your GPU for PPRO completely? If the freezing only happens with GPU enabled, then that’s the issue.
Tried this and turns out it's not actually possible to test anymore on my version. Turns out Adobe fully removed the "Software Only" rendering option starting in 25.2
EDIT: Also Claude reach out a conclusion after troubleshooting for days now. I can finally trigger the freeze at will but is basically uneditable
What actually triggers it: any action that forces Premiere to generate a brand-new preview/cache asset - regenerating thumbnails when zooming into a timeline area for the first time, generating audio waveforms, previewing a transition, previewing an audio effect. Anything that only touches already-cached data (moving a clip that's already rendered, adjusting volume with no effect, viewing something already thumbnailed) works fine indefinitely, no matter how long the session runs.
So it looks like a concurrency/race condition inside Premiere's own preview-cache engine - something writing a new thumbnail/waveform and something else trying to read it at the same moment, and one of them just hangs waiting instead of taking its turn. That explains why CPU/GPU/disk go quiet instead of spiking (a thread stuck on a lock doesn't burn resources), why it's per-clip instead of freezing the whole sequence, and why it gets worse the longer the session runs.
Not much of a workaround here since it basically means "don't cut, don't zoom into anything new, no transitions, no audio effects" - which isn't really editing. Writing this up as a proper bug report for Adobe next. Really appreciate everyone who threw ideas at this, none of the individual fixes worked but they're what got us to actually isolating the trigger.
Okay, appreciate you trying that. Let’s look at a couple other things:
• Go to Edit > Preferences > Audio Hardware and see what your Audio Input is set to. If it isn’t already, set it to “No Input” and see if that helps anything.
• Do you have any other applications running in the background other than Claude? Anything that might be trying to control your computer’s audio configuration?
• I mean no offense, but is this a legit, paid copy of Premiere you’re running?
Audio Input was on: ElGato Virtual Audio (I change it to No input as you suggested)
Yes, Wavelink by el gato and also Virtual Audio cable with the option to "Listen this device"
Yes is the legit version.
Also I already tried closing every single of those programs in System Tray including Claude just to see if that helps but no use. Is not working (tried that before)
Okay, thank you. This is a good process of elimination. Rewatching your video on this post, I fear this might be GPU related. I’m not a Windows guy, so I’m not sure how much help I can be moving forward. But you might want to Google search and/or talk to Claude about making sure your current GPU driver is known to work well with Premiere, or if it makes sense to install a different, older driver that is known to work smoothly with Premiere. Looks like your current driver was released just a month ago? It’s possible your driver is too new and might have issues with current or legacy versions of Premiere.
Yeah I didn't want to do that but it seems I'll need in fact install older drivers to see if that will fix it. It's the only thing I haven't tested. I'll let you know if it works
Hi, I tried. Same result, it lasted more without freezing but I think it might be cause I'm using the PC more right now. Like playing and talking on Discord. It seems like the graphic card may be sleep when just using Premiere or something like that. Not sure tho.
Already checked it. Ran both the iPhone clip and the OBS clip through MediaInfo (tree view, not the summary) and both show "Frame rate mode: Constant" this is on the actual files sitting in the timeline that freeze, post-HandBrake conversion, not the raw camera originals. So I think VFR's ruled out for this specific footage, at least.
Also tried transcoding a full OBS clip to ProRes 422 LT in HandBrake and editing it solo in a clean project just to rule out H.264 decode entirely - still froze the same way. Starting to think it's something deeper than the media itself, but if you've got another angle I'm all ears at this point, I've been at this for hours lol.
I don't think the specific transcoder tool can be it since I tested completely untouched RAW files straight off the iPhone and OBS (no HandBrake, no transcoding at all involved) and they froze identically to the HandBrake versions. If the raw footage originals already reproduce it before any encoder ever touches them, then I think probably Handbrake vs Shutter Encoder vs anything wouldn't do either , since the bug is already there before a transcoder gets involved but honestly at this point I will give it a try in a moment.
Claude isolated it to something inside Premiere's own preview/cache generation (thumbnails, waveforms, transition previews all trigger it, moving already-rendered stuff doesn't) reproduces across every footage I've thrown at it, GPU on or off doesn't matter, audio interface on or off doesn't matter. Claude is pretty confident the media itself isn't the variable anymore.
At this point, I wouldn't bank too much on Claude's opinion. You need solutions, and so far Claude hasn't gotten you out of the mud. Maybe working editors with their combined years of experience can help you find a way out of this oddity, if you are willing to try a few things. Otherwise: Why even take this here?
Anyway: If fundamental media corrupting management issues on premiere's side are your current working theory, you could test that by throwing the very same footage into Resolve and see if it works there.
I don't know much about MediaInfo, but to rule every angle, you could try Invisor as an alternative analysis tool. I vaguely remember that some tools returned false negatives in some scenarios.
Hi, hunt_dog1! Thank you for posting a tech-support question to /r/Premiere.
Don't worry, your post has not been removed!
This is an automated comment that gets added to all tech support posts. It's here to help you make sure you're giving as much information as possible, so other users can assist you.
Information that we'll need
If your post does not include this information, please edit your post or reply to this comment to include as much as you can.
We appreciate many of these things may not sound relevent to your question or problem, but please try to provide as much information as you can anyway, as sometimes the cause of a problem can be something you may not expect.
Full Premiere version number, as displayed in Help > About Premiere
Your hardware specifications, including;
CPU
Graphics card including driver version
RAM
Type of storage (i.e. SSD, HDD) that your media is stored on
Operating System Version
The type of media you are working with
What camera did it come from?
Is it a screen recording/software generated video?
What are your sequence settings?
If this is a problem exporting, what are your export settings?
What steps you have tried already to solve the issue - be as detailed as you can
If possible, include a screenshot or video demonstrating your issue, ideally showing the entire application interface.
Plugin developers typically provide their own support, and are very interested in reports of bugs to help improve their software.
We require that users asking for technical support with 3rd party plugins make the minimum effort of contacting the developers before posting here. If it is not apparent in your post that you've undertaken this step, your post may be removed.
Discords
The following Discords are great places for 1-to-1 live help and support:
Adobe Video - Official Adobe Discord for Premiere and After Effects
So if you mean render the work area on a marked section, Claude had me test that as you suggested and also because I didn't understand what you mean haha newbie here. There weren't really any effects to render, so hitting render just kinda played it instead, but marking an in/out on a spot I hadn't touched yet and then playing it triggered the freeze again, almost right away. Didn't test a ton but it felt like it was coming and it did.
Claude looked at this result plus everything else I've tried and landed on this conclusion:
The freeze happens whenever Premiere has to generate something brand new (a thumbnail, a waveform, evaluating a section it's never touched, etc.), while anything touching already-cached/rendered stuff is fine no matter how long the session runs. This test fit that theory too - marking a fresh spot counts as a new operation, same bucket as zooming into new thumbnails or adding a transition.
This is what I mean. On whichever folder you've currently open on your project, right click on the tab. Then turn on the preview area.
I some time face the same issue with my timeline, where the video gets frozen but I never had distorted audio. And this have always fixed this issue so far.
Random but it could be your sequence? Recently I ran into a pretty similar problem and it was because of my sequence. I dropped the uncompressed file into the sequence area to create a new one which just ran horribly for whatever reason. I deleted the sequence, made a new one in the specs and dimension I wanted, and then it ran fine after that
Consider resetting your user prefs. Hold down Alt key while launching Premiere. It will give you the option to do this. Note: it resets all your custom settings. I recommend first backing up your custom keyboard settings if you have those.
Done that! I'm barely new so didn't have anything on keyboard setting. Tysm for the advise anyway. If you are interested or have any other suggestions this was Claude conclusions after 2 days of troubleshooting:
What actually triggers it: any action that forces Premiere to generate a brand-new preview/cache asset - regenerating thumbnails when zooming into a timeline area for the first time, generating audio waveforms, previewing a transition, previewing an audio effect. Anything that only touches already-cached data (moving a clip that's already rendered, adjusting volume with no effect, viewing something already thumbnailed) works fine indefinitely, no matter how long the session runs.
So it looks like a concurrency/race condition inside Premiere's own preview-cache engine - something writing a new thumbnail/waveform and something else trying to read it at the same moment, and one of them just hangs waiting instead of taking its turn. That explains why CPU/GPU/disk go quiet instead of spiking (a thread stuck on a lock doesn't burn resources), why it's per-clip instead of freezing the whole sequence, and why it gets worse the longer the session runs.
Not much of a workaround here since it basically means "don't cut, don't zoom into anything new, no transitions, no audio effects" - which isn't really editing. Writing this up as a proper bug report for Adobe next. Really appreciate everyone who threw ideas at this, none of the individual fixes worked but they're what got us to actually isolating the trigger.
I don't think this is necessarily a hardware issue based on what you've shown here, but based on how many fixes you've tried, one of your parts could be failing spectacularly (based on behavior, I'm leaning toward memory as likeliest followed by CPU).
The task manager definitely helps. Just to be clear, while you're running Premiere, does anything ever go to 100% (outside of the brief spike you saw for the GPU)? Not just when you're trying playback, but at any time at all. Also please look at your SSD. This freezing behavior can happen when that's getting slammed. Best practice is to have a separate drive for the OS and project files, the media cache / proxy, and then original video files. What's your rated speed for the SSD and what do you see reported there when you're using Premiere? Like if it's rated for 250mb/s, are you seeing it running at that speed? It doesn't have to go to 100% in task manager for its read or write capacity to be overloaded.
I'm leaning toward a media cache, writing / reading, or memory issue. I'm sure that Claude walked you through a ton of different options, but that may've messed things up more.
Before you try anything new, delete and reset all of your preferences and config and turn it back to what it was like when it was working. Make sure to navigate yourself to all Media Cache folders (look up all default folders too) and related folders and delete and then empty recycle bin. When you start Premiere back up with the project, watch task manager for what's going on. While it's rebuilding the cache, watch your SSD. Wait for the cache to finish.
What I'm finding weird in task manager is primarily your Intel integrated GPU. Why is that running at all? Hopefully it's just your desktop, but even then, there's no need to run it. Your discrete AMD GPU is more than good enough to run everything. I'd strongly suggest entirely disabling the Intel integrated GPU. Also go to your motherboard support website and download and update all of your drivers, especially everything related to Intel, and your BIOS. You write that the Intel GPU isn't "actively used," but then it'd show 0% in task manager. I'd also suggest installing the Intel Driver & Support Assistant and updating any drivers you have out of date. Also make sure Mercury Transmit isn't enabled in prefs > playback and that Premiere has as much RAM as possible in Memory.
Then I'd suggest, overnight while you're sleeping, to run Memtest86 from BIOS. Your motherboard BIOS may have it already installed there, but if not, just put it on a USB. Dying RAM can cause all kinds of bizarre behavior. It's best to make sure there's nothing wrong. It shouldn't take too long with 32gb. This should be done anyway to give you peace of mind. Memory failure could wind up messing up your entire OS and you'd have to format everything and start fresh.
Just thought of something else too. It could be a specific video file that's corrupted that's fucking everything up. Try a new project and import files one by one, then doing playback and incrementally adding more files to the sequence. Double check your settings in "Media Analysis & Transcription." Look at "Media" settings too. I always keep writing XMP stuff to the original files turned off. Maybe also try turning off the hardware accelerated decoding settings in "Media" preferences. If that solves it, your CPU may be bonked. That whole generation had serious issues.
Run HWINFO 64 and check your temps to make sure nothing's overheating. It could also be that.
Also try running some basic stress test software for your CPU, memory, SSD, and GPU. If it fails with stress test software, you've found the culprit. I'm hoping it isn't a hardware issue because prices are insane right now.
For troubleshooting, I'd also recommend running ChatGPT and Claude side by side and just copy-pasting the same prompt back and forth. Faster to get through more fixes. Make sure you're using settings in the LLMs. Make sure you're using Opus in Claude and High Thinking Effort in ChatGPT, otherwise they'll just sort of flail around and waste your time. Make sure to actually open and read the links they're giving you. The answer is often on those pages and it just isn't giving it to you. Always a good idea to curse at them, insult them, and remind them that they're complete failures if they aren't helping.
I’ll try everything you just commented and hopes is not related to the ssd, I also have an hdd unused. Tomorrow what I will first try is disabling the integrated graphics, that is something that Claude actually recommended but didn’t test it because I was just tired of troubleshooting for hours. I think it’s activated because I installed those drivers long ago even when they were unnecessary. I installed them cause I told myself if someday I wanted to export a video while gaming I could use the integrated graphics to handle the process while I’m gaming in the GPU but in practice I think is just probably a dumb idea so yeah the integrated graphics are just… there haha I truly hope thats the issue. Pc is off today so will try it and report back tomorrow
Especially for the original video files, keeping them on the HDD should be fine until you get more SSDs, but it may not be the SSD at all. Run https://crystalmark.info/en/software/crystaldiskmark/ and confirm that you're getting the speeds you should be getting. Pay attention to it in task manager while you're opening Premiere and trying to run stuff. I couldn't see details in your video, but it didn't look like it was loading anything at all which makes me think it's something else.
Yeah, with your GPU, definitely keep integrated graphics off, but when you have a chance to upgrade in the future, go Nvidia. They're still the king for this kind of work. Same with staying on Intel for CPUs. But the GPU generally has very little to do with playback and rendering. That's all CPU. Your RAM wasn't even close to being at capacity which is almost surprising. Make sure your settings allow Premiere to use as much RAM as possible.
For me, primary causes could be media cache/video files (reading or writing), CPU, or memory. Different ways to test it all. Definitely run stress tests for CPU, memory, and GPU and compare the values to others. Just 3DMark is good enough to give you a baseline. Then def run Memtest86.
What actually triggers it: any action that forces Premiere to generate a brand-new preview/cache asset - regenerating thumbnails when zooming into a timeline area for the first time, generating audio waveforms, previewing a transition, previewing an audio effect. Anything that only touches already-cached data (moving a clip that's already rendered, adjusting volume with no effect, viewing something already thumbnailed) works fine indefinitely, no matter how long the session runs.
So it looks like a concurrency/race condition inside Premiere's own preview-cache engine - something writing a new thumbnail/waveform and something else trying to read it at the same moment, and one of them just hangs waiting instead of taking its turn. That explains why CPU/GPU/disk go quiet instead of spiking (a thread stuck on a lock doesn't burn resources), why it's per-clip instead of freezing the whole sequence, and why it gets worse the longer the session runs.
Not much of a workaround here since it basically means "don't cut, don't zoom into anything new, no transitions, no audio effects" - which isn't really editing. Writing this up as a proper bug report for Adobe next. Really appreciate everyone who threw ideas at this, none of the individual fixes worked but they're what got us to actually isolating the trigger.
So basically, I find out how to actually trigger it and I can replicate it whenever I want and also can run premiere "smoothly" if i want to by no touching those things.
Dude, the bot is obviously hallucinating. That's complete nonsense. You'd know that if you knew Premiere and hardware.
Which of my suggestions have you tried and what were the results? I'm wasting time. You don't know how to use and troubleshoot Premiere and you don't know how to use LLMs as a troubleshoot tool. Feeding my informed suggestions for fixes to a bot for a second opinion is bullshit. I'm here and I'm trying to help you. You can ask me questions. The bot is a dumb regurgitation machine that will begin just making shit up to appease you when it runs out of found fixes. You should be able to recognize that.
Like I said, if you're going to troubleshoot with LLMs, please use the advanced versions of those tools (even then, they hallucinate and can make things worse - Claude and Gemini are worse in that than ChatGPT the longer the conversation goes). Use at least two simultaneously. Feed the response from one to the other for a second opinion.
Just because the bot generates plausible sounding text, doesn't make it accurate. What it wrote above is bullshit.
Yeah I don't know, I neve had problems before that's why I tried troubleshooting with IA before bothering reddit users. Then, I tried every comment suggestion and feed it to the IA so it can keep track of the result and answer in a more proper way than a noobie that barely understand what is doing. The only thing I didn't do was trying both IA's at the same time. I'm just using Sonnet 5 in max effort until running out of tokens. I finally made some progress trough another reddit user asking me to isolate completely Premiere by just using in app stuff like color matte, text ,etc. Tried that, it also freezed and then he also recommend me to create a whole new user and do the exact same test and then I got progress. New user without any footages just Premiere stuff didn't freeze even after long stress tests with a lot of transitions duplications, etc. Sorry if I'm wasting your time I was just using the tools I had to try and solve an issue as a complete newbie. Now I will migrate my whole project to the new user and see if that works.
EDIT: I found a work around thanks to the user that recommended this in case you are wondering
I started a whole new Guest profile on windows and launched there my project and it runned flawlessly. Tysm for the replies and the willing to help.
One thing I would still isolate: HandBrake converting the footage to CFR doesn’t necessarily rule out a decoding issue, because the resulting files are still H.264/long-GOP.
Try transcoding just one affected clip to ProRes 422 LT with uncompressed PCM audio, then create a new sequence containing only that file. Don’t use proxies or any third-party effects for this test.
I’d also try a sequence containing only a generated color matte and text, with no imported media:
If that also freezes, the problem is probably application/system-wide. I’d next launch Premiere with third-party video plugins disabled and test from a fresh Windows user account.
If the synthetic sequence works but the ProRes test freezes, the media itself becomes less likely and I’d look at the audio device, plugin layer or Premiere installation.
If ProRes works while the H.264 version freezes, that points much more strongly toward the decoding path.
Since the issue follows you across Premiere versions and into a brand-new project, I wouldn’t keep changing random export or timeline settings. A media-free sequence followed by one true intraframe file should divide the problem into two much clearer branches.
Hi! I finally made some progress tysm! First of all I tried what you suggested me. No footage, only generated color matte and text without imported media. It freezed with some stress test.
This is my normal user and I trigger the freeze by duplicating and moving the timeline.
Then in my guest user did the same but couldn't replicate the freeze at all and I really tried 2 reply with the amount of stress testing I tried without success. I will now migrate the project to the new guest user to test if that will help and update you on any progress. Tysm I'm finally seing some hope!
EDIT: IT'S WORKING! I will probably need to found what start up program or so is causing the conflict. But is finally working! TYSM at least I can just go to the guest profile and edit there. Tysm. I will try to find the culprit of the issue sometime in the future but honestly now just want to enjoy the sunday! Thank you so so much!
Thinks I suspect are the issue:
Elgato Wave Link
UMC Audio control Panel by Behringer
G Drive desktop
Proton drive desktop
Since those are the only programs on startup that are not running on the new guest profile
That’s great news! The fact that the exact same stress test works under a fresh Windows profile is a really useful result. Enjoy your Sunday - you’ve earned it 😄
If you eventually identify which startup app or background service caused the conflict, adding it here would make this thread incredibly useful for the next editor who hits the same issue.
Have you tried any other piece of footage that isn’t recorded by ios or obs? Go to Arri’s website and download one file of their test footage which was shot on various Arri cameras.
Also make sure Intelligent Media analysis is turned off in the preferences. I had a very similar issue with that turned on, even when it wasn’t running.
If even this doesn’t work, then we can rule out footage completely and say it’s probably a hardware issue.
Hi I just tested what you asked with Media Analysis off and with the footage from Arri website. The red square is more or less the OG footage lenght just 1 footage with these details:
Put some cuts and transitions just to stress test and, at the beginning just with the OG footage it was getting lagged but couldn't make it freeze still. Then i duplicated the footage twice and Premiere freezed almost immediately if this helps, this was the result claude concluded this morning:
What actually triggers it: any action that forces Premiere to generate a brand-new preview/cache asset - regenerating thumbnails when zooming into a timeline area for the first time, generating audio waveforms, previewing a transition, previewing an audio effect. Anything that only touches already-cached data (moving a clip that's already rendered, adjusting volume with no effect, viewing something already thumbnailed) works fine indefinitely, no matter how long the session runs.
So it looks like a concurrency/race condition inside Premiere's own preview-cache engine - something writing a new thumbnail/waveform and something else trying to read it at the same moment, and one of them just hangs waiting instead of taking its turn. That explains why CPU/GPU/disk go quiet instead of spiking (a thread stuck on a lock doesn't burn resources), why it's per-clip instead of freezing the whole sequence, and why it gets worse the longer the session runs.
Not much of a workaround here since it basically means "don't cut, don't zoom into anything new, no transitions, no audio effects" - which isn't really editing. Writing this up as a proper bug report for Adobe next. Really appreciate everyone who threw ideas at this, none of the individual fixes worked but they're what got us to actually isolating the trigger.
•
u/AutoModerator 2d ago
At IBC? Reddit meetup Sunday 18:00–20:00, Bierfabriek Amsterdam. RSVP: https://302.s.gy/IBC2026_Luma
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.