Picked one of these up last week. Sending it back this week. Had I known the current state of the Android tablet experience, I would have been more upset when ChromeOS lost the Pixel team.
They really shouldn't stop, because CoreAudio is a mess and their commitment to professional audio has plummeted since they switched over to x86-64 architecture.
I put together iago[1] a little while back, from a few people's work, including a great article[2] by Hot Cashew on how he uses Emscripten to transpile the Ogg/Vorbis library to javascript.
Willingness to discuss and critically evaluate ideas no matter who they come from, rather than blindly following people off a cliff due to fame, is a critically useful skill.
Sadly, so is recognizing when you're working with a person who wants that and when you're working with someone whose ego and unwillingness to admit mistakes thrives on blind followers. Mistaking the former for the latter can be a career-limiting moment.
Thanks! re: corner frequency, ha, yeah I maybe oversimplified the example code a bit. That code will, however, work, because the Web Audio API specifies a default frequency of 350Hz ( http://webaudio.github.io/web-audio-api/#attributes-17 ). You can also dig into the source code of the page for the code that makes the audio examples happen (search for "click", which will give you the click handlers).
I think we'll circle around and try again in a less naive way :)
Thanks! I think the answer is that it would fall down pretty hard if the tempo started varying, the reason being that the algorithm seeks out interval modes instead of averages, with only a little wiggle room.
In the testing section, the songs that we fail to identify correctly are usually those we couldn't get a "handle" on in the form of identifying common intervals. A varying tempo would exacerbate that problem.
Additionally, the question becomes: what is the tempo of a song that has an inconsistent tempo?
