Live data from Hacker News

Show HN: A macOS app to prevent sound quality degradation on AirPods

apps.apple.com

241–250 of 356 posts

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#241
Well, one thought about your pricing model - you’re thinking that it might need work in the future, but you’re charging each month without delivering any additional value to customers. How about charging additional money for each new major version, corresponding to either new feature development or support for new versions of the OS?

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#242
post #75

This is really a Bluetooth issue. The same happens with any headphones that have a mic on any OS. When Bluetooth mode is switched from Headphones to Headset (with mic), only much lower quality audio codes are used. Does anyone know if Bluetooth 6 adds support for higher quality codes for Headset? It's a big issue, in my opinion.

It was a Bluetooth issue years ago. Now it's only an Apple issue where it can't use a more decent codec. On Linux you can choose the mSBC codec and get decent two-way quality on a modern headset.

> It was a Bluetooth issue years ago

It still is, mSBC is really not that good, plus all things considered reasons go beyond just the codec, see my nearby comment: https://news.ycombinator.com/item?id=41705258

Switching to "2x half-duplex" on both ends is really the best thing. I hate it that you can't separately select audio input and output in iOS.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#243

Well, one thought about your pricing model - you’re thinking that it might need work in the future, but you’re charging each month without delivering any additional value to customers. How about charging additional money for each new major version, corresponding to either new feature development or support for new versions of the OS?

How do you implement that?

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#244
post #214
post #205

This is more or less only (sadly) a problem with apple headphones. You can switch the current microphone on Mac by ALT-Clicking the audio menubar icon. Normally MacOS will remember and follow your decision, except when you have apple headphones. For some stupid reason MacOS forces the headphone microphone on those.

Not true. I have a HyperX moc and it’s always the default, no matter what app I use. I have several Apple headphones, works that way with all of them. macOS 14.7 now, it’s always been this way.

Never had a problem using my Sennheiser PCX 550 (Bluetooth) with a Rode Video Mic Go II (USB). But when connecting my AirPods MacOS would switch the mic to them.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#245
I'm honestly asking this with minimal snark, but...

Does macOS not have a setting where the default audio out and in device can be selected and configured independently of the actual physical device connected? On Windows and LinuxMint it's a change in the settings app, and it persists between Bluetooth device reconnects. Windows abstracts the audio in and out away from the actual device, and they show up as two separate devices on my machine. When I re-pair my headphones I need to change the setting again, but that rarely happens.

This has been a non-issue for me for years. I have one bluetooth headset that does not play nice with MS Teams (Shox OpenRun), but I don't use it for calls any more.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#246
post #245

I'm honestly asking this with minimal snark, but... Does macOS not have a setting where the default audio out and in device can be selected and configured independently of the actual physical device connected? On Windows and LinuxMint it's a change in the settings app, and it persists between Bluetooth device reconnects. Windows abstracts the audio in and out away from the actual device, and they show up as two separ…

It has, It's just that you have to do it every time.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#247

Earlier quoted context omitted.

Sounds more like a shitty-software issue. The Shazam function should turn the Bluetooth mics off after the song is identified. Why does it just leave them on? Isn't that obvious, or is there some aspect to this I'm not aware of (I care about sound quality, so I don't use AirPods)?

It's not just Shazam but any app that uses the mic over Bluetooth. Like if you wanted to have background music playing during a Zoom call, or wanted to wear Bluetooth headphones while gaming and voice chat kicks in when you group up, etc. It's a very annoying problem because the Airpods actually sound fantastic, but as soon as the mic kicks in, it sounds like crap. Same thing happens with my Sony XM3s or any other Bl…

Understandable, but in that case what's the value of the utility posted here?

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#248
post #49

Earlier quoted context omitted.

The mic quality from my macbook is usually better for me than from headphones, but maybe it depends on the macbook.

Also on whether you use it in clamshell mode (I believe the microphone openings are under the speaker grills), and on your habits during meetings – I like to walk around while talking.

~all modern Macs have an electrical disconnect for mics when the lid is closed.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#249

Earlier quoted context omitted.

Why is Bluetooth so bad? This, plus the literal second of latency to my car's speakers. All these problems are solved by headphones with proprietary wireless dongles and they work great, so why can't Bluetooth incorporate those improvements so we can get them on other devices than desktop PCs?

We currently have Bluetooth headphones in the market that are not even using the current spec/API properly. For some of them, the hardware is perfectly fine, if they did use the API correctly, the experience could be almost as good as AirPods are on OSX.

The irony is that even among the same brand they differ vastly:

Beyerdynamic MMX 200 does it wrong: pair up to, uh, I don't know (undocumented!), n>2 devices (I have 4), connects to the last one on power up, but if you want to switch devices, you have to disconnect on the device it has just connected and hope it doesn't connect to yet another you have paired and happens to be in range but is not the one you want to pair with, or you have to disconnect from there too. Confused yet? Yup, it's that bad.

Worse, upon that second disconnect the headset itself initiates a reconnect by going through the MRU list again, so if you disconnect from the second (incorrect) one it might try the first (incorrect) one again since it's now the next in the MRU list, so you actually have to DISABLE BLUETOOTH on each device except the one you want to connect to.

Too bad if one of these devices is in the next room, even more annoying if it's your iPad borrowed by your SO who is now annoyed at losing sound from their movie.

At that point, it's easier to forget the headset in the device you have in hand and re-pair, which is absolutely ridiculous.

Beyerdynamic Free BYRD does it correctly: pair up to 5 devices, connects to the last one on power up, any device in the pair history can force-connect to the headset, yanking out the virtual cord from the undesired device. No interaction required on any other device.

Even better, when pulled out of the charging case they actually wait a bit (a few seconds? or detecting when they're put in ear?) so you can actually invoke some quick setting pane and connect without the connection ever going to an unsuspected device.

Dishonourable mention for Bose QC-35 II, who operates like the MMX 200, only it has two BT radios as an attempt to work around that it's doing it wrong. So, it connects to the last two devices. Unfortunately if I'm walking around the house listening to music and the second-to-last device goes out of range the headset goes " disconnected" then a few moments later " connected", which is horrible when is made out of a serial number (work laptop) and it goes on to spell it out "C. O. M. P. H. 4. 7. X. 3. 9. 9. 7. P. K. Q. L. disconnected".

The only way to prevent that is to go through the Bose app and remove devices from the history, essentially pairing it with one-device-at-a-time only. Oh, it's also great for jump scares when your SO is aping the iPad again and it turns out the headset is connected to it. All of which could be avoided if it behaved like the Free BYRD.

Re: Show HN: A macOS app to prevent sound quality degradation on AirPods

#250
post #4

Couldn't I just make an aggregate audio device which uses the mic on my MacBook Pro, and speakers of the AirPods?

You don’t even need it to be as complex as that, I just have an aggregate device which only has the MacBook microphone input enabled and no outputs, then you set this as your _input_ device in Sound preferences, but leave the output device as is. It’s easy to create the aggregate input device, go to the Audio MIDI Setup app, in the audio window click the plus in the bottom right and choose “new aggregate device”, the…

What exactly is the logic osx is using here that causes non-aggregate input to always be switched when plugging in external source, but aggregate sources remain sticky?
Post reply on HN