this post was submitted on 28 Jul 2023
124 points (94.3% liked)
Lemmy
12524 readers
10 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No video is fantastic method to minimise bandwidth usage and strain. Video astronomically scales up in file size compared to anything else, with audio (64kbps OPUS) and images (80% quality JPEGs or WEBMs or GIFs) being orders of magnitude smaller.
GIFs are way bigger for the same length vs video because they're basically just a series of full images, whereas videos include the diff between frames.
But the rest is absolutely correct.
Incorrect, GIFs have a lot less frames than 24/30/60 frames per second, and are usually 4-8x smaller than 1080p video resolution. In case you are referring to the smart frame-based compression in videos with H.265/AV1, those cannot be embedded into webpages to be played the way GIFs can be treated like JPGs. The web still relies on H.264 for video embedding due to its decent compression and no decoding effect on battery life of any device, no matter a Pi, phone or laptop.
Yeah, videos don't have that repeating effect that GIFs do, but if you don't need that (and I personally find that annoying), H.264 videos are smaller and can have much higher frame rate. So H.264 video should be preferred unless there's a specific reason to use GIFs
@sugar_in_your_tea @TheAnonymouseJoker personally I think web players should just auto repeat videos if they're under like 8 seconds
Could calculate battery life effect of showing GIFs versus playing/autolooping H.264 videos, perhaps. GIFs will win any day.