8 ms·
There is simply absolutely no need for on ear computation to make low quality drivers sound better. In ear headphones have evolved beyond plastic cones for a l
by sudosysgen 6y ago
There is simply absolutely no need for on ear computation to make low quality drivers sound better.
In ear headphones have evolved beyond plastic cones for a long time. At that price, you're competing against the very best balanced armature drivers, which basically have perfect frequency responses and harmonics, as well as against planar magnetic and the very best dynamic drivers too.
As for computing audio, yeah that's simply useless. Just have the DSP at the device. The device, iPhone, or Mac, or a PC, or whatever, is aware of which headphones it is connected to, and can trivially run the correction routines itself. In fact, this is already done by many.
In ear headphones aren't going to have enough battery to power a cellular modem.
- beagle3 6y agoIs this still true when active noise cancellation is involved?
- sudosysgen 6y agoNo, it's not. If using ANC, you do need a chip on the device to do ANC for latency reasons. But that's already a solved problem.
- koffiezet 6y agoSorry, but when the DAC can be tuned to the specific hardware, and the engineers know what the hell they are doing, the result can be pretty damn impressive. This is the reason modern active bookshelf speakers like the Klipsch The Fives punch way above their weight and pull off stuff its hardware shouldn’t be capable of. Apple can do the same thing, they have the engineers and know-how. And on top of that, the positional audio is something that requires compute power anyway.
- sudosysgen 6y agoI never argued that point. I just said that it makes no sense to make the vast majority of that processing in the headphone when your phone and computer already have specialized hardware to do it. Also, DACs today are pretty much transparent. For example, for positional audio and driver/amp compensation, people already do the same as Klipsch does in software on their computer. You just need a good enough microphone and then you can do it by your own using REW and EqualizerAPO, for example.
- ubercow13 6y agoSounds absolutely horrible. I'd rather not install some bloatware crap headphone software that injects itself into my operating system's audio stack and introduces extra latency on every device just to get the headphones to sound right.
- sudosysgen 6y agoYou already have to install software that inserts itself into the audio stack and introduces extra latency to be able to use your wireless headphones. Those are called "Bluetooth drivers". In any case, I run processing on my computer to apply a convolution filter on my audio stack with adds around 2.3ms of latency and uses 0.15% of my CPU. Compared to the ~200ms of Bluetooth latency it's completely unnoticeable, and I'm sure Apple can figure this out better than I can.
- ubercow13 6y agoHardly the same - they are generic, provided by the OS, follow a standard, don't require specific support to be provided for individual devices.
- sudosysgen 6y agoThey do need some pretty wide support per individual device. A proper stack requires something like 6 different codecs, all of which are quite heavy and very different. In any case, the transformations are not generic at all. You basically need to do one convolution, that's it. The headphones can provide the impulse response with which to convolve at pairing. For things from Apple, of course, this is trivial.
- ubercow13 6y agoYes, basically Bluetooth is already almost too complicated to do well, and you would rather it were more complicated still? And like you say applying a convolution is computationally trivial especially compared to decoding a lossy audio codec and running a Bluetooth stack and antenna, which the headphones are already doing. Offloading this to the device is going to make absolutely no difference to battery life while increasing complexity and unreliability, while also restricting what processing can be done to static convolution with an impulse response. There is no reason to do this on the device.
- adolph 6y agoThere is simply absolutely no need for on ear computation to make low quality drivers sound better. Sure there is. If the cost of computation for a required sound quality is lower than the difference in driver cost, then computation will win, especially when it adds additional value unavailable to the non-computational approach. Positioning the computation at the device is advantageous since it allows for a simpler data interface. For example, adjustments to the soundstage based on head movement can be performed on-device instead of making a round trip to source for the adjustment. In ear headphones aren't going to have enough battery to power a cellular modem. Sure, and when the first iPod was released it lacked wireless networking and was storage constrained compared to comparably priced products. I can appreciate the pragmatism and be appreciate folks working towards an exciting future. Pardon me for departing, my kid wants to watch the SN8 livestream together; hope you enjoy some high quality Soyuz laserdisks. https://slashdot.org/story/01/10/23/1816257/Apple-releases-iPod https://slashdot.org/story/01/10/23/1816257/Apple-releases-i...
- sudosysgen 6y agoRead carefully. I said there is no need for on ear computation. I personally even have impulse response profiles for my headphones that I load onto my phone and computer to make them sound much better. For things like on ear sound stage correction, sure. That can be done. You will pay a heavy cost in sound quality, but it can be done. If your goal is sound quality, you're not going to be doing anything more that is very latency sensitive than ANC. As for the last point, have fun with your sound streaming device that has 3 bit/s of UI bandwidth and a battery life of 1/5th that it would otherwise. It's not an issue you can fix by trying to fix it in that use case, it's an issue you fix by improving human interfaces, battery technology, and cellular technology, which is already being done. When that will be good enough for what you're describing, we can talk. As for me, I'll enjoy having headphones with high quality and essentially unlimited battery life, and use the carefully optimized interfaces and computational power of my phone and computer to listen to music.