handbrake to compress video

[Alwyn]

but i am going to try it again at 23 CRF see if thats any smaller

The smaller/lower the CRF value, the bigger your file will be. Yep, it seems @rse-about.

[jagabo]

Think of the crf value as the amount of detail that is thrown away. The higher you set it the more spacial detail you are throwing away. And the lower the quality of the resulting video.

[cholla]

@ jagabo , Which is correct ?
Per your post #5 formulas. Calculating the Stream size:
I find 3 different amounts for converting MB to Kb.
MB x 8000=kilobits per second(Kbps)
MB x 8192=kilobits per second(Kbps)
MB x 8388.608=kilobits per second(Kbps)
ffmpeg wiki says use the last one:
https://trac.ffmpeg.org/wiki/Encode/H.264

Two-Pass

Use this rate control mode if you are targeting a specific output file size, and if output quality from frame to frame is of less importance. This is best explained with an example. Your video is 10 minutes (600 seconds) long and an output of 200 MiB is desired. Since bitrate = file size / duration:

(200 MiB * 8388.608 [converts MiB to kBit; note: not 8192 as 1 kBit is always 1000 bit]) / 600 seconds = ~2796 kBit/s total bitrate
2796 - 128 kBit/s (desired audio bitrate) = 2668 kBit/s video bitrate

[jagabo]

@ jagabo , Which is correct ?
Per your post #5 formulas. Calculating the Stream size:
I find 3 different amounts for converting MB to Kb.
MB x 8000=kilobits per second(Kbps)
MB x 8192=kilobits per second(Kbps)
MB x 8388.608=kilobits per second(Kbps)

There's only a few percent difference between using Kb (1000 bits) vs. Kib (1024 bits), or using Mb (1000*1000) vs. Mib (1024*1024), so it usually not critical. If you need the accuracy you need to know what the particular tools mean by K and M. Note that some tools don't use the terms correctly. Some may use "KB" or "MB" when they are really using "KiB" or "MiB" internally. And even if you specify the the value correctly doesn't mean the tool will deliver exactly what you specified.

Note that the 8388.608 value comes from 8 * 1024 * 1024, ie 8388608 bits, 8 Mib.

[VWestlife]

The U.S. Federal Trade Commission ruled that 1 KB = 1024 bytes, so that's what I go with. But let's not get into that whole debate.

I will point out that uppercase B = bytes and lowercase b = bits. So however you define it, make sure not to confuse MB (Megabytes) with Mb (Megabits).

[Sharc]

...and 1B (1 Byte) is 8bits. Therefore the factor 8 in above conversion formulas.

[eco-by-different]

We still don't know the target file size, and we're also missing some basic information about the source video.

Is it 720p, 1080p or 4K? What are the frame rate and duration?

A 1.67 GB file can be considered either very large or very small depending on the source material. For example, a bicycle ride recorded in 4K60 is a very different compression challenge than a 1080p30 clip.

Without knowing the target size and the source video parameters, it's difficult to recommend specific HandBrake settings.

[cholla]

@ eco-by-different.
natty supplied some of the information but made me dig for it.
If it will help here is what I found:

Source: Bike-Ride-Me&Richard-23-8-2026-Dtayton-To-Norwich 1920x1080 (1920x1080), 23.35 FPS, SDR (8-bit 4:2:0,1-1-1), 1 Audio Tracks, 0 Subtitle Tracks Duration: 00:48:47

No specific target size was ever given.

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

If this helps for the math: I know I do Not always use them correctly. Like most of us I suspect.
KB (Kilobyte): Strictly means 1,000 bytes under international standards, though
operating systems historically used it to mean 1,024 bytes. SB Microsoft Dev Biogs+3
KiB (Kibibyte): Unambiguously means 1,024 bytes. It was created to stop confusion
between decimal and binary measurements, though it is rarely used in casual
conversation.
Kb (Kilobit): Means 1,000 bits.
Kib (Kibibit): Means 1,024 bits, though this exact capitalization is
uncommon.
kb / kib: Lowercase "kb" often casually means kilobits or kilobytes depending on
context, while "kib" informally refers to kibibits. Because casing matters in computing,
lowercase letters can introduce ambiguity if not paired with a clear "B" or "b".


[Attachment 93700 - Click to enlarge]

[Alwyn]

@Natty, your original video is 4900kb/sec. Set your Handbrake video tab up like this:


[Attachment 93701 - Click to enlarge]

and give it a whirl. That has the bitrate at 4000, so if the video still looks good, you can lower it some more. If the video looks bad, you'll need to increase the bitrate a little.

Also note the output file path down the bottom, and the file extension (MKV or MP4) setting.

[eco-by-different]

Try bitrate 3000 (kbps)

Audio - COPY
Resolution - COPY


[Attachment 93705 - Click to enlarge]

[Alwyn]

[QUOTeco by different]Is it 720p, 1080p or 4K? What are the frame rate and duration?[/QUOTE]
Post 20.

I don't think we should be introducing yet another app.

[natty]

Thanks all for helping me on this, But its all too hard for me to take in, so not going to bother, also like i said earlier I have a few pen drives so no problem really, sorry all for this post but i have learnt a few more things on movie clips now.

[eco-by-different]

[QUOTeco by different]Is it 720p, 1080p or 4K? What are the frame rate and duration?
Post 20.

I don't think we should be introducing yet another app.

The screenshot is only intended to illustrate the settings. There is no need to use another application. In HandBrake, change only the video setting to 1-pass average bitrate at 3000 kbps and leave all other settings as in the original.

[cholla]

I had the best results with ffmpeg cli .
Using a 2 pass encode.
I set the bitrate for 1 GB but the new encoded video was still some larger.
It went from 2.28 GB to 1.23 GB.
The quality was "acceptable" but not as good as the larger video I encoded it from.

When I used Handbrake set to Target size the encoded video was smaller 1.11 GB.
The quality was poor & unacceptable.

I could not get VidCoder to complete an encode on the video I was using for this test.
I did try VidCoder on a smaller video & it completed OK.
The results were acceptable.