lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A question for the wise with brains or those who just used it for a


From: Carl Sorensen
Subject: Re: A question for the wise with brains or those who just used it for a while and know :)
Date: Fri, 14 May 2021 14:18:22 +0000
User-agent: Microsoft-MacOutlook/10.10.1b.201012


On 5/14/21, 7:05 AM, "darkijah@jesusgod-pope666.info" 
<darkijah@jesusgod-pope666.info> wrote:

<snip>
    
    The Half note of cause is should still be a half note or half break, I 
    just don't want it taking precious space like that, that is nonsense in 
    my view. I like how they did it in the old days without concern of such 
    things. I just want it nice spread out really, the lower notes I would 
    like to get a little more room as well. Like mixing the new with the 
    old, the best of both worlds :)
 
If you want to make every note take up the space of an eighth note, you can 
scale the durations.

Instead of e2, use e2*1/4
    
You can do the same for rests.
   
<snip>

    g4^
         \markup
         \center-column { " " " "
         \override #'(size . 0.5) % 1 standard
         \override #'(thickness . 0.1) % 0.1 standard
         \woodwind-diagram #'flute #'((cc . (one two three))(lh . ())(rh . 
    ()))
    }

If you want to make this process easier, you can define an alist with the flute 
diagrams, one entry per pitch.  It will be a big alist, but you only have to do 
it once.

You can then define a music function (call it fluteNotes) that will take a 
sequence of notes, and return the notes with the flute diagrams attached as 
markups.  It's possible that Harm (Thomas Morely) or Aaron Hill might even 
write the music function for you, as they seem to like this kind of programming 
challenge.

So then you could do something like

\new \Staff {
  \fluteNotes {g'4 e'2 d'4}
}

And you would automatically get the notes with the flute diagrams attached.  I 
think this is the easiest way for you to get the automatic flute diagrams you 
want.

If  you are willing to do some more work  (and you seem to have the right kind 
of programming mindset to do it), and you'd like to make it easier for both 
yourself and others in the future, you might define a FluteDiagrams context, 
similar to the current FretBoards context.  Then, instead of doing markups, 
you'd just pass the notes to both the Staff and FluteDiagrams contexts, and 
everything would work out automatically.

I hope this helps give you some ideas.

Carl
   


reply via email to

[Prev in Thread] Current Thread [Next in Thread]