Your feedback on APTX is welcome. The thing is not enough source devices support it. So I'll listen to your feedback closely, but first let's get some in users hands and AB test!
Cables aren't going away, we are just using them more and more for different use cases. Like flying and commuting wireless is king. For musicians and audiophiles Wired still rules.
Regardless, it is very hard to tell the difference on codecs, and it doesn't help that you cannot find what it's using on IOS and even perhaps windows?, I think you will love the sound as there are a lot of other little items we made it for the best experience Wired or Wireless.
The microvAMP in Wireless mode sounds spectacular.
And for absolute best sound we still recommend an AMP or DAC. Our new REMIX makes a great amplifier and speaker.
Hey wow! The CEO of V-Moda in da house! Hey man, really respect your company and think you're doing a fantastic job producing headphones that are very innovative, stylish, wonderful sounding and very well built products. It's so easy for me to automatically recommend your brand over Beats.
That said, I wasn't so much downplaying AptX as a codec but rather kind of trying to point out to the community that it's very well marketed while AAC isn't. I wish this well more well known and talked about in the industry. I imagine the Crossfade2 works with AAC, right? That's actually something you can sell! If it doesn't support AAC, what the heck? Missed opportunity by the design/engineering team.
The point is that, the iPhone transmits audio in AAC first over bluetooth but switches to SMB when AAC is not available. It maxes out AAC at 320bits which should actually outperform most other codecs at the same bitrate.
Here are supporting links with AAC compression performance comparisons and articles talking about how it's not only better but how, honestly, AptX is just the android/windows equivalent and maybe actually underperforms for the same amount of data/computation.
https://forums.anandtech.com/threads/mp3-vs-aac-vs-ogg-a-simple-quantitative-comparison.2168530/
https://www.quora.com/Which-is-the-best-AAC-MP3-VBR-V0-or-OGG-Vorbis
And more articles highlighting how AAC and AptX might be similar enough to call them similar enough to Windows/Mac or iPhone/Android or maybe BMW/Mercedes
http://forums.naimaudio.com/topic/bluetooth-to-unitiqute2-apt-x-vs-aac
https://www.cnet.com/news/can-aptx-give-you-better-sound-over-bluetooth/
So, assuming AAC is enabled and able to perform at 320bit throughput, the iPhone should sound just as good - or better - than it's AptX enabled sister-wieless-source.
_______________
The reason I'm writing about this is because I got caught up in the whole AptX hype and researched into why Apple didn't support it. It's very unlike a company who puts great emphasis on audio products to completely skimp on an audio codec that doesn't take advantage of bluetooth's existing bandwidth.
So after researching, I found the Apple defaults to AAC 320b just about an hour ago. And that this has been tested. But you know, no one really talks about if it's implemented in their products. And that's kind of weird, right?
If the crossfade and its competitors use something like the Qualcomm
CSR8675, it should work with a variety of codecs/sources - including iPhone's AAC audio at max bitrate throughput.
_________________
Anyway, I'm very interested in your product and have been looking very much forward to the Blue Satellite with it's ANC and will be comparing with our Crossfade2.
I have to say, your price, weight, performance specs, design and overall presentation and super compelling.