musipedia.org// ?
Deutsch  English  Français  中文 
 

Logging in is required for posting.

Special forum features: inserting music notation, posting audio recordings.

All Categories > Musipedia > Musipedia General > HELP with search methods!
Total Posts: 3 - Pages (1): [1]
 Author: gilliermok
Posted: Mar 21 2011 - 10:48 PM
Subject: re: re: HELP with search methods!
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
user picture go to site Author: rt
go to link Posted: Mar 20 2011 - 11:31 AM
Subject: re: HELP with search methods!
gilliermok wrote:
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.


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.

gilliermok wrote:

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.

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


gilliermok wrote:

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.


Fixed this bug.

gilliermok wrote:

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


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.

gilliermok wrote:

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!!


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.
Author: gilliermok
Posted: Mar 20 2011 - 08:47 AM
Subject: HELP with search methods!
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!!
Total Posts: 3 - Pages (1): [1]
You must login to post a message to this conference.

How to insert music:

Add a bit of sheet music, along with a MIDI file, simply by entering note names in Lilypond syntax between the [L] and [/L] tags.
For example, you can try what happens if you enter: [l]g'4 g'4 d''4 d''4 e''4 e''4 d''2[/l] (use the Preview function if you don't actually want to post this).
You can create these lists of note names by clicking on piano keys here.

How to post an audio recording:

If you just want to sing, whistle, or play a melody so that other forum visitors can hear it, follow these steps:

  1. Record your audio here.
  2. You should notice a 32-character hash code, something like: 2a40281c5001c5a7d8c9f57fcdeccfaf
  3. copy this hash code and paste it into a forum post, enclosed in the audio tags, for example: [audio]2a40281c5001c5a7d8c9f57fcdeccfaf[/audio]

How to mark a thread as solved:

If the original question in a thread is solved, please mark it as solved using the "solved" icon (or by just typing [solved] into your post). This makes life easier for people who are willing to identify melodies, since unsolved problems are easier to spot that way. If a problem turns out to not be solved after all, just write [/solved] in a new post, and the thread will be labeled accordingly.