3 ms·
I had a few reasons for picking Chromaprint. I was interested in building a media player with Scala (still working on that on-and-off). I noticed that Python se
by mgdigital 7y ago
I had a few reasons for picking Chromaprint. I was interested in building a media player with Scala (still working on that on-and-off). I noticed that Python seemed to be a more popular language for this type of thing and was frustrated that some key libraries I wanted to use, particularly this one, are available for Python but not on the JVM. The more I looked into Chromaprint the more it intrigued me; I wanted to understand how it works and in a way set the algorithm free as it's almost become a standard for audio identification. I found a few reimplementation attempts in other languages on GitHub but couldn't get any of them working, so I guess I saw it as a challenge, you could also call it a rabbit hole. Aside from that, I was looking for an excuse to use Scala in a project. Kotlin looks interesting too and I'll hopefully get the chance to work with it someday, I can see that it is probably easier to pick up and might be a better choice for a big team - but Scala seems more faithful to functional programming principles and I find the style more elegant.
- doh 7y agoAll makes great sense. Well good job!