Handbrake: save custom preset/encoding command out for use on handbrake-cli on another machine

Max Williams picture Max Williams · Jan 3, 2014 · Viewed 9.9k times · Source

I have a bunch of videos to convert, from flv to mp4. In the Handbrake gui, in Ubuntu, i've got all my settings sorted out. I've saved it as a preset called "all-tablets".

I need to use HandBrakeCLI on a different ubuntu machine, that's command line only. So, i have two options i can see, and i can't work out how to do either of them:

1) See what the settings used by the handbrake gui are, so i can copy them and use directly with HandBrakeCLI, replacing filenames as necessary.

2) Save out my "all-tablets" preset in such a way that i can copy it to the other machine and use it with HandBrakeCLI there.

Option 2 seems nicer. When i list the available presets in HandBrakeCLI, it doesn't list my custom one, suggesting that the GUI version saves them to somewhere different to the cli version.

Any suggestions? thanks, Max

Answer

Max Williams picture Max Williams · Jan 14, 2014

I actually ended up figuring this out: i tried the Windows version of Handbrake in a Windows 7 virtual machine. In windows, the GUI version is just a wrapper for the CLI, unlike Linux where they are two totally seperate things. (i'm not sure what the situation on Mac is).

I first tried importing the preset plist file that i'd saved out of the linux version, but the windows gui couldn't parse it properly, or wasn't happy with it anyway: it seemed to be treating one of the boolean values as if it was a variable name (ie trying to do something like true = "foo"): i couldn't work out what was causing this in my plist file: side by siding it with one saved out of windows, it looked fine.

So, i started from scratch in the windows GUI. The interface is styled a little differently, but I was able to set all the options i have in my linux gui. Then i did a conversion with these settings: because the windows gui uses the CLI version, you can see the command sent to the cli in the conversion log. I copied this, and tried the same set of options in the linux CLI, and it worked fine.

I never thought i'd write this as an answer to any question, but the answer seems to be "Use windows" ;-) Who'd a thunk it.