Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Will..
Contributor
Will..
Contributor
Activity
‎Aug 12, 2025
09:01 AM
For the last 3 releases (PR V 25, 25.1, 25.2, and now 25.3), Premiere Pro is constantly crashing every few clicks while working with Sony H.265 footage. This is the same footage from the same camera I've been using for 5 years in Premiere Pro on several hundreds of projects. Crashing while playing/moving the footage in the timeline has only started to happen extremely frequently in the last 6 months of Premiere Pro's releases, so this is definitely a bug. I'm also using the same computer (Mac Studio M1 Ultra with OS 14.7.6). Sometimes I get 10 minutes then it crashes, while other times I get just a minute after relaunching, but it's always when I'm doing something with the footage. It doesn't matter if I only have a few clips or a full timeline; it seems to hate the footage. I'll trim a clip then hit spacebar to play for example, and it'll crash. We shoot in 420-10 bit 4k h.265 because it's very high quality, and efficient. Our computers can play it back flawlessly without needing proxies, and it saves on hard drive space. It has been great for 5 years, but in the latest Premiere Pro versions, it is honestly terrible how much it crashes. I've submitted probably 30 crash reports, and waited 2 new versions, but it still is happening. I'm finishing projects in Resolve a lot more these days because of things like this, so I've been thinking of canceling my creative clown account because there's basically zero support to help me as someone who pays for the CC suite, and who has submitted numerous reports and waited over half a year to have this fixed while struggling to finish client projects. V2024 was somewhat stable, but we're back to how it was before Adobe put effort into stability, it seems..
... 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
2 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
3 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
‎Apr 25, 2024
06:08 PM
3 Upvotes
Well we are now comparing free software to a yearly subscription that's in the hundreds of dollars. That being said, Davinci Resolve does support .mkv files natively and has since version 17. Seems like Premiere is going backwards. As for Prores support, you can use the ffmpeg workaround to get the export in Resolve on Windows. For the cost of Davinci (free), I'm ok with that.
Mod note: off-topic conversation branched to the video lounge.
... View more
‎Apr 25, 2024
12:29 PM
Well, that's certaintly the case with remuxing the file with OBS, however, the problem still lies with Premiere removing support of .mkv files. Needing to rely on third party software is ridiculous. What is the point of Media Encoder then? What is the point of paying several hundreds of dollars every year for what's suppose to be the best suite of video editing tools if it can't even help me encode a video file to something that Premiere Pro can use? Why are we spending time converting files because of Adobe removing support? .mkv videos worked perfect 4 years ago. No muxxing required. no converting required. I've never had a problem with .OBS recordings up until Adobe choosing to remove support of .mkv which made my editing workflow significantly worse.
... View more
‎Apr 25, 2024
12:21 PM
If there is an OBS crash after recording for a while, with .mkv files the file will still be saved up until the crash. With .mp4 files, you lose the entire recording if it crashes. This is why so many people use .mkv and why so many people want .mkv support back in Premiere Pro. I just checked and it says .mp4 AND .mov will be unrecoverable if there's a crash. So this is not a solution. You haven't had any crashes? or are you getting around this with entering some sort of custom remux settings? Unfortunately, I've had 30minute plus recordings crash and lose the entire thing and have to redo it all.
... View more
‎Apr 23, 2024
10:57 AM
2 Upvotes
Premiere Pro STILL has the audio pop bug from imported .mp4 remuxxed OBS .mkv files!!!!! How is this still a thing? This has existed for years!! I've created another bug report in the past, and have mentioned it to Adobe directly via Twitter several times. I'm tired of importing screen recordings from OBS and then the audio POPS at random places. I have confirmed it is PREMIERE causing it because if I close Premiere and open it up again, the pop sound goes away, then as I use Premiere, it will show up again in a new spot. The issue wouldn't be so bad if Premiere didn't export the pop!!! If it exists during timeline playback, then it will render into the final export!!! It's something to do with audio cache files with Adobe. If it happens, I can even send it to Adobe Audition and see the pop in the waveform there, select it a heal it to remove it, then it goes away. Or if I simply tab out of Premiere and don't use it for a few minutes, if I tab back it, the pop will fix itself!!! Extremely frustrating because it's inconsistent. I'm on Mac OS 13.6.3, but it also happened on Mac OS 12. I've used several versions of OBS as well. For some reason, Premiere doesn't like .mp4 files from OBS that were remuxxed from .mkv files. Not sure if this has to do with Premiere deciding to remove support of .mkv files and there's a bug happening somehow, but when they removed support of .mkv files, I was FORCED to remux files to .mp4 to edit my screen recordings! So in either scenario, the Adobe team created this problem for no reason. There's a giant thread with over a dozen pages of comments on this forum regarding bringing back .mkv support. It makes absolutely no sense why Adobe would even remove it in the first place!!! Media encoder can't even import the file!! It's a joke. The point of media encoder is to ENCODE MEDIA!! but it can't!! Anyway, it's extremely frustrating that in the latest version of Premiere, this is STILL happening. Everything version of Premiere in the last 3-4 years has had this issue. FIX IT. Im sick of paying for a product that doesn't work, or at least stop taking away features like .mkv support that worked just fine. Whoever is making these decisions at Adobe should not be in charge. These decisions are making the lives of paying customers WORSE
... View more
‎Dec 27, 2023
10:35 AM
2 Upvotes
Once again I literally cannot complete my commercial project using Premiere Pro as a paying customer. I have to deliver the project today and Premiere decided it won't let me export my last 4 clips. No third party plugins, no luts. Literally only using Lumetri Color and Warp Stabilizer. The issue is warp stabilizer. If I remove it, it exports without error. I've tried restarting Premiere, restarting computer, adding new warp stabilizer, changing settings. It refuses to work. I get 'Error compiling movie' every time, so I literally cannot export and deliver this project on time because of PREMIERE PRO ONCE AGAIN!!! I just spent 1 hour exploring the clips individually to ProRes WITHOUT warp stabilizer, then importing the clips back into Premiere, then adding warp stabilizer, then exporting all the clips again to ProRes. That's the only way I could get it to work. A complete waste of my time. Best part is, earlier today I exported a dozen clips with Warp without problems in the same timeline, but today, it's giving me issues. Same footage, same timeline. This is unacceptable. Adobe advertises '5x faster timeline'! I constantly see ads for it. Cool! Too bad we can't export. How about you guys spend the money on engineers or managers that can make the program work instead of ads? Will there ever be a day where Premiere just works? Premiere won't even let me highlight the error code in the error prompt window so I cant even copy it here to share it so I took a screenshot below. MacOS 13.6.3 PR 24.1 Footage: Sony A7siii HEVC 4k 422 10bit Trying to export to ProRes
... View more
‎Dec 01, 2023
10:00 AM
I don't know why I fill these reports out; 99% of these get ignored, but anyway: Applying a preset I made to footage (Something I've done hundreds of times) to quickly grade footage filmed at the same location with the same lighting and for some reason in this version of Premiere the Lumetri Color setting Hue vs Sat curves isn't showing an accurate result in the program monitor. For example; If I reset it, or have no keypoints on it, meaning I haven't changed anything in the Hue vs Sat Curves, then turn it off and on, it will change the saturation on my talking head clip. If I add a single point on the line (Without adjusting the point). It seems to correct itself and then when I turn it off and on, the saturation is fine and doesn't change. If I turn off and on any of the other hue saturation curves, they work fine. It's subtle so I probably didn't notice this for a bit, which is frustrating because I spent a lot of time creating this preset with scopes to nail the skin tone, but I came back to this edit a few weeks later and with my eyes reset, I noticed that the skin tone seemed a bit off and looking into it. So I can't trust Premiere to keep the work I did. Even if it gets fixed, by the next release something else that worked fine will become broken... M1 Ultra Mac Studio MacOS 13.6 Pr23.6 A7siii 422 10bit HEVC footage
... View more
‎Dec 01, 2023
09:39 AM
3 Upvotes
It's been two months of v24 and it's still at 24.0 with so many people complaining about bugs. The top feature of this release is 'stability' LOL Where are the updates to address the issues paying customers are having? How are weekly updates not being rolled out for the people that rely on your software to pay their bills? Adobe is worth over 200 BILLION dollars. There's no excuse for this. Whoever is in charge of the Premiere team needs to be swapped out with someone who can manage all of this better, as the existing situation is just straight up deceptive. (marketing that it's stable when it completely isn't.) Last night I tried to do speed ramping in Premiere by copying and pasting work I've already done to a new clip (Something I've done many times in the past). It just wouldn't work this time. Half the clip glitched at the end, so I ended up not being able to finish the project in Premiere. I was forced to do it in DaVinci Resolve, which worked perfectly on the first try. (Their workflows are actually significantly better for slow mo speed ramping too. It's easy to make adjustments in comparison)
... View more
‎Dec 01, 2023
09:29 AM
1 Upvote
Just updated Mac OS to Ventura (13.6.1) with the latest OBS, and the files in Premiere Pro are still causing audio pops constantly. Would really love a fix for this; any comments from Adobe? Why is this happening all of a sudden?
... View more
‎Nov 08, 2023
04:54 PM
9 Upvotes
If you all haven't used the Facetune app, you're missing out. It's incredible. It can autotrack your footage and with just a few clicks do a great face refinement that includes a ton of stuff (Even more stuff than what DaVinci Resolve can do). It's really good. Adobe should just buy the FaceTune company and build it into Premiere. It seriously is a game changer. No masking/rotoing/tracking, or any other time consuming tasks. Seriously, it's a 10/10 for features and how well it works. It costs like $72/year though, so I canceled after the free trial. It blows my mind that Premiere isn't the leader in all of this. For the cost of Creative Cloud, Adobe should be the ones with all of these amazing features. PLEASE build into Premiere Pro quick-use features like the FaceTune app. Features that are a must from the Facetune app that are needed in Premiere (All of these auto-track and apply the effect with a slider bar for how much you want the effect): Smooth skin (Softens the skin on your face and evens it out to hide imperfections) Conceal (Blends in the areas under your eyes to hide wrinkles/bags) Vibrance (Adds vibrance only to the skin on your face) Glow (Adds a nice glow only to the skin on your face) Smile (Makes teeth whiter) Eyes (Can brighten, sharpen and increase the color of your eyes, as well as increase the white around the pupil.) Those are all MUSTS in premiere pro. They can be applied in literally seconds and auto track, it's amazing. You can then save the 'look' for future videos and apply it even faster with the settings you like. There are SOOO many other features like it can reshape parts of your face to your likely, change clothes, change hair, but those are honestly just bonuses. The list I mentioned above are the things that would be a massive help for video editors. Literally every client edit my production company does we spend HOURS on face refinement. It takes forever. I would rate this as an extremely important feature to have.
... View more
‎Nov 01, 2023
08:56 PM
This is already a feature request many others have made. In my opinion, this is a must.
... View more
‎Oct 11, 2023
11:16 AM
1 Upvote
Hi, Downloaded the latest version (24.0) as it says 'more reliable than ever. ' However, this is not the case. While working on a project, I included a .PSD image over my footage, nested it and then after waiting waiting over an hour for my large project to export, it failed. I then spent two hours trying to figure out why it failed because Premiere did not tell me which part of the project caused the issue. So after spending the time to figure it out, it was the .PSD image that did not export. A reminder that because it failed to export, I couldn't view the video to determine any issues visually. So I had to delete the .PSD image from my project sequence and have my edit look different than what I actually wanted, which is not good for a 'professional' program. My choices were basically to remove the image, or export an .XML and continue in Davinci. Due to timing for when I needed the project finished, I was forced to remove it. Best part is it is a duplicate of the original image I used earlier in the edit that exported just fine when I removed the duplicate at the end of the timeline.. Needless to say, I gave up on version 24 and started my next project on Davinci. I can't have a program making creative decisions for me against what I want. I wanted the image in my edit. How is it that Adobe's own image program (.psd) caused an issue in Premiere Pro. I've been importing .psd's into Premiere for many years without issues. Doesn't the various teams at Adobe talk with each other to ensure compatibility with each new release? Shouldn't this have been caught in beta?
... View more
‎Sep 18, 2023
11:11 PM
Hi, I want to speedramp footage WITH sound but Premiere can't do that so I'm forced to use AE. After doing the slowmo ramp and setting up the color space in AE and PR to be the same (rec709), when I import the dynamically linked composition into Premiere Pro, the footage doesn't match. One of them has more saturation. (Specifically the green trees at the top right) Why does the exact same footage look different between Adobe software using the same color profile? I've tried about 6 different color profiles just to see if I could get a match, like rec 2020, 2100, etc, but I was unable to get ANY profiles to match between the programs. I have the sequence in Premiere set to rec709 (Turn on and off tone mapping doesn't change anything). I have the footage itself interpreted to rec709. In AE, I have the footage interpreted to rec709, and the project working color space set to rec709. (Yes, I know the footage is over exposed, please ignore that. This is just a personal project filmed on an iPhone before the skateboarder rides into frame) What am I doing wrong? Is is this another bug with Premiere? Why does AE have options showing gamma 2.4 but Premiere doesn't? Shouldn't the footage be identical if the color spaces are set to the same??
... View more
‎Sep 07, 2023
11:04 PM
1 Upvote
Yep, it's unfortunate how little they listen to paying customers. These features would take just a few MINUTES to implement and would HELP us complete our work faster...
... View more
‎Aug 31, 2023
01:45 PM
10 Upvotes
Over the last several versions, Premiere is randomly adding audio pops/clicks in audio. I've confirmed it isn't in the source media. I will play through an edit I've made and randomly there will be an audio pop/click that wasn't there before. If I restart Premiere, it goes away, but it happens constantly, so I started to right click the audio clip when it happens, send it to Auditon, close auditon, then undo, so that it's back to normal. Then the audio pop won't be there anymore. So it's definitely a bug with Premiere Pro and how it's processing/rendering the audio files.
This was not a problem last year with the same audio format coming from the same program. My system is fast and transcoding is a waste of time; this bug shouldn't exist.
Happens in Premiere Pro v23.5 and 23.6 (This wasn't happening in the previous years versions)
My setup: Mac Studio M1 Ultra
OS 12.6.8
Audio is from h.264 .mp4 files recorded from an OBS screen capture.
For some reason it's not liking the audio in these recent versions. (I've edited hundreds of videos in prior versions and can guarantee this was not an issue before.)
I've noticed if I tab out of Premiere for like 5-10 mins then go back, it resets Premiere and the pops don't happen, then as I start to playback parts and move the timeline curser around, the pops come back. It's very random though. If the pop isn't addressed, it ends up in the export as if Premiere has baked it into the render preview files during the editing!!
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices