I'm converting two videos to x264 MKV file with Handbrake. First video is in 4:3 format and has black bars on the left and right side. So I used "Automatic" cropping which cropped it to 1440x1080. The other is 16:9 so the resulting video is 1920x1080. However, both resulting videos have roughly the same filesizes (bitrate is the same, see below). Shouldn't the first one be smaller since the resolution is lower? How does that work?
I have the following set in Handbrake:
Codec: H.264 (x264)
Framerate (FPS): Same as source
Variable framerate
x264 Preset: Fast
x264 Tune: Animation
H.264 Profile: High
H.264 Level: 4.2
Avg Bitrate (kbps): 2900
2-Pass Encoding
+ Reply to Thread
Results 1 to 13 of 13
-
-
You used the same Avg. Bitrate. That's what you got.
size=bitrate x running time -
I forgot to mention, the videos have the same duration. I still don't understand how they're the same size if the (average) bitrate is the same but the ammount of pixels differs significantly between them. Does that mean the first one (with fewer pixels) is of better visual quality than the second one (meaning less blocking, etc) ?
-
-
The file won't play on your tv/media device if it's not uhd since it's set to H.264 Level: 4.2,if just on your computer then there won't be any issues.
I think,therefore i am a hamster. -
-
-
The definition of bitrate is:
Code:bitrate = stream_size / running_time
Rearranging the equation gives:
Code:stream_size = bitrate * running_time
But different videos require different bitrates in order to retain quality. Different frame sizes, frame rates, the amount of action, the amount of film grain, the sharpness, even the brightness of the picture, will change the amount of bitrate you need.Last edited by jagabo; 2nd Nov 2020 at 07:50.
-
So if I use the average bitrate setting to encode a 720p and a 1080p animation video of the same duration, the resulting filesize will be approximately the same? Does that mean the quality of the 720p video would be "higher" (meaning, there would be a higher chance of seeing potential compression artifacts in the 1080p video compared to the 720p one) ?
I guess I would like all the videos I encode to have the same overall quality. That means I would expect shorter videos to be smaller and lower resolutions ones to be smaller as well. Did I go the wrong route with the average bitrate then? Should I have chosen Constant Quality (RF) ? But then I guess that would mean high-paced / complex scenes would be blocky, wouldn't it?
This is really confusing me. I'm not really into encoding videos so I guess that's why.
BTW, I didn't know about the level 4.2 limitations. I just Googled it and decided on it based on the supported resolution (1920x1080). But I went and copied the video onto a portable hard drive, plugged it into the USB port on a Full-HD LG smart TV model 43LF630V-ZA, selected the attached storage menu via TV OSD, navigated to the file, and the video played fine.Last edited by Perplexer; 2nd Nov 2020 at 09:27.
-
Yes.
All else being equal, yes. But it really depends on the nature of the two videos. There an easily be a several fold difference in bitrate requirement between different videos of the same frame size.
Yes. If you encode all your videos at very high bitrates they may all look good but you would have wasted a lot of bitrate on the videos that didn't really need it. If you encode them all at a very low bitrate a few might look ok but others will look terrible.
Yes.
No. The encoder will use more bitrate where it's needed, less where it's not. This is why constant quality encoding was invented. -
Ah, I misread what I myself wrote. It's "Constant Quality" and not "Constant Bitrate", ok. So then Constant Quality still is not constant bitrate ? If it means the encoder will use more bitrate where it's needed, that makes it variable bitrate then. But isn't that what "Average Bitrate" is also ? Or how does Average Bitrate option work then? I see only Average Bitrate has the checkbox for 2-pass encoding. MediaInfo reports 2900 in my case for all files encoded with this option. I'm wondering, is there an option that would just use a constant/fixed bitrate throughout the file, regardless of the scenes ?
-
With constant quality encoding you are picking the quality you want. The encoder uses whatever bitrate is necessary to deliver that quality. You don't know what the final file size will be.
With average bitrate you are picking the file size. The encoder delivers whatever quality it can for that file size. You don't know exactly what that quality will be.
With bitrate based encoding you get the best quality with two (or more) passes. During the first pass the encoder analyzes the video. During the second (and optional later passes) it allocates bits optimally to each scene.
When average bitrate is done with a single pass the encoder has no idea what's coming later in the video. So it can't allocate bits optimally.
If you preform a CRF encoding and it results in a particular average bitrate, then encode the source again (2-pass) with that same average bitrate, the quality of the two videos will be nearly identical.
So the decision is simple: If you have a size constraint (4.3 GiB on a DVD for example) use 2-pass VBR encoding. If you don't have a size constraint use CRF encoding.Last edited by jagabo; 2nd Nov 2020 at 11:59.
Similar Threads
-
Handbrake: Simply need to change video resolution
By WannaBeAVideoGuy in forum Video ConversionReplies: 6Last Post: 1st Dec 2019, 08:44 -
DVDFab, TMPGEnc Video Mastering Works 7, or Handbrake to X264/X265
By magnu in forum Video ConversionReplies: 3Last Post: 27th Jun 2019, 10:42 -
[handbrake] x265 sometimes freezes when navigating video, x264 doesn't
By 2zv7m53cc3 in forum Software PlayingReplies: 3Last Post: 20th Dec 2017, 10:46 -
x264vwf filesize (H264 rendering KBPS and filesize insane)
By Joris Ceoen in forum EditingReplies: 11Last Post: 2nd Apr 2017, 09:49 -
iTunes HD vs Handbrake x264 RF20
By hogger129 in forum Video ConversionReplies: 1Last Post: 27th Apr 2016, 11:47