Author: ...and solved again:
Seems to work now. I had to update some JavaScript.
Seems to work now. I had to update some JavaScript.
|
Logging in is required for posting. |
Special forum features: inserting music notation, posting audio recordings.
Total Posts: 5 - Pages (1): [1]
Thanks for reminding me. Let's see if it is now fixed - I'll try to set this to unsolved:
good enough for me. i'll keep that in mind next time i'm transcribing somebody else's tune. :-)
BTW, the solved marker is still buggy.
BTW, the solved marker is still buggy.
w0lfie wrote:
Did the forum music search link change? I seem to remember that it used to link to a Parson's code search. Now, it does a text search using note names.
search Musipedia for this
search Musipedia for this
From what I can tell, it's trying to use the new search algorithm, but it only picks out the notes with length numbers beside them, and it throws away relative pitch. Is there some way to improve this?
...
Yes, I am now using the new search algorithm for these links. Most of the time, this should improve the results (for example, the old post with the query for "Greensleeves" can now be directly answered by clicking on the search link).
However, you are of course right to point out these problems. What happened is:
- My program expected fully specified Lilypond notes as they are generated by the melody editor. Incomplete notes like "g" were simply not recognized as Lilypond notes.
- The search program checks whether Lilypond code is really Lilypond code; if it isn't, it assumes that the user just added random search terms in the Lilypond field and does a text search instead of a melody search.
- The combination of these two things made it treat your examples as text searches, but this is of course unintended.
Now I also support the omission of octave and duration information; if it is omitted, I use the information from the previous note, or, if there is none, I assume a quarter note and the octave above middle C.
I do not fully support \relative, though, because I have to draw a line up to which I re-create Lilypond in my own programs. However, I try to degrade gracefully by completely removing the \relative statement, including the note that belongs to it. This leads to an okay interpretation of your examples, but might lead to sudden jumps by an octave or so in other cases. The obvious alternative, interpreting the Lilypond code by using Lilypond, has turned out to be too slow for something like a search where the user hopes for an immediate response.
Did the forum music search link change? I seem to remember that it used to link to a Parson's code search. Now, it does a text search using note names.
search Musipedia for this
search Musipedia for this
From what I can tell, it's trying to use the new search algorithm, but it only picks out the notes with length numbers beside them, and it throws away relative pitch. Is there some way to improve this?
search Musipedia for this
This search doesn't return the "right" song, because the entry for Mary had a Little Lamb does not have a MIDI file (yet).
Total Posts: 5 - Pages (1): [1]
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:
- Record your audio here.
- You should notice a 32-character hash code, something like: 2a40281c5001c5a7d8c9f57fcdeccfaf
- 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.