The bulk update request #1468 is active.

create alias looping_animation (0) -> loop (38627)
create implication loop (38627) -> animated (171918)
create alias perfect_loop (0) -> seamless_loop (534)
create implication seamless_loop (534) -> loop (38627)
change category seamless_loop (534) -> meta

Reason: Some pretty straightforward relationships that are long overdue. Looping logically requires animation, for example.

EDIT: The bulk update request #1468 (forum #318834) has been approved by @gattonero2001.

The bulk update request #1468 (forum #318834) has been approved by @gattonero2001.

I realized exsistance of "seamless loop" tag. What's the purpose of this tag really?
Problem here is that essentially all loops in GIF format are "perfect" and anything using WebM is dependant on if the looped animation has sound and on end users software.

Could go further and say that seamless/perfect loop is where you cannot determine when it starts or ends, but at that point if you can then it isn't really a loop to begin with.

mairo said:
I realized exsistance of "seamless loop" tag. What's the purpose of this tag really?

I presume it's for a loop that doesn't have a jump or noticeable break when going from the end back to the beginning.

Which makes me question how it's different from loop. If a loop isn't seamless, that is there's a break/cut/jump/etc, is it really eligible for the loop tag? From my perspective, a GIF that continuously replays isn't automatically a loop in the animation sense (e.g. post #4455003 isn't a loop as there's a cut from the end to the beginning). It's only a loop if the beginning seamlessly follows from the end (e.g. post #4455310 the character ends in a pose that follows back to the beginning pose, creating a loop).

watsit said:
I presume it's for a loop that doesn't have a jump or noticeable break when going from the end back to the beginning.

Which makes me question how it's different from loop. If a loop isn't seamless, that is there's a break/cut/jump/etc, is it really eligible for the loop tag? From my perspective, a GIF that continuously replays isn't automatically a loop in the animation sense (e.g. post #4455003 isn't a loop as there's a cut from the end to the beginning). It's only a loop if the beginning seamlessly follows from the end (e.g. post #4455310 the character ends in a pose that follows back to the beginning pose, creating a loop).

That's literally what I was saying :V

GIFs do have flag to determine if they should loop or not, but even for start to finish animation it's usually enabled because othervice you would have to refresh the page to start from beginning. For WebM files they are forced to loop by the site, but the limit on filetype and format is that it can never be truly seamless, hence why having WebM files under that tag as well made me question this as the loops hitching depends on your software rather than file. APNGs actually have counter how many times you want the animation to loop, so badly made APNG could loop 999 times instead of infinity.
So from technical standpoint this is already null point.

mairo said:
For WebM files they are forced to loop by the site, but the limit on filetype and format is that it can never be truly seamless, hence why having WebM files under that tag as well made me question this as the loops hitching depends on your software rather than file.

I think it should be based on how the content was authored in the file, not the specifics of the user's system. The webm animation itself can still be made as a (seamless) loop even if a given user's system causes a hiccup because of heavy resource usage for rewinding a webm. It's still seamless in the file, and it plays fine seamlessly on a less-bad system. Just like how a 4K video is still 4K even if a user needs to view it in 1440p, so a looping webm is still looping even if a user's system needs to take time to rewind it.

So given that it's based on the content, the problem I see is that loop and seamless_loop are equivalent.

The question of audio is an interesting one. Would it still qualify for the tag if the video loop is perfectly seamless but there's a noticeable cut in the audio? Except for audio-specific tags, the tags are supposed to be for the visual element, which is a proper loop, but the audio is not looping.

watsit said:
The question of audio is an interesting one. Would it still qualify for the tag if the video loop is perfectly seamless but there's a noticeable cut in the audio? Except for audio-specific tags, the tags are supposed to be for the visual element, which is a proper loop, but the audio is not looping.

That's still what I'm talking about and you seem to ignore, there's also files where audio loop is seamless, if you open up those files in video or audio editor, you cannot hear any gaps from end to start, but there's just simply no video player that does it similarly without gap or pause.
However the one who defined this tag goes by "Do not use this tag if any seam is present, no matter how small or minuscule." at which point I started to point out technical stuff because at that point webm files will have absolutely miniscule seam, regardless of how good system or what you use.