mirror of
https://github.com/imputnet/cobalt.git
synced 2026-03-09 07:17:16 -05:00
Twitter videos don't play properly on Windows after a muxer/encoder change on Twitter's side #920
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @77Arbiter on GitHub (Jul 29, 2025).
bug description
I've recently been saving videos from Twitter (x) via cobalt and they've had issues in playback. The main issue is that none of them work in VLC Media player or any Windows based media player (Photos, Media Manager, etc) and usually bug out in a multitude of ways:
This issue also extends to uploading the mp4 anywhere, including Discord and Twitter itself. It will usually bug out in the same way as the first issue mentions above, but can also sometimes just freeze inexplicably.
The Redux feature doesn't seem to work at all, and usually either does nothing or just makes it glitch out in a different way. This is a recent occurrence as older videos i've downloaded from Cobalt about a month ago seem to be fine.
This seems to ONLY be an issue with Twitter (x). Reddit, Bluesky, and Instagram don't have this issue in the slightest.
reproduction steps
screenshots
No response
links
platform information
Windows 10; Firefox
additional context
Was sent here via the Discord after asking about it there. Was told to submit an issue.
@wukko commented on GitHub (Jul 29, 2025):
i can't replicate it in quicktime on macos, but it may be caused by twitter's weird encoder (again). cobalt downloads the source file from twitter without any modifications, so we're not really responsible for any compatibility issues here
@77Arbiter commented on GitHub (Jul 29, 2025):
Sorry for the wrong label, and yeah others don't seem to be having the issue, i asked a friend to do it, although he wasn't on Firefox. I made sure to check though and it's not browser specific. I assume nothing can be done but to wait and see if Twitter's encoder ever decides to play nice?
@wukko commented on GitHub (Jul 29, 2025):
i'll try to figure out why this is happening either later today or early tomorrow. surely there has to be a fix without having to re-encode the video
@77Arbiter commented on GitHub (Jul 29, 2025):
Thank you kindly