Author: Hello,
some of the issues you mentioned were indeed caused by introducing the new Flash piano, but some things I could not reproduce.
However...I put a new melody, then tried searching for it, and a) when entering a search melody it seems only non-relative lilypond mode works, plus you can't use flats, which is a bit annoying and...
Did you try placing a check mark next to "Use flat signs instead of sharp signs"?
b) it couldn't find my melody. I first deliberately searched for it transposed both in pitch and duration (all notes at double the length I added it), and 10 pages of results, but the melody I just put in wasn't there. Then I tried it exactly as I put it in (r8 g'16 c''16 e''8 e''8 d''8 ais'8 d''8 e''8 / flats not sharps) - and it still didn't find it...lastly I tried including some search terms (name of artist and name of song), but it returned no results at all. The only thing that worked was ONLY searching on the name of the artist, with no notes specified at all.
I can't reproduce this - for example an augmented version is found with no problem:
search Musipedia for this
Further, while the flash piano entry looks very nice, it's pretty useless without having the ability to delete and using lilypond notation directly. But it's the default when editing a search, and when switching to the javascript version, you lose your original search.
Still...I like the idea, hope to see it improved in the future.
The Flash piano is useful for quickly entering a query without having to think too hard, and it looks flashy. I am trying to reduce the "bounce rate" (the percentage of visitors who stumble upon Musipedia but look only at the very first page they found) by putting the easiest query method on the front page. Once you know what you are doing, the Lilypond piano might indeed be better, and that has the features you are requesting.
I fixed the problem you mentioned: if you now click on "Edit Query" at the beginning of a result list, you can actually edit the query with the Javascript piano. When I quickly added the Flash piano yesterday, I did not consider the fact that this page was the target page for the "Edit Query" button, which of course lead to the loss of the query. I hope this is the problem you meant?
Cheers,
Rainer
some of the issues you mentioned were indeed caused by introducing the new Flash piano, but some things I could not reproduce.
wizofaus wrote:
However...I put a new melody, then tried searching for it, and a) when entering a search melody it seems only non-relative lilypond mode works, plus you can't use flats, which is a bit annoying and...
Did you try placing a check mark next to "Use flat signs instead of sharp signs"?
wizofaus wrote:
b) it couldn't find my melody. I first deliberately searched for it transposed both in pitch and duration (all notes at double the length I added it), and 10 pages of results, but the melody I just put in wasn't there. Then I tried it exactly as I put it in (r8 g'16 c''16 e''8 e''8 d''8 ais'8 d''8 e''8 / flats not sharps) - and it still didn't find it...lastly I tried including some search terms (name of artist and name of song), but it returned no results at all. The only thing that worked was ONLY searching on the name of the artist, with no notes specified at all.
I can't reproduce this - for example an augmented version is found with no problem:
search Musipedia for this
As is a transposed and augmented version:
search Musipedia for this
Could it be that you entered a query that was longer than the piece you put into the database?
"r8 g'16 c''16 e''8 e''8 d''8 ais'8 d''8 e''8" is, for example, more than what you added to the database. Maybe you are right, and items which are shorter than the query should be returned too, if they are similar to part of the query.
wizofaus wrote:
Further, while the flash piano entry looks very nice, it's pretty useless without having the ability to delete and using lilypond notation directly. But it's the default when editing a search, and when switching to the javascript version, you lose your original search.
Still...I like the idea, hope to see it improved in the future.
The Flash piano is useful for quickly entering a query without having to think too hard, and it looks flashy. I am trying to reduce the "bounce rate" (the percentage of visitors who stumble upon Musipedia but look only at the very first page they found) by putting the easiest query method on the front page. Once you know what you are doing, the Lilypond piano might indeed be better, and that has the features you are requesting.
I fixed the problem you mentioned: if you now click on "Edit Query" at the beginning of a result list, you can actually edit the query with the Javascript piano. When I quickly added the Flash piano yesterday, I did not consider the fact that this page was the target page for the "Edit Query" button, which of course lead to the loss of the query. I hope this is the problem you meant?
Cheers,
Rainer