Live data from Hacker News

Bose has released API docs and opened the API for its EoL SoundTouch speakers

arstechnica.com

161–170 of 416 posts

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#162
post #8

This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.

This this also good marketing, if other companies I currently buy speakers from follow their footsteps I'll keep supporting them, but I might otherwise just move towards Bose in the future. I wish Apple would do this for their ultra legacy stuff, Microsoft does it for their legacy stuff. Not sure if we'll ever get a fully open sourced legacy version of Windows (ignoring the source code leak) but it would be cool to one day see the Windows XP source code on GitHub.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#163

Earlier quoted context omitted.

In current dynamic world product quality of a company 'today' vs '5y+ ago' may drastically change. Sadly, usually to the bad side

Bose's QC/QC Ultra lines continue to receive praise for comfort, durability, sound quality, noise cancellation, etc. They make pretty great consumer quality headphones. Until quite recently, they were widely one of if not the most recommended wireless headphones. The new Sennheiser's that come with a USB-C dongle might have finally stepped past what Bose has been delivering, but at a higher price.

I had the new QC Ultra and gave it away. The sound was mediocre at best and you can't turn NC off - a dealbreaker for me (no, passthru is not the same as off). Hope it helps someone make my mistake aa they are quite pricey.

Now if I could change the firmware to turn NC off, that would be something entirely different...

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#165
post #8

This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.

[flagged]

Who's losing here?

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#166
post #75

Earlier quoted context omitted.

My experience is the opposite: Bose hardware and sound quality seems excellent to me. This may be subjective. Bose might sound good to some people's ears and less good to other people's ears.

Bose in general (there are many models...) is not what I'd call high-fidelity. It doesn't mean you can't enjoy your music or your movies with it. Just don't buy this if you care about transparency, otherwise it's usually a pleasing hearing experience. Their PA line is IMO overpriced and sacrifices too much to the design and weight.

I've been playing with the idea for a bit, can you give me an order of magnitude for "entry-level HiFi"? Even if that's an oxymoron, how many zeroes does it take to get an experience that's noticeably superior to, say, default car speakers or built-in Smart TV speakers?

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#167
From https://www.bose.com/soundtouch-end-of-life:

> Open-source options for the community

> We’re making our technical specifications available so that independent developers can create their own SoundTouch-compatible tools and features. The documentation is available here: SoundTouch API Documentation (https://assets.bosecreative.com/m/496577402d128874/original/...).

AFAIK, the soundtouch web API was already accessible via some bose developer portal. It doesn't seem like they are open sourcing anything. This API just allows you to make basic requests to do things like change volume on the speaker.

To support the smart features of the SoundTouch speakers, we would the soundtouch user management service. Speakers connect to this very frequently and its where refresh tokens for music services and presets are stored. The speaker firmware itself has lots of source code, including the bit to handle music services and playback. There is an abstraction layer for music service APIs. There is a process on the speaker that reaches out to a music service registry, which is an index of bose music service adapters. Each of these adapters essentially proxies a music service like tunein, spotify, and even the "stream a custom station" feature.

If bose open-sourced the speaker firmware, we could make a firmware build which talks to a 3rd party user management service, and reaches out to a 3rd party music service registry. Then we could add and maintain music service playback for the community. But there is no open sourcing of any actual code here and this soundtouch web api cannot change the URLs on the existing firmware of the user management service or the music service registry.

So to my eye this story seems misleading and just some PR nonsense. It's a little frustrating reading all of the "great job, Bose!" comments here like anything was actually done... Disclaimer: I used to work at Bose.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#169
post #84
post #75

Earlier quoted context omitted.

My experience is the opposite: Bose hardware and sound quality seems excellent to me. This may be subjective. Bose might sound good to some people's ears and less good to other people's ears.

I don't know about Bose. But sound quality in general is absolutely objectively measurable.

[deleted]

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#170
post #30

Earlier quoted context omitted.

This def needs to be celebrated and rewarded. I am more likely to purchase Bose now.

Agree. This is huge. Definitely makes me want to buy more Bose products for my house.

Not huge, they didn't open source any code
Post reply on HN