HandBrake

I will look into doing so. Ultimately, I was just looking for a way to make a batch job of scripts and someone had recommended PowerShell. Anyone have some ideas for scripting languages to run on Windows? I'm sure HandBrake works just fine with PowerShell. I would just figure out the issue, than lo...

I am constantly flabbergasted that people get upset when software actually makes use of the computer resources they've paid good money for.

Thanks! I'll give it a whirl.

Be happy to. I can give it a go tonight when I get home from work.

Ok, thanks. I'll check it out.

Thanks, Rodeo. Very helpful.

I thought I remembered from the old Trac docs that there were some advanced "tweak" settings for 264 uses in the high profile preset. No?

I'm more interested in what 264 settings the preset uses, not what tracks are selected, etc. The latter I can figure out. The former is black magic to me.

Thanks.

What I'd really like to know (and what the old documentation use to show) is what command line options are used by a given preset. Is there way to get that information?

Awesome! Thanks, Woodstock. I've never noticed that option.

Thanks. Can you tell me what settings the "High Profile" preset uses? It use to be shown in old "trac" documentation, but I can't find it in the new stuff.

I'm not referring to the 264 profiles, but the HandBrake preset called "High Profile." I'm not I don't see an changes. I just noticed that the Windows GUI version (which I use to visually inspect sources before I run them through the cmdline) now put that preset in a group called "Leg...

Please describe the problem in as much detail as possible: When encoding using --start-at/--stop-at with "duration" the current (some previous) nightlies hang a 100%. I let it sit for an hour (no CPU usage at all). (using chapters instead of seconds does not exhibit this behavior). FYI: I...

Hi. I apologize if this information is already posted somewhere (or if your policy is to not reveal future plans). I see that the "High Profile" preset is now labeled "legacy" in the nightly build. Does this mean it is being deprecated and will be removed in the future? If so, ca...

I was just ripping my special edition "Romancing The Stone" DVD, and was having problems finding some of the special features in Handbrake. Turns out there are three titles on the disc all called Title 20. MakeMKV identifies them as Title20#1, Title20#2, and Title20#3. I had to use Make M...

OK, gotcha. Thanks a lot, guys.

Rodeo wrote:I mean it's still technically a bug in 0.10.5, but there won't be a bugfix 0.10.x release now that we're focusing on 1.0, and it's already fixed in master.

Hi, Rodeo. What are you say is a bug? Is "-m" being removed from the High Profile?

Thanks.

JohnAStebbins wrote:Um, there is a "--no-markers" option. HandBrakeCLI --help shows it right below the -m option. Does this not work?

Thank you!! It's not in the CLIGuide, and I didn't think to use --help. I will do so next time.

Regards,
DX

Is there a way to specify "high profile," but turn off chapter marks. The High Profile includes them by default (-m), but there is no option to then turn them off (that I can see). I was hoping there was a way to do without having to replace --preset "High Profile" with all the o...

No standard desktop cooling is designed to run the CPU with x number of cores at 100% for any length of time. As others have said, that is completely wrong. Whenever I build a new rig, I run the CPU and GPU at 100% for hours as a burn-in test. NO properly built computer will overheat regardless of ...

FYI: This bug seems to have been introduced sometime after nightly "20160508174001-d61a9be". That's the latest version I have that works.

I don't see how the choice of shell would affect how HandBrake parses it's arguments.

FYI: I didn't stumble on the use of the "=" by accident. Older versions of the Windows build put the command line arguments in the queue file. It was in the file that I saw the equals sign being used.

I came searching the forum because I am having this exact same problem with the command line interface. If I specify a "--start-at" duration of more than a few seconds, it spins forever with the "searching for start time" message. Scan: [17:59:48] hb_init: starting libhb thread [...

OK, I think I've figured it out. The subtitle-burn option needed to be of the form "--subtitle-burn=2", not "--subtitle-burn 2". I believe the CLIGuide is in error.

Thanks.

Please detail your question or problem in as much detail as possible: Please tell me what I am doing wrong. I am trying to transcode a DVD title with two subtitles, and burn-in the second one. I am using these options: "--subtitle "1,3" --subtitle-burn 2". It burns in the track ...