Skip to main content
CMRMediaProductions
CMRMediaProductions
Participant
November 28, 2022
Question

Premiere Pro v.23 update has CPU 100% spiking issue

  • November 28, 2022
  • 2 replies
  • 1975 views

Hey there! Having the same issua all of a sudden. Editing for my clients last month was peachy clean. This month Premiere is bricking my PC. 

 

I've tried PP2022 and PP2023, all drivers are up to date, I've completely cleared the cache. No idea what or why but the "experts" answering in this thread do not give me much hope. 

 

Specs: 

i7 11700 KF

RTX 3070

32gb 3600mhz RAM (2x16bg)

 

Footage specs:

4K 60fps in a 4K 30FPS timeline. Runs fine until I try to speed ramp or adjust anything. Playback at 1/4. 

 

I have been editing this way for this client since 2020 and have never had any issues. All of a sudden its an issue. 

 

This topic has been closed for replies.

2 replies

MyerPj
Community Expert
MyerPjCommunity Expert
Community Expert
November 28, 2022

Also, you could use AE to create the reverse clip, and then export out as ProRes.

    Kevin-Monahan
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    November 28, 2022

    Hi,

    Sorry for the issue. When you have the CPU spiking like this, it is a sign that your project is corrupt and needs repair. There are a few ways to address this.

     

    One is to import the old project into the new one. This task is often all you need to do if it is a simple project.

     

    A more complex project sometimes needs to be rebuilt in the new project by reimporting assets, deleting unnecessary sequences, and so on. For necessary sequences, copying and pasting contents from old sequences into new ones is another helpful rebuilding technique. Larger projects can be divided into smaller ones and collated using the Productions feature. This situation has happened to all of us.

     

    A couple of other observations is that you do not have an iGPU, so (like AMD CPUs) any H.264 or HEVC content needs to rely solely on the GPU for any accelerated processes for these formats. Look into using proxies or transcoding to ProRes LT, and even smart rendering, as workflow alternatives due to your system being more heavily stressed by these formats. You find some workflow wins here at the expense of larger hard drives (which you need for ProRes LT).

     

    Because of this shortcoming, you should ensure that the media is decoding H.264 and HEVC media as expected. If it is not, you may need to roll back a driver version.

     

    Please also check if Project Settings > General has the Mercury Playback Engine enabled. 

     

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    CMRMediaProductions
    CMRMediaProductionsAuthor
    Participant
    November 28, 2022

    Hello, 

     

    Thank you for the reply. Upon further tinkering, it seems like my issue stems from using the "reverse speed" function. I went in on my own and checked some of the things you mentioned beforehand. Mercury playback is enabled. Since I have never had any issues with this workflow before, I did a bit more digging. It looks like the client I am working with got a new camera and instead of me receiving 4K 30fps XAVC files from a Sony FS5 MkII as I have from them for the past year, instead I received the following:

    Type: MPEG Movie
    File Size: 160.15 MB
    Image Size: 3840 x 2160
    Frame Rate: 59.94
    Source Audio Format: 48000 Hz - 16-bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00;00;51;00
    Pixel Aspect Ratio: 1.0
    Alpha: None
    Color Space: Rec. 709
    Color Space Override: Off
    Input LUT: None
    Video Codec Type: HEVC 10 bit 4:2:0

     

    As far as project complexity goes, this is a product video that (when the issues first arose) was simply a .wav music file with a 10-second video-only clip ontop of is. The timeline is 29.97fps and the clip was 59.97 interpreted to 29.97. The reason for the need to use the reverse speed function was that the pan they had sent was left to right when the rest of the footage was right to left and I needed everything to match. Only once I added this to the clip did the issues start. Do you have any advise on how to fix this since it has never happened before, or any insight as to why this is causing Premiere such an issue out of the blue?

     

    Thanks in advance. 

    MyerPj
    Community Expert
    MyerPjCommunity Expert
    Community Expert
    November 28, 2022

    You can always create a new sequence and do the reverse time there and then export out as a ProRes. For me, PR LT is good enough for everything I do, so I use that. You could export at plain ol' prores and that file will not loose anything visually, and then you can put the exported clip into PP.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices