Creating HandBrakeCli Profile with JSON input


(Anders V Williams) #1

Hey everybody, been toying around with setting up a MCEBuddy Profile relying on HandBrakeCli using a JSON preset configuration to setup the encoder with the specific settings I want.

The profile I have been testing with looks like this:

[Handbrake Cli 1.2.0 JSON Testing]
Description=nVidia HEVC (H265) JSON Input Testing
order=handbrake
handbrake-general=–preset-import-file E:\Configuration\HandBrake\Handbrake_H265_Q17_Yadif.json -Z “H265 DVD Convertion”

Alas this fails though it works when thrown into the regular command line for HandBrakeCli.exe with the -i -o parameters, anyone got any experience applying JSON’s as the source for the encoding in MCEBuddy?


(RBoy) #2

MCEBuddy expects to see an encoder and bitrate in the video command line. If you want to use custom JSON profiles then you need to instruct MCEBuddy to not run any safety checks and automatic adjustments for the video and audio parameters.

You would probably need to use these in your profile:

handbrake-VideoOptimized=true
handbrake-AudioOptimized=true
handbrake-HardwareEncodingOptimized=true

See this topic for more details on how it works.