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.
-
Show this thread
-
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).
4 replies 3 retweets 35 likesShow this thread -
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.
5 replies 7 retweets 58 likesShow this thread -
-
Replying to @11rcombs
Anything that performs worse than MP3 is tied for last place.
1 reply 0 retweets 1 like -
-
-
Replying to @marcan42
they used to! now they use FDK (which is why it's open-source-ish to begin with)
1 reply 0 retweets 0 likes -
Replying to @11rcombs
So on the sample I'm testing now libfdk_aac actually does worse than LAME. Though to be fair, the original file was already an MP3, so that probably gives LAME a bit of an advantage.
1 reply 0 retweets 0 likes -
Replying to @marcan42
qaac (QuickTime/AudioToolbox) is usually considered best-in-class fwiw
1 reply 0 retweets 0 likes
Scratch the previous reply; libfdk_aac falls over with overshoots (makes sense, it's integer) and I was feeding it some fairly clipped mix. After lowering levels it's better than LAME.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.