Skip to main content
Known Participant
August 29, 2022
질문

Premiere Pro crashing at the most random times of simple editing

  • August 29, 2022
  • 3 답변들
  • 2514 조회

Adobe Premiere Pro crashing after a simple editing task, this is just getting out of hand. Why is this program becoming so unstable.

See video:
https://youtu.be/mLvv1XepQ3w

Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
Motherboard: ASUS TUF GAMING PLUS PRO X570
BIOS: 3603 (type: UEFI)
Processor: AMD Ryzen 9 5900X 12-Core Processor (24 CPUs), ~3.7GHz
Memory: 32768MB RAM 
Card name: AMD Radeon RX 6800

이 주제는 답변이 닫혔습니다.

3 답변

Known Participant
September 9, 2022

Update on my troubleshooting steps. 

1. Not alt-tabbing seems to keep Premiere Pro more stable, with less crashes. However with a 5900x CPU and Radeon 6800 GPU, Alt tabbing should not be a problem. As it isn't within other NLE's, Or OBS or DAW's.

2. I tried using Proxy's again. (Bought a whole new PC to avoid having to deal with proxy's, but hey, sure let's try it the old way I used to work). Playback improvement, but alt-tabbing still makes Adobe very unstable.

3. Moved my files from a HDD to a samsung T5 SSD ( I usually always edit from this SSD, but lately I've been dealing with lots of multiple projects. thuss too little space. No improvements.

4. Upped my RAM Speed, as it wasn't on it's full potential yet in auto settings. No improvements.

I'm not sure wether this is AMD-Premiere Pro related again, but I feel like Adobe is just very unstable with AMD, even though it claims my computer should be fully supported.

R Neil Haugen
Legend
September 10, 2022

That's a pretty decent troubleshooting bit there. And a good post about it.

 

Your system seems to run quite differently than mine, which is a 3960X with 128GB of RAM and a 2080Ti. The main difference seems to be that AMD GPU.

 

My rig doesn't have issues with Alt/Tab. So yes, it might be that the AMD GPU is problematic. Or a driver issue. I know there have been reports that although Premiere is running better now on AMD GPUs than it used to, it still runds better on most later Nvidia GPUs. Which is why I went with Puget's suggested GPU.

 

Yet among the apparently several million PrPro users, there have to be a fair amount with AMD GPUs. Why are some having issues, and others not so much? That's the kind of thing that I can't answer, and drives me batty. Variability between users.

 

Neil

Everyone's mileage always varies ...
Known Participant
September 15, 2022

Yeah it seems that it all comes down to my AMD GPU, again. 
(See my other threads where I'm already having problems with my AMD GPU and Premiere Pro
https://community.adobe.com/t5/premiere-pro-discussions/windows-file-browser-doesn-t-appear-or-gets-stuck-behind-premiere-pro-program-freeze/m-p/13188711#M429503

https://community.adobe.com/t5/premiere-pro-discussions/low-exception-error-gpu-filter-universe-plugin/m-p/13181256#M428947



However I did come across this thread. Where someone has the same GPU as you, but a 3950x CPU:
https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-freezes-and-crashes-when-alt-tabbing/m-p/13199180#M430333

 

He's having quite the similar problem.

R Neil Haugen
Legend
September 1, 2022

So V1 is the nest of the Fuji clips, V2 is the nest of the Panny clips, and V3 is the BRAW.

 

With the BRAW being a continuous run, you could simply do a multicam selecting all the clips. Premiere will probably put the 'cuts' clips on separate tracks, but expert multicam guy Jarle Leirpoll suggests that ... and then opening the multicam and quickly dropping all the same-camera clips onto one track.

 

That would avoid the nesting step. Jarle has the best book on pro work in Premiere Pro, 1200+ pages, in The Cool Stuff in Premiere Pro  available in both kindle & paperback versions. I have both.

 

And also he was the chief author of their new and detailed document, Adobe Long-form and Episodic Best Practices Guide  ... which has a very good section on multicam work. And he expanded on that part on his site ... Premiere Pro Multicam ... all short, direct, and well presented. 

 

Neil

Everyone's mileage always varies ...
Known Participant
September 1, 2022

Correct. However I wouldn't see how avoiding nests should solve my problem. Nesting is an official Adobe feature right, shouldn't that just work properly?

With opening the multicam do you mean opening the multicam-view in Adobe right? I get that you're suggesting a better workflow, however I feel comfortable with mine and i'll surely look into it when I've got the time but for now I just got too many projects to finish. 
I'm using the nests to speed up my syncing process. Because if I had to leave all clips seperate following eachother I'd have to put cuts in the BRAW footage to each sync them up.

Also the whole sequence has already been edited, which is an edit of 30 mins long. I'd like to avoid redoing that whole edit as it would cost me days again. For now the only option seems to avoid alt-tabbing. AKA not getting distracted by other browsers and programs and using my laptop besides my PC to look things up. This until Adobe fixes it's stability.. which lately seems to be following the same line as the western world's health..downwards.

Known Participant
September 9, 2022

Going to the original individual clips in the Project panel and bringing them up in the Source monitor, then using Lumetri, is a good way to grade all uses of that clip in your multicam. Then you're not having to grade each 'instance' of that clip in the sequnce.

 

I'll select say the 2, 3, or 4 clips original clips in the Project panel, right-click, open in Source monitor.

 

Neil


Sure, that were if you would not want to use that clip with different colors in a later sequence, within the same project. To avoid having to grade each 'instance' I always grade my full length clip, BEFORE I cut them. This works best 'for me'.

However critizing my workflow isn't really fixing another issue/error I discovered within Premiere Pro. 

R Neil Haugen
Legend
August 29, 2022

From what little I can see in your video, it looks like you've got two tracks of either nested or multicam media, and a third track on top.

 

What's the media involved in all that? Any other effects used on it?

 

Neil

Everyone's mileage always varies ...
Known Participant
September 1, 2022

Hi Neil,

It's all Panasonic Gh4 MP4/MOV H.264 4:2:0 footage and Fujifilm XT-4 MP4/MOV H.264 4:2:0 (Full Range) footage. When doing long recordings (30 mins) these camera's split up 30 mins into multiple clips. I use nests inside premiere pro to make them one long take again. (see the picture included)

However I do think it might have something to do with either the blackmagic raw filetype (12:1 compression) or the large filesizes. (It's stored on a relatively new (2022) 4TB external HDD, brand: WD elements) 
And it only happens when I use alt-tab to check my browser or open another program and then try to continue back in premiere pro. As long as I stay in Premiere Pro no crashes occure, footage runs fine with about 20fps a few stutters but nothing too crazy. Adjusting lumetri works fine and editing seems smooth. But whenever I switch to another program or to my browser and come back it either freezes, stops rendering the program view or crashes. 
This is also why I suspect it has something to do with large file sizes or BRAW footage, because when working in smaller a smaller project with only 2 recorded livestream clips of MP4/H.264 (both clips are aprox 60mins) no crashes seem to happen and everything works fine when I alt-tab or switch to another program or to my browser.

 

R Neil Haugen
Legend
September 1, 2022

So is the Fuji recorded in BRAW?

 

 

Everyone's mileage always varies ...