Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GUI preset usage in the CLI

Open
#199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
cli, documentation

Research direction

Start with the CLI preset import documentation and the references to --preset-import-gui and -Z. Update the relevant guidance so it explains that a GUI preset file with one preset still requires -Z and verify that the documented behavior matches the reported result.

Written by the indexing model from the issue text.

Description

Improvement

Hi,

I've run into a problem where i tried to use a GUI preset (*.json) in the CLI. I've exported the preset in the GUI and included it with the --preset-import-gui option, but it failed to use it until i specified the preset name wit the -Z option. Instead it didn't fall back to the standard CLI preset (something H264) but used my chosen encoder (H265) with some other options. Would be nice if there was a note that even with a file with a single preset you still have to use the -Z option.

Thanks in advance

Dominant language
Shell
Stars
268
Forks
104
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HandBrake/HandBrake-docs

All issues in HandBrake/HandBrake-docs

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.