HandBrake

AMF is just the framework name for VCN/VCE

Nothing you've listed is a problem. If your distributing HandBrake, as long as you provide source, including any modifications, on request and including all the origional copyrights, your fine. It doesn't matter so much if you don't include with the binary. As long as it's available. Screenshots are...

There is an msbuild script "Build.xml" with instructions embedded. That build, just embeds the .NET dll's in the main binary. Note. hb.dll is still required and must be built under WSL or Linux Alternatively, there are snapshot builds of the main branch that you can download from https://g...

Error code 1 = User Cancelled. (Probably to generate that log)

Reinstall .NET **Desktop** Runtime 6 https://dotnet.microsoft.com/en-us/down ... -installer and see if that helps

Last I heard, they don't consider it a bug in MediaInfo either.

They see the single frame jitter that a 90khz clock causes as VFR.

I'm not sure if there are any good resources that explain this in plain English but you could start here. https://en.wikipedia.org/wiki/Presentation_timestamp

HandBrake doesn't yet support the Nvidia AV1 encoder.

The GTX1080 does not have the required hardware for AV1 encoding either. It's only available on the RTX 40-series.

Your output is Constant. Media Info will incorrectly sometimes report HandBrake CFR as VBR due to the 90khz timebase.
The output file is fine.

h264, not x264 You don't. The hardware on the PI is not supported in HandBrake. We don't officially support ARM on linux either although it (mostly, but not fully) seems to unofficially work. Lastly, in the more bad news department, the official debian / ubuntu builds of HandBrake are on our ban lis...

Your CPU is no longer supported. You'll need to use 1.5.1 or earlier with that CPU if you want to use QuickSync

If you prefer smaller file sizes, use the software encoders instead.

Nope. The hardware is closed to changes.

Nvidia has a "single frame level" sort of "2pass" which HB enables by default in the background but it's just not the same as what x264/5 do for example.

Yoli. There is infact an error message but that can only work if your system doesn't have a corrupted install of .NET already on it.

Unfortunately you and a few other seem to have had a pre-existing broken install on the system. There isn't much we can do about that.

I suspect the older MacPro will probably lack hardware encoding. Even if it does, it'll be very early hardware encoder and not worth using.

Just a note that the behaviours window will show the bitrate and other controls beside the passthru option and these get applied to the fallback encoder should it be needed.

The issue you link to is not a HandBrake Bug. It's a confirmed system issue so there is no fix coming for it.

If you want support, maybe try some of the suggestions.

It's a bug. It will be corrected with 1.6.1 or you can use a development snapshot in the meantime if you wish.
https://github.com/HandBrake/HandBrake-snapshots

An upstream library changed in it's behaviour and broke the Open Dvd/bluray options. It's been fixed for the upcoming 1.6.1 so those buttons work again.

Use Folder -> Select the VIDEO_TS folder

Rather than using the drivers that show up on the source panel. It should then scan

It's an indication that your breaching an attribute of the level. We'd need to see teh full log to say what exactly but you'll probably have to use 5 or 5.1 for this source.

Start Menu -> Windows Event Viewer -> Windows Logs (left side), then Application. Start the app, then refresh it. You should get an error here. Also, make sure all GPU drivers are fully up to date and re-install .NET Desktop Runtime 6 (https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/run...

Your out of luck then I'm afraid.

1.6.0 requires a newer driver due to the newer Intel SDK we use. If acer are not providing that and you can't use the Intel one, your next best option is to rollback to 1.5.1

Upgrade your graphics driver to the latest.

Select the Video_TS folder in folder mode and it should scan fine.

Note, any copy protected discs will ofcourse not work, same as 1.5. You'll need to use 3rd party tools for those.

There was nothing stopping you having rivatuner / afterburner installed. You just couldn't run both HandBrake and them at the same time. The cause was the way they hook the operating system, was causing breakage in a way that could not be worked around. As long as there weren't running, or in the tr...

NVEnc is not a GPU Encoder. It's a hardware encoder that happens to be on the GPU so depending on how your monitoring the card, little activity is normal. It's the encode engine that's active with very little activity on the GPU cores. It's likely your heavily decode bottlenecked here. There isn't a...