Hi pabuhr.
On Wed, Oct 17, 2012 at 10:48 PM, pabuhr wrote:
> I've been working on the last version of David Nalesnik's guide-finger code.
> The reason is a horizontal and vertical placement problem when the guide line
> is long and/or at a steep angle. I have managed to fix the vertical problem,
I've been working on the last version of David Nalesnik's guide-finger code.
The reason is a horizontal and vertical placement problem when the guide line
is long and/or at a steep angle. I have managed to fix the vertical problem,
but the horizontal problem has me flummoxed. The example below show
On 08/10/12 15:16, Werner LEMBERG wrote:
>> programming error: Glyph has no name, but font supports glyph naming.
>> Skipping glyph U+10002E3A, file
>> /usr/local/lilypond/usr/share/lilypond/current/fonts/otf/emmentaler-18.otf
> Uh, oh, this is a nonsense error message. There *never* exists
> U+10
> programming error: Glyph has no name, but font supports glyph naming.
> Skipping glyph U+10002E3A, file
> /usr/local/lilypond/usr/share/lilypond/current/fonts/otf/emmentaler-18.otf
Uh, oh, this is a nonsense error message. There *never* exists
U+10002E3A, since this is outside of the valid Uni
Me again--
On Sun, Oct 7, 2012 at 6:20 PM, David Nalesnik wrote:
[...]
>
> It's meant to connect fingering numbers, but you can hide the first
> number to mimic the effect of the function earlier in the thread.
> (I'm sure something could be done to this so you wouldn't need to do
> that!)
>
I
Hi again,
On Sun, Oct 7, 2012 at 6:00 PM, David Nalesnik wrote:
> Hi Nick,
>
[...]
> if you're interested simply in
> drawing lines, then there will be greater flexibility with a line
> stencil, rather than em- and en-dashes and such. I've adapted the
> function to do just that (see attached).
Hi Nick,
On Sun, Oct 7, 2012 at 4:39 PM, Nick Payne wrote:
[...]
>
> Thanks, that's very useful. I added three functions to your code which which
> take just the slope as parameter and default to using either hyphen, en
> dash, and em dash, to cater for different degrees of tightness of note
>
On 07/10/12 11:07, David Nalesnik wrote:
> Hi pabuhr,
>
> On Sat, Oct 6, 2012 at 5:21 PM, pabuhr wrote:
>
> [...]
>
>> Below is my attempt at a guide finger (which I'm sure you saw a few months
>> ago).
> http://www.mail-archive.com/lilypond-user@gnu.org/msg73509.html
>
> [...]
>
>> The problem wi
Hi Harm,
On Sat, Oct 6, 2012 at 6:20 AM, Thomas Morley
wrote:
[...]
> two month ago I created the code below (the same is attached, too).
> It is not exactly what you want, but it should give you some ideas.
Just tried this out. Very cool!
-David
Hi pabuhr,
On Sat, Oct 6, 2012 at 5:21 PM, pabuhr wrote:
[...]
>
> Below is my attempt at a guide finger (which I'm sure you saw a few months
> ago).
http://www.mail-archive.com/lilypond-user@gnu.org/msg73509.html
[...]
> The problem with my
> version is that the combined guide/finger-number
I'm using glissandos to indicate a guide finger in fingering, and in ...
Hey Nick, we certainly struggle with indicating a guide finger. 8-)
First, an observation, which I know you are already aware of, but I'll make it
anyway. It is important to differentiate between the glissando, which ma
2012/10/6 Nick Payne :
> I'm using glissandos to indicate a guide finger in fingering, and in
> most cases where there are chords, I don't want it between all the notes
> in successive chords. Can this be done without creating a separate
> hidden voice with the single notes having the glissando bet
I'm using glissandos to indicate a guide finger in fingering, and in
most cases where there are chords, I don't want it between all the notes
in successive chords. Can this be done without creating a separate
hidden voice with the single notes having the glissando between them.
e.g. in the followin
13 matches
Mail list logo
