Fun Expander 2.5.3 - Video converter with ffmpeg to i-frames added [Updated 2025-09-17]

Your program is absolutely amazing.
It used to be really hard to make scripts in OFS, but now the stuttering is gone!

1 Like

Yeah scripting VR without conversion is quite a pita.

Any chance you could use Nvidia card instead of the CPU to convert to i-frames as options? Faster and more fire resistant?

if you can find the command for ffmpeg to use the grafic card instead of the cpu then i can implement that, @roa

No, no idea. But I know someone who may know @CertainlyWicked

Usually you’d have to say my name 3 times in a row. :wink:
Beetlejuice anyone?

Whatever, should be something like this:
ffmpeg -y -i input.mp4 -c:v h264_nvenc -g 1 -bf 0 -no-scenecut 1 -forced-idr 1 -qp 38 -preset p2 output.mp4

Hope that helps.

2 Likes

LOL Thanks bud. uhuhuu this will be great Funexpander running on the Nvidia card.

Done, download link in the first post!

Amazing thank you Heels and of course thanks CertainlyWicked. Have you tested the speed? Faster?

yes, it is now more than twice as fast for me

Nice, so was a good idea.

Heels conversion to iframes exits at once with a 0 bytes file. Somethings wrong.

LOL, it works perfectly fine for me. Do you realy have an NVIDIA graphics card :wink: ? What if you uncheck “use NVENC”, does it work then? Here’s the complete command string for ffmpeg:

“C:\ffmpeg\bin\ffmpeg.exe” -i “D:\video.mp4” -filter:v “scale=-1:-1” -c:v h264_nvenc -preset p2 -g 0 -qp 30 -acodec copy “D:\video_i-frames.mp4”

Throw it into the command prompt, maybe you’ll see more then.

Hmmm, doesn’t seem to like me either. I have a 4090.
[h264_nvenc @ 0000021b4e1d0ac0] No capable devices found
[vost#0:0/h264_nvenc @ 0000021b4e1d0580] [enc:h264_nvenc @ 0000021b4cdad8c0] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.

So with that, it’s an FFMPEG and Nvidia issue, which is a rather annoying rabbit hole to go down haha

I can confirm it works just fine (have a 5080) and also that speed increased (at least twice to thrice as fast for me in comparison to my 9800X3D). Noice.

2 Likes

For those who have problems:

  1. Check and update drivers
    NVENC requires current NVIDIA graphics drivers to function properly

  2. Check if NVENC is supported
    Make sure your NVIDIA graphics card supports NVENC

  3. Testing with ffmpeg
    Enter this in the command prompt: ffmpeg -encoders
    This will give a list of codecs, search for h264_nvenc

  4. DirectX or CUDA support
    Make sure that the DirectX and CUDA libraries are correctly installed on your system, as NVENC is based on CUDA

Just to further troubleshooting, specs for me:
Drivers are at 581.29
CUDA Toolkit is at 13.0.1
h264_nvenc IS listed.

If I find anything further, I will update

Interesting… I can get it to work on 2D files, anything VR fails.

Edit: It’s not handling the resolution properly. Pretty sure it was broken before as the logs are quite clear about the problem now. Can’t see myself missing it haha

I did have an older CUDA installed for testing FunGen so maybe that was part of the problem.

Now that I think deeper on it, it’s not going to work well for VR content as there is a 10 bit incompatibility with h264_nvenc.

4090 here too, latest driver installed.

Worked just fine for me today. I converted the newest Marvel Rivals VRConk scene in 8 minutes (40 minute 4K VR video).