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
Despite no clue how to duplicate whatever issue you're experiencing I did a few lazytests and didn't notice a huge difference between aac and libfdk_aac. Sounded fine to me. So at this point all we can offer are apologies for the behavior of the encoder and the rude developer.
If you're serious about listening and fixing this and willing to listen and either improve the encoder or change the documentation to stop claiming it's better than libfdk_aac, I can put together some samples (not now though, busy organizing an event).
If I do, I sure hope I don't get any more of the "sounds fine to me" and, when I do diff tests to show the issue, "you can't do that with psychoacoustic codecs". If you don't trust me when I say it sounds bad, and reject my attempts at making it objective, you're wasting my time.
Using cascaded transcoding is invalid to prove anything.
Where does it say it is better than libfdk_aac? I am not aware of such a statement anywhere. The samples would be helpful, but no hurry. Thanks.
Ah, there is the sample and command in your later tweet... But still curious about first question.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
