![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
This feels nice to my fingers as I'm falling asleep (though interrupting the falling-asleep process to transcribe it undid the progress I'd managed to make towards falling asleep):
![[guitar lick, bottom three strings, first position]](https://p2.dreamwidth.org/f6c7147d77a3/109641-84329/www.kempt.net/~glenn/lj/20071210.0455.png)
(I didn't explicitly notate them as such, but assume any slur that can be played as a hammer-on or a pull-off is to be played that way. And there's a subtle lengthening of the fourth note that I didn't want to take the time to sort out how to notate precisely lest I wind up too awake for too long by the time I did so.)
I had to write it down because I want to use it in something later (well, most of it -- I'm not sure whether I'll keep the endings) and stuff that falls out of my fingertips as I'm nodding off is too likely to escape recall later. Now to try again on that falling-asleep thang.
(no subject)
There's no need to notate bits of rubato; someone else playing the tune wouldn't do it exactly the same way anyway.
(no subject)
I'm still playing with ways to make music auto-format to the width of the browser window (or the relevant CSS region of the window). Best would be a nearly universally installed plug-in that rendered from ABC on the fly and gave the viewer controls for zooming and maybe other formatting tweaks (maybe even a play-as-MIDI button), but first the plug-in needs to be written and then enough people have to decide it's worth installing ...
Another thing I've tried in the past is a separate image for each measure, so the browser will just line-wrap the row of images at display time (this means no clef and key signature at the start of lines other than the very first, but most folks could deal with that, right?). The trouble with that one is that chopping up an image of a score by hand is tedious, and I haven't figured out how to automate it with ImageMagick yet because ledger lines affect vertical spacing, which causes problems getting adjacent measures to line up correctly if they originally came from different lines.
The other idea I had was to use SVG as my image format and specify the height and width attributes of the IMG tag in percents, but it turns out not enough browsers support SVG well yet, and the ones that I tried that displayed SVG at all truncated the image instead of scaling it (so what's the point of the 'S' in SVG then?). If I could get SVG to work, then I'd 'merely' need to either write a PS->SVG converter or modify the back end of my favourite ABC engraving tool to generate SVG instead of PS directly.
So for now I try to guess at a legible size for most folks, and try to guess whether I need to tuck it behind a cut-tag to avoid breaking their layout or having to scroll horizontally to read the rest of their friends-pages.
As for not notating the rubato: good point. You're right.
(no subject)