Hi! That's why I chose the player in two. In one case, the target would be the movie type, so I fix it to 25fps and it's also faster because it doesn't pay attention to anything other than decoding (not the palette). The "proper" version is slower but it handles changes (palette, sounds, fps...etc). If there is a delay between successive frames in the animation file (because without it it would just spin all the way through and that's it), then in principle the player uses it. Changing the palette also works, but it is problematic. The problem is that the palette is not done simultaneously with the decoding of the images. Unfortunately, there are two separate commands for this purpose in AMOS and both of them appear as immediate results, so either the image appears with a wrong palette and then the palette is updated, or the palette changes first and then the image. Regarding the sound, if it is integrated with the animation, you need so much more RAM. the audio rate/volume/ect is handled but I did not care to handle stereo files, sorry. if we load it from a separate file, could be streamed from hdd, it saves ram. In that case the audio limit is: mono 8bit max 22khz, basicly it is one audio chanel since I don't have the resources for mixing real time. I'll just send it out to an audio channel. Since animation editors sometimes use unique descriptors (chunks) within the file, playback problems may occur. If I have the appropriate description, I can incorporate what the development environment allows. The description is what I usually miss... or I can't find it. I am willing to continue modifying/experimenting with the player, but in this case it would be advisable to experiment with the animation in which the problem occurs.