Thanks for your informative reply, and addressing the issues I was encountering.

I'll keep trying to find this particular tune that's in my head. I'd be glad to add it if it's not in the database.... but that would be a lot easier if I knew what it was! LOL

Sorry about that. A MySQL table had crashed, making it impossible to insert new values. That's why recordings could not be stored, and no hash code could be produced.

I ran a "REPAIR TABLE", so it should work again.

The microphone search is one of the trickier methods to use, though - I suspect that success is likelier with the contour search or the Javascript keyboard search where you enter the note duration by picking different symbols (quarters, eighth notes etc.) instead of relying on the timing of hitting keys.


good point, and I should add that. This is a simple addition.




Fixed this bug.



This is not a bug but a feature. Results which are identical to your query should always be listed first; but you should not be denied results which are almost identical. After all, you might slightly misremember a contour, or it might be stored in the database with a little deviation, and such a small difference should not make it impossible to find something.

If you don't find some contour, it is most likely not in the database. But if you post it here, I can also check for you if something that should be found is maybe not found because of some bug.



Musipedia always tries to give you the closest matches first. If it does not, there are two possibilities:
1. the item is not in the database; if you happen to know it, please add it! (under "contribute")
2. or there's a bug - in that case, please give me a bug report.

Help!! I'm having a load of trouble with Musipedia. Is there something I'm missing as I use these methods?

1) Microphone -- no hash code is produced, therefore this method is useless.

2) All search methods -- there's no way to cut down the results. For example, I know a piece isn't by Mozart, but I can't filter him out.

3) Tapping a rhythm -- Each page of results is the same; for example, page 1 shows the exact same musical selections as page 8, and page 3, and page 11... So if the piece I'm looking for isn't in the first 10 (page 1), then I'll never find it using this method.

4) Contour -- The results seem full of pieces that merely *resemble* the contour I created.

5) Keyboard -- Same as contour.

6) Flash piano -- nice tool, but unless I mouse-click the keys as well as a pianist would play them, then I can't be certain the search results aren't polluted with non-matches due to my screwing up note durations.

7) All methods -- Some methods allow you to enter an additional text search parameter, but not all.


Overall, I can't tell how picky Musipedia is being when it conducts a search. It seems pretty picky when asking you to tap out a beat or play a melody on a keyboard, but then the results seem to take a lot of liberty with what you entered. Is there any way to find "closest match" using any of these methods... or am I completely misunderstanding the purpose of Musipedia in general?

Help!!