logo for ffe - FFmpeg front-end for windows. it's converting some raw video from my camera - the logo is a simple large text of the three letters, coloured from top to bottom, green, yellow, red, in a smooth gradient.

FFmpeg is, by miles and miles, the best multimedia converter / streamer / recorder in existence. It is capable of handling a vast number of input and output (audio, video and other) formats, and depending on which binary you use; supports either a huge number of control parameters, or a really huge number of control parameters. In the time it took you to read this paragraph, a new format has been added.

FFmpeg, by Fabrice Bellard, et al., is truly incredible software. And free. With FFmpeg you can basically convert anything to anything, whilst doing crazy stuff like mixing MP3 audio tracks with H264 video, and adding ID3 tags to AVI files. Big fun. Of course, it allows you do do things the correct way, too. No limits.

It is also command-line-only. Because of this, accessing its magic is only possible in the shell, or else with some kind of interface between regular human beings and the wonders of FFmpeg..

Enter ffe; a simple, powerful Windows front-end for FFmpeg; designed for rapid testing of FFmpeg's many, many conversion options inside a (hopefully more) user-friendly interface. While FFmpeg can do many, many things, the focus here is on its media conversion capabilities.

ffe takes your ffmpeg operations to the next level; aiming to be powerful and flexible yet intuitive and intelligent. ffe turns complex processes into buttons and simplifies just about every aspect of FFmpeg's operation, whilst simultaneously catering for the most advanced FFmpeg processing needs.

If you are looking to transcode a collection of old AVI video files to HEVC/x265 or AV1 to save space, or convert a folder of WAV or FLAC files to MP3, or mux subtitles into a movie, or make a GIF from a video clip, or part of a video clip, or speed up or reverse a video, or toy with AV1 or, well, you get the idea; pretty much anything you can imagine; ffe+FFmpeg can do it.

Find a cute FFmpeg command online? Or get something finally working exactly the way you want? Save it to a button and it's there whenever you need it. Want to convert and join a folder-full of files? No problem. And then join them all together? Easy. Need to calculate the cropping to remove black bars? With ffe it's one click.

You can setup a complete FFmpeg work-flow, with pre- and post-batch commands, file post-processing and much more, and with a click; save it all to a preset, available for scripted or interactive use at any time. Or drop some files in and save the whole lot as a Windows batch script. Or tell ffe to start up the job in a couple of hours, when you're asleep, then shutdown when it's done. Or next Tuesday.

Out-of-the-box, ffe is ready to start work, with a selection of useful (and fun) built-in presets and custom buttons (which you can add-to/edit/delete). When you need more power, ffe can handle that, too.

ffe is completely free, as in beer. And completely open source, with ready-to-use binaries and ready-to-compile source packs that regular folks can get up and running in a jiffy. Have fun!

a star Screencaps a star

ffe, an FFmpeg front-end for Windows..

ffe provides a huge set of features designed to make working with FFmpeg painless, even joyful, such as..

* Okay, technically you can only make 500 buttons, but seriously, how are you fitting 500 buttons into a GUI?

ffe uniquely uses MATOF™ technology to automatically update the output file name (and extension) to match your encoding parameters; you can tweak-and-go, working at a rapid pace, without obliterating any of your previous tests. And then know exactly what parameters were used to encode each and every one of them, all without making notes.

ffe is FREE (though possibly not bug-free!), and can be download as a ready-built Windows program, or a full source pack, with AutoIt code, icons, includes, all that stuff, below. And that's all you need, right?

That and an FFmpeg binary, of course. It's also free, open-source software, and there are quite a few different versions kicking around. If you have some developer tools onboard, I recommend you checkout the source and build it yourself. Or else Google and take your pick..

This is generally reliable - all versions should work fine.


Installation is simple. Here is the entire process. Also available in plain text, here.

  1. Go here: (note: this site has nothing to do with me)


    Download the latest release (you will most likely want the static build, either 32 or 64 bit).

  2. Or here: (note: this site also has nothing to do with me)


  3. Unzip that file to somewhere, probably inside your program files, e.g..

    C:\Program Files\corz\ffe\

    If you don't have an unzipping utility that can handle the 7z (7-Zip) format, see here:


    7-Zip is free. WinRAR (not free) can also handle the format.

    You should now have some files in that folder, including..


  4. Drop ffe.exe into the same folder, next to ffmpeg.exe for instant operation. You can keep them in separate places, too - ffe will ask you where your FFmpeg binary is before you start work.

  5. Launch ffe.exe

ffe Usage..

ffe's operation is simple. Drop media files or folders onto ffe's input (or funky floating drop window), set your chosen parameters (or choose a preset) and click "do it". That's it.

As you work, ffe constructs a set of command-line arguments for FFmpeg and when you "do it", launches FFmpeg with those same arguments. Simple.

Creating an FFmpeg command-line is the main reason for ffe's existence. Most of the controls simply add or remove text to the FFmpeg command-line. ffe of course can do a lot more, like run that command and lots of other useful stuff, but that is essentially ffe's main task. You can see the command-line being constructed, live, as you work.

Some of the more common FFmpeg parameters and flags are available from drop-downs and logical inputs; things like codec selection, bitrates, sizes and cropping. Any settings and parameters you use often can be saved to custom buttons that you can click to insert that snippet into any command.

NOTE: Standard Operating Procedure is to drag your source file(s) into the "input", then setup any parameters, then drag the destination folder into the "output", then hit "Do It". Doing things this way let's ffe calculate any MATOF strings and such afresh, and saves frustration!

Once you have created a set of parameters and settings that work for a particular job, you can save the whole lot as a preset, for later use.

Keyboard shortcuts..

Most commonly-used ffe commands and settings have HotKeys..

  • F1 =>  "do it". Run the job/batch.
  • F2 =>  Change (global) default video output extension.
  • F3 =>  Search in console output.
  • F5 =>  Clear console output.
  • F6 =>  Toggle FFplay console output.
  • F7 =>  Automatic codec drop-downs.
  • F8 =>  Copy console output to clipboard.
  • F9 =>  Toggle drop window.
  • F11 =>  Perform FFmpeg Quick Task.
  • F12 =>  Perform FFplay Quick Task.
  • Ctrl+D =>  Delayed/Scheduled Start.
  • Alt+F4/Esc =>  Quit ffe.
  • Alt+F5 =>  Restart ffe.
  • While FFmpeg is running you can also use..

  • Pause/Break =>  Abort entire FFmpeg batch/job.
  • Ctrl+Q =>  Abort current FFmpeg job.
  • ScrollLock =>  Suspend/Resume FFmpeg.
  • Alt+C =>  Pause console output.
  • Ctrl+R =>  Toggle running time in title bar.
  • Alt+Space opens the app menu where you can navigate entirely by keyboard.

    Custom Button Accelerators..

    While I'm here, I should add that you can put keyboard accelerators in the names of your custom buttons and then Alt+ keyboard shortcuts to access them. To do this, simply add an ampersand (&) before the letter you wish to use as an accelerator, e.g.. To use the Alt+B accelerator, name your button for example; "&Blur"

    Most of the sample buttons have Alt+ accelerators. The button's title has the accelerator underlined, e.g..

    Blur  =>  Alt+B

    If you don't see the underlining, hit the Alt key one time!

    Active Labels..

    A few of ffe's labels are "active", that is, something happens if you click on them..

    Click the "crop w / h" and "crop x / y" buttons to perform "auto-crop", which uses FFmpeg's built-in cropdetect mechanism to interrogate your video file for the position of black bars and automatically inserts the values into your crop inputs.

    Click the source label (to the left of the source input) to open the source folder, with the source file selected (if it exists).

    Click the output label to disable output (for image sequences, etc.)

    Right-click the output label to delete the output file(s). By default this deletes to the Recycle Bin without warning, but you can set it to also delete directly with or without warning. Be careful!

    The text of the above labels will change to a light blue on mouse-over, to indicate their extra functionality.

    Many of ffe's control have extra functionality when you Shift+Click, Ctrl+Click or Right-Click the control. Hover your mouse over any control for details of its capabilities. Many controls have context menus, too. Right-click for details!

    The Console..

    ffe has its own console. While working, the output from FFmpeg can be viewed live inside the ffe console, and when complete, the entire process log is available for viewing and searching. ffe uses the console for many things..

    When you run pre-job, post-file and post-job commands, their output can be piped to the console, so ffe's job log contains every scrap of available information.

    ffe also uses the console to keep you informed of important events, updated information, settings, errors and more. Help files, media report, script output; everything is fed to the console. There is even a search feature.

    It should also be noted, the console output area is fully editable. You can copy from there, paste, type. In other words, if you are ever wondering, "where can I paste this groovy command I found on the web, so I can edit and try it?" No need to switch to your text editor, there's an edit area right there! You can drag files in, too; their paths get pasted in-place.

    The App Menu..

    ffe makes extensive use of the "App Menu". That's the one you get by clicking the icon in the top-left of the program window, or right-clicking the main window's title bar, or hitting Alt+Space. It's always handy.

    This is used for application global toggles and settings. The system tray menu is used for one-off commands, and the main GUI is for your regular FFmpeg fun and games, which makes sense to me. Basically, everything you can see, can be saved to a preset. Both app and tray menus contain the "about" options.

    If you activate the app menu using Alt+Space, you get to use keyboard accelerators, which if your hands are on the keyboard anyway, makes operation real quick. All ffe app menu options have keyboard accelerators attached. Enjoy!

    Command-line usage..

    As well as its beautifully thought-out graphics user interface, ffe can accept instructions on its command line. You can send it files and folders, and they will be loaded into the input upon launch (real handy in your SendTo menu). You can also process presets at launch time. Or both.

    You can instruct ffe to jump right to it, start conversion immediately, generate batch scripts and other stuff. You can use this facility in Windows batch scripts, Explorer context commands and other places. Examples..

    To load a file at launch..

    C:\path\to\ffe.exe E:\path\to\video.flv

    To load a preset at launch (in this example, a preset named Reverse Video+Audio, which does just that)..

    C:\path\to\ffe.exe load(Reverse Video+Audio)

    To load that same preset at launch, but override its input files (if any) with a different file..

    C:\path\to\ffe.exe load(Reverse Video+Audio) E:\path\to\video.flv

    The same as above, but for a batch run of all files in the specified directory (Windows wildcards accepted)..

    C:\path\to\ffe.exe load(Reverse Video+Audio) E:\path\to\*.*

    This more modern version of Windows "all files" wildcard also accepted..

    C:\path\to\ffe.exe load(Reverse Video+Audio) E:\path\to\*

    Load a file (with a long path, including spaces, enclosed in "quotes"), and begin conversion immediately, using the SpeedUp x2 preset..

    C:\path\to\ffe.exe go(SpeedUp x2) "E:\very\long path\to some\video.flv"

    Load a file and begin conversion immediately, using your ffe default parameters..

    C:\path\to\ffe.exe go(ffe) E:\path\to\video.flv

    Load a file and begin conversion immediately, using your ffe default parameters then quit..

    C:\path\to\ffe.exe run(ffe) E:\path\to\video.flv


    C:\path\to\ffe.exe quit(ffe) E:\path\to\video.flv

    Load a group of avi files and generate an FFmpeg Windows batch script, using settings from the x265 Simple preset, then quit..

    C:\path\to\ffe.exe generate(x265 Simple) E:\path\to\*.avi

    Load multiple presets on the command-line, process a folder of videos with the layered settings and quit..

    C:\path\to\ffe.exe quit(setup|anim filters|tweaks) "E:\path\to some\video\*"

    Note: When you layer presets, settings from later presets override settings from earlier presets. This facility has many uses. See below for more details.

    If you supply an input file path on the command-line, your output will be automatically filled with its converted counterpart, and if MATOF™ is enabled, the preset's parameters inserted into its name, ready-to-go.

    And by files, I also mean URLs. http and ftp and both fine. You can grab the first 100 frames of a movie online (or any number of frames from any part, though near the start makes sense), check it out, and then if it's what you want, download it. Or not.

    FFmpeg can handle lots of other internet protocols, too. Want to grab a chunk from a RTMP stream? (do any still exist?) Or grab a nice cool Icecast or pluck some Apple HTTP Live Stream? No problem! More details here.

    URLs also work for output files; you could grab part of a movie stream and save it directly to a remote FTP server (ftp username and password in the usual format is supported). Quite why one would want to do this is uncertain, but there you have it; flexibility! Just like ffe..

    Pre-Job, Post-File and Post-Job Commands..

    ffe has the facility to run tasks before (pre-job) and after (post-job) your ffmpeg job. It can also run tasks after each file processed (post-file), aka. "post-processing".

    The pre- and post-job tasks execute actual Windows batch files, which ffe will create automatically for you in your chosen location if you activate this feature. Their locations are stored inside your preset. These batch (.bat) files can be run internally, line-by-line, by ffe (where you can use @tokens and other goodies) or externally, through the Windows command interpreter (cmd.exe).

    These commands can be anything at all. You can move stuff around, delete, zip, unzip, run input and output files through other programs, whatever you need to do before and after a multimedia conversion job. To reduce time wasting and head scratching, enclose all paths and path @tokens in "quotes" inside your commands.

    If you are running lots of tests, a great pre-job command is..

    del /f /q "@outdir\*.*"

    Which would delete all your previous tests before you begin the next batch.

    note: you can also right-click the output label to delete the most recently-created file(s).

    The Post-File (post-processing) command is one single command which is stored inside your preset. ffe executes this command (internally or externally, tracking or not, hidden or not) after each completed file (in a batch, this command will run multiple times).

    Generally you would want to use the @outputfile token in this command, to work on the file just created. But you don't need to. This command can be any valid command.

    NOTE: Pre-Job, Post-Job and Post-File settings can all be saved inside presets, even the default preset. However, if you have any of these set (enabled or disabled; they have three states; enabled, disabled and unset) and you then load a preset with them unset, their state will remain unchanged. This is by design..

    You can load a preset with some commands setup, then another preset without any commands, then (perhaps after some tweaks) re-save the second preset, except now it has commands ini it. All the job buttons work this way, remaining in their current state (the default) unless mindfully changed, either manually or via preset.

    You could conceivably create presets solely for loading pre- and post- commands, leaving that stuff completely out of your regular presets and loading only when required. Or, ignore all those buttons completely and they will never get in your way!

    The [reset] button resets all job buttons to unset.


    ffe accepts @tokens for most settings, parameters and inputs, even the extra parameters input, so you can do stuff like..

    -frames:v 50 -r 0.1 "@parent\@item_%04d.png"

    Or set your FFplay quick task button to something simple and useful, like..


    @Tokens are dynamically transformed at runtime. Here's what they transform into..

    Input/Output File @tokens.. @inputfile Full path of current input file. @item Basename of current input file, minus extension. @ext File extension of current input file. @outputfile Full path of current output file. @ofilename Basename of current output file. @oext File extension of current output file. Date & Time @tokens.. @sec Seconds value of clock. Range is 00 to 59 @min Minutes value of clock. Range is 00 to 59 @hour Hours value of clock in 24-hour format. Range is 00 to 23 @mday Current day of month. Range is 01 to 31 @mon Current month. Range is 01 to 12 @year Current four-digit year @wday Numeric day of week. Range is 1 to 7 which corresponds to Sunday through Saturday. @yday Current day of year. Range is 001 to 365 (366 in a leap year) Dynamic Path @tokens.. @parent Parent directory of current input file @outdir Output Directory (wherever ffe is currently outputting files) @tempdir System Temp directory @datadir ffe data directory (in portable mode, it is the program folder) @desktop Current user's desktop folder @programfiles Your Program Files directory @appdir ffe program directory @homedir Current user's user directory, e.g. "C:\User\Fandango" @mydocuments Current user's "My Documents" directory. Special @tokens.. @arguments The current arguments to be fed to FFmpeg.

    Portable Install..

    If ffe finds an ini file next to itself, it switches to portable mode. In other words, if you want a portable installation, simply copy an ffe.ini file next to ffe.exe. You're done. Your ffe.ini is probably (Vista, Windows 7, 8, 10, etc.) here..


    On older Windows most likely here..

    C:\Documents and Settings\<Username>\Application Data\corz\ffe

    If you are new to ffe, and want to start with a fresh portable install, do your first run using the special portable switch..

    C:\path\to\ffe.exe portable

    Which will create a fresh ini file right next to ffe, for instant portable operation. Or you can drag a fresh ini file next to ffe.exe yourself; there should be one inside the "Info" folder in the distribution.

    Drop your FFmpeg binary (ffmpeg.exe) in the same folder and you are good to go.


    Q: I've changed a bunch of settings. I want to save this to my default "ffe" preset. How do I do this without first loading the default preset and obliterating the settings I just made?

    A: Type or choose "ffe" (no quotes) into the presets drop-down and hit "Save".

    Q: When I choose MPEG4 for the video codec I get an .mp4 file, but when I use libx264 or libx265 I get .mkv. What gives?

    A: .mkv is set as your default fall-back extension and MATOF is enabled. If you want an mp4 container, set mp4 as your default extension. You can set it globally with the {F2} HotKey. You can also set this inside presets, if required (right-click the presets drop-down control for the menu option).

    Note: THIS IS NOT RECOMMENDED! ffe handles extension mapping internally. If it doesn't recognise some format, let me know and I will add it. And maybe one day, create some kind of user preference for these mappings!

    ffe uses your chosen video codec to select the correct extension. Here is what they are currently..

    xvid,mjpeg => avi mpeg4 => mp4 mpeg,mpeg2 => mpg gif => gif flv,flash => flv msvideo,wmv => wmv vp,webp => webm

    All other video output will fall-back to your current default extension (normally mkv).

    Audio extension mapping is currently..

    dca,dts => dts flac => flac gsm => gsm mp3 => mp3 mp2 => mp2 ac3 => ac3 aac => aac opus => opus real => ra tta => tta cook,Gecko,Real => ra vorbis => ogg wma => wma pcm => wav

    All other audio output will fall-back to your current default extension (normally aac).

    When simply extracting (plain copying) audio out of a video file, ffe will automatically interrogate the file for the existing codec before applying the extension mapping.

    By the way, if you see any errors or obvious omissions in the above lists, please let me know about it!

    Q: Custom Buttons & Presets.. What's the difference?

    A: Think of the custom buttons as a place to keep "snippets". The sort of things you regularly add to ffmpeg commands, perhaps setting a CRF value or a favourite blur filter. Any small string that you might want to add to the output (or input) parameters.

    Custom buttons are designed to be quick. Click once to add the string, a second time to remove it. Ctrl+Click to add to input parameters. Shift-Click to edit or add buttons.

    Presets contain everything. All the settings and switches and parameters, pre- and post-job commands, (optionally) input and output file paths; an entire work-flow. The entire ffe interface is setup from a preset, named "ffe". The default preset. Your retained exit settings are another preset, named "EXIT-SETTINGS". Make your own!

    ffe is pretty flexible. You can load multiple presets on top of each other to combine layers of settings / parameters / pre- & post- commands. Then tweak input and output parameters with snippets from your custom buttons.

    Then save the whole lot as a second preset for later access, via the command-line or from batch scripts or in the GUI; running jobs manually, or on a delay or even generating a Windows batch script for some other program or user or time. Flexibility underpins most of ffe's design decisions. It aims to be part of the solution.

    Q: I edited my help button and now when I press it nothing happens. Help!

    A: It sounds like you have entered an invalid command and ffe, by design, does not display error output for help button comands (which would interfere with the help output).

    You can do a quick check of your command with the FFmpeg Quick Task button, which does show error output. Simply right-click on your FFmpeg quick task button [ffmpeg task], enter your experimental help command, then click [ffmpeg task]. All output will be displayed in your console.


    Replace your old ffe.exe with the new one. That's it.


    ffe's itstory is too lengthy to include here. If you want to know what's been changed, fixed, updated, broken, and so on, check out the itstory

    Quick Start..

    There's a short, quick-start type guide, here. I'll include it in the next release.

    More info added continually..

    Meanwhile, you can get details of all the new features, as well as lots of tricks, tips and hints, from the latest ffe itstory. These days it's a big read but well worth it.

    Or check out some screencaps, here.

    Want some funky transparent images for your drop window? Access my stash of ffe goodies here.

    You may notice ffe is comprehensively self-documented - there are ToolTips for everything. Hover your mouse anywhere in ffe for useful (often dynamically updated) information.

    ffe download..

    Like FFmpeg, ffe is free to download, and free to use, though all donations are warmly accepted. If you discover a bug, please let me know about it!

    Note: You will need a Unicode capable, 64-bit Windows system to run ffe, that is; Windows XP, Vista, 7, 8 and 10 x64 Windows operating systems. ffe will not run on Windows 9x, ME, 2000 or 2003. And I've stopped building 32 bit binaries. If you need that, you can grab the source pack and build it yourself! It's easier than you may think.


    ffe v2.5.4.5

    click to see zip archive contents

    LIVE MD5+SHA1 Multi-Hashes..
    # made with checksum.. point-and-click hashing for windows (64-bit edition). # from corz.org.. http://corz.org/windows/software/checksum/ # #md5#ffe v2.5.4.5.zip#2022.02.19@23.16:46 ee618b055a2caf86fce60b98e36c626d *ffe v2.5.4.5.zip #sha1#ffe v2.5.4.5.zip#2022.02.19@23.16:46 8556946e152214c6cdd5be3575a9c905ef40dcfb *ffe v2.5.4.5.zip

    Download ffe source pack..

    The beta source pack contains everything you need (at least from me) to build ffe for yourself; AutoIt code, icons, includes, documentation, all that.


    ffe source pack v2.5.4.5

    click to see zip archive contents

    LIVE MD5+SHA1 Multi-Hashes..
    # made with checksum.. point-and-click hashing for windows (64-bit edition). # from corz.org.. http://corz.org/windows/software/checksum/ # #md5#ffe source pack v2.5.4.5.zip#2022.02.19@23.16:47 7739561c4c7210a630480e49d7f47970 *ffe source pack v2.5.4.5.zip #sha1#ffe source pack v2.5.4.5.zip#2022.02.19@23.16:47 0a750edd495e14de71916394eaf0896f5beba13a *ffe source pack v2.5.4.5.zip

    If you find a bug, please, please let me know about it!

    Note, you will want to use AutoItWrapper to add the icons for the buttons (and for so many other reasons). You can get a copy of the AutoItWrapper binary I use (source included), right here..



    click to see zip archive contents

    LIVE MD5+SHA1 Multi-Hashes..
    # made with checksum.. point-and-click hashing for windows (64-bit edition). # from corz.org.. http://corz.org/windows/software/checksum/ # #md5#AutoIt3Wrapper.zip#2021.03.15@01.09:45 fbdf5d0bc8735e034e2f732e19bc635b *AutoIt3Wrapper.zip

    Have fun!

    ;o) corz.org

    ps. If you have any problems, questions and what-not, leave a comment, below..

    Known bugs, foibles and limitations..

    If you place the OK button of some dialog you created with a Right-Now-Click™ action directly over another control that has Right-Now-Click™ action, you may, when you okay the first dialog, activate the Right-Now-Click™ event on the second control. I think it's a small price to pay for Right-Now-Click™ functionality!

    If you set double_check_rclicks=false in your ini it will prevent this occasional phenomena, at the expensive of occasionally not registering your first right-click on a control. Your call.

    The best option is leave it enabled and don't place dialogs where their OK button is over another Right-Now-Click™ enabled control!

    FIVE times I managed to squeeze that in. Five! lol

    By the way; in case you missed it; Right-Now-Click™ is my fun description for the alternative to a control that under normal program-writing circumstances would have a context menu. The thing is; if that menu were to have only one item, it becomes instantly redundant, forcing the user to perform two clicks for a single action. I think that's barmy.

    So new-and-improved Right-Now-Click™ steps in and takes you straight to the only action there is. Believe me; once you try Right-Now-Click™, you won't go back.


    Welcome to the comments facility!

    previous comments (ten pages)   show all comments

    Cor - 23.05.18 4:01 pm

    If you look in your current ffe.ini, there will be a backup section named..


    Also note: there is an "Edit ffe.ini" option in the tray menu - no need to raking about!


    Mozz - 05.06.21 5:56 pm

    Can you provide a link for the last 32 bit version of the program? I did consider compiling a 32 bit version of ffe using the source code provided, but instructions for doing so are not provided, and figuring out how to compile with Autoit would be challenging for someone who is not a programmer.

    I no longer supply 32 bit versions. If you want to compile ffe yourself, mostly-complete instructions are included/posted, though they are probably more scattered-around than I'd like. At least a passing familiarity with AutoIt is assumed.

    Inside the distro are file to help you set up a develop+build environment in Notepad++. Once you've edited in your own program locations (where AutoIt is installed) you can basically hit a Hotkey to run, build, and so-on. Program output is piped back to Notepad++ so you can edit some code and run it immediately to check the changes, with debug output there in your console.

    Download the ffe source pack, see inside Resources \ Notepad++ Goodies for more details.

    The process is the same for most decent editors, if you don't use Notepad++; essentially assigning some HotKeys to run AutoIt and AutoIt wrapper commands, piping output back into the editor. The actual commands you would want to port over are in a file called "npes_saved" in the source pack distro.

    If you need any help with setting this up, feel free to ask.


    BH - 05.02.22 9:31 pm

    I installed the latest version of FFE 2.5.2 on my Windows 10 / Lenovo W541. I can do file conversions and use the app just fine. However, if I manually minimize or close the FFE window, I can not get back to the FFE window. I have to stop the FFE service, reboot my PC, delete the FFE files and then reinstall FFE in order to use it again. If I exit out of the app using the FFE menu, it's not a problem. It's only after I minimize the window that
    it becomes a problem

    I am installing FFE into a separate windows directory (not c:\Program Files\)

    I have tried run as Administrator.
    I have tried alt-tab to get back to the FFE window.
    Even if I just stop the FFE service, and tried to restart it, does not work.

    What am I missing ?

    Thank you

    Left-click on the tray icon. Also note: ffe is/has NO service, so I'm unsure what you are referring to. ;o)

    BBanger - 09.02.22 6:46 pm

    I have a folder of videos I want to convert. They all have srt subtitles files. Can I mix them together when I convert them so the subtitles are inside the video?

    Sure. In your input parameter override, do..

    -i "@parent\@item.srt"

    In your extra parameters, you might want something like..
    -c:s srt -metadata:s:s:0 language=eng


    ps. it's "mux".

    John Q User - 19.02.22 3:48 am

    One thing to add to this manual of sorts, is just some of the text at this changelog.


    From the shorter manual text here, it actually didn't describe exactly how batch processing works. I mistakenly assumed you would drop all the files in the batch on the program, which obvs didn't work at all smiley for :geek:

    From that doc it's much clearer; that you'd just insert a wild card in the file name box...


    rage - 19.04.22 7:50 pm


    ffe.exe file seems to be infected by W32.FamVTAppLQNE.Trojan regarding Virustotal.com. Any clue?
    False positive?
    My McAffee tools chains (on Win10Enterprise) is frozen the thread.


    Of course it's a false-positive. Feel free to let them know!

    lasered - 08.03.23 7:12 pm

    Critique: why is your download link 3/4 of the way down the page? Scroll all the way to the bottom -- no link; scroll to the top -- no link; in directions where you download ffmpeg there is no link. It took me 2 minutes to figure out where it was. You should fix this.

    Thanks for developing this amazing software!

    If you click the big icon at the top it takes you straight to the downloads. There's also a "Download" item in the navigation menu at the top of the page.

    Steven Stoddart - 12.03.23 12:40 am

    Love the idea of a GUI to simplify the use of FFMPEG... Unfortunately, the app is not possible to use with UHD displays... The dialogue widows are too small and the font is to big for the available space..

    I have tried using a lower resolution (1920 x 1080) but this seem to make no difference...

    Can you provide some pointers?



    This isn't a thing I can test, but if you want to get together while I try a few things, I'm up for it - mail me.

    Claus Schneider - 13.03.23 10:34 pm

    I have trouble installing using choco

    PS C:\WINDOWS\system32> choco install ffe -y --force
    Chocolatey v1.2.1
    Installing the following packages:
    By installing, you accept licenses for the packages.
    Progress: Downloading ffe 1.1... 100%

    ffe v1.1 (forced) [Approved]
    ffe package files install completed. Performing other installation steps.
    WARNING: Url has SSL/TLS available, switching to HTTPS for download
    Downloading ffe 64 bit
    from 'https://corz.org/engine?section=windows&download=ffe_x64.zip'
    WARNING: C:\Users\yyyy\AppData\Local\Temp\chocolatey\ffe\1.1\ffeInstall.zip is of content type text/html; charset=utf-8

    The file is unfortunately a text file saying: "please inform the webmaster that ffe_x64.zip is missing"

    That is, of course, the wrong URL ;o)

    toronto - 09.09.23 5:33 am

    Hi. Thanks for the cool tools.

    I want to convert audio files from FLAC to ALAC. In the Audio drop-down menu, I see AAC and AC3, but no entry for ALAC.

    The entries are a user preference. See the ini file. Add whatever you need (and is available in your build of ffmpeg).

    Blobb75 - 28.10.23 1:17 am

    This might be the tool I was looking for. What is the best preset to use for combining a still image with a mp3 audio, i.e. to merge it into one avi or whatever video format? Thanks bro!

    First, confirm that you are human by entering the code you see..

    (if you find the code difficult to decipher, click it for a new one!)

    Enter the 5-digit code this text sounds like :

    lower-case zed, Upper-Case Pee, fore, lower-case en, Upper-Case You


    Welcome to corz.org!

    I'm always messing around with the back-end.. See a bug? Wait a minute and try again. Still see a bug? Mail Me!