- looping is solved and convenient to configure
- it can be cross media barriers (copied into a text, copied into an e-mail, etc.)
- it pleases the bandwidth gods (are gifs usually smaller? i know that they have a limited color palette)
161–170 of 327 posts
- looping is solved and convenient to configure
- it can be cross media barriers (copied into a text, copied into an e-mail, etc.)
- it pleases the bandwidth gods (are gifs usually smaller? i know that they have a limited color palette)
The most important part of GIFs for me is that they behave like images in browsers. They are always auto-playing with no concept of play and pause. You can drag and drop them from a browser to your desktop to save them. You can save an entire page and have all the image files save with it. I've never had this work for webm or other video formats. You could even argue that GIFs not being a video with no video decoding…
At this point, killing GIF is a UX problem, not a format problem. I've talked about this before [0], but the big problem for me is that video is just difficult as hell. Compared to a GIF, it is just that much harder to save a video on a phone, and then upload it the same way as an image. Try to save a "GIF" from Twitter or from GIPHY - it's a /huge/ pain. Whatever the GIF killer is will need to pass the right click t…
1. Similar looping behavior 2. No audio 3. Can be put in an tag
You should be able to save the file like you would a gif, and viewers should also show it as they would a gif (not a video).
And yes, I know websites can send subtitles separately then render the subtitles over the element, but that's no excuse for an ostensibly modern media container to not support subtitle tracks.
The most important part of GIFs for me is that they behave like images in browsers. They are always auto-playing with no concept of play and pause. You can drag and drop them from a browser to your desktop to save them. You can save an entire page and have all the image files save with it. I've never had this work for webm or other video formats. You could even argue that GIFs not being a video with no video decoding…
I had to turn off GIFs and animated emoticons in Slack because it was making my fan spin up and consuming a significant amount of CPU.
Earlier quoted context omitted.
Yes. Just one problem I discovered recently is that no other format does looping properly. With a GIF, you can right-click and save it, and all the looping info is inside the file. The quality is crappy, but it just works. With all “proper” video formats, looping info is metadata, stored separately. You can’t even go for something slightly more modern, animated PNGs, because there are warring formats and very few too…
Looping is up to the video player, not the format or container. What "video formats" have looping as metadata? Gifs only have a loop flag so static images can be displayed instead of looped indefinitely as video.
The Internet has voted in favor of looping, "GIF-like" moving images. Platforms try to emulate this with proprietary video players. Some have sound (wanted or not), some of the video players prohibit copying, and none of the files work as simply as GIF for sharing.
We need something more modern than GIF, but that has playability baked in. Something that browsers treat as a moving image and not a video.
At this point, killing GIF is a UX problem, not a format problem. I've talked about this before [0], but the big problem for me is that video is just difficult as hell. Compared to a GIF, it is just that much harder to save a video on a phone, and then upload it the same way as an image. Try to save a "GIF" from Twitter or from GIPHY - it's a /huge/ pain. Whatever the GIF killer is will need to pass the right click t…
Earlier quoted context omitted.
Challenge accepted. https://www.hampsterdance.com/classics/originaldance.htm Just did it on my 2011 MacBook Air. Pushes all four cores up... about 15%.
For best results, use a Slack channel, or a forum reply page with an array of animated smileys.
Calling AV1 something that looks almost exactly like AVI seems like a mistake...
The most important part of GIFs for me is that they behave like images in browsers. They are always auto-playing with no concept of play and pause. You can drag and drop them from a browser to your desktop to save them. You can save an entire page and have all the image files save with it. I've never had this work for webm or other video formats. You could even argue that GIFs not being a video with no video decoding…
> It may take longer to load, but I can have 100+ GIFs playing at once with no impact to my CPU. I don't know what you're talking about really... I was just using Google Slides today and both Firefox and Chrome went to 250% CPU usage, only because there was one slide with a 5 seconds full screen recording GIF. I begged to the person who added it to turn that to a video.