Bose has released API docs and opened the API for its EoL SoundTouch speakers
201–210 of 416 posts
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#202Earlier quoted context omitted.
Bose hardware quality is rather low and, and their sound quality is sub-par, while forcing you to pay the Bose brand tax, riding the corpse of Amar around for profit. I'd avoid, even if they happened to do this.
Please suggest better alternatives
Also, there are multiple forums and subreddits you can ask this question on. You will get more answers than you would from me and the rest of HN.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#203This 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.
++1 I do not get why not more companies are doing this! Also it pays so much into your brand perception etc.; also you will always have all ecological folks on your side because of "not producing new stuff". This is the cheapest and best way to get the most out of your investment after it entered end-of-life.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#204Earlier quoted context omitted.
Please suggest better alternatives
Beyerdynamic DT1990s run circles around consumer-grade stuff.
Their build quality is exceptional, and they're built like tanks. The only problem, imo, is the Beyer house sound is very shouty and fatiguing, especially with the "990" versions of the product line over the years.
Disclaimer: I owned a Beyer DT880/600ohm (the neutral one of the 770/880/990 siblings), paired with an amp that could properly handle it. Its one of the few headphones I sold and did not retain in my collection, it deserved someone that could love it. The new Tesla-based drivers are better (such as that 1990), but still retain that Beyer sound.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#205Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#206This 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.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#207Earlier quoted context omitted.
> "Bose blows" is a popular comment amongst the audiophile community but, to me, it seems like they don't blow at all[0] That comment is not wrong, you are imo just not making an important distinction that the criteria on which audiophiles judge Bose as “blowing” (which is almost purely the sound profile + a few other smaller things like physical comfort/connectivity/price/etc.) vs. what you judge it on (which is mor…
Build quality of Bose products is good in my opinion. The headphones are alright but so are Sony, Plantronics and Apple. I love the sound of Airpods Pro in particular even if they don't want to stay in my ears [1] and the pairing experience even with the iPhone isn't what I expect of >$100 headphones in 2016. If you want really good stereo or 5.1 sound there is no substitute for big speakers that can move a lot of ai…
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#208Earlier quoted context omitted.
Exactly this. "Bose blows" is a popular comment amongst the audiophile community but, to me, it seems like they don't blow at all[0]. In fact quite the opposite: this is a fantastic example for other companies to follow. Top marks, Bose! [0] What is actually true is that they are opinionated about sound reproduction in ways that a bunch of people don't agree with but which in the right context are often effective and…
> "Bose blows" is a popular comment amongst the audiophile community but, to me, it seems like they don't blow at all[0] That comment is not wrong, you are imo just not making an important distinction that the criteria on which audiophiles judge Bose as “blowing” (which is almost purely the sound profile + a few other smaller things like physical comfort/connectivity/price/etc.) vs. what you judge it on (which is mor…
If we gave tax breaks for open sourcing EOL products, we'd see a lot more of it. Code escrow companies might not like it, though.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#209Earlier quoted context omitted.
This def needs to be celebrated and rewarded. I am more likely to purchase Bose now.
Exactly this. "Bose blows" is a popular comment amongst the audiophile community but, to me, it seems like they don't blow at all[0]. In fact quite the opposite: this is a fantastic example for other companies to follow. Top marks, Bose! [0] What is actually true is that they are opinionated about sound reproduction in ways that a bunch of people don't agree with but which in the right context are often effective and…
Glad to see them setting a great example here instead of letting these speakers become expensive paperweights.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#210Earlier quoted context omitted.
If the publish the API for the server, as well as allow the device to specify the API hostname to connect to, that's all I need. We can write our own server implementation fairly easily, and this saves us the hassle of having to reverse-engineer the API, plus makes setup much easier if we can just tell the device where to connect. I wish more manufacturers would unlock their devices for local use when they don't want…
Exactly. Open source is great and all, but all 99% of these devices need is simply a way to configure them to connect to a different server, when the manufacturer inevitably turns their own server down (usually) bricking devices. The open source community will happily reverse-engineer the protocol and clean-room develop their own server code.
[0] discussed https://news.ycombinator.com/item?id=45813343