ffmpeg_write v2.0

This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Jeang Jenq Loh
A custom node that launches ffmpeg and convert sequences.
12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11.0, 10.5 or later
Linux, Windows
24 Nov 2020

Change log

I don't actively update my files on nukepedia so for potential future updates for this tool you can check my github repository.


  • Added support to launch other terminals in linux environments
  • Added support to Windows (Need to set up environment variable or set your path to ffmpeg)
  • Some stuff, it's been a while


  • Initial release


Recently I found out that nuke in linux doesn't have H.264 codec available in write node, and for the project I was working on I need to use ffmpeg to convert my output to H.264 repetitively. So I created this tool that wrapped some ffmpeg command line together and able to launch ffmpeg quickly to do the job. Here are its main features in version 1.0

  • Grabs connected read node’s file paths automatically when connected (If the fields are empty)
  • Options to add prefix and suffix
  • Adding audio file in the output file
  • Adjustable fps, CRF settings
  • Gamma 2.2 or linear output
  • Output of .mov and .mp4
  • Output of H.264 or H.265
  • Custom FFmpeg path if it’s not set up in user’s environment variable
  • Preview output path and command to execute ffmpeg
  • Clear button to clear all the settings.

Version 1.0 works best with exr sequence input as I'm still unfamiliar with ffmpeg color conversion. Hence the colorspace option that allows linear output instead of conversion to gamma 2.2 which works with exr sequence.

ffmpeg uiffmpeg ui info

There's a custom ffmpeg path option which is for user who don't have their environment variable set up for ffmpeg, you just have to point it to ffmpeg manually through the custom ffmpeg path option. Note that when the field is empty or when the file path is invalid the command preview won't show up. And it bugs the interface a bit by removing the command preview occasionally, just change one of the file name setting and let it refresh and it's fine.

If you get ffmpeg error when it launches it might be version issue, which I included information on installation or update of ffmpeg in the info tab.



  1. Extract 'ffmpeg_write' folder to your .nuke directory.
  2. Add the following line in your menu.py. Create menu.py in .nuke folder if you don't have it
    • nuke.pluginAddPath('./ffmpeg_write')
Please login in order to download these files.


+2 # Ed Englander 2018-11-25 01:14
This is great, thanks for the legwork on this.
0 # Shahin Toosi 2020-04-22 08:31
hey dude, just wondering what do I need to change to make it work on windows 10?
0 # Jeang Jenq Loh 2020-11-24 04:44
Apologies, I did not notice your comment until now. ffmpeg_write v2.0 now support Windows and other terminal emulator on linux.
0 # Keith Rogers 2021-03-01 14:52
Hello there. I'm getting an error 'Option framerate not found' when I run this from Nuke. Any ideas how to fix it?
0 # sean martin 2022-01-31 07:45
Hey this is awesome, but is there anyway to change the command executed by ffmpeg? I have a string that retains the alpha for overlays which looks like this:

.\ffmpeg -i "file path" -f webm -c:v libvpx -b:v 2M -acodec libvorbis -auto-alt-ref 0 model1v3.webm -hide_banner

I have executed this before through a shell, but its clunky and I am not much of a programmer. Would be much nicer to have this in a node!

Thanks for this node either way! :)
+1 # Jeang Jenq Loh 2022-02-04 13:01
Interesting. I haven't used this tool for a while but I can look into adding a "custom arguments" function.

You have no rights to post comments

We have 3250 guests and 28 members online