Why xHE-AAC is being embraced at Meta
engineering.fb.com
Why xHE-AAC is being embraced at Meta
1–10 of 61 posts
Re: Why xHE-AAC is being embraced at Meta
#2How long until the patents expire?
Re: Why xHE-AAC is being embraced at Meta
#3This codec isn’t supported on the web. So it is Android and iOS only. This post talks about the improved audio quality, but I don’t buy it. This was probably done to reduce storage and bandwidth, not to improve audio quality. Phone speakers aren’t good enough to notice.
Also, I wish they had backed opus…
Re: Why xHE-AAC is being embraced at Meta
#4This codec isn’t supported on the web. So it is Android and iOS only. This post talks about the improved audio quality, but I don’t buy it. This was probably done to reduce storage and bandwidth, not to improve audio quality. Phone speakers aren’t good enough to notice. Also, I wish they had backed opus…
Why can’t it be supported in web browsers? Is there a technical limitation or it just hasn’t been done because only Meta uses it?
Re: Why xHE-AAC is being embraced at Meta
#5Exhale - Open Source USAC / xHE-AAC encoder
Re: Why xHE-AAC is being embraced at Meta
#6This codec isn’t supported on the web. So it is Android and iOS only. This post talks about the improved audio quality, but I don’t buy it. This was probably done to reduce storage and bandwidth, not to improve audio quality. Phone speakers aren’t good enough to notice. Also, I wish they had backed opus…
Why can’t it be supported in web browsers? Is there a technical limitation or it just hasn’t been done because only Meta uses it?
Patents. I presume that the Facebook and Instagram apps bundle their own decoder (which Meta paid) but you need to convince other companies (or wait for OS integration for Firefox) to include xHE-AAC.
Re: Why xHE-AAC is being embraced at Meta
#7Earlier quoted context omitted.
Why can’t it be supported in web browsers? Is there a technical limitation or it just hasn’t been done because only Meta uses it?
Patents. I presume that the Facebook and Instagram apps bundle their own decoder (which Meta paid) but you need to convince other companies (or wait for OS integration for Firefox) to include xHE-AAC.
Android, iOS, macOS, and Windows come with support for xHE-AAC.
https://developer.android.com/guide/topics/media/media-forma...
https://developer.apple.com/documentation/http_live_streamin...
Re: Why xHE-AAC is being embraced at Meta
#8As far as I know, xHE-AAC has no advantages over Opus, however, Opus is free from patent licensing.
Re: Why xHE-AAC is being embraced at Meta
#9Earlier quoted context omitted.
Why can’t it be supported in web browsers? Is there a technical limitation or it just hasn’t been done because only Meta uses it?
Patents. I presume that the Facebook and Instagram apps bundle their own decoder (which Meta paid) but you need to convince other companies (or wait for OS integration for Firefox) to include xHE-AAC.
When I set up my jellyfin server I learned that Firefox doesn't support h.265 and that there's no way to add codecs to the browser.
Does anyone know why it isn't possible to add codecs to the browser?
Re: Why xHE-AAC is being embraced at Meta
#10Sooo... How is the loudness management feature not just a reimplementation of "mp3 replay gain" that was introduced over 20 years ago?