Open ghost opened 2 years ago
Agree completely, this is especially annoying when it happens with videos that are several minutes long.
it might make sense to abandon the concept of a "gif" entirely when not referring to the file format. rather, the user should be able to set an API parameter to determine whether the video loops or not (regardless of whether it has sound or not).
+1 on this issue. I wanted to upload an animation as a GIF. Ran into the hard coded dimension limits, but even when honouring them, the file would not be accepted. Noticed that ffmpeg wasn't able to process the GIF. After a brief "WTF why ffmpeg" moment, I read up on why this is done and can see why it makes sense.
Figure that I better upload a video instead of an animated GIF to a) bypass the dimension limitations, b) give the viewer video controls so they can easily stop the animations. I.e. I was glad to have run into this problem as otherwise I would not have thought about the advantages of giving viewers the controls.
So yay, video upload works, but now my video is displayed as if it was an animated GIF. WTF time again.
I agree with the OP of this ticket that Mastodon should not make that decision for me.
When I upload a video, I do this on purpose and Mastodon should not care that the video does not have an audio track. There are plenty of use cases for silent videos.
Or at least one should have a choice to turn on the video controls. The context menu controls are too awkward to be a full replacement for standard video controls.
But I guess in the meantime I have to add a silent audio track to the animation.
Pitch
Currently, when you upload a mute video, they are displayed as gifs. You can't have media controls on them. They should be displayed as videos or have media controls.
Motivation
When you miss a part in the video or want to watch it again, you have to wait the video to finish; it is frustrating.