You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
ffmpeg's terrible AAC encoder (and its documentation claiming it's not terrible) is literally responsible for basically every Twitch streamer's audio being crappy. Also I'm pretty sure Twitter uses it too.
It's extremely sad that it's 2020 and internet streaming and Twitter video are stuck with 90s era 96kbps mp3 quality audio, **because of bad code**, and apparently nobody cares.
OBS doesn't let you pick a codec for streaming, but it *does* let you configure a "recording" output that actually goes to an RTMP stream, and *that* lets you pick codecs, so you can pick MP3 and get way better audio quality than with the ffmpeg AAC encoder (at a lower bitrate).
Honestly it's kind of funny how the open source world has best-in-class h.264 encoding (x264) and worst-in-class AAC encoding (ffmpeg aac) and those two are most often used together.
oh no, but that means the video game footage I upload to Twitter is doubly, possibly even triply bad-AAC-encoded
would it be easy to fix?
I don't know, but I do know that the reason it isn't getting fixed is that the ffmpeg dev who wrote that code no longer cares.
What’s worse is that the videos always start streaming at even lower bitrates and then out of a sudden it jumps to a “better” quality. I still can’t understand why they can’t just buffer the thing for a couple more seconds. Like you said, it’s 2020.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
