HandBrake

Everyone has moved away from CUDA to dedicated hardware for de/encoders so no, it's no longer viable.

minoush82, setting a pause won't help with cooling problems. A fully loaded CPU will saturate, sometimes within second, if not a low number of minutes on marginal cooling so the pauses are indifferent. Going though heat and cool cycles may actually be worse for the processor as your putting a differ...

If the same file works on one, but not the other, then your likely having some kind of filesystem level IO issue. It's fairly unlikely that Windows is causing HandBrake to behave differently here.

Shouldn't see any real difference in performance.

We don't support it for Nvidia. Hardware decoding in general proved to be too unreliable to support. With your system, you'd still end up bottlenecking the card regardless. as A/V Sync processing, audio, any filtering is all done on the CPU and the pipeline going through system memory would bottlene...

Your CPU is heavily bottlenecking the GPU. This is expected for your setup. Remember, only video encoding here is on the GPU. everything else is bound by the slow CPU.

If you don't need it, turn off Decomb on the filters tab. That'll gain you a few extra fps.

Assuming they've not released another busted driver (they do from time to time), the only other thing I can think of is you got a "SafeMode" version from Github or some site other than HandBrake.fr where it's not compiled with nvenc support.

1. Intel QuickSync requires Intel onboard graphics to be enabled. It's not on your system. Likely disabled in the BIOS.
2. For nvenc, make sure it's enabled in preferences -> video.

48, 24, 16, 12 and 8 are valid options for Opus.

The UI is simply showing a few invalid options and opus appears to be sanitising to the nearest valid option.

Please report it to Nvidia.

There are options in the Nvidia control panel to disable Gsync for specific applications that you can also set to avoid this in the mean time.

5 is file read error. Typically path, permissions, storage errors would trigger it.

It might be related to a lost frame somewhere in that encode or bad source metadata

Your hardware is too old. H.265 is only available on Skylake and newer CPU's (6th Generation +)

Nightly build, and CLI only for windows right now.

The audio controls on the behaviour screen relate to the "fallback" encoder, should the passthrough option you select turn out not to be possible. There is no way to guarantee passthru. If you select auto-passthru, it'll passthru if a) the output container supports it. b) the source format...

There is no need to tweak advanced options.

If you want higher quality, adjust the quality slider and accept files will get larger as a result.

no.

There is no error. The job you ran was successful.

Your previous job either errored or you cancelled it.

Read it more carefully. It says Errors or Cancellations. See the queue window. It'll tell you which job is being flagged.

HandBrake is a hobby, not a business. There is no legal entity, no staff therefore no costs.

Just a bunch of hobbyist developers putting free time into it.

HandBrake doesn't support downloading video from YouTube.

If I was in your place, I'd be using x264 rather than 5, purely because of your system specs. if you had a newer system I might be more inclined to go 5 That said, you gotta work with what you have so I'd make note of the suggestions I made above to speed things up a bit and really it'll be down to ...

I can tell you without looking at your next log, that this is normal and expected behaviour. Your basically asking it to do a high resolution encode, with very slow settings on an ultra slow CPU. Your not even going to hit 1fps encode rate on that CPU so even showing progress will take an extremely ...

@rollin_eng your confusing posts / people here. He has *no* issues. Since he has said patch, without problem, he's suggesting that it might be a patch installation failure issue rather than a patch content problem.

Not quite weekly no.

Development is pretty slow these days so it's somewhat irrelevant anyway.

Was nightly. They are no longer nightly. The nightly build platform was shutdown a while ago.

Back to snapshots again which are mostly random but usually 2~3 weeks unless something bigger happens. When GitHub fixes a few API problems, we'll hopefully go back to nightly again in the future.