MKV Files Trigger “Frame Substitution Recursion” Error Render Settings in Version 25.2

[C27618681pmp5]

Could everyone please let me know if, after updating to version 25.2, it’s possible to modify the render settings? It’s not just limited to Premiere Pro or Media Encoder—on my end, all of them appear grayed out. However, After Effects still allows its settings to be configured.

[Ann Bens]

Render settings cannot be changed.

If it's not set to MPE hardware by default, you most likely have a GPU that is not compatible or outdated driver.

AE's hardware acceleration is not the same as Premiere MPE.

Please post comp specs and OS.

[C27618681pmp5]

Is it true that MPE cannot be modified?

I was able to modify it after reinstalling version 25.1. It only becomes grayed out when installing version 25.2.

[jamieclarke]

Hi @C27618681pmp5 - Software Rendering has been removed in version 25.2.0 please see this article. Software rendering option removed

Can I ask what you need software rendering for?

[C27618681pmp5]

I use Influx’s plugin to read MKV files recorded from OBS (using NVENC x264). In version 25.1 (render : CUDA)
, when I dragged the file into the timeline for playback, everything worked fine. However, after updating to version 25.2, the file only shows a black screen, and I keep receiving the following message on the file: "frame substitution recursion attempt aborting after multiple attempts." Reverting back to version 25.1 makes everything work normally.

I have cleared the settings and tried every available reset method, but the problem persists.

On another computer that can only use Software Only mode in 25.1, updating to version 25.2 does not encounter this issue.

It is not that I insist on using Software Only mode; rather, the current behavior in version 25.2 prevents me from working properly.

As a productivity tool, any significant architectural changes should provide an option to revert to the original behavior. As others have noted:

"Software Only is a good fallback option for troubleshooting or avoiding render errors. It either helps narrow down the issue to the GPU, or allows you to render anyway if necessary."

Thank you for your consideration and assistance with this matter.

[R Neil Haugen]

I record a lot in OBS. But then I totally avoid mkv, and use the direct mov option. Plays beautifully i. Premiere without t-coding converting or proxies.

[jamieclarke]

Hi @C27618681pmp5 - I'm wondering if there is a conflict with you plugin and Premiere.  Premiere now supports
MKV files with H264 support

can you try uninstalling the plugin and letting us know if that helps your issue.

what gpu and driver are you using Adobe recommends using the "Studio" driver version when working in Premiere Pro.

I would try updating to 24.2, clear your media cache and then import your file

[C27618681pmp5]

I have reinstalled version 25.2 and conducted two tests,and tested on two computers: one with CUDA and one with software only., My graphics card driver is Studio 572.83. I used the same MKV file, which contains multiple audio track inputs (files recorded from OBS using NVENC x264).

1. Removing the Influx Plugin: When rendering with CUDA, I still encountered the error message, “frame substitution recursion attempt aborting after multiple attempts.” However, the file opened normally in Software Only mode.

2. Applying the Influx Plugin to All Files: Under CUDA rendering, the file also opened normally.
   
   

This clearly indicates that the issue lies with Premiere Pro 25.2’s insufficient support for hardware decoding of MKV files, rather than a problem with the plugin, for file formats that are supported in Premiere Pro, unless specially configured otherwise, the decoding is handled directly by Premiere Pro.

So, are you saying that the 'Software Only' mode is ineffective and does not give the user a choice? It can be very effective for debugging, at least in this case.

[jamieclarke]

Hi @C27618681pmp5 - Would you be able to send a sample file that is causing you issues to jamiec@adobe.com 

We have seen the Frame Substitution error in version 25.2, but in some cases has been fixed by clearing media cache.  We are still investigating the issue.  

As a diagnostic in 25.2 Users can   Hold down “Shift” while launching Premiere Pro, then check “Use Software Rendering only (one-time only).” 

Since you’ve already done this, our goal is to help resolve the issues users are experiencing without requiring them to switch to Software Rendering.

[Ann Bens]

As far as I know 25.2 does not support MKV with multi audio tracks: 25.3 beta does.

[C27618681pmp5]

Of course, here is the file:
https://gofile.io/d/qottvD

It's quite strange. I used your method—holding Shift while starting Premiere Pro
and enabling software-only mode. However, the same error message still appears.

The video showcases another bug in Premiere Pro.
When launching the PR project file directly from File Explorer,the shortcut key characters disappear.
This issue has existed since at least the 2023 version and has not yet been fixed.
https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-2023-23-2-shortcut-keys-display...

[jamieclarke]

HI @C27618681pmp5 - I do see this issue on Windows but not on mac.  I will get this bug filed.  Thank you for the sample file.

[jamieclarke]

Updating Status to Acknowledged

[Wil Renczes]

Turns out it's a straight forward issue - nVidia hardware decoding for h264 only works for 4:2:0 sources.  The new Blackwell GPUs have added support for 4:2:2.  Meanwhile, this clip is encoded as 4:4:4, so that won't decode in hardware.  Should be a relatively straight forward fix to make this clip fall back to software decoding.

Thanks for the sample file!  It definitely helps to clear up things like this.

[jamieclarke]

Hi @C27618681pmp5 - There is currently a fix in Beta version 25.3.0 build 53 and later if you want to try it out.  Thanks for all of your help getting this issue resolved.

[C27618681pmp5]

Thank you for the information about the fix! However, I usually wait for the official release before updating. I hope the issue will be fully resolved by then. Thanks again for your effort

[jamieclarke]

Updating Status to Fixed in 25.3