JasonSct

I'd assume that the Bluetooth audio quality when using Apple gear + AudioEngine B1 equals a max quality AAC VBR at ~ 265kbps, i.e., identical to the audio quality of music purchased from the iTunes Store (if i remember correctly). Likely aptX performs a bit better with a bit less lag. Each manufacturer's documentation says they support the non-standard bluetooth format MPEG2-4 ACC, for the reason that it performs with better audio quality than Bluetooth's previous generation SBC codec. Apple says: https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf AudioEngine's B1 FAQs says: "What if my source doesn't support aptX®? Can I still use B1 and if so, how will it sound? You can absolutely still use the B1, and it will sound great. aptX® is a high quality Bluetooth audio codec that works really well. With that said, in addition to mandatory support for SBC, Bluetooth also includes optional support for many other codecs, like MPEG-1, MPEG-2, MPEG-4, and AAC, all of which have their own advantages, and some of which sound very close to aptX®."

Apple gear is not Bluetooth aptX compatible. Regardless, the previous generation of the Bluetooth codec is good quality. Testing with Apple gear is good to reflect the baseline consumer experience for the Audioengine B1. Still, my curiosity leaves me wondering if the review would produce stronger impressions if done with aptX compatible gear... I'd suggest borrowing a colleague's aptX compatible phone for future tests of aptX Bluetooth gear.

My D 7050 has the May 2014 firmware (ver 1.63). DLNA gapless playback seems to "work" but with sound quality issues, well, it depends on the brand of media server. It "works" gaplessly using either JRiver MC or Foobar 2000 but both media servers, regardless of music format, result in choppy and clicky sound quality when the second track starts. Using Windows Media Centre it plays with 2 second gaps of silence between tracks yet all of the tracks sound perfect. May I ask someone else with the ver 1.63 firmware to check this out? Either I got a dud unit or the firmware broke it. Obviously not an issue with everyone else's units running the old firmware.