Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Presets -- without applying previous file's DIMENSIONS #2307

Rumourd opened this issue Sep 11, 2019 · 3 comments


Copy link

commented Sep 11, 2019

I set up many Custom Presets...
I have hundreds of BluRay files to encode, all with different dimensions...

How can I use my Custom Presets -- withFilters/Video/Audio/Subtitle/Chapters already preset by me -- wherein Handbrake interprets each fresh video file's Dimensions independently (and correctly calculating Cropping, then summing up correct Source Size)?

What's happening now is, I import a fresh file, apply my Custom Preset, and it applies the previous file's Dimensions. This happens whether I apply the Custom Preset before or after importing a fresh file.

Is there a way to bypass this?

Upon importing a fresh file, OFTEN the proper information is not interpreted, instead defaulting to the previous files info. Audio channels and Chapters are especially susceptible; I then have to select a different preset, then reimport said fresh video file -- OFTEN 2-3 TIMES -- before the file's info is correctly imported. It is maddening.


This comment has been minimized.

Copy link

commented Sep 11, 2019

When you save a new custom preset, you are asked if you want it to use the current dimension information. If you select "No", the preset will not change any dimensions on future files using that preset.

If you select "Yes", the dimensions you have set become the LIMITS for future files. If the source is smaller than those limits, it will not be up-converted; it will use the source dimensions instead.

Audio behavior can be a can of worms, since sources vary so much.


This comment has been minimized.

Copy link

commented Sep 14, 2019

Can you provide the activity log please (scan log will suffice)

@sr55 sr55 closed this Sep 18, 2019


This comment has been minimized.

Copy link

commented Sep 18, 2019

We've not heard back in a while so we are closing this issue out. If you can provide the requested details or feedback we can re-open this issue.


@sr55 sr55 removed the Awaiting Feedback label Sep 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.