Hello,
I’ve been using Asepire for about 2 - 3 years now, only now I decided to ask about a problem I’m having - when exporting a gif and sending it on Discord some of the times the gif would have glitches in it, for example - frames staying more on the screen while the other frame has been drawn, frames merging, colors switching to other colors on the canvas, sometimes a piece of a frame is cut and stays there until the end of my animation.
This is my Discord: Ameidox#8032 So I can share this with anyone that wants to see it.
Does this only occur on Discord? I’ve noticed what may be the same problem, GIF previews in Discord are glitchy, but when the GIF is opened in full (i.e. in a web browser), it’s fine. If this is the problem you’re describing, it’s only to do with Discord’s GIF resampling when it creates the previews, and is not related to Aseprite.
I have the same issue for a long time. It occurs only in Discord. I’m on macOS. Any other GIFs are fine, except Aseprite exported. Some frames leave trails.
Hi, I’ve been having similar issues for quite a long time, and unfortunately I have no idea what causes these export glitches. The only workaround I can give is export the animation as a sequence of pngs and using a third-party software to combine them into a gif. PNG to GIF websites seem to work well, just make sure to use same animation speed as your aseprite project.
I suspect it’d take some discipline to get to the bottom of the problem, unfortunately.
There are a lot of variables within Aseprite – a sprite’s color mode, transparent color index, presence of colors with alpha other than 255 in the palette, number of colors used on the canvas, presence or absence of a background layer – that can change how a file is exported. There are also options for the gif format that you’d not know made a difference unless you turned on alerts in preferences.
A few suggestions for any interested:
Create a small gif and open it in a hex editor. (I’m talking 3x2 pixels, maybe 3-4 frames tops to really dig into it. The one below is too big and is just for illustration of the gif’s header info… and in retrospect would be more helpful if it had transparency.)
Look at Aseprite’s source code for gif io. If not the code itself, the comments can help summarize the general approach and problem areas. I mentioned options in the file save alerts earlier. For some options, such as “Preserve palette order,” you’d need to look here to piece together what they do.
Look at a file format specification, or gloss of it, to help understand what’s in the hex editor.