HandBrake

Each title of on a disc (represented by the title dropdown in HandBrake), would need to be encoded into a separate file. You can't putan entire Bluray into an MP4 file.

see https://handbrake.fr/docs/en/1.2.0/advanced/queue.html if you wish to queue up multiple jobs

What is the name of the file you downloaded? Sounds like you may have downloaded HandBrakeCLI (which is a Command line app, not an installer)

This is correct. If you use QSV Decode currently, we have all filters disabled. There is work TBD to complete the zero-copy implementation that's not in yet that is required to allow re-enable of filters.

There is no option to change this. Your creating a "new" file that's different from the source, so the file created dates will be the encoded time. You can potentially write a script to do and have this run using the "When done" option in preferences. You'd probably need the source/destination filen...

HandBrakes pipeline is still 8bit, so you can't maintain true HDR output yet.

The primary vendor must be the computer (or video card) manufacturer. If they are f**king up, they need to know it.

They know, they don't care and currently have no reason to care. They have your money.

Could be literally be one of a hundred things. You can't tell from this log.
Since it happened on the subtitle pass, it's pretty much irrelevant in this case.

Your OEM Nividia drivers, are from Nvidia so there should be no issue there. As always, there is a risk of problems with driver updates, but given the trend for OEMs providing out-of-date, broken, or stripped down drivers i'd always go towards the primary vendor as a first call, and only fallback to...

I'd maybe hold off until the 16-core comes out until we cans see some reviews for it. While it will depend on your settings/source resolution etc, I would expect that reasonable settings (with few/no filters) should scale to 16 cores fine assuming a bottleneck doesn't show up. It doesn't look like I...

Either is fine. Performance will be the same.

ffmpeg, potentially. The different encoders potentially. There are many factors that affect core count scaling. (Including decode, source content resolution, settings used, filters used etc. It's complicated is the best answer.) A more human readable expectation on performance can be read here: http...

Thread Locked, OP is spam user.

What your trying to do, isn't supported I'ma afraid. There isn't an upgrade path available for the older format.

You managed to post in the archived section of the forum (Something I've now fixed the permissions to prevent). Please take note of the header that states we are using GitHub for feature releases. Finally, I'd note, HandBrake is at currently at version 1.2.2 so it sounds like your using a version of...

Maybe try a forum like Neowin if you want good hardware recommendations for games.

This forum is for HandBrake support.

The log indicates it didn't crash, it simply failed the encode due to invalid settings. The GTX 730 does not support H.265. We have an open ticket to hide the encoder option when it's not supported: https://github.com/HandBrake/HandBrake/issues/1666 Officially we only formally support 1050+, 1650+ a...

HandBrake makes no connections to Amazon. We have no infrastructure there.

Are you sure it's the HandBrake process and not something else making the connections?
Where did you get this build of HandBrake from?

Sorry, I wasn't clear. The nightly and release versions have independent settings storage. Changes to one won't impact the other. Copying settings between manually is not supported and could lead to issues. If you've never installed a nightly before, only once, it'll try import a previous versions s...

Nightly runs independently from the release build so no settings or presets will copy over. The .NET error comes from Microsoft. Not sure why it would double up but not much we can do about it. If you get a white error window again, try press ctrl-c and see if you can get a stack trace from it and r...

ffmpeg cli master encoded, but the output video didn't playback in vlc.

I didn't check if their windows builds were actually up-to-date though, so maybe it's lagging behind.

Intel i7 8700K with GTX 1060 - HQ 720p30 - Change x264 Encoder preset to SuperFast: Around 740fps average. - Turn off Decomb / Interlace Detection. (Possible if your source isn't interlaced) Around 1200 fps average. - Switch to NVEnc (Slow Preset) Around 2000fps average To give you some ideas. Even ...

If you change the setting, then change back after setting to English, it should resolve it.

Otherwise, it's fixed in the nightly builds. There were language related issues with the wrong value being stored for the setting.

Not with HandBrake

Something like MkvMerge might do that for you.

This thread has clearly gone off track and frankly, I don't understand what y'al talking about so I'm going to lock it.

Test results: - ffmpeg 4.1.4 -> Can't read file Duration: 00:00:02.88, start: 0.000000, bitrate: 115387 kb/s Stream #0:0: Video: none, none(progressive), 3840x2160, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 25 tbc - VLC -> Can't read file - ffmpeg master -> Seems to recognise the file now, and will ...