Hacker Newsnew | past | comments | ask | show | jobs | submit | Humbly8967's commentslogin

EQing for a flat in room response is NOT ideal!

Correcting a speaker requires measuring the *anechoic* response, and only the bass should be tuned to subtract the room's effect.

This video [1] provides a crash course on science of audio reproduction.

[1] https://www.youtube.com/watch?v=zrpUDuUtxPM


Yes. I work for a company that tunes dozens of speaker systems in high-end recording studios a year and our target frequency response balance can generally be described as this: A spectral "tilt" in which the bass frequencies are +6 dB louder than the highest frequencies. The slope downward should be gradual, from lows to highs. Again, with a 6 dB difference between the bottom and the top octaves.


FYI, when attempting to apply this to speakers, the anechoic frequency response is required. If you try to equalize for flat-in-room response, the results are terrible. See this video[1] for loads more information and context.

[1] https://www.youtube.com/watch?v=zrpUDuUtxPM


No, FUTO made a new "Source First License"[1] that is not Open Source by the OSI definition.

[1] https://github.com/futo-org/android-keyboard/blob/master/LIC...


I can get behind people doing their own custom "licenses" that amount to throwing their work into the public domain, but if someone builds their own limited licenses around a thing, I won't touch their product. This FUTO license is garbage. Use a real license and either be open source or not; inventing new personal licenses doesn't do anyone any good.


Oh, that's lame.


This is actually a common misconception. In blind testing, the average listener reliably prefers the more accurate speaker. There is a talk [1] by Dr. Floyd Toole that is an excellent crash course on the science of sound reproduction and listener preference.

[1] https://www.youtube.com/watch?v=zrpUDuUtxPM


If you are interested in contributing to OSM to make the data better in your region, you can even make basic edits from within Organic maps, including adding addresses.


Yes, there are many possible conflicts of interest in mapping. This is why I'm excited to see the improving usability of Open Street Maps through apps like Organic Maps, and big commercial investments in open mapping data from the Overture Maps Foundation.

In many cases OSM has much more detail than google maps, with business listings and addresses being the biggest exceptions I have encountered. Fortunately, business listings are one of the main things added to the first data release from Overture Maps. For the curious, you can interact with the POI data [here.](https://bdon.github.io/overture-tiles/places.html)


If you really just want a map, go use OSM. I love it as well and even contributed. But Google Maps is much more than OSM. The biggest difference and most important feature is its real-time traffic. OSM is just a totally different product seen through the car navigation lens.


Absolutely true. OSM, conversely, is an infinitely better dataset for pedestrian and bike navigation.


Yup, have been using it through Komoot for many years for biking and hiking.


For me the killer Google Maps feature is using it as a search engine. The POI data on OSM has low coverage, is often out-of-date, and lacks reviews, so while it's quite good for (non-car) navigation, it's not very useful at all for finding places meeting certain criteria.


The non-starter with OSM for me is lack* of high-DPI ("retina") support, making it like rubbing my eyes with scratchy wool when I try to read it

* well, there's https://osm.rrze.fau.de/testhd.html , but that has no search.


To my knowledge, we just have to guess based on the various development details that they have teased on Mastodon/twitter.


System76 might be willing to collaborate on this. They are designing a trackpoint into their upcoming in-house laptop, and they make open hardware.


That's good to hear! Maybe they'll take cue from TEX[0] and source their TP modules from Lenovo, so that they feel the same.

[0]https://tex.com.tw


I have also only seen a couple JRE episodes since the Spotify takeover, but the UI is not my problem. My problem is Spotify trying to seize control of an open ecosystem.


I believe they said UX. to me, Spotify has always been an example of good UI, but not so for its UX

Spotify used to have this great thing where if you long-pressed a song, it’d play ~15s from the main hook. it was amazing for quickly getting the sense of a playlist or recognising a song, but they removed it because not enough people used it.

and there’s the big one everyone talks about: Radio. Spotify radio used to be fantastic. in goes a song and out comes exciting new songs, with a few you know sprinkled in. for a lot of people I know, this was why they chose spotify over anything else

then at some point the metrics will have shown that - shock! - people prefer songs they already know??? so now radio crams in as many songs you know as the genre will allow

of course the numbers show that people like what they’re already familiar with! but that’s not the point of a fucking radio


This is why Graphene OS has an auto-reboot feature. So that a device cannot be kept plugged in until an exploit like this is discovered.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: