4 ms·
I have to wonder if it's time to just say screw Bluetooth, and deploy a new standard that's specially oriented for audio. Requirements aren't crazy. It just ne
by TylerE 5y ago
I have to wonder if it's time to just say screw Bluetooth, and deploy a new standard that's specially oriented for audio.
Requirements aren't crazy. It just needs to support uncompressed 96/24, full duplex.
- smoldesu 5y agoI know some people have experimented with WiFi direct for that, but I'm not really familiar with it's limitations besides "you have to be hooked up to a router for it to work". One thing's for certain though, if someone made a pair of lossless cans that could "find" devices over arbitrary WiFi networks, I'd probably switch just for the improvement in latency alone.
- Gigachad 5y agoWifi has an ad-hoc mode which doesn't require a router.
- fphhotchips 5y agoAh yes, the famously well supported and not at all prone to weird bugs Wifi Ad-hoc mode.
- vineyardmike 5y agoI've long wished for a Wifi headset that you could Airplay/cast to
- pahomov 5y agoAnd zero delay, please. I'll take two.
- bsder 5y agoExcept that requirement IS crazy--when you put all the other stuff around it. Must work at 2.4Ghz--even in the face of 200 WiFi access points and 3 times that number of devices. Must stay in sync to within a millisecond ... even though there is a large bag of RF absorbing water in between them. Should work on a battery smaller than a thumbnail. Should process audio but not generate enough heat that you notice it in your ear. I can go on. The engineering requirements are quite severe. ... for something that we can do with a 10 cent wire, ironically.
- jonwinstanley 5y agoSo true, we take the complexity for granted. It's actually a really hard problem.
- Dylan16807 5y ago> Must work at 2.4Ghz--even in the face of 200 WiFi access points and 3 times that number of devices. At low range and less than 1/100 the speed of wifi. > Must stay in sync to within a millisecond If you have a working data connection at all, that level of sync is trivial. It only takes a few bits to align things, and they use pretty big buffers. > even though there is a large bag of RF absorbing water in between them That's hard. > Should work on a battery smaller than a thumbnail. That part is quite hard. But also it doesn't apply to over-ear headphones. > Should process audio but not generate enough heat that you notice it in your ear. I'm skeptical of that part being hard. How many milliwatts do those codecs take? Also once you add the battery constraints then the heat levels solve themselves.
- chowells 5y agoYou can hear 48kHz tones? Wow.
- oynqr 5y agoWhy waste a bunch of bandwidth on 96 kHz when 44.1 is fine?
- deleted 5y ago[deleted]
- chipotle_coyote 5y agoI don't think you need a new standard for that -- UWB radios, like Apple's already-deployed U1 chip, have the bandwidth to easily be bandying about 96/24 FLAC/ALAC files, at the least. (Personally, I'd settle for topping out at 48/16 lossless ALAC.)
- climb_stealth 5y agoBluetooth / BLE 5.2 is bringing in a lot of functionality and standardisation for audio scenarios. Hopefully this will improve things. Previously there hasn't really been much official support and implementations are messy and differ across platforms. Source: have worked with various BLE stacks. Getting this stuff working well is difficult. I have much respect for companies that actually get it to work reliably. Funnily enough, I try to avoid Bluetooth as much as possible and everything is wired on my setups.