Anonymous

My feedback

  1. 164 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    86 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Okay, based off the comments below and some testing, I think I have a script based workaround. It changes the affinity to 2 cores for 10 seconds and then to 24 since I have 24 threads. If you have 32 threads (1950X or the likes) replace 0xFFFFFF in the second command with 1FFFFFFFF. This is simply a HEX number so you can use the windows calculator in programmer mode to calculate the required HEX number.

    1. Create a powershell script (.ps1) in notepad or Powershell ISE with this code:

    $APPCCset = Get-Process -ProcessName "Adobe Premiere Pro"
    foreach ($APPCC in $APPCCset) {$APPCC.ProcessorAffinity=0x3}

    Start-Sleep -s 10

    $APPCCset = Get-Process -ProcessName "Adobe Premiere Pro"
    foreach ($APPCC in $APPCCset) {$APPCC.ProcessorAffinity=0xFFFFFF}

    2. You'll need to change your powershell execution policy to RemoteSigned in Powershell:

    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

    The important part, Premiere must be playing back some media. If it's paused, changing affinity doesn't affect premiere no matter what you do.

    3. Run the script while playback, may take 1-2 tries. The next time playback is initiated it should work.

    This is what has reliably gotten me by, hope it works for you.

    An error occurred while saving the comment
    Anonymous commented  · 

    To the comment below about using Davinci Resolve, you're right. I've even got a copy from buying a camera from BMD. Problem I have with Resolve is that it's not great as a NLE. I hate the locked down UI and there's no full screen output without an add in card. DR makes you adapt to it rather than the other way around. Otherwise I would switch to it in a heartbeat, right now I rather switch to Final Cut Pro on OSX than DR.

    An error occurred while saving the comment
    Anonymous commented  · 

    I have severe dropped frames with a GTX1080, 1920X and 32gb of ram in a clean 1080p timeline, it performs worse than a 4770K with the same gpu and ram. That being said I feel like this is more of a bug than a downright optimization issue as there have been instances where I have opened premiere and playback is flawless with all 24 threads. Not sure how to reproduce it, as changing affinity doesn't have a great effect for me.

Feedback and Knowledge Base