Description
Tweet by @Fruit_Cock
Holding him tight, no squirming allowedπ¦π https://t.co/v4ieCk3Muw
Converted using FFmpeg: -c:v libvpx-vp9 -pix_fmt yuv420p -b:a 192k -b:v 2000k -minrate 1500k -maxrate 2500k -crf 16 -quality good -speed 4 -pass 2
Raishu
Memberis the audio broken?
Piano0000000
Memberflagging cause it sounds like the audio is corrupted
Mairo
JanitorWhenever I see these I just always question so many things.
Like why use 192kbps audio? Source is 128kbps AAC and Opus will not sound almost any differend from 160kbps upwards with this kind of source.
Also it's 7 second clip, why force 2mbps bitrate with lower and upper bounds when you can literally only use CRF and it will adjust the bitrate however it's needed.
Constrained doesn't even make sense on longer videos, because then you can just adjust bitrate and it will distribute it depending on scene complexity with two pass.
Only reason to use constrained quality is if you have twenty videos and you want to limit that CRF doesn't make bitrate skyrocket with some of the videos all of a sudden.
Audio is identical to source, so it was like this at some earlier stage already.
As the video itself is fine I don't think audio warrants deletion in this case.
Also this is like 7 second teaser from longer animation, I don't know why to upload this here, artist seems to upload bit longer teasers themselves and then free full release is most likely also higher quality than π upload (they seem to subscribe to π premium so bitrate and resolution are higher, but it's still full of macroblocking).
Their next tweet teaser is already essentially same, with longer amount of actual content.
https://x.com/Fruit_Cock/status/1839887913175179481
https://video.twimg.com/ext_tw_video/1839887716692983808/pu/vid/avc1/1920x1080/goZINO4TYJxSmJng.mp4?tag=14
Login to respond Β»