Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Will..
Engaged
Will..
Engaged
Activity
‎Nov 29, 2025
08:49 PM
Another crash report submitted and I've DMd you.
... View more
‎Nov 23, 2025
04:11 PM
Since this was changed to a 'discussion', instead of an 'idea', I guess the idea of preventing crashes is something they don't take seriously.. I would argue that a huge amount of people simply abandoned Premiere and cancelled their subscription due to the lack of stability. For example; a new issue just popped up for me; h.265 footage (that I've used in quite a lot of projects over the last 2 years and that was rendered in Pr 2023 or 2024) suddenly isn't playing in the lastest Premiere. It won't even export; just shows the first frame for the entire clip. This was not an issue in prior versions.
... View more
‎Nov 23, 2025
11:43 AM
1 Upvote
Currently, if anything happens that Premiere doesn't like, it just instantly crashes. Resolve RARELY does this because the code in the backend is MUCH better, obviously. There needs to be a way to prevent crashes built in, so that if Premiere gets stuck doing something, it knows what to then do automatically to prevent a crash; either by undoing the issue that cause it to get stuck, or by forcing Premiere to jump to a safe state and inform you of the issue + sending an automatic crash level report that the Premiere team then takes very seriously (As a top priority). So the idea is for the Premiere team to focus on stability to prevent crashes so users can continue working. (This is what a professional editing program offers.) Either do that, or reduce the price to FREE because Premiere in its current form is not a professional program with how often it has bugs, and crashes. For example, I've been experiencing the exact same crash bug for a year, from version 25.0 to the current 25.6. I've submitted over 50 crash reports, yet nothing changes. The Premiere team even said they'd look at my crash reports.. ... that was 3 versions back yet the same problem is happening, hence why I'm here yet again, reminding the Premiere team how terrible the stability is and that a paying customer is still having the same issue a year later with their poorly coded program. Let's do some critical thinking for a second: Why does After Effects RARELY crash? The answer is the Dev team behind After Effects is doing a much better job. It's that simple. The Premiere team is constantly pushing out flashy new features to pull in new subscribers, likely from pressure from the the marketing team, but regardless, it's causing the coders to neglect stability and testing. This is a horrible strategy long term. It's making everyone have a miserable experience to edit with Premiere. I'm constantly scrambling to finish paid client projects on time because of how unreliable Premiere is. It's unacceptable and shocking that this is how it's managed, especially after the 'stability fix' era of Premiere 3 years ago. The issue is 100% a management or skill issue with the Dev team. They are being told to not care about stability, or are being restricted by not having the time to address stability issues, or they simply do not have the skills like the After Effects team does to prevent stability issues.
... View more
‎Nov 23, 2025
11:22 AM
Similar issue for over a year now. Not sure if it's the footage, or MOGRTs, but version 2025 has crashed for me over 50 times across 30+ projects. The theme is either the use of MOGRTs, or Premiere hates h.265, h.264, or iPhone footage. Very frustrating since I spent approximately 30 hours creating a bunch of MOGRTs to have presets to speed up editing, and then it might be the reason I'm losing so much time trying to finish paid client projects.. Why do the Premiere Devs introduce features that break the program? And why do these issues then take years to fix? We just had a span of several years with very poor Premiere stability, then it was addressed and it was good for a couple years, and now we're back again at poor stability. This is really a problem with the APPROACH to how Premiere and the Dev team are managed. Stability is not the priority, obviously. And it will eventually cause most subscribers to stop paying. Not a good strategy for Adobe.
... View more
‎Oct 14, 2025
08:42 PM
Decided to update my OS, which took over an hour to do, and PR is still crashing; just submitted another crash report....
... View more
‎Apr 07, 2025
11:32 AM
It took the Adobe team 6 years to listen to customers and bring support back haha, but I guess it's better than nothing...
... View more
‎Jan 12, 2025
11:29 PM
Thanks for the reply. When you say 'next release', does that mean next update (v2025.2?)
... View more
‎Jan 09, 2025
03:14 PM
What new details do you need? This is easily repeatable. All you do is go to h.265 and deselect audio, then it automatically turns off HARDWARE encoding, which then takes forever to export. I'm on MacStudio M1 Ultra, on PR 2024, and PR 2025.
... View more
‎Jan 09, 2025
03:12 PM
THIS IS A MUST!! I requested this years ago, and Adobe just doesn't listen. Hopefully, they start... It's so frustrating when you create a new position keyframe.. It AUTOMATICALLY creates an auto-bezier keyframe, and you have to then select it and change it to Linear.. Makes no sense. In 20 years of editing, I have NEVER needed to use auto-bezier even once. I would rather having auto-bezier completely removed from the program if it means it's never defaulted on again....
... View more
‎Jan 09, 2025
03:07 PM
4 Upvotes
One of the most upvoted feature requests is adding back .mkv support. It has been a mess for the community since Adobe randomly decided to remove it for no reason. After several years, Adobe announced they would add it back and it's in beta (2024), well, I just updated to the lastest version of 2025 and Premiere Pro as well as Media Encoder cannot import the file type, which is a huge pain still. Work around have caused audio pops due to remuxxing, corrupt files due to segmented .mp4 files, lost files due to non-segmented .mp4 files, and a ton of time converting it with third party programs. DaVinci Resolve can import .mkv files natively. It's embarrassing that Adobe can't even convert .mkv files with their MEDIA ENCODER program. With the cost of Adobe, it's a joke that us users have to bend over backwards trying to workaround a file type that used to work in Premiere and Media Encoder for a DECADE. When will .mkv be put back in?
... View more
‎Jan 09, 2025
02:55 PM
1 Upvote
The issue I have confirmed was the REMUXXING process and Premiere Pro not liking variable frame rates. The .mkv files recorded in OBS when remuxxed to .mp4 seem to ignore the frame rate, so it ends up being set to variable frame rate. This in Premiere Pro creates inconsistent matches in playback, which causes the audio pops. It completely stopped for me after pulling my hair out for months when I switched OBS to 'Fragmented .mp4'. The audio pops did not happen again. HOWEVER, a much BIGGER problem was created; One of my screen recordings became corrupted and the entire 5 GB file had a dark purple frame for the entire video. I tried for hours to uncorrupt it, by remuxxing, encoding several different ways, using different programs, but the file is lost. So now I'm back to square one, which is recording in .mkv files, and this time I made a Terminal script using FFmpeg to convert the file to .mp4 without OBS doing the remux, and I force FFmpeg to convert it to .mp4 and keep it as 24fps instead of variable frame rate, with all other settings (Including resolution and audio tracks) the same as source settings. So now after each screen recording in OBS, I run the Terminal script and it converts the file and so far so good. With all that being said, it was ADOBE that created this massive mess. They used to be able to import .mkv files and everything worked flawlessly. I had no problems for YEARS until they decided to remove support. Even DaVinci Resolve can now natively import and work with .mkv files. Adobe is a joke these days. Over priced and you can't even use their 'Media Encoder' program to encode media. It literally won't allow you to import the .mkv file in Media Encoder....
... View more
‎Nov 14, 2024
02:22 PM
3 Upvotes
As the title suggests, if I deselect audio when exporting an h.265 file, it changes the codec to use software instead of hardware, making the export take about 10 times longer. From time to time I export b-roll clips from projects to help with creating future demo reels, or other projects and I do not need audio in those close (It's just for b-roll and it takes longer in the edit to deal with audio if it was there), so being able to export with hardware in h.265 with NO audio selected would be ideal. Can we get this looked into please? I brought this up a couple years ago but I guess it was overlooked. Thanks
... View more
‎Nov 14, 2024
02:16 PM
1 Upvote
I agree with your response. I ultimately ended up recreating them yesterday which took most of an afternoon, but it's done. On to the next. Thanks for the reply!
... View more
‎Nov 11, 2024
09:16 PM
I am not the only one. See here: https://www.reddit.com/r/premiere/comments/1b21o2h/is_there_any_way_to_fix_the_bug_where_all_the/ and here: https://www.reddit.com/r/premiere/comments/18j9dn5/lumetri_color_sliders_all_stuck_to_the_left_in/ and here: https://community.adobe.com/t5/premiere-pro-discussions/lumetri-color-sliders-not-working/td-p/14323482#M20170 The bug seems to be caused by any lumetri preset created in 24.1. Which for me was MANY! and I need to use them on dozens of projects... I have complex lumetri presets where I have 3 different lumetri colors applied in the preset, each one with their own masks, luts, specific adjustments, etc. It took a really long time to dial things in. So in other words, ANYONE using presets from 24.1 will have this issue still, but I assume most don't have many presets they rely on from 24.1, which is why it's not an issue for most now.. Opening a new project, then importing the project with the corrupt presets fixes it only while the project is open the first time, but then when I save and relaunch in the new premiere (Or previous 2 versions), it resets to being broken again! Even applying a brand new lumetri color doesn't work then. The only thing that gets it to work is literally deleting all lumetri color from the projects, then one by one opening a new premiere project and importing the old one, then saving... I even tried applying the corrupt preset, then saving it as a new one in the new premiere, but when applying it even in a new project, the corrupt original preset still somehow carries over.
... View more
‎Nov 11, 2024
08:11 PM
Just updated to 24.6.2 Build 2 and the issue is still there, so then I updated to 24.6.3 Build 4 AND THIS PROBLEM STILL EXISTS!!!!!! How is this possible? There's been THREE OR FOUR releases from Adobe over the last 3 months. So what do I do next? I go through the process of installing version 25, transfer all my settings over and then open the project up. IT STILL DOESN'T WORK!!!! THE LUMETRI COLOR PANEL IS BROKEN FOR ANY OLD PROJECT I OPEN. EVERYTHING IS STILL STUCK ON 0. ONLY NEW PROJECTS WORK!!!! This is unbelievable. I literally CANNOT use Lumetri color. It's completely broken............... If I start a new project, then import the old project it works. However when I save and reopen, every time i double click the project to open it from mac finder, or right click and open it with PR 24 or PR 25 it resets lumetri color to the broken state like the following, and if I try to adjust any of the parameters, it changes everything to max value completely washing out my footage. I've tried resetting the cache during launch, didn't fix, and I've tried now 3 different versions of Premiere. This is insanity.
... View more
‎Nov 01, 2024
03:32 PM
I requested this YEARS ago, but unfortunately the Adobe team doesn't care to listen to paying customers. I have not ONCE in my 17 year editing career wanted to use auto-beizer, yet it defaults to it constantly whenever creating position keyframes, which means you have to always select the keyframes and change them back to linear; it's a HUGE waste of time.
... View more
‎Oct 10, 2024
11:08 AM
4 Upvotes
After a long battle with the audio pops, I gave up and switched OBS from .mkv to the new segmented .mp4 and the issue stopped. Premiere did not like the remuxxed .mkv files. I suspect it has something to do with the remixing process in OBS, or that Premiere still can see it was made from .mkv somehow and since they dropped support of .mkv it's giving issues. I don't know, but for everyone with the issue and OBS, switch it to segmented .mp4 and it should solve the issue.
... View more
‎Sep 20, 2024
12:50 PM
I can confirm that the bug is not fixed. Every single project I open with the last two versions of Premiere cause the bug to happen. The only way around it is to open a brand new Premiere project and then import an already created project into it, as you suggested. Obviously this is not ideal. I just checked and see that there is no new update to Premiere, so am I missing something when you say the bug is fixed? Do you mean internally you've fixed it but haven't released it to the public yet? Dumping the cache did NOT work. I have dozens of projects for videos in the works, needing to open a new project and import the old project for every one just to be able to color correct is a huge waste of time. UPDATE*** After opening new PR projects and importing the bugged ones to fix it (Which took 25 minutes), I then went back and opened the first project that I created via the 'new project' workflow and it defaulted back to having the bug!!!! Every single project I spent time updating went back to having the bug when I closed and reopened!! This is unbelievable that Adobe would release a version with one of the biggest features that everyone uses completely broken.
... View more
‎Sep 09, 2024
08:13 PM
2 Upvotes
Updated to 24.5 and Lumetri Color now has all the parameters in the 'Basic Correction' tab stuck to the left of the sliders, even though I'm using a preset. If I try to change it, it doesn't work, instead it sets the value to 100. I can only have it stuck to the left or I can click it and it goes to 100% on for EVERY slider in that tab. So I update to 24.6.1 and still the same issue. Completely broken and unusable. I've tried it on an adjustment layer and on the clip itself. I have a deadline tomorrow and I CANNOT finish this edit because of this. Updates should FIX things, not break things. Who is testing this stuff before release? No one? Has Adobe moved on from their 6 months of caring about stability? Even if I apply a brand new Lumetri Color, it still doesn't work. Infuriating.
... View more
‎May 05, 2024
08:40 PM
There are 10s of thousands of people, if not more using the non-studio version, which they paid $0 for. That sounds like free to me. My point though was that .mkv works in Resolve, and not in Premiere, or even Media Encoder. Adobe has not a single program that I can use to play, edit or convert .mkv files, which is a file type that thousands upon thousands of people use all over the world. Not being able to even convert it in Media Encoder is wild. Anyway, OBS now allows 'Fragmented .mp4' which will skip the need to remux. I'm hoping Premiere likes a non-remuxed file.
... View more
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more
Copyright © 2025 Adobe. All rights reserved.
AdChoices