This has not happened this frequent until this morning when I try to start working for the day, I use BOTH Premiere Pro and After Effects a lot, and very rare do I get a crash. But this morning, I've gotten well over 10+ crashes happening when just booting up either software, and its making me nearly have a panic attack because I can't work.

I've tried restarting my computer, resetting preferences (that didnt work), manually deleting third party stuff I use, and right now I'm clearing up space on my external SSD which I use to edit on to see if that will work. If it crashes again, then I might just crash out myself.

Forgot to mention thanks commentor 😂

I'm on a mac studio with the M2 Max chip

32GB memory

MacOS Sonoma 14.6

and editing is mostly done on a Samsung T5 external ssd

eu gravei alguns clipes mas quando vou aplicar uma transição no começo de um clipe a transição não fica no centro de cada clipe?

I am currently attempting to export a video to YouTube, I’ve attempted to export it many times and was met with the same error message.

However, I got it fixed and am now attempting the export. The encoding processes take a little and then it gets to the uploading and the times get as high as 62 hours for the upload.

I’ve attempted uploading from Premiere, Media Encoder, and YouTube and they all take forever.

I have:
NVIDIA GeForce RTX 5070
Intel(R) Core(TM) i7 - 1700KF
48GB of installed ram
WD Blue SN5000 1TB
Windows 11 most recent

most of my clips are recorded with OBS

My WiFi works fairly well for other applications on my computer and everything runs fine.

I’ve tried a couple fixes but not have prevailed.

Does anyone have a solution?

Hi! I’m working on documentary right now and I wanted to do this effect when the picture is also in the back but the back is blurry (Picture 1). Works good so far.

When I go to export it (and when it’s exported) it looks like picture 2 and I don’t know how to fix it!!!!!

Please help 💔

I'm having a bit of trouble improving the audio on the videos I'm editing. Unfortunately, I don't have a microphone yet, and the vlog I recorded has some annoying background noise because I filmed it outside...

Anyway, I wanted to know if there’s a way to improve the audio a little so it’s not so unpleasant for viewers. I tried to fix it, but it ended up sounding like I was underwater, I don’t know how to explain it...

I used Essential Sound > Enhance Speech and DeNoiser

As the title suggests as of today my premiere pro 2026 keeps force closing itself after around 2 minutes of use. Doesn’t matter if I’m actively doing something in the timeline, just sitting in the project select screen or actively editing. After setting a timer multiple times I found that it force closes in the range of 2-2.5 minutes every single time. It doesn’t freeze nor does it slow down before it closes it just closes as if I had hit alt + f4. My specs are a 9800x3d, 5070ti and 32gb of ram (25gb allotted to premiere) so unless there is a very specific bug with these components I don’t think my pc is the issue. Since this only started happening today I tried many different fixes such as re-encoding the footage, turning off any hardware acceleration features, performing a DDU and installing studio drivers, and clearing preferences/cache/plugins, but unfortunately nothing has worked. Kind of at a loss right now so I am writing this in hopes someone else has experienced and has found a solution to this issue.

Thank you for reading and for any help you may offer.

So this is a strange one. Doing color correction through another vendor (who is using baselight), we found his exported files don’t match our source. But only by one frame. Like if you look at the export from him at the timecode 1:00:00:00, it would match the image of the source file at 00:59:59:22. But that would be the case for every clip. The image would be offset by one frame.

To make matters more strange, it looked like things were even further off on some clips (we figured out something else going on there and solved it), so we had him re-export everything with a few seconds of handles so we could adjust things and make them match. On that batch, only one file was off. Everything else matched perfectly.

But this apparently isn’t isolated to that vendor or baselight. Because we have had the same (or at least very similar) results with another project going through Resolve.

I understand if you don’t have frame rates matching between source media and sequence, or if you’re time remapping, or myriad other combos, that can cause issues with XML communications. But this isn’t drift or total mis-matches. This is the picture in one file being offset by one frame from the source file.