; ; Setting for ffe - the corz.org FFmpeg front-end. ; ; Most of these settings can be altered from the main GUI. Some values can only ; be hacked in here. There's lots of useful info in here, too.. ; ; ; NOTES: ; ; Lines beginning with ";", like this one, are comments; ignored. ; ; The checkboxes/booleans will also happily accept 'yes' and 'no', 'on' and ; 'off', 'true' and 'false', etc. (no quotes) ; ; ; If you delete this file, you will get a vanilla version in its stead. ; This file is updated and new prefs are added automatically when you run future ; versions of ffe. ; ; ; NOTE: Some settings can accept dynamic @tokens. ; For more information about the available @tokens, see here: ; ; https://corz.org/windows/software/ffe/#@tokens ; https://corz.org/engine?section=beta/windows/ffe&source=version.nfo [ffe] ; ffe is the main preferences section and also the default preset ; any parameter settings inside here will load automatically at startup.. ; ; We start with the editor setting - in case you are in Notepad right now, and ; can barely tell the comments and settings apart! ; ; Enter the path to your preferred text editor.. ; This is invoked if you select the "edit ffe.ini" tray menu option. ; ;editor=C:\Program Files\Notepad++\notepad++.exe editor=notepad.exe ; Edit file_types to your heart's content (or rather, your computer's).. file_types=All (*.*)|Audio Files (*.mp3;*.wav;*.ogg;*.mp2;*.wma;*.asf;*.asx;*.ape;*.shn;*.mpc;*.flac;*.tta;*.m4a;*.aif;*.aac)|Movie files (*.avi;*.mpg;*.mpeg;*.mov;*.mkv;*.ogm;*.ogv;*.mp4;*.asf;*.wmv;*.rm;*.flv;*.vob;*.webm;*.rmvb;*.nsv;*.mpe;*.3gp) ; Combo box (drop-down) options.. ; Whatever you put in here, gets inserted into the combo controls (drop-downs). ; The double pipe at the start of the combo box values ensures you get a blank ; entry above all the others. because many folk don't realise you can simply hit ; delete to remove a value from a combo box, this technique provides a logical ; means to do exactly that. remove the "||" if you prefer. ; Codecs. depending on your system, and build of FFmpeg, you could have more or ; less of these. Add/remove what you need/want. ; ; Note we are using the new format definitions. Please update your binary! ; *** IMPORTANT NOTE ***: ; ; All these lists (which create drop-downs) have a double pipe ("||") entry at ; the beginning. This is required to create the blank entry, when you aren't ; using a setting. Omit it at your peril! ; Formats.. ; ; Audio/Video Encoders (aka. "codecs").. ; ; Depending on your build of FFmpeg, you will probably have a *large* number of ; available encoders. ; ; See FFmpeg's codec encoders help (one of ffe's help buttons is set to this). ; ; It's probably best to keep the menu small in size, including only codecs you ; actually use. It's also nice to have a list with *everything*. Your call. ; ; In fact, you can now have *both*.. ; Automatic Codec DropDowns ; ; If you want a list of ALL the available codecs in your current FFmpeg binary, ; set this to true. You can switch back and forth between this automatically ; generated list and you own (favourites) list, below using the app menu item or ; HotKey, which is F7. ; auto_codecs=false ; Audio Encoders.. ; Audio encoders available in ffe interface.. ; audio_codecs=||copy|aac|ac3|adpcm_ms|eac3|flac|libgsm|mp2|libmp3lame|nellymoser|libopus|sonic|sonicls|libspeex|tta|libvorbis|wavpack|dts|- disable audio - ; NOTE: You will probably want to keep "copy". You *need* to keep ; "- disable audio -" and "- disable video -". If you omit them, they will be ; added back automatically. ; Video Encoders.. ; ; Video encoders available in ffe interface.. ; video_codecs=||copy|bmp|cinepak|dvvideo|gif|libx264|libx264rgb|libx265|libopenjpeg|ljpeg|mjpeg|mpeg1video|mpeg2video|mpeg4|libxvid|msmpeg4|png|qtrle|rawvideo|libvpx|libvpx-vp9|libwebp|xbm|y41p|yuv4|- disable video - ; Purely arbitrary values, for me (I rarely use them). If you have specific ; needs, add those here.. ; video_bitrates=||360k|512k|640k|768k|1000k|1200k|1600k|1800k|2000k|4000k|8000K|16000K|32000K|64000K audio_bitrates=||32k|48k|56k|64k|80k|96k|112k|128k|160k|192k|256k|320k|384k|480k|960k ; Although FFmpeg accepts other frame rate formats, fps is probably the easiest ; to work with, and is the default. Because FFmpeg will accept other formats, ; you can put them here instead of these, if you prefer. ; frames_per_second=||12|15|20|23.976|24|25|29.97|30|50|60|120 ; These are built-in to FFmpeg, and will auto-configure all the correct values ; for the target type. handy. You can override other values manually, so long as ; they are valid for the specific target type. ; ; "("vcd", "svcd", "dvd", "dv" or "dv50" with optional prefixes "pal-", "ntsc-" or "film-")" ; target_types=||vcd|pal-vcd|ntsc-vcd|svcd|pal-svcd|ntsc-svcd|dvd|pal-dvd|ntsc-dvd|film-dvd|dv|dv50 ; Preset resizes. check the help file for the exact x/y dimensions of these. ; This is built into FFmpeg, so these could change over time. You can edit them ; here, if need be.. ; preset_resizes=||sqcif|qcif|cif|4cif|qqvga|qvga|vga|svga|xga|uxga|qxga|sxga|qsxga|hsxga|wvga|wxga|wsxga|wuxga|woxga|wqsxga|wquxga|whsxga|whuxga|cga|ega|hd480|hd720|hd1080 ; This checkbox will normally be 1/on/true/etc. (checked) or 0/false/off ; (unchecked) but if you hack it to - (a minus symbol) you will disable the ; checkbox altogether, and from that point on, presets will load and save only ; parameter data, not file names. ; store_filepaths=false ; Fall-back Folder/Directory ; ; If, for some reason (perhaps you loaded a URL and have no outputfile specified ; in your preset), ffe can't work out where you want the output file to go, ; where should it put them? By default this is the parent dir of the input file ; (@parent). You might prefer @mydocumentsdir, or something else. ; ; NOTE: if you use @parent, and the inputfile is a URL, ffe will default to ; dropping the files in your "My Documents" directory. If you don't want this, ; specify an output directory! If you download from URLs a lot, you will ; probably want to set a firm location, here or in your preset. Yes, this can be ; set inside your presets for per-preset fall-back locations. It's still best to ; set the output location (folder) inside the preset, e.g.. ; ; outputfile=d:\downloads\video ; fallback_folder=@parent ; Default Extension/Container. ; ; When ffe can't decide what extension to give your output video, it will fall- ; back to using which extension (also sets the container used).. ; Note: You can also set this inside presets. ; default_extension=mkv ; ; NOTE: You should rarely if ever need to change this. Well, not more than once. ; This is usually easy for ffe to work out. The codecs map simply, and when you ; are copying audio from a video file, ffe will interrogate the file for the ; codec used. However, when it can't figure it out, it uses this, which you may ; want to change. Note: You can also set this inside presets. ; default_audio_extension=aac ; Do MATOF (Magical Automatic Transforming Output Filename) ; ; Yes! YES! YES! This enables ffe to automatically generate your output file ; name based on the input file name and encoding parameters used. This prevents ; all sorts of issues and enables you to save lots and lots of different ; versions of a file very, very quickly, aka. "Find the best settings". It's ; also required (and will be automatically enabled) for batch runs. ; ; There is a button for this in the GUI, right next to the output file input. ; do_matof=true ; Sort the Presets Drop-Down.. ; ; By default, ffe sorts the list of presets (Alphabetically) to make it easier ; for regular folk to find their chosen preset. But you might prefer ffe not do ; this. With sorting disabled you get your presets presented in the order they ; appear inside ffe.ini; most likely the order in which they were created. Also, ; the default "ffe" preset will always be at the top. Your call.. ; sort_presets_list=false ; When using a sorted presets list, the "ffe" item will likely be right in the ; middle. In that case, you may prefer to hide it. ; You can still write settings to the default preset by typing "ffe" into the ; preset list and saving it. It simply won't show in the drop-down.. show_ffe_in_sorted_list=true ; These next three settings can also be got to from the Application Menu.. ; ; You can wrap the console output.. ; console_wordwrap=true ; This boolean for "always-on-top" status is either true or false.. ; on_top=false ; Use images for (some of) the buttons? (true/false..) ; image_buttons=true ; The mafot separator is simply the character between your regular output ; file name and the matof (Magic Auto-Transforming Output Filename) information ; eg "myvideo [640x400].avi" <- in that example, it is a space character, which ; is the default. Leave the preference blank for the default, or use some other ; character, or combination of characters, instead. ; ; Tip: to use a combination with a space at the start, enclose it in quotes, eg.. ; ; matof_separator=" foo=" -> would give us -> myvideo foo=[640x400].avi ; matof_separator= ; By default, ffe expects the FFmpeg binary to be in the same folder as itself ; but if you need it to be somewhere else, override that here.. ; ; You can use @tokens in this preference. ; ffmpeg_binary=@programfiles\corz\ffe\ffmpeg.exe ; ; If ffe cannot find the binary, it will ask you to locate it. However, note; ; the GUI won't allow you to select a binary named anything but "ffmpeg.exe", ; so if you need to use a different name, put that here, and ffe will use it. ; ; NOTE: you can drag an ffmpeg.exe directly into ffe's file input or drop window ; to quickly change this setting. ; ; FFmpeg plugins path.. ; ; If you want to run fancy plugins like the wonderful frei0r collection, you ; will want to set the location of your plugins folder here. This way, ffe will ; insert the corect system path environment variable for you, which will enable ; the plugins to work. By default it is a folder called "plugins" next to ; ffe.exe/ffmpeg.exe ; ; You can use @Tokens in this preference. ; plugins_path=@programfiles/corz/ffe/plugins ; If you are having trouble getting hold of 64 bit frei0r plugins, download ; this https://shotcut.org/ and extract the plugins from lib\frei0r-1. ; You might also want to give the editor a whirl. It's also free. ; ; See here: https://ffmpeg.org/ffmpeg-filters.html#frei0r-1 ; Commands for the quick task buttons.. ; ffmpeg_command=-help ; ; this works in a similar way to the help buttons, piping FFmpeg's console ; output to the ffe console. You can use this for anything you like; post- ; processing, information, adding subs, whatever. @tokens are fine. ; And one for ffplay.. ; By default, this is @outputfile, so you can see the reults of your latest work ; immediately. Use anything you like. Dynamic @tokens are fine. ; ffplay_command=@outputfile ; The console output can be piped to your ffe console.. ; show_ffplay_output=false ; ; If you are simply playing video, keep this set to false. For troubleshooting / ; debugging, ffe console output can be most useful. If your ffplay window ; flashes away before you can read it, set this to true. ; ; You can toggle this setting via the app menu or with the Hotkey: F6. ; Log file location override.. ; ; By default, ffe will log to your application data folder, or in portable mode ; ffe will log to the application directory (where ffe.exe lives). ; ; You can also specify a directory here, ffe will create "ffe.log" in there. ; ; If you wish to specify a log location, enter the full path here.. ; To disable regular logging, use a dash, e.g. log_location=- ; ; You can use @tokens in this preference. ; log_location=@datadir ; ; NOTE: If your specified location is not writeable, ffe will create the log in ; your system's temp folder. ; ; You can also set this inside your presets for per-preset logging. ; save a log of each job next to the output file.. ; log_each_job=false ; ; You can also set the location of the per-job logs. By default, it is in the ; parent directory of the input file. ; ; Note, you can use @tokens in this setting. ; job_log_location=@outdir ; If you want, you can put ALL your logs in the same location. The main log will ; be named "ffe.log" and the per-job logs will have names corresponding to the ; jobs themselves. Batch jobs are named after the directory, with any MAFOT ; string added to the end, for clarity. ; Font for the console output control.. ; Defaults to "Consolas". Monspaced fonts work best. ; console_output_font="Consolas" ; Similarly the font size.. ; (note: if using "ProFontWindows", set the size to 9!) ; console_output_font_size=8.5 ; ; NOTE: This is also the font used for the extra parameters input. ; Fancy Input Boxes use this font for the text input area.. ; inputbox_font=Consolas ; NOTE: All your wee dialogs will remember their x/y/width/height values. ; Default "joined" name.. ; ; For concatenation (joining) of the output files, ffe will use this as the name ; for the file. The extension is added automatically. ; joined_name=joined ; ; Process Priority ; ; You can set the CPU priority of FFmpeg here. The "Normal" value is 2. ; ; 0 = Idle/Low ; 1 = Below Normal ; 2 = Normal ; 3 = Above Normal ; 4 = High ; 5 = Realtime (Use with caution, may make the system unstable!) ; ; You can change this setting from the app menu. Even whilst FFmpeg is running. ; cpu_priority=2 ; FFmpeg built-in help texts.. ; ; FFmpeg has built-in help. Lots of it. ffe enables you to keep it handy, right ; next to where you are working. ; ; You can configure any number of readily-available help buttons, right above ; the extra parameters input, each outputting some predefined FFmpeg help output. ; There is a trade-off between space taken up by these buttons and the custom ; command buttons. You will find a balance, I'm sure! ; ; Each help file button section is separated by a comma "," and each property is ; separated by a pipe "|" character, basically.. ; ; TITLE+ToolTip|output-filename.ext|ffmpeg command ; ; The first property is used in the ToolTip entry and a BIG label above the ; buttons which makes for faster recognition, should you forget which button is ; which and need to hover over them to get help (there is also ToolTip help for ; the buttons). ; help_texts=Main|help.txt|-h,Filters|help-filters.txt|-filters,Encoders|help-encoders.txt|-encoders,Full|help-full.txt|-h full,ffprobe|ffprobe-help.txt|@appdir\ffprobe.exe -h,ffplay|ffplay-help.txt|@appdir\ffplay.exe -h ; ; Leave blank to disable help buttons. Commenting out the preference will get ; you the default set. Note: you can add & remove buttons from inside the GUI. ; ; BE CAREFUL with your pipes and commas, it would be real easy to mess this up! ; You can edit these from inside the GUI; simply right-click the help buttons. ; ; ; Here are some other commands you might consider.. ; ; -h topic show help ; -help topic show help on ; -version show version ; -buildconf show build configuration ; -formats show available formats ; -muxers show available muxers ; -demuxers show available demuxers ; -devices show available devices ; -codecs show available codecs ; -decoders show available decoders ; -encoders show available encoders ; -bsfs show available bit stream filters ; -protocols show available protocols ; -filters show available filters ; -pix_fmts show available pixel formats ; -layouts show standard channel layouts ; -sample_fmts show available audio sample formats ; -colors show available color names ; -sources device list sources of the input device ; -sinks device list sinks of the output device ; -hwaccels show available HW acceleration methods ; ; See the current FFmpeg help for commands you might want to buttonize. By ; default it is available as the last button in the row("-h full"). ; "Short Test" Frames. ; ; The "Short Test" Button adds parameters to your extra parameters input telling ; FFmpeg to process only the first 500 frames of video. Or some other number.. ; ; Shift+Click or Right-Click the short test button, to set this from the GUI. ; short_test_frames=500 ; Custom Command Buttons. ; ; These are nifty! You can specify any number of custom buttons to add whatever ; parameters you want to the extra parameters input. This is especially useful ; for filters and other things you use over and over. ; ; See the [custom buttons] section for the actual buttons. ; ; Here you can control how many columns of buttons there are (there are always ; one or more ROWS, depending on how many buttons you create).. ; custom_buttons_columns=auto ; ; If you set this to 0 (zero) you get no buttons. ; ; The app menu will give you the option for 1-12 columns or "auto". But there is ; no limit to the number of columns you can create. You will need a wide monitor ; and a large window to display double-digits of columns. ; ; If you create 10 buttons (below, inside [custom buttons]) but only 3 columns, ; you will only see 9 buttons as there is a limit of three ROWS (to fit them ; inside the interface). So ensure you create enough columns to house all your ; buttons! Or better yet.. ; ; There is an automatic setting, "auto", which will calculate the best fit for ; your window and number of buttons. This works well. ; ; The custom_buttons_columns setting can be got to from ffe's App Menu. ; ; The default settings line up the button rows nicely with the three button on ; the right (reset, short test, report).. ; You can also control the width of the actual buttons. You can have HEAPS of ; small buttons or a few, well labelled, big buttons. Your call.. ; The default is 72. custom_buttons_width=72 ; You can also set the font size for the custom buttons (default=8.5).. custom_buttons_font_size=8.5 ; If you want TOTAL control over the placement and size of your buttons, you can ; mess with the following settings (all measurements in pixels).. ; The height of the buttons. The default is 22.. custom_buttons_height=22 ; ; If you want *lots* of buttons, you can make this 16 or even less. ; Remember to also reduce the font size. ; The starting X (horizontal) position, from inside the buttons space. ; default=10 buttons_x_shunt=10 ; The starting Y (vertical) position, from inside the buttons space, default=7. buttons_y_shunt=7 ; The space between the buttons. Default is 1. Also affects horizontal spacing. ; Again, negative values are OK. You want overlapping buttons. Knock yersel oot! button_spacing=1 ; ; You should be able to get six rows of buttons in there easy! ; Alternatively, a few HUGE buttons. ; A few example buttons are provided. ; See the [custom buttons] section in this ini for those actual buttons. ; When you click on a custom button, any associated notes can be piped to the ; console.. ; button_notes_to_console=true ; If you want, you can disable custom buttons. Completely. ; ; Of course you would be mental to do this. But here it is. ; And in the app menu. enable_custom_buttons=true ; The delimiter used to separate commands from comments inside the custom ; buttons has been changed from "|" to "***", as the pipe interfered with ; certain FFmpeg advanced commands. Sorry. ; ; If you want back the old behaviour (though I definitely recommend just ; updating your buttons!), you can hack it here.. ; button_delim=*** ; ffprobe media reporting.. ; ; NOTE: To generate media reports, you need to have ffprobe.exe sitting next to ; ffmpeg.exe, which it probably already is. ; ; Or else use MediaInfo.exe (CLI VERSION!) ; ffprobe report format ; ; Set the output printing format for the generated report. ; Available formats are: default, compact, csv, flat, ini, json and xml. ; report_format=default ; ; You can get to this setting from ffe's app menu. ; ffprobe report file extension ; ; When generating media file reports with ffprobe, which file extension to use? ; You can enter whatever extension you like here. You can also use "auto" (the ; default), to have ffe use an extension which matches the report format. ; report_extension=auto ; ; Remember, if you SHIFT+Click the "media report" button, it will, rather than ; show in your console output, open in your system's default viewer for this ; extension, which can be handy. So if you always want to see the reports in a ; particular editor/viewer, use an extension which will launch it. ; Report Directory. ; ; Where would you like ffe to store your media reports? ; By default, ffe stores them next to the input file. ; ; NOTE: You can use @tokens in this setting. ; report_directory=@parent ; Extra Switches.. ; ; You can add any extra switches and parameters for ffprobe, here. These are ; placed directly before the input file. ; report_switches= ; ; Un-Escape Output. ; ; Finally for ffprobe, you can choose to have the output un-escaped. To explain: ; The ffprobe output will usually be escaped, in other words, special characters ; will have a backslash before them, e.g. "\\", "\:". If you prefer, you can have ; ffe convert that to "\" and ":". ; un_escape_output=true ; Use MediaInfo ; ; If you prefer, you can have your report generated by the wonderful MediaInfo.. ; ; http://mediaarea.net/en/MediaInfo/Download/Windows ; ; You want the 64 bit CLI version. ; use_mediainfo=false ; Enter the full path to THE CLI VERSION of MediaInfo.exe, e.g.. ; mediainfo_location=C:\Program Files\MediaInfo\CLI\MediaInfo.exe ; You can set the extension to be used when creating reports with MediaInfo.. ; ; default: nfo ; mediainfo_extension=nfo ; If you want to pass any extra parameters to MediaInfo, put them here.. ; Run: MediaInfo --Help for more information. mediainfo_switches= ; If you like, you can disable saving reports altogether. ; You will still get them in the console. save_reports=true ; You can get to this setting from the app menu. ; When spewing out preset notes, ffe prefixes them this. ; notes_prefix="\nnotes:\n" ; ; Note: the "\n" is translated into a linebreak in the final output. ; Of course you can put notes in the default [ffe] preset! ; notes=Custom Welcome Message Here! ; ; You can, of course, delete the above notes! ; Floating Drop Window ; ; This is a funky, shaped window which is created from any transparent PNG/GIF. ; ; Once activated, you can drop files into it and they will be immediately ; processed by your current "Drag-And-Drop Command", whatever that may be; ; currently either "go" (process the file with the current settings, or "report" ; which produces a media report of the file, using your current media reporting ; preferences. ; ; For PNGs, ffe will use your alpha channel to produce a proper transparent ; window with full alpha blending - drop shadows will look lovely. ; ; Specify the image here. A few demo images are included. ; drop_win_image=images\ffe.png ; ; NOTE: You can input any common image type here, ffe will understand it. ; However, only PNG and GIF files will appear in the menu. If you *must* use a ; JPEG, you will need to set its full path here. ; You can also set the overall level of transparency for the drop window, 0-100. ; At 99, the drop window is practically invisible. Default is 0 (opaque). ; You can set this from the Drop Window's context menu, in 5% graduations. ; drop_win_transparency=0 ; ; A note about drop window transparency and mouse hover: ; ; When you hover you mouse over the drop window, the transparency will switch to ; 50%. Unless your transparency is between 45% and 65%, in which case it will ; switch to 0% transparency (completely opaque), as these values are too close ; to 50% to see an obvious change on mouseover. ; ; If this behaviour bugs you, you can set the mouseover transparency explicitly, ; here.. (the default is -1, which lets ffe work it out). ; drop_win_hover_transparency=-1 ; these will get filled automatically, but we put them here so they are handy. do_drop_window=true drop_window_x=0 drop_window_y=0 ; Allowed image types.. ; ; A list of the image extensions you want ffe to accept as drop images. By ; default we only use PNG, GIF & ICO, because they can have transparencies, but ; feel free to add any other common types you need. Whatever you add here, that ; type of image will be displayed in the drop window context (right-click) menu. ; ; Extensions that do work: bmp,png,ico,emf,wmf,jpg,jpeg,gif,pcx,tif,tiff,eps ; ; Most eps files don't work. Some PCX don't work. Others should work fine. ; If some image doesn't work, export it to a PNG in your image editor. ; allowed_image_types=bmp,png,ico,emf,wmf ; ; If you want to enable jpegs, remember to add jpg AND jpeg. ; ; NOTE: You can also use "*" here, which will load the following types: ; ; bmp,png,ico,emf,wmf,jpg,jpeg,gif,tif,tiff ; Drop Window Images Location.. ; ; This is you main Drop Window Images folder.. ; Either enter a full path, or else a path relative to ffe's data directory. ; drop_win_image_folder=images ; Fluid or Fixed Menu.. ; ; By default, ffe shows the files in your drop_win_image_folder, and all its ; subfolders in cute cascacing submenus. If you drag in images, whether you ; copied themover (see below) or not, the menu remains the same. But you can ; also set itto "fluid" mode, where the menu dynamically switches to the parent ; directory of whichever image you select/drag in. Your call.. ; fluid_image_menu=false ; ; If the above (fluid_image_menu) is set to false, this next setting takes ; effect. Enable this to have ffe automatically copy all dragged images to your ; fixed drop window images directory. Enabled by default. ; auto_copy_images=true ; Drop Window Image Pack ; ; You can download a starter pack of images to use for your drop window, here.. ; image_pack_url=https://corz.org/windows/software/ffe/files/DropWindowImages/ ; ; This feature is available from the tray menu. ; ; You can specify your own URL, if you prefer. Upload a list of images named.. ; ; image_pack_urls.txt ; ; and drop it into the root images folder. Subfolders are fine; ffe will re- ; create those locally and make them available in your drop window's cascading ; images context menu. Pretty neat. All this is nicked from my upcoming app; ; BlobDrop. ; ; The format of the file is a simple plain text list of image paths from the ; root, e.g. ; ; Film-Reel-Simple.png ; Folder-Videos-icon-By-Zerode_small.png ; Animated Gifs/Animated_film-strip-trans-by_Cor.gif ; ; Location of GDI+ DLL.. (for Windows Vista & Windows Server 2008 only) ; ; This is used to display the PNG Drop Window ; ; For Vista & Win2008, GDI_dll must be defined. ffe will attempt to locate a ; likely dll for you, which might take a minute the first time you open your ; drop window. ; ; If that fails for some reason, you can locate one yourself and enter the full ; path here ("Clipboard As Name" is great for that stuff). The gdiplus.dll can ; be found in %Windows%\winsxs\*.gdiplus*\gdiplus.dll (use F3). It shouldn't ; matter which one you use, start with the biggest. ; GDI_dll= ; Pre- and Post-Job Commands.. ; ; You can specify a set of windows shell commands to run before your FFmpeg job ; runs. ; ; These are standard windows commands, exactly like you would put in a .bat file ; (ffe doesn't care what extension you use, it will still run the commands, in ; order, one-by-one). ; ; You can enter simply a file name, in which case it is assumed to be inside ; your data directory (in portable mode, that is the same directory as ffe.exe) ; or you can enter the full path to the file. ; ; I use this to empty a target folder then copy test files over from the source ; folder for a fresh batch of tests, but the facility has many potential uses. ; ; You can also set this file path inside individual ffe presets for per-preset ; pre-run commands. ; ; If a pre-run commands file exists for the current preset, you will have an ; "Edit Pre-Job Commands File" option in your ffe system tray menu. Otherwise you ; will have a "Create Pre-Job Commands File" option. ; ; NOTE: these commands are processed by ffe, one-by-one; forget GOTOs! ; ; NOTE: It is better to set these inside individual ffe presets. ; ; ; You can use @tokens inside this setting, e.g. @datadir\pre-job-commands.bat ; pre_job_commands_file= ; Whether or not to run pre-job commands.. run_pre_job_commands= ; And again for Post-Batch Commands, which run after the job is complete. ; post_job_commands_file= ; Whether or not to run post-job commands.. run_post_job_commands= ; Pre/Post-Job Commands Time-out.. ; ; If the Pre/Post-Job commands continue running past a certain time, we can kill ; them and move automatically onto the job. By default this is set to 0, which ; means do not kill pre-job commands, no matter how long they run for. ; ; Enter the number of minutes to allow Pre/Post-Job Commands to run for. ; batch_commands_timeout=0 ; Post-File Command.. ; ; You can also run a command after each file is processed. This is designed for ; processing files created during a batch, but has other uses. You can enable/ ; disable/unset this from the main ffe gui (job buttons). ; ; Here is the text of the actual command.. ; post_file_command= ; And whether or not we run it.. run_post_file_command= ; The following three settings cannot (currently) be set from the GUI but can be ; set manually in presets, if required. If unset, their values will be inherited ; from these master settings.. ; Post-File Command Run Style (direct/dos/shellexecute) ; There are a few choices for how to run the Post-File Command. ; By default, we run it directly.. ; post_file_run_style=direct ; ; When using the bult-in (direct) method, you can use arguments and redirection ; ">" in your command to pipe standard output to a file. In that case, ffe will ; capture that output and save it to the specified file. ; ; If your program is a console app and it's not working the way you expect, ffe ; can run your command through the Windows command interpreter (cmd.exe). To get ; this option, use "post_file_run_style=dos". ; ; ffe can also use the Windows API "ShellExecute" method, which launches a file ; using whatever is set as Explorer's default "open" command. There are a ; limited number of things you can do with this method and it usually best ; avoided. To use this, set "post_file_run_style=shellexecute" ; Post-File Command Capture (true/false) ; We can also choose whether or not to capture the output (which will be visible ; in your ffe console). If you are capturing the output, you will obviously need ; to wait for the process to end. If your cammand is expected to take a long ; time, you may want to disable this. post_file_capture=true ; Show Post-File Command Window (true/false) ; This sets whether or not we run the command hidden. By default we show the ; program window.. post_file_show=true ; NOTE: ALL Pre/Post Commands settings can be set on a per-preset level. ; ; If you set a commonly-used command here, it will always be available, ; should you ever need it in any particular preset. ; Normally, ffe runs the commands itself, via the Windows Command Interpreter, ; but you can also have ffe run the file as a batch (.bat) file. If your script ; contains loops or GOTOs, you will want to enable this.. ; run_commands_with_shell=false ; Set default Settings on Exit ; ; I tried to think of the best way to word this. "Remember last used settings". ; Hmm. At any rate, whatever settings you have when you quit ffe can saved to ; the EXIT-SETTINGS preset, to be used the next time you launch ffe, so you ; can continue from exactly where you left off. ; retain_exit_settings=true ; ; Note, even if you have file paths disabled in your preset preferences, these ; WILL be retained on exit, so they auto-load on next launch. ; You can also keep the recently completed files list between sessions. These ; are available from ffe's system tray menu, for easy launching. Moved/deleted ; files are automatically removed from this menu. ; retain_recent_files=true ; Start ffe in a minimized state? ; ; If you have retain_exit-settings enabled, ffe will remember your minimized/ ; maximized state for next launch anyway. THIS setting enables you to tell ffe ; to ALWAYS launch in a minized state, or at least until you disable the it, ; maybe just for next time.. ; start_minimized=false ; Allow Multiple Instances of ffe? ; ; Normally, we do not allow multiple instances. If ffe is open and you send ; another file to ffe.exe, it will redirect the file to the existing running ; instance. HOWEVER, you might be experimenting with multiple FFmpeg builds, or ; have multiple portable installations setup differently, or something, so you ; can disable this behaviour, if required. ; allow_multiple=false ; ; You can get to this setting from the app menu. ; Drop Command ; ; You can setup a special command that will be run every time you drag-and-drop ; a file onto ffe's file input. Choose from "go", which will run whatever is ; currently setup in your GUI, or "report", which will immediately generate a ; media report in your currently selected format (which can be viewed ; immediately in the console output pane). You can also have "play", which will ; play the file with FFplay, using your regular settings and "generate" which ; will generate a batch script from the input using your current settings. ; drop_command= ; ; You can get to this setting from the app menu. ; Run drop command on files set at launch? (true/false) ; You can get files into ffe a number of ways, like with ffe in your sendTo ; menu, or perhaps an explorer context command. ; ; Should ffe run the drag-and-drop command on these files at launch time? ; If you expect to see a report instantly no matter how you get your files into ; ffe, set this to true.. ; launch_with_drop_command=false ; Superlative Countdown Timer in TitleBar ; ; When Delayed Start is activated, ffe posts a splendid countdown timer in the ; main window's TitleBar. It is human-readable. If preferred you can disable ; this magnificent timepiece here.. (Boos from the audience!) ; do_countdown_timer=true ; ; Note: this user-setting is currently not ignored. ; You can get to this setting from the app menu. ; Time in Title. ; ; While FFmpeg is running, you can show the total time in the title bar. ; time_in_title=true ; Kill FFmpeg on exit. ; ; You can now set whether or not you want ffe to kill the FFmpeg process when it ; is itself quit. You can setup a job, start it, and then quit ffe and FFmpeg ; will continue running in the background, until the job is complete. Not ; something I recommend, but there it is. ; ; Of course, this also means you can explicitly tell ffe to do the opposite, ; killing any FFmpeg process when it quits; the default behaviour.. ; kill_ffmpeg_on_exit=true ; ffe job toggles ; ; These actually have three states; enabled, disabled and unset. For the third ; (unset) state you can leave it blank, delete the entire preference, or use the ; literal value "unset". Note: ffe will delete unset preferences when you save a ; preset, for more compact presets. ; ; The REASON there are three states, is so that you can stack presets, where ; the most recently loaded preset overrides and builds on existing settings. ; With three states we can set it to "unset" which basically means, "leave this ; setting alone when loading this preset". All these settings can be saved and ; restored in presets.. ; ; Force FFmpeg to overwrite existing files, the way it used to do by default. ; With MATOF, it's usually safe to leave this set to true. Your call.. overwrite= ; whether or not to join output files in batch operations.. concatenate= ; If you want ffe to quit at then end of the job, set this to true. ; Actually, that would be annoying! Probably better to set this inside a preset. quit_when_done= ; It can be handy to have ffe shutdown your computer at the end of a long job.. shutdown_when_done= ; ; NOTE: the final two settings will be saved with your preset, but NOT to your ; default preset. If you want this behaviour for ALL jobs, you need to set it ; here inside ffe.ini. ; Miscellaneous hacks.. ; ; ToolTips.. ; The main switch for these is in the App Menu (NO! DON'T!!!!) ; icon resource file, usually blank - will use ffe.exe as the icon resource. tip_icon_res= ; icon index inside said resource file. default is -11, the "i" icon. tip_icon_index=0 ; you can override the icon and use a system tooltip icon. ; ; = Use tip_icon_res [default] ; 0 = No icon ; 1 = Information icon ; 2 = Warning icon ; 3 = Error Icon ; 4 = Large Information Icon ; 5 = Large Warning Icon ; 6 = Large Error Icon ; system_tip_icon= ; Tip style. ; ; 1 = Normal balloon tip, above. (the default) ; 2 = Centre the tip horizontally under the control. ; 3 = Center tip, under control. ; 7 = Left-side center tip, below. ; ; NOTE: These numbers can be added together (i.e. 3). ; tip_style=1 ; ; If you set system_tip_icon=0 + tip_style=0, you get a regular WindowsToolTip. ; I have discovered that 8 gives you a nice greyed tip with no "balloon"ing. ; How to get it above? hmm. See the notes inside cel.au3 in the source pack. ; ToolTip Time ; ; You can even tweak the length of time ToolTips appear for. ; The default is 10000 (milliseconds), 10 seconds, long enough to read the ; longest lovingly-crafted help-text ffe has to offer. If you read very quickly ; or very slowly (mouse away and then back!), you can change this value here.. ; tooltip_time=10000 ; Disable Console Output ToolTip.. ; ; If you want to retain the useful tips over your buttons and controls, but NOT ; over your console output, where it can annoy, you can disable that here.. allow_console_tooltip=true ; ; .. and also from the app menu. ; Pause is Global.. ; ; You can suspend/resume ffmpeg with a Hotkey (ScrollLock). Here you can set ; whether or not this key operates only when ffe is at the front (false) or ; globally, no matter what app you have at the front (true). As ScrollLock is ; used for NOTHING ELSE it's a decent idea to make this global.. ; pause_is_global=true ; This double-checks for right-clicks on particular buttons. If you are having ; issues with dialogs appearing twice, disable this (shouldn't happen). ; double_check_rclicks=true ; Auto-Crop settings.. ; ; Uses FFmpeg's "cropdetect" functionality to get the likely cropping values for ; the video and inserts them, as if by magic, into the cropping inputs, ready ; for you to encode the video. Exactly *how* it does this, is up to you.. ; ; Number of frames to grab (default:24). auto_crop_frames=24 ; Black value threshold (default: 24). From 0 - 255. An intensity value greater ; than this value is considered non-black. auto_crop_limit= 24 ; ; *** OR ELSE ***.. ; It's a float (from 0 to 65535). The default being 0.0941176. Check the FULL ; FFmpeg help file for your current binary (there is a button in the ffe GUI) to ; see what expects as a value. If your auto-crop isn't working, this is what you ; may need to play around with. ; The value which the width/height should be divisible by (default: 16). ; The offset is automatically adjusted to center the video. Use 2 to get only ; even dimensions (needed for 4:2:2 video). 16 is best when encoding to most ; video codecs. auto_crop_round=16 ; Recalculate the crop area after this many frames (default: 0). ; Set the counter that determines after how many frames cropdetect will reset ; the previously detected largest video area and start over to detect the ; current optimal crop area. ; ; This can be useful when channel logos distort the video area. 0 indicates ;'never reset', and returns the largest area encountered during playback. ; auto_crop_reset=0 ; Delete options.. ; ; You can right-click the label to the left of the output file (input) to ; instantly delete the output file. These options control how this file is ; deleted. We set safe defaults that you can change at your leisure.. ; ; When set to false, you will get a one-time warning that you are going to get ; NO MORE WARNINGS! always_warn_on_delete=false ; delete_to_recycle_bin=true ; If you are messing around with the code or producing a debug report, ; set this to 10. The default is 1; log only errors. debug_level=1 dump_file=@datadir\ffe_debug.log ; Maximum debug log size, in MB. ; Generally we leave this set to the default (0 = no limit). ; The file is deleted at launch time. max_debug_log_size=0 ; Set this to true and it will remove all comments from this ini file. ; For when it gets big and you've read them all already. ; clean_comments=false ; ; NOTE: This happens automatically if your ini grows to more than 60KB in size. ; This keeps you automatically updated with the latest preferences.. ; version= ; Version Checking.. [bool] [default: version_checking=-1] ; ; ffe can check online to see if a newer version of ffe is available. ; ; Enter a number here, which will represent the number of days between checks, ; i.e. to check weekly, use: version_checking=7 ; ; To disable version checking, set version_checking=0 ; There is also a special switch, "always", meant mainly for debugging. ; version_checking=-1 ; ; The first time you quit ffe, it will ask you about this. ; ; More Default Parameters. ; ; You can put *any* default parameters right here, and they will load at launch. ; ; You can even hard-code input (and output) files into this ini, and they will ; be picked up and used as the default files. e.g.. ; ;infile=I:\Rip\dvd_in\VTS_01_1.VOB ;outputfile=I:\Rip\dvd_in\ ; ; Same for any other parameter. in fact, you can setup ffe just the way you like ; it and then save it in the preset called "ffe" (no quotes). Tada! Instant ; default preset. ; ; NOTE: It's advisable to set outputfile to your default output directory and ; let ffe work out the rest. The trailing backslash "\" is optional. ; And finally... ; ; FFS! DO NOT TOUCH THIS!!! this_pref_does_almost_nothing=maybe ; Those super-handy custom buttons (max 500!).. ; ; It's best to add/edit/delete buttons from inside the GUI. ; If you want to roll your own, do.. ; ;