Skip to main content
L
Lewisjh
Participating Frequently
June 12, 2024

ProRes RAW - Stuttering on render and export

  • June 12, 2024
  • 13 replies
  • 1291 views

Been having issues with the latest version of Premiere - using CUDA render results in ProRes RAW footage stuttering.

 

Since the problem is only with the Pro Res RAW clips, I've found that the issue seems to lie in the sequence settings being a different frame size - as my output is going to be 1080p, I've been working in this space and scaling down within the edit.

 

I've tired exporting the single clip in matching sequence settings timeline to then import and use that way but for some reason, one frame from the other pro res shot (despite not being on that timeline) came out with the export.

 

PC Specs

CPU: Intel Core i7-14700KF

RAM: G.Skill Trident Z5 - 32GB 6800MHz CL34 DDR5

EDIT DRIVE: WD Black 4TB SSD Gen4

GPU: RTX 4060 Ti 16GB 2X

 

What I've tried

Rolling back drivers

I was on the game drivers - I tried the latest studio driver but no luck, so I rolled back to this version:
Driver Version:555.85 - WHQL

Release Date:Tue May 21, 2024

 

Premiere Pro Beta

Still the same issue

 

Nesting/Subsequence footage

Tried nesting the footage and sub sequences with the correct resolution - this seems to work within the timelines but once back in the master timeline, the stutter will happen again.

 

Exporting the subsequence and using the import file

When I tried this, the shot came out with a single frame from the other shot (despite it not being on that timeline)

 

Sequence settings:

https://imgur.com/a/9LdCsrN

Only two clips are ProRes RAW - the rest are ProRes422LT

 

ProRes files properties:

https://imgur.com/a/jNmBeQ1 (These are slowed to 25%)

    13 replies

    Show previous replies
    L
    LewisjhAuthor
    Participating Frequently
    June 18, 2024
    quote

    Other workaround attempted

    I created a sequence with just the ProRes RAW clip (100fps) by dragging it onto create new sequence (It made a 60fps one) - this seemed to play back correct when rendered; also seem to be fine at 25% speed.

     

    When this sequence is put into the other timeline, it stutters again. So it seems to be mixing the two formats.

     

    Exporting this sequence that is setup for ProRes works fine too.

     

    I will attempt this with the latest driver and report back.

    @Lewisjh

     

    I have reverted back to the latest driver, and it seems that the problem happens on a timeline set up as PRORESRAW as well.

     

    So I guess the problem persisted in previous versions but only when mixing prores into another timeline - but on the latest driver it doesn't even work on a proresraw timeline

    L
    LewisjhAuthor
    Participating Frequently
    June 18, 2024

    Hey @Kevin-Monahan - Thanks for the response. I have rolled back to Studio driver 552.22 (I did not roll back HD audio or Physx or the geforce app) - Still have the issue on both exporting and rendering on timeline.

     

    Playback when unrendered (yellow) is fine, when rendered (with GPU / Green) it stutters and is playing back incorrectly.

     

    As far as I am aware, this issue only started within the last update or two of Premiere Pro. But I cannot pinpoint exactly when.

     

    Other workaround attempted

    I created a sequence with just the ProRes RAW clip (100fps) by dragging it onto create new sequence (It made a 60fps one) - this seemed to play back correct when rendered; also seem to be fine at 25% speed.

     

    When this sequence is put into the other timeline, it stutters again. So it seems to be mixing the two formats.

     

    Exporting this sequence that is setup for ProRes works fine too.

     

    I will attempt this with the latest driver and report back.

    Kevin J. Monahan Jr.
    Kevin J. Monahan Jr.
    Legend
    June 12, 2024

    Hello @Lewisjh,

    Thanks for filing this bug report. I have not seen this issue otherwise, but other performance issues are cropping up with this GPU driver. Can you try rolling back to 552.22? If so, what happens? Let us know. I hope the advice helps.

     

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices