AVS Forum banner
1 - 13 of 13 Posts

· Registered
Joined
·
4,582 Posts
Discussion Starter · #1 · (Edited)
Handbrake is very popular as a video encoder. It can resize a video file from a full 25-50GB down to several gigabytes. Handbrake allows you to use the built-in software or different hardware (CPUs and CPUs) to encode the video files. Depending on how fast your CPU or GPU is, it can be really quick or painfully slow. I decided to make some comparisons and share it with you.

The version of Handbrake used is 1.2.2 (2019022300). The computer used is a configured with a four-year old Intel i7-6700K on a MSi Z170A Gamer Pro motherboard with 16GB of RAM. The video cards used is the Intel 530 QSV built-in on the CPU (Note that not all CPUs have the hardware to encode videos). The other video cards are the MSi GeForce GTX 1660 Ti with 6GB DDR6 RAM and an older AMD Radeon RS560 with 4GB RAM.

Handbrake was set to Fast 1080P with video parameter set to 22. Audio was set to AAC 5.1 @ 1536 bps. The test movie was Alita, Battle Angel. The original file size was 27GB.

Setting the video quality to SHQ instead of fast can double (or more) the encoding time using HB software. The end file should be smaller with some better detail, depending on how you set the parameter. For example, the default parameter on SHQ is 18 which will make the file much larger. But the encoding time increases to a whopping 200 minutes using the default software encoder. Using the Intel QSV mode made no difference on SHQ or Fast mode, clocking at 28 minutes. Using the NVidia solution, encoding times was a smidgen longer, at 28 minutes like the Intel, two minutes longer than the NVidia default.

As you can see, using the hardware encoding was considerably faster than using Handbrake's built-in software encoder. But the disadvantage of using hardware encoding are two-fold. First, the resulting file size is larger and the video quality is impacted. TBH, the image quality is negligible IMHO, but it can be seen. The AMD has the worst image, followed by the Intel. I think the NVidia and the software HB are pretty close.

HB has the smallest file size (3.4GB), followed by NVidia (4.05GB) and AMD (4.1GB). The Intel has the largest end file size, about 4.8GB. I did notice one anomaly with the Intel file. All the other files started very quickly on my Sony BR Player (BDP-S7200) but the Intel file took several seconds before the movie started.

I am planning to repeat the test, using either an AMD Ryzen 3 3900X or an Intel i9 9900K. From what I have read, the Intel should be 100% faster than my older i7 6700K. But the AMD Ryzen 3900X is even faster, 30% faster than the Intel i9. The drawback with the AMD CPU is that it does not have any integrated graphics. The Intel i9 has a later version, QSV 630 which should be faster than my i7 6700K.

It will be interesting to see how much faster the new CPUs really are and if they make a difference on the GPU's performance.
 

Attachments

· Registered
Joined
·
4,582 Posts
Discussion Starter · #2 ·
I ended up picking up an AMD3900X CPU on a MSI Carbon Pro mobo. Running Handbrake on H.264 on Alita was about 30 minutes, faster than the Intel i7-6700 and the Intel i9-9900K which I estimated should be about 37-40 minutes... The NVidia was a tad faster than on the i7-6700, clocking in at 22 minutes, faster than the CPU only.


This shows that using a fast GPU will probably faster than any current CPU, even the highly regarded AMD 3900X. I must note that the 3900X Wraith Prism fan really ramped up when Handbrake was running. So getting a faster video card would be even faster than what I got. My only question is how fast the Intel i9 would be using QSV for encoding.
 

· Registered
Joined
·
1,092 Posts
Do you guys see the difference after re-encode 1080p bluray from 27G to several gig in size?
I'm sure the average bitrate will drop to around 10Mbps.
Honestly, maybe I need to see my eye doctor, but I can't really see the difference :(
Not sure whether my eyes have issue or HB does such a great job.
I watched newly re-encode/re-size MKV on my 22" monitor as well as on my 4K 75" TV and do not see any difference.
 

· Registered
Joined
·
4,582 Posts
Discussion Starter · #4 ·
IMHO, I cannot see much of a difference and I have a 108" screen. I downsize my videos to about 4GB in size and it looks perfectly fine. If I pause a scene and do a comparison, there is a minimal degradation in image quality, not enough to bother me.


On a side note, I exchanged my NVidia GTX1660 Ti to a NVidia RTX2070 because they had a sale for $480 (the RTX2070 Super is coming out next month). Running Handbrake with Alita in SHQ mode rips through in 35 minutes, in Fast mode, takes 10 minutes and HQ mode takes 23 minutes.



I cannot fathom how much faster a 2080 Super GPU would be... Benchmarks show the new 2080 Super to be 25% faster than the 2070...
 

· Registered
Joined
·
4,582 Posts
Discussion Starter · #5 ·
On a side note, I noticed something odd... When using the NVEnc encoder, times can be all over the map on different videos.... There are instances when encoding a 4GB video to 720P in fast mode can take only ten minutes. Another similar video can take as long as 25 minutes using the same parameters.


I am testing Ready Player One in SHQ mode using the software encoder in HandBrake, it takes 100 minutes. In fast mode, it is several times shorter... So quality levels greatly impact the encoding time..
 

· Registered
Joined
·
1,092 Posts
IMHO, I cannot see much of a difference and I have a 108" screen. I downsize my videos to about 4GB in size and it looks perfectly fine. If I pause a scene and do a comparison, there is a minimal degradation in image quality, not enough to bother me.


On a side note, I exchanged my NVidia GTX1660 Ti to a NVidia RTX2070 because they had a sale for $480 (the RTX2070 Super is coming out next month). Running Handbrake with Alita in SHQ mode rips through in 35 minutes, in Fast mode, takes 10 minutes and HQ mode takes 23 minutes.



I cannot fathom how much faster a 2080 Super GPU would be... Benchmarks show the new 2080 Super to be 25% faster than the 2070...
Thanks for your input.
I have a decent but few years old Dell PC with i5 (can't remember which gen it is) and it took normally 8 hours to complete (either x264 or x265 1080p with RF to somewhere between 18-22)
 

· Registered
Joined
·
19 Posts
On a side note, I noticed something odd... When using the NVEnc encoder, times can be all over the map on different videos.... There are instances when encoding a 4GB video to 720P in fast mode can take only ten minutes. Another similar video can take as long as 25 minutes using the same parameters.

I am testing Ready Player One in SHQ mode using the software encoder in HandBrake, it takes 100 minutes. In fast mode, it is several times shorter... So quality levels greatly impact the encoding time..
I can confirm that the time of a 4GB 720p video conversion can vary enormously.

However I do not have an option in Handbrake to encode H.265 Intel QSV only the H.264 Intel QSV is available in the menu.
I'm using Handbrake version 1.3.1 (2020010400).
 

Attachments

· Registered
Joined
·
4,582 Posts
Discussion Starter · #8 ·
Just an update... I replaced my MSi X570 MEG Gaming Pro Carbon motherboard with an ASUS X570 ROG Crosshair Hero VIII (where the heck do they come up with this name?). This motherboard has been reviewed as the crappiest AMD motherboard out there (if you are using any AMD 105-watt CPU, it is fine for lower powered AMD CPUs).

This motherboard, like ALL other MSi MEG X570 motherboards, have a extremely crappy power delivery system. The VRMs are underpowered and overheat when the CPU is in full throttle mode. The VRMs reaches a temp of 100 degrees Celsius which triggers the motherboard to throttle down the CPU to 500 MHz (from about 4.0 GHz) speed until it cools down. It will then ramp back up and again overheat which throttles down the CPU speed in an unending cycle.


Video encoding maxes out the CPU's resources so this throttling problem will always happen when using Handbrake in the software encoding mode. The new ASUS motherboard has a lot beefier power delivery design and maxes out at 50 degrees Celsius which is a lot cooler than the MSi.


On a side note. Under the filters tab, there is a Sharpen option in Handbrake. I find that enabling this makes the image a bit sharper. You can vary the degree of sharpness but I find that Light or Medium settings offers the best results. This will lengthen the encoding time a bit but I find that the image shows better detail with minimal if any of the dreaded egdge enhancement that normal sharpening filters inject. Try it out.
 

Attachments

  • Like
Reactions: G€€RT

· Registered
Joined
·
19 Posts
Just an update... I replaced my MSi X570 MEG Gaming Pro Carbon motherboard with an ASUS X570 ROG Crosshair Hero VIII (where the heck do they come up with this name?). This motherboard has been reviewed as the crappiest AMD motherboard out there (if you are using any AMD 105-watt CPU, it is fine for lower powered AMD CPUs).

This motherboard, like ALL other MSi MEG X570 motherboards, have a extremely crappy power delivery system. The VRMs are underpowered and overheat when the CPU is in full throttle mode. The VRMs reaches a temp of 100 degrees Celsius which triggers the motherboard to throttle down the CPU to 500 MHz (from about 4.0 GHz) speed until it cools down. It will then ramp back up and again overheat which throttles down the CPU speed in an unending cycle.


Video encoding maxes out the CPU's resources so this throttling problem will always happen when using Handbrake in the software encoding mode. The new ASUS motherboard has a lot beefier power delivery design and maxes out at 50 degrees Celsius which is a lot cooler than the MSi.


On a side note. Under the filters tab, there is a Sharpen option in Handbrake. I find that enabling this makes the image a bit sharper. You can vary the degree of sharpness but I find that Light or Medium settings offers the best results. This will lengthen the encoding time a bit but I find that the image shows better detail with minimal if any of the dreaded egdge enhancement that normal sharpening filters inject. Try it out.
@Jon S

Thanks for sharing.

Can you check if H.265 Intel QSV is available in the list.

If yes what Intel driver do you use?
I'm using Intel driver version 20.19.15.5126 date 21 Jan 2020.
 

· Registered
Joined
·
4,582 Posts
Discussion Starter · #10 ·
@Jon S

Can you check if H.265 Intel QSV is available in the list.

I no longer can check the Intel settings because I no longer have an Intel CPU but a 12-core AMD R9 3900x. The H.265 Intel QSV will only appear if the Intel CPU you have has the latest built-in GPU co-processor. Older Intel CPUs do not have the H.265 QSV option.
 

· Registered
Joined
·
14,494 Posts
I can confirm that the time of a 4GB 720p video conversion can vary enormously.



However I do not have an option in Handbrake to encode H.265 Intel QSV only the H.264 Intel QSV is available in the menu.

I'm using Handbrake version 1.3.1 (2020010400).
Only the newer Intel chips support H.265 HEVC encoder. I have tried it and it does work.

Sent from my Pixel 3 using Tapatalk
 

· Registered
Joined
·
19 Posts
I no longer can check the Intel settings because I no longer have an Intel CPU but a 12-core AMD R9 3900x. The H.265 Intel QSV will only appear if the Intel CPU you have has the latest built-in GPU co-processor. Older Intel CPUs do not have the H.265 QSV option.
How can I determine if my Intel CPU supports the H.265 Intel QSV Coding (not encoding because it can)

This is the CPU I use:
Intel Core i7-4790K processor (4 Cores, 8 MB cache, 4.00 GHz - 4.40 GHz)
 
1 - 13 of 13 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top