Here is source material if you want to try for better.

I can't do better, tried with GIF to no avail. Is there a good APNG encoder/workflow these days? Most of the APNGs I made were bigger than the GIFs and not necessarily better quality, and then I accidentally ruined them running optipng and stripping metadata.

I dunno. I tried it once some years ago when it was posted on the KC and then lost interest.

I just use some website called ezgif to do it

>>25500893 >webp Forgot about that. Why does KC allow animated webp thumbnails but not larger animated webps?

>>25500903 Because Helmut didn't like it, if you want animated webps they need to be under 25kb and 200x200 or smaller iirc.

Stop posting Hitler, it's obscene.

>>25500884 I scaled down frames with gimp and then generated apng with ffmpeg. I do not know if there is a better way to compress frames so that output can be larger size or higher quality. I have never used such program as imagemagick and I do not know if it works better. >metadata I stripped metadata with exiftool. `` exiftool -all= kotler.png ``` It does lower file size slightly.

>>25500911 Especially when Germans have just rejected nazism and committed themselves to high immigration forever. It's very distasteful.

>>25500903 That's because it doesn't need to generate a new thumbnail if the webp is <200x200px, it just embeds the original file directly. >>25500910 It's not that he doesn't like it, generating animated thumbnails for every webp/gif/apng above that size would use a lot of resources needlessly. I see why he disabled it.

>>25500903 This is so much better!

>>25500912 You have to reduce the amount of colours n shit >>25500916 he disabled larger animated webps entirely, but not gifs even though it doesn’t generate an animated thumbnail anyway

>>25500912 APNG is a hack on top of regular PNG that uses metadata fields to store frames. If you strip metadata with a program that doesn't handle APNGs specially like optipng, it removes all the frames except the first. When APNG came out, I made a few animations, but then accidentally destroyed them in this way. This file is one example, but at least I also made a GIF version of it and the original was already 256-color so I can restore it. One big issue with APNG is that it doesn't have a good encoder, the format should be capable of creating images a lot smaller than GIF, but all the encoders I know just assemble separate PNGs without any inter-frame optimizations.

>>25500912 APNG is a hack on top of regular PNG that uses metadata fields to store frames. If you strip metadata with a program that doesn't handle APNGs specially like optipng, it removes all the frames except the first. When APNG came out, I made a few animations, but then accidentally destroyed them in this way. This file is one example, but at least I also made a GIF version of it and the original was already 256-color so I can restore it. One big issue with APNG is that it doesn't have a good encoder, the format should be capable of creating images a lot smaller than GIF, but all the encoders I know just assemble separate PNGs without any inter-frame optimizations.

>>25500893 These are really nice. >>25500924 >You have to reduce the amount of colours n shit I have no experience in this :\ >>25500934 >APNG is a hack on top of regular PNG that uses metadata fields to store frames. If you strip metadata with a program that doesn't handle APNGs specially like optipng, it removes all the frames except the first. When APNG came out, I made a few animations, but then accidentally destroyed them in this way. I did not know this. APNG must be compatible with exiftool then. >One big issue with APNG is that it doesn't have a good encoder, the format should be capable of creating images a lot smaller than GIF, but all the encoders I know just assemble separate PNGs without any inter-frame optimizations. I do not know which encoder I am using. I have been using

ffmpeg -r 5 -i test%02d.jpg -plays 0 -vf setpts=PTS-STARTPTS -f apng final.png

>>25500944 That's the ffmpeg encoder, usually apngasm is slightly better because the ffmpeg encoder just encodes each frame to PNG using ffmpeg's PNG encoder which sucks, while you can feed frames that you ran through a PNG optimizer to apngasm and it'll use them unchanged. And if you need to reduce color depth to 256 colors to reduce filesize, use pngquant which is better than other quantizers. Most tools for manipulating APNGs were abandoned right after the format came out because it got 0 adoption, so although the format has potential, it has never been realized, and in practice it's worse than GIF. Here's an animation I just made showcasing the different formats: The smallest version (lossy GIF) of this animation was made by taking an anime clip, averaging all repeated frames and removing duplicates for better image quality, tiling all the frames into one image, giving the resulting image a single global 256-color palette with pngquant, taking out the tiles, and then running gifsicle on the result. The 2nd smallest (256 color APNG) had the same source as the lossy GIF but without the gifsicle pass, and it was assembled with ezgif (my god I hate SaaS) which produces smaller images than ffmpeg's APNG encoder. The 3rd smallest (lossless GIF) was made like the lossy GIF, but without the gifsicle pass. The 4th smallest (8bpc APNG) was made like the lossless GIF, but using its 16bpc source quantized down to 8bpc instead of down to 256 colors. After all this optimization to reduce file size, the GIF version is still the smallest and looks good enough. A webp version would beat all of those with the least effort though. It's also worthy of note that the lossless GIF isn't all that much bigger than the 256 color APNG, looks exactly the same, and you won't have any compatibility issues like you will with APNG and webp.

>>25501022 >quantizers. I have never heard of such things before. >The smallest version (lossy GIF) of this animation was made by taking an anime clip, averaging all repeated frames and removing duplicates for better image quality, tiling all the frames into one image, giving the resulting image a single global 256-color palette with pngquant, taking out the tiles, and then running gifsicle on the result. This level of optimization I have never been made aware of. It still looks very good. >ezgif (my god I hate SaaS) which produces smaller images than ffmpeg's APNG encoder. Interesting. >After all this optimization to reduce file size, the GIF version is still the smallest and looks good enough. Yes it does. >looks exactly the same I can understand why apng doesn't see any use then. I watch all of these in mpv. >étoile praying for the death of all males femoidmaxxer

>>25501022 >>25501081 2 garlics! Who's the cunny poster?

Where are the bernds who make GIFs/APNGs/animated WEBPs?

I'd post the jxl but sadly browsers don't support it yet.

>>25504635 I will once jxl gets support.

trying

Test.

>>25504767 Not happening anytime soon. In any case, do it in now and keep the lossless source around for later. t. often forgets to keep the lossless source.

>>25504820 Google Research said they are working on the Rust decoder they'll put in Firefox and Chrome when they are finished.

bump

Is there a good way to stay under the size limit with ffmpeg?

>>25511287 >>25511629 Maybe limit the color palette as much as possible. With Mono8 you can fit a lot I bet.

what do I use to reduce the size to 25kb?

make this live