1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.

    Dismiss Notice

iPhone AAC vs. Aptx and Aptx-hd real world

Discussion in 'Sound Science' started by neil74, Oct 4, 2017.
2 3 4 5 6 7 8 9 10 11
  1. neil74
    The info on the interweb is both plentiful and vague on the comparative bitrates of APTX, AAC and SBC but as I understand AAC is capped at around 256 kbps and APTX around 350 kbps?

    I regularly switch between iOS and Android I am curious as to the real world limitations of wireless headphones on an iPhone vs APTX equipped droids? e.g. using Apple Music and it's 256 kbps AAC should mean no loss but I'm unsure how higher bitrate stuff like Spotify 328 kbps or the standard Tidal 328 kbps AACs would compare and how much of a bottleneck the AAC codec would be on an iPhone?

    With aptx-hd now available on both phones and headphones I am wondering how much of a real world quality advantage Androids now have with wireless headphones?
  2. bigshot
    AAC goes up to 320 and if you do AAC 320 VBR, it can actually go above 320 if necessary. It really isn't though, because AAC is audibly transparent at 256. Once a codec reaches audible transparency, throwing more bitrate at it won't make the music sound better. So good enough truly is good enough.
    KopaneDePooj, JaeYoon and neil74 like this.
  3. pinnahertz
    The Apple A2DP includes the mandatory SBC codec, which can run up over 320k, but usually is bumped down much lower. Apple also includes AAC at 250K. Android A2DP also includes SBC with similar bitrate chokes, but throws in AptX at some reasonbly high rate, possibly up to 320k, but I couldn't confirm that.
  4. neil74
    All things being equal I am wondering though if this is black and white?

    1 - iPhone 256 kbps AAC files piped straight over ACC so in theory no encoding. Spotify on an iPhone would presumably need to be re-encoded first. So an advantage to apple music on an iPhone?
    2 - On Android with aptx those same 256 kbps AAC files would need to be encoded too so spotify may have the edge here?

    For the above 2 scenarios the non-aptx iphone with native AAC files could actually be the better sounding combo?
  5. jfvny
    I just got a pair of bluetooth headphones capable of AAC and was interested to test this out! I'm new-ish to describing sound though, so please bear with me

    equipment used: AIAIAI TMA-2 H05-S01-E06 (the most "neutral" combination they have), iPhone 8, AAC 256 kbps (Apple music) vs MP3 320 Kbps (played through the default iOS quicktime player), track used (link here) (cos it starts out quiet, and there's a number of vocal nuances throughout)

    pre-test: Just to make sure my iPhone was using the AAC bluetooth codec (or is it profile?), I played the same track from my Surface pro (regurlar bluetooth profile, can't remember if it's SBC or A2DP) on iTunes vs from my iPhone. The iPhone playback win hands down. (edit: after longer use, I'm finding that not all tracks sound different to me for SBC vs AAC; take from that what you will)

    Short answer, both were equally good!
    Long answer, there seems to be some differences in both tracks: the AAC one seems to have slightly less volume difference for the quick low-to-high vocal portions, but slightly more detail in the vibratos. Might be something to do with the players themselves, or the source tracks, and was really minor anyways. So I assume the 320kbps MP3 is still getting encoded to AAC to be transmitted since it doesn't lose out (and Apple certainly doesn't use the aptx codec)? Which is pretty good, cos I half expected Apple to just ignore mp3s. Whether it works for the Spotify app (or others) I can't say though, since I don't have Spotify premium.

    edit: just for fun, I tried it with an AIFF (Apple's lossless format) vs the aforementioned AAC file; and there's no discernible difference either
    Last edited: Nov 10, 2017
  6. bigshot
    That sounds like a very small difference in volume between samples. If one track is slightly quieter than the other, your ears will perceive less dynamics than if it's slightly louder. Encoders will sometimes adjust the overall level of a track to prevent clipping on a hot mastered song.
  7. jfvny
    Yeah that was probably what happened
    Thanks for clarifying!
  8. DarwinOSX
    256k AAC is a much more modern and efficient codec than 256K MP 3 or the 320k OG that Spotify uses.
  9. Jeepz
    Thanks for the timely thread! I'm new to this so it's all going over my head. I'm an Apple abuser (iPhone, iPad, iMac, Watch, etc) so APTX doesn't really apply.

    I'm in the market for bluetooth IEMs. I use Apple Music (which is AAC). Should I be looking for ones that support AAC for best sound quality? Or is A2DP support good enough?

    I'm not an audiophile (but I do appreciate good sound) and I don't plan on spending over $200 for a rig.
    Last edited: Dec 18, 2017
  10. DarwinOSX
    AAC is all you need and pretty much all of the support that.
    Jeepz likes this.
  11. Jeepz
    Thanks for the quick reply :)

    What do you mean by this? AAC encoding is supported by all bluetooth headsets?

    I'm looking at a pair of NuForce BE2 (to get my feet wet) and their product page says it's the only BT IEM in its price range to support AAC.
  12. DarwinOSX
    I think most bluetooth headsets do but people often do t realize it like the Bose for example.
    Jeepz likes this.
  13. DarwinOSX
    It’s just as good as AptX without Qualcomm’s obnoxious licensing and ASC in general is a very good codec.
  14. Jeepz
    Yeah, that's interesting. I'll start experimenting with AAC branded and unbranded IEM's and see if there's a difference to me.
  15. Monstieur
    The global audio is encoded to AAC on iOS, so music will undergo an additional transcode to AAC. However, AAC has been tested to be transparent even after 100 transcodings.
    Last edited: Dec 21, 2017
    Jeepz likes this.
2 3 4 5 6 7 8 9 10 11

Share This Page