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
I am doing this **because when I previously tried to bring up single-generation issues to your devs, I was dismissed as "hearing things"**, and because I actually have a use case for this, and because even transcoding repeatedly I'd expect it to be okay at 320kbps.
This is my way of saying "look, here's *one* way of using the ffmpeg AAC encoder that shows it being quite inferior to libfdk_aac, and *anyone* can hear that, and I even have a valid use case for it, so please don't brush me off?" after being brushed off for subtler cases.
My *actual* "I noticed the ffmpeg aac encoder is bad again" use case that brought things up again, this time, was 256kbps MP3 -> 320kbps ffaac -> 320kbps ffaac, which is much gentler and I *expected* it to be transparent, but it wasn't. The second ffaac had quite noticeable loss.
But the last time I tried to bring loss of that level up to the person working on the AAC encoder at the time I was dismissed, so here I am saying "okay, let me do it 4 times at 128kbps to try to prove my point in a way anyone can hear".
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
