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
Today in "ffmpeg's AAC encoder is still a embarrassment and nobody should ever use it": OBS on Windows using it, at 320kbps, makes music sound like a low bitrate mp3 (metallic hi-hats, etc). No problem with a custom OBS build on Gentoo with libfdk_aac enabled, at *160* kbps.
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.
Wasn't the whole reason ffmpeg's version exists is because of shitty licensing of the alternatives?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
