Adobe Premier Pro Freezes repeatedly and predictably again and again and again

Forum|Forum|2 years ago
March 15, 2024
3 replies
770 views

Processor AMD Ryzen 9 5900X 12-Core Processor 3.70 GHz
Installed RAM 64.0 GB
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 22H2
Installed on ‎9/‎25/‎2023
OS build 22621.3296
AMD Radeon RX 6700 XT

Part of using premier for me is closing and re opening about every 5 minutes. I had an older PC so I decided to get stronger hardware and assembled the one spec'd above. Zero change.

I can open a project with just a couple 1080 clips in it and with near 100% consistancy, drag a video file from Windows explorer to the project window or timeline and premier stops functioning. Either it quits responding or freezes. Sometimes I can move the play head around but the picture never changes.

Here is a video of me making it freeze just by adding a clip. Why are we paying for this product to perform terribly so consistantly?

https://www.youtube.com/watch?v=MA8nd5z4q_I

This topic has been closed for replies.

R Neil Haugen

Legend

1) Is that an internal or external SSD?

2) Where's your cache files?

3) I'd like @RjL190365 to pop in, because I think your system may not be equipped to handle long-GOP media, and your clips are all long-GOP. Which could be the heart of your problem.

Everyone's mileage always varies ...

B

Bryan233923755bq7Author

Known Participant

internal SSD

Cache: AppData / Roaminf / Adobe / Common on the C drive
I tried moving them to the editing drive to see if that helped and I didn't notice a diference.

What are long GOP media files?

R Neil Haugen

Legend

Search for "long-GOP video files" maybe. This format is great for fast compression and writing to card in-cam as they have specialized chips in the cameras for that. But the GOP is "group of pictures". Which to me is a total misnomer.

You actually only have a complete frame every 9-30 ... or in the case of GoPro's, maybe even 100 or more frames. Those are called iframes.

In-between, you have data sets in table format of 1) the pixels that have changed since the last iframe 2) those that will change before the next iframe or 3) BOTH. GoPros are even throwing in partial iframes now.

So to play it back, the NLE has to decompress and decode and fully recreate up to 100 frames of video ... just to play the next frame. Yea, that's a load.

It's far easier on the system to play 6k RED raw files than UHD GoPro files. Most of the pro colorists I work with don't like working with long-GOP clips at all. When the drives come in from a client, they see any long-GOP, that gets transcoded right off to maybe ProRes422 or a DNx format. And they work on systems that make yours and mine look puny.

For reference, I've got a 3960X Ryzen ... 24 cores, 128GB of RAM, and a 2080Ti with 11 GB of vRAM. And that's because I don't need to work with much long-GOP. And am willing to proxy or t-code if needed. If I were going to work with a lot of long-GOP, I'd use a newer Intel CPU with the internal hardware to process the stuff.

I don't think your rig has much long-GOP capability ... but that's why I asked about RJL. That user knows that stuff cold.

Everyone's mileage always varies ...