Have been playing with Handbrake. Thank you for suggestion. Wondering if you can offer more advice. Am testing encoding some recent unhoards. For example a 4K, 60fps, 16000kbps file. Encoding to 1080p, is it important to keep it at 60fps or is 30fps preferred/standard?
Should I maintain the original bitrate? If not, what CR value or what bitrate should I enter manually? I've made a number of test encodes, and they all look good to me with various file sizes (I dont have trained eyes however). I want to make the most "ideal" 1080p encode to maintain as much quality as possible but also reasonable, so that I can provide 1080p versions to people here. Using h264 and mp4 file type. Appreciate any insight.
1. Yes it's important to keep original 60fps (or 50fps if the original is just such, that's for European cameras), this 2 times higher HFR is much more smooth to look for eye. Especially when there's a lot of moving scenes in video. Also, when re-encoding down to 30fps (or 25fps) there's often flickering appearing in moving scenes if you do not apply special smoothering tools.
2. No, you do not need to maintain the original bitrate, which is given for 4K there. In theory you can lower the bitrate 4 times here, but in practice please still do not lower so much. In example YouTube re-encodes 1080p60 videos at 6000kbps (this is for H264 version, the same VP9 version has lower bitrate) but sometimes even it isn't sufficient (depends on the source video real quality and objects and movings nature there). I recommend to use variable bitrate (VBR) H264 encoding with setting maximum bitrate at something like 12000 but average bitrate at something like 8000 (or 6000). Again these values depend a lot on the real visual quality of the original source video.
Note: As we know there's also H265 encoding existing which ensures much smaller filesize, but I personally do not like its results, it looks still too much compressed for me, with several areas oversmoothened or some areas with more artefacts visible.
Looks like the video software you used takes the proposed peak bitrate value just as an average bitrate value. As a result you got a video with an average bitrate 10000kbps now. The video file size shows also just the same ratio (the file size always changes just the same like the average bitrate change). Confirmed by a simple math:
12000/16000=~0.75
930MB/1.2GB=~0.76
10000/16000=~0.62
745MB/1.2GB=~0.61
I downloaded your result video now, too. Visual quality is true excellent, also the 60fps really gives to all object moves unique enjoyable smooth feeling, so this is very appreciated! The video tech characteristics analyzer shows also the average video bitrate as 10005kbps, so it really must be your encoding software took this value 10000 for average (or constant) bitrate.
But no problem... So I think you can now safely lower this value even more, instead 10000kbps put there 8000kbps or even 6000kbps (this 6000 will then be exactly equal to YouTube 1080p60 quality). The file size will become also smaller just by the same margin then (for 8000kbps ~600MB, for 6000kbps ~460MB).
I recommend you to do now also the 6000kbps test with just the same video (all other encoding settings let the same) and upload this also. Then we can download this one too, and compare the quality change with the 10000kbps version you just produced.
BTW, The best timestamps to make quality comparisons in this video are at 6:08 and 8:45 where camera is focusing on the net-fabric string panties frontals in close-up frames. Just to see if these tiny seethrough-net cells are all clearly visible every one of them, without any artefacts. Additionally, approximately at the same timestamps, there's also dark pussy hair stubble (out of the string panties edges), which is another good video quality detecting object here, too.
Although, throughout almost all this video there's some repeating camera focus off-drifting moments. This is of course videographer's failure and we can do nothing with repairing it. But it must be taken into account when visually comparing the video quality, not to pause video frames on these blurred moments there.
0 comments:
Post a Comment