handbrake to compress video

[natty]

I have followed this tutorial on making a video size smaller but its made it a bigger size, it was at 1st 1.67 GB, but after its now 27.1GB I cannot understand it as followed the tutorial

https://www.youtube.com/watch?v=GNlqGgCQpIU

[ProWo]

I have followed this tutorial on making a video size smaller but its made it a bigger size, it was at 1st 1.67 GB, but after its now 27.1GB I cannot understand it as followed the tutorial

Set the constant quality slider to 23

[jagabo]

If you want a video of a specific size you should use Avg Bitrate encoding, not Constant Quality. To get a smaller video use a lower bitrate than the starting video.

Note that the youtube video recommends RF values from 18 to 25. But with CRF encoding the resulting file size is unpredictable (other than "the higher then number the smaller the size -- for a particular video"). You may have to go to even higher values to get a smaller file than the source.

And when using bitrate based encoding you should use the Multi-pass option for better quality.

[cholla]

The main problem is the "constant quality" .
You have it set to 2 . Ive never tried that "high" of a setting. It would be almost like a zero setting which is AKA Placebo> (Which no one recommends).
Try 18 to 22.
Set the "Encoder Preset" to slow or very slow.

For Frame Rate:
I would recommend "Same as source".
Variable frame rate should be some smaller but may create some problems.
For example on higher motion scenes. Can also create Audio sync problems.

jagabo's recommendation is also good but it may take a couple of tries on the size to get what you want.
Meaning if set too small you may not like the quality.

For either my preference is .mkv .
Also the Encoder Profile set to High is usually OK.
The Encoder level set to "Auto" may not be correct.
This is if you have an older set top BD or other player . Try 4.0 or 4.1 .

[jagabo]

x264's RF=0 is lossless encoding. As with all other lossless encoders the file will be very large. The RF=2 setting the OP used is very close to lossless and will also deliver very large files. Around RF=18 is nearly visually lossless at normal playback speed on most material.

But if the OP wants a guaranteed file size he should use bitrate based encoding because the definition of bitrate is:

bitrate = stream size / running time

So:

stream size = running time * bitrate

Half the bitrate will deliver half the size of the video stream.

[natty]

Thanks all for your help, but i am afraid all this is too much for my little brain lol. I am not into doing all this. but its not a big problem, as I have plenty of space on pen drives. I did try a few ways got video smaller size but then the quality was terrible

[cholla]

Thanks all for your help, but i am afraid all this is too much for my little brain lol.

If you are still interested.

All you need to do is use these settings in Handbrake:

[Attachment 93662 - Click to enlarge]

I just used aac pasthrough because the audio was already compressed enough.
If you have a large bit audio you can also compress it to get a smaller size.

[Attachment 93663 - Click to enlarge]

I do not know if this will be enough compression for you.

The Video used 2.28 GB
The compressed video is 1.48 GB

[eco-by-different]

The first question should be: what file size are you trying to achieve?

If your goal is around 100 MB for a 40-60 minute video, then RF-based encoding is not the best starting point because file size becomes unpredictable. In that case a bitrate or target-size workflow makes more sense.

For example:

100 MB/40-60min: expect heavy downscaling (e.g. ~576x320), denoising, low bitrate audio and aggressive compression.
300-400 MB/hour: a much more balanced approach would be around qHD resolution (960x540), light denoising such as RemoveGrain(2), AAC-LC 96 kbps audio and x264 slow/veryslow.

The required workflow depends entirely on the size budget. There is no single "best" HandBrake setting.

[natty]

Thanks all for your help, but i am afraid all this is too much for my little brain lol.

If you are still interested.

All you need to do is use these settings in Handbrake:

[Attachment 93662 - Click to enlarge]

I just used aac pasthrough because the audio was already compressed enough.
If you have a large bit audio you can also compress it to get a smaller size.

[Attachment 93663 - Click to enlarge]

I do not know if this will be enough compression for you.

The Video used 2.28 GB
The compressed video is 1.48 GB

Ok I will give it a try and let you know, my clip is 1.67GB so lets see if it makes it smaller and ok to view still, You must have a different version of handbrake as its not like mine version 1.11.2 the latest


Well tried your settings .mkv not mp4 and it went from 1.67GB to 3.29GB so not shrunk clip at all

[natty]

The first question should be: what file size are you trying to achieve?

If your goal is around 100 MB for a 40-60 minute video, then RF-based encoding is not the best starting point because file size becomes unpredictable. In that case a bitrate or target-size workflow makes more sense.

For example:

100 MB/40-60min: expect heavy downscaling (e.g. ~576x320), denoising, low bitrate audio and aggressive compression.
300-400 MB/hour: a much more balanced approach would be around qHD resolution (960x540), light denoising such as RemoveGrain(2), AAC-LC 96 kbps audio and x264 slow/veryslow.

The required workflow depends entirely on the size budget. There is no single "best" HandBrake setting.

Well not any particular size just a bit smaller size than 1.67GB

[jagabo]

When you use RF based encoding you don't know if the resulting video will be larger or smaller than your source. Use MediaInfo to determine the video bitrate of your source. Then use multipass bitrate based encoding at a lower bitrate.

Get rid of all those x264 command line options unless you have some hardware requirement for them. And use a slower preset -- the slower the preset, the better the quality. I recommend "slow" for standard definition video, "medium" for high def video.

Basically, with RF based encoding your are specifying the quality (relative to the source) but you don't know the size. With Bitrate based encoding you know the size of the resulting video but not the quality.

[cholla]

You must have a different version of handbrake as its not like mine version 1.11.2 the latest

I'm certain I have a different version of Handbrake.

Well tried your settings .mkv not mp4 and it went from 1.67GB to 3.29GB so not shrunk clip at all

The settings should still work the same.
This is where a MediaInfo would help. To see where the gain in size is.

Since you tried the settings i suggested with RF & they did not work for you .
Try the method suggested by jagabo.
To make it clear these are the "x264 command line options" he says to get rid of:

[Attachment 93667 - Click to enlarge]

[jagabo]

The fact that the OP's original video is 1.67 GB and a near lossless reencoding resulted in 27.1 GB indicates the video is already highly compressed. Recompressing at CRF=22 wasn't likely to make it smaller. Especially with the Advanced Options he was using -- most of which were going to increase the file size.

[eco-by-different]

Jagabo is right.


Use Average Bitrate in a single pass. For a 1 GB target, calculate 1000 × 8000 / duration in seconds, then subtract the audio bitrate.

Enter the result as the video bitrate and use x264 slow.

The final size should be close to 1 GB.

[cholla]

The calculations should be based on 1024 instead of 1000.
1 GB = 1024 MB = 1048576 KB
1048576 KB x 8 = 8388608 kbps
8388608 kbps ÷ duration in seconds

If you need to subtract the Audio stream size because you want a more exact video stream size.
Then the Audio stream size should be subtracted from the total stream size.
Then use the math above.

I believe for the OP's video since I do not have the Audio stream size.

This should be the math for a 1 GB stream size of the OP's video:
8388608 kbps ÷ 2908 = 2884.6657 (kilobits per second) .
Rounding this up or down should not make much difference.

[davexnet]

Or you could just use Vidcoder, a Handbrake clone, which offers something Handbrake doesn't.
Instead of having to calculate bit rates, just enter your target size, and the program will work it all out