On 21 March 2010 13:08, Morten mor...@lemvigh.org wrote:
The \finger apparently ensures the correct font, but is there some command
to make it behave or position itself like a fingering instruction?
Use the 'tweaks property to override the Fingering stencil:
underlineFinger =
#(define-music
I'm trying to have underlined fingering instructions in Lilypond v.
2.12.3. - On a button accordion this would mean that the helper rows
(I don't know the English term) should be used instead of the main rows.
I've seen different posts about this, but in every case, the solution
has had to do
Hello,
as always: I just don't get it right. I want to set the fingering for the
melody above and for the bass-line below the system. But they are written
all the time above.
melody = \relative e'' {
\set fingeringOrientations = #'(up)
e4-0 f-1 g2-4 | % 1
}
bass = \relative e
fingeringOrientations = #'(down)
e-02 g-3 | % 1
}
Hope that answers your question.
Regards,
David
On 03/06/2010 02:50 PM, Hajo Dezelski wrote:
Hello,
as always: I just don't get it right. I want to set the fingering for
the melody above and for the bass-line below the system
Just use ^ or _
e4^0 or f_1 for example.
You can explicitly set it then.
Thats what I do for my Trumpet Music.
James
-Original Message-
From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of Hajo
Dezelski
Sent: Sat 06/03/2010 19:50
To: lilypond
Subject: Fingering
The disadvantage of this method is that if you change your mind later,
you have to change each f_1 to f^1, whereas if you do f-1 you can
change them all by doing \set #'fingeringOrientations
This is a good solution if you use only a few fingering orientations in
a piece.
Regards,
David
.
You can explicitly set it then.
Thats what I do for my Trumpet Music.
James
-Original Message-
From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of
Hajo Dezelski
Sent: Sat 06/03/2010 19:50
To: lilypond
Subject: Fingering Infos always above the system
Hello,
and thanks for the solutions. I see the better solution in using the
brackets. It writes the number nearer to the note but if I have something
like the example below, the numbers are written over the beams, so that they
are not readable.
\set fingeringOrientations = #'(up)
{ e' [b
.
\set fingeringOrientations = #'(up)
{ e' [b d-4 c-1] | % 1
b8 a-2 r8 d-48 | % 2 }
You can also use
\override Fingering #'add-stem-support = ##f
to get the fingering below the beam, and
\override Fingering #'staff-padding = #'()
to get the fingering inside the staff.
Nick
the fingering.
Is there a simpler way?
Nick
attachment: trillfingerslur.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
, and then tweaking it to the desired
position over the fingering.
Is there a simpler way?
You could try starting from here
{
{ b'4.^\markup{\finger 2020}^\trill-
\tweak #'outside-staff-priority #450( s8 ) } \\
e'2
}
and then tweak the positions into shape.
--
David Kastrup
://lilypond.org/doc/v2.13/Documentation/notation/common-notation-for-fretted-strings#index-right-hand-fingerings-for-fretted-instruments
it's said:
Note: There must be a hyphen after the note and a space before the closing
.
Let's say I also have a left-hand fingering, for example:
c-3 c'-14
the note and a space before the
closing .
Let's say I also have a left-hand fingering, for example:
c-3 c'-14
According to the sentence I may think this is correct:c-3\rightHandFinger #1
c'-1\rightHandFinger #4 4
That's why I think that sentence may be slightly misleading.
It took me some
Don't know if this has been thought of before (I couldn't find it in the
lilypond-user archives), but while having to do some tweaking to get
stroke fingering in one voice to avoid notes in another voice, I
realised that multiple stroke fingering indications can be attached to a
single note
Very nice!
Nick Payne wrote:
Don't know if this has been thought of before (I couldn't find it in
the lilypond-user archives), but while having to do some tweaking to
get stroke fingering in one voice to avoid notes in another voice, I
realised that multiple stroke fingering indications can
Looks like you can't have both left and right specified for fingering of
different notes in a chord. The first \set fingeringOrientations is
correctly engraved but the second isn't. Couldn't see anything in the
documentation mentioning this as a known issue:
\version 2.13.12
\relative c
Nick Payne wrote Thursday, February 04, 2010 11:11 PM
Looks like you can't have both left and right specified for
fingering of
different notes in a chord.
Correct
Couldn't see anything in the
documentation mentioning this as a known issue:
You'll find fingering is explained much more
Hi,
Running lilypond 2.12.3, I was trying:
\relative c' {
\override Fingering #'direction = #DOWN
c-5 e-3 g-1
}
expecting, but not getting the same result as:
\relative c' {
c_5 e_3 g_1
}
Can someone explain why the first example does not put all the fingering
below the notes ? Just
Martin Tarenskeen wrote Monday, January 11, 2010 11:07 AM
\relative c' {
\override Fingering #'direction = #DOWN
c-5 e-3 g-1
}
expecting, but not getting the same result as:
\relative c' {
c_5 e_3 g_1
}
Can someone explain why the first example does not put all the
fingering below
In the following example, forcing the staccato to appear below the note
also moves the fingering from immediately below the notehead to below
the staccato marking, and I haven't found a way to stop this happening
- setting Fingering #'outside-staff-priority to ##f or a negative value
doesn't
Since this:
\version 2.13.7
upper = {
b\4 e\3 gis\2 e' 4 s2
}
lower = {
s2.
}
{
\time 3/4
\new Staff \relative c'' {
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\set
Thanks Federico,
Not so much wrong, but 'doesn't match the original' ;-)
--hsm
On Fri, Dec 4, 2009 at 11:10 AM, Federico Bruni brunol...@gmx.com wrote:
Hugh Myers wrote:
Since this:
\version 2.13.7
upper = {
b\4 e\3 gis\2 e' 4 s2
}
lower = {
s2.
}
{
\time 3/4
\new
Original-Nachricht
Datum: Fri, 4 Dec 2009 11:17:18 -0700
Von: Hugh Myers hsmy...@gmail.com
An: Federico Bruni brunol...@gmx.com
CC: lilypond-user lilypond-user@gnu.org
Betreff: Re: tablature fingering (again)
Thanks Federico,
Not so much wrong, but 'doesn't match the original
...@gmail.com
An: Federico Bruni brunol...@gmx.com
CC: lilypond-user lilypond-user@gnu.org
Betreff: Re: tablature fingering (again)
Thanks Federico,
Not so much wrong, but 'doesn't match the original' ;-)
--hsm
On Fri, Dec 4, 2009 at 11:10 AM, Federico Bruni brunol...@gmx.com wrote:
Hugh
Given the nature of the guitar fret board a note like a b may be
indicated in tablature in at least two ways. For instance in this
example:
\version 2.13.7
upper = {
\times 2/3 { e,8 [ e' b ] } \times 2/3 { gis8 [ e' b ] } \times 2/3 {
b [ e b ] }
}
lower = {
s2.
}
{
\time 3/4
\new Staff
Hugh Myers wrote:
So how do I get from here to there?
reading the Notation Reference (NR), in this case
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page#Default-tablatures
Default-tablatures
--
View this message in context:
http://old.nabble.com/tablature-fingering
/user/lilypond-big-page#Default-tablatures
Default-tablatures
--
View this message in context:
http://old.nabble.com/tablature-fingering-tp2650p26567057.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond
for Fingering. So we need to set it to
something greater than 100 for the bowing commands.
Or set the Fingering's priority lower than the Script's. ;)
If a script doesn't have a default in script.scm, the engraver
allocates it a priority starting at zero, so a negative value for
the
fingering
Jan,
Fair enough the scans show your point, though there is other music I know
that has the asymmetric glyph for upbow and I do think the glyph I'm
proposing better matches the stroking on the downbow.
That matter of taste aside, the problem I'm having - while trying to typeset
chamber music
Hello,
When writing bowing marks on notes that have fingering with Lilypond, I'm
always getting the bowing mark close to the note and the fingering above
that bow mark.
Using:
d''4-2\upbow
or say
d''4^\markup { \finger 2}\upbow
This is rather atypical in my experience. Is there a way to have
John Ervin wrote Monday, September 07, 2009 10:32 PM
When writing bowing marks on notes that have fingering with
Lilypond, I'm
always getting the bowing mark close to the note and the fingering
above
that bow mark.
Using:
d''4-2\upbow
or say
d''4^\markup { \finger 2}\upbow
2009/9/7 Trevor Daniels t.dani...@treda.co.uk:
The relative positioning of script objects
is controlled by the 'script-priority property.
By default this left unspecified for most
articulations (including bowing commands) and set
to 100 for Fingering. So we need to set it to
something
Trevor,
Thanks that solved it. I just added
(script-priority . 2000)
to upbow and downbow in script.scm (which is
in \usr\share\lilypond\current\scm in my Windows installation). This now
gives the typical behavior, but my .ly files won't be as portable as they
could be.
Now if someone just knew
-Original Message-
From: lilypond-user-bounces+nick.payne=internode.on@gnu.org
[mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] On
Behalf Of Mark Polesky
Sent: Sunday, 23 August 2009 11:29 AM
To: Nick Payne; lilypond
Subject: Re: Vertifal alignment of fingering
The following puts the fingering on the d above the accent rather than
below. I've played around with various values for script-priority and
outside-staff-priority for both fingering and accent without managing to
change the order. Any suggestions on how to rearrange them to have the
fingering
Nick Payne wrote:
The following puts the fingering on the d above the accent rather than
below. I've played around with various values for script-priority and
outside-staff-priority for both fingering and accent without managing to
change the order. Any suggestions on how to rearrange them
fingering down.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
At 18:50 on 12 Aug 2009, michel.villene...@gmail.com wrote:
I don't understand why the fingering indications are up and not
down because I specified it by : \set fingeringOrientations =
#'(down) Sorry if it's a stupid question but I can't see where is my
mistake.
\set fingeringOrientations
For fingering orientation to take effect, you have to put the note inside a
chord construct . I thought we had added a warning about this. Here's what
it should look like:
\set fingeringOrientations = #'(down)
sib-34
Ok I've just added this warning about the chord construct requirement
On Wed, Aug 12, 2009 at 12:37 PM, Mark Knoop m...@opus11.net wrote:
At 18:50 on 12 Aug 2009, michel.villene...@gmail.com wrote:
I don't understand why the fingering indications are up and not
down because I specified it by : \set fingeringOrientations =
#'(down) Sorry if it's a stupid
On Wed, Aug 12, 2009 at 1:09 PM, Jonathan Kulp jonlancek...@gmail.comwrote:
On Wed, Aug 12, 2009 at 12:37 PM, Mark Knoop m...@opus11.net wrote:
At 18:50 on 12 Aug 2009, michel.villene...@gmail.com wrote:
I don't understand why the fingering indications are up and not
down because I
Yes, the construct around the note is needed. If you just have e-4 e^4
e_4, all three fingerings will appear above the notes. You need e-4 e^4
e_4.
^ and _ also work with articulations and slurs and ties. It's briefly
mentioned in s.2.2.3 of the LM as working for articulations and
On Wed, Aug 12, 2009 at 01:09:59PM -0500, Jonathan Kulp wrote:
Is the use of _ and ^ with fingerings documented anywhere? I don't remember
seeing this. It's certainly easier than using the chord angle brackets.
Fingering instructions may be manually placed above or below the
staff, see
On Thu, Aug 13, 2009 at 06:59:01AM +1000, Nick Payne wrote:
Yes, the construct around the note is needed. If you just have e-4 e^4 e_4,
all three fingerings will appear above the notes.
Really? That's odd, apparently 2.13.2 is broken.
{
c'4^3 c_2
}
gives me a 2 below the staff.
Cheers,
-
correct in thinking that you'll still have to use if you
want the
fingerings to go left or right of the note? In that case, \set
fingeringOrientations is still necessary for single notes
sometimes.
The fullest explanation of fingering is in
section 4.4.2 of the Learning Manual, which
deals
I understood. By searching lilypond fingering in Google I found the
2.9 doc page about fingering. The 2.12 doc page on this subject is
enough detailed for me (beginner point of view who managed this
evening to put fingering indications in the right place).
Thank you very much for you help
Hi,
from my privileged position of newbie ;-)
I have a suggestion for a very tiny edit in the Notation Reference
which might ease the understanding for new users.
This is the page (section Selected Snippets):
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Inside-the-staff#Fingering
-the-staff#Fingering-instructions
What is missing there, IMHO, is a clear statement like
left-hand fingerings must be entered within a chord construct
(i.e.: even single notes must be enclosed by ).
There is a similar sentence in the right-hand fingering chapter:
http://lilypond.org/doc
Selected Snippets):
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Inside-the-staff#Fingering-instructions
What is missing there, IMHO, is a clear statement like
left-hand fingerings must be entered within a chord construct
(i.e.: even single notes must be enclosed
2009/7/28 Jonathan Kulp jonlancek...@gmail.com:
The changes should
make it into the development docs in the next couple of days, if I
understand the way this works.
If only it were that simple. :)
The LSR changes won't make their way into the docs until I run
makelsr.py on the nightly docs
On Tue, Jul 28, 2009 at 2:42 PM, Neil Puttock n.putt...@gmail.com wrote:
2009/7/28 Jonathan Kulp jonlancek...@gmail.com:
The changes should
make it into the development docs in the next couple of days, if I
understand the way this works.
If only it were that simple. :)
The LSR changes
Mike,
could you post this attached as a file? I can not process it as copied
from the mail client.
2009/7/7 Mike Solomon mike...@ufl.edu:
Hey lilypond-users,
Before I put this on the LSR, please play around with this.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
I think that is EXCELLENT and certainly prettier than mine.
Which one to use depends which ones would serve the needs of a
particular score/chart better. Some performers prefer less information w/ a
textual description (ie play the G# key) whereas others prefer the graphical
representation
decimal places.
Good for guile; but any decimal expression of pi remains an
approximation.
Of course. But 14 decimal places should be enough for the fingering
chart. (: And (angle -1) is a pretty neat trick, don't you think?
- Mark
Hey lilypond-users,
Before I put this on the LSR, please play around with this.
Specifically, please
1) Make it less sprawling.
2) Find anything that's broken (the below examples work).
3) Change layout to better-suit your wind-playing needs.
4) Make any and all layout or coding suggestions.
Mike, great work!
I have some comments below
On 7/7/09 2:46 PM, Mike Solomon mike...@ufl.edu wrote:
Hey lilypond-users,
Before I put this on the LSR, please play around with this.
Specifically, please
1) Make it less sprawling.
Decrease your tab settings. Follow the indentation
Mike Solomon wrote:
Hey lilypond-users,
Before I put this on the LSR, please play around with this.
Specifically, please
1) Make it less sprawling.
2) Find anything that's broken (the below examples work).
3) Change layout to better-suit your wind-playing needs.
4) Make any and all
Caro Neil esiste anche un modo per abbreviare questo?:
\override StrokeFinger #'text = #(lambda (grob)
(markup #:center-column (#:lower 2.5 ^ (stroke-finger::calc-text
grob
Grazie!
2009/5/10 Mario Moles mario-mo...@libero.it:
Caro Neil esiste anche un modo per abbreviare questo?:
\override StrokeFinger #'text = #(lambda (grob)
(markup #:center-column (#:lower 2.5 ^ (stroke-finger::calc-text
grob
You could use identifiers, but here's a better solution, using your
2009/5/7 Mario Moles mario-mo...@libero.it:
Perdonatemi ma non so l'inglese. Provo comunque a spiegarmi.
Vorrei sapere se c'è un modo per fissare una distanza tra \markup e nota
in modo da non aggiustare nota per nota la distanza. Io uso i \markup
perchè mi servono le lettere con ^
2009/5/9 Mario Moles mario-mo...@libero.it:
Grazie mille! Ora non mi resta che mettere tutto a posto!
Grazie ancora!
You're welcome. :)
I can't bear to see somebody having to use 'extra-offset when there's
(usually) a much better solution. ;)
Regards,
Neil
2009/4/25 Nick Payne nick.pa...@internode.on.net:
This reduction seems about right to me, comparing the sizes on the normal and
grace notes:
Thanks, I've made the changes in git.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
2009/4/21 Nick Payne nick.pa...@internode.on.net:
Fingering indications on grace notes doesn't shrink to be proportional to
the reduced size of the grace note, and the full size indication looks
excessively large alongside the note. It's easy enough to override - using
\override Fingering
This reduction seems about right to me, comparing the sizes on the normal and
grace notes:
\version 2.12.2
gfsn = {
\once \override Fingering #'font-size = #-8
\once \override StringNumber #'font-size = #-8
\once \override Fingering #'padding = #0.2
\once
Fingering indications on grace notes doesn't shrink to be proportional to
the reduced size of the grace note, and the full size indication looks
excessively large alongside the note. It's easy enough to override - using
\override Fingering #'font-size = #-8 seems about right - but perhaps
2009/4/13 Nick Payne nick.pa...@internode.on.net:
Guitar stroke fingering is lower case, but with the orientation set to up,
the p is not correctly aligned with the other characters in a succession of
fingering indications, and with the orientation set to down, the i is
similarly misaligned
I find the same thing happens with guitar fingering - that sometimes the
order in which the fingering indications appear above the stave doesn't
match the pitch order of the notes they are applied to. I just use \tweak on
the fingerings to fix it.
Nick
-Original Message-
From: lilypond
Nick Payne wrote Sunday, April 12, 2009 12:10 PM
I find the same thing happens with guitar fingering - that
sometimes the
order in which the fingering indications appear above the stave
doesn't
match the pitch order of the notes they are applied to.
Do you have an example which shows
order in which the fingering indications appear above the stave doesn't
match the pitch order of the notes they are applied to.
Just to be clear, that wasn't happening for me... the order was fine,
it was just that the fingering indications in one voice were colliding
with note heads/stems
Guitar stroke fingering is lower case, but with the orientation set to up,
the p is not correctly aligned with the other characters in a succession of
fingering indications, and with the orientation set to down, the i is
similarly misaligned.
This doesn't look pleasing to the eye, and indeed
Hi everyone,
I'm having a bit of trouble fingering a chorale-like work for piano.
The upper staff has mostly two voices, and it looks best if I finger
them both above the stave. My first approach was to use \override
Fingering #'direction = #UP for the second voice, but then the
fingerings
hi
which version are you using? when i compile your code wit version 2.12.2 i
do not get collisions.
if you feel stems and fingerings are to close you could add some extraspace
with
\override Fingering #'extra-offset = #'( -0.5 . 0)
or choose the value you prefer
hth
--
View this message
On 4/11/09 9:27 AM, Gerard Neil xy...@devferret.org wrote:
So I've got two questions:
1. Can someone help me write a macro/function to make this simpler? It
would be nice to be able to write something like a^\multiFinger { 2 3
}, for example. I'm sure this is possible, but I've spent a
and fingerings are to close you could add some extraspace
with \override Fingering #'extra-offset = #'( -0.5 . 0)
Thanks very much for that, I'll give it a try.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo
2009/4/12 Carl D. Sorensen c_soren...@byu.edu:
I thought this would be easy, but it took me a while longer than I expected.
This file includes two slightly different ways of doing it:
Carl, you're a champion! Thanks! That's exactly what I was trying to
do. I'd sort of worked out that those
Is this a bug or not? The fingering indications for C and D don't sit just
above the noteheads as they do for the other notes. If I remove the slur
between those two notes, then the fingering is positioned at the desired
location. Why should a slur positioned below the notes affect the location
2009/4/7 Nick Payne njpa...@internode.on.net:
Is this a bug or not? The fingering indications for C and D don't sit just
above the noteheads as they do for the other notes. If I remove the slur
between those two notes, then the fingering is positioned at the desired
location. Why should a slur
@gnu.org
Subject: Re: Slur below note affects fingering location above note
2009/4/7 Nick Payne njpa...@internode.on.net:
Is this a bug or not? The fingering indications for C and D don't sit
just
above the noteheads as they do for the other notes. If I remove the
slur
between those two
The padding that is applied to fingering on the left when there is an
accidental is greater than when there is no accidental. From my measurements
it seems to default to 0.5 staff units from a note but 0.7 units from an
accidental, which looks odd to me. Is it possible to reduce the default
2009/3/30 Nick Payne nick.pa...@internode.on.net:
The padding that is applied to fingering on the left when there is an
accidental is greater than when there is no accidental. From my measurements
it seems to default to 0.5 staff units from a note but 0.7 units from an
accidental, which looks
-Original Message-
From: Neil Puttock [mailto:n.putt...@gmail.com]
Sent: Tuesday, 31 March 2009 07:07
To: Nick Payne
Cc: lilypond-user@gnu.org
Subject: Re: Fingering padding with accidentals
2009/3/30 Nick Payne nick.pa...@internode.on.net:
The padding that is applied
See attached. The arpeggio on the chord without the fingering is fine, and
the fingering without the arpeggio is fine, but the two together results in
a large gap appearing between the fingering/arpeggio and the notes. What I
want is the fingering just to the left of the notes and the arpeggio
This is a known bug, see
http://code.google.com/p/lilypond/issues/detail?id=556q=arpeggio
In this bug database you can also see that this is one of 258 open
issues. :-(
/Mats
Nick Payne wrote:
See attached. The arpeggio on the chord without the fingering is fine, and
the fingering without
Hi Mats,
In this bug database you can also see that this is one of 258 open
issues. :-(
I'd love to see Coda Music's open issues file for Finale... ;-)
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
Nick Payne wrote:
What I want is the fingering just to the left of the notes
and the arpeggio just to the left of the fingering.
I'm pretty sure you ought to change the order in which
these things are hung onto the side of the notes.
But I'm afraid I can't help you with that.
As regards
Thanks. That fixes the problem.
Nick
-Original Message-
From: Robin Bannister [mailto:r...@dataway.ch]
Sent: Saturday, 28 March 2009 01:31
To: Nick Payne; lilypond-user@gnu.org
Subject: Re: Problem with arpeggio across voices and fingering
Nick Payne wrote:
What I want
On 14.03.2009, at 04:48, Mark Polesky wrote:
James,
You're funneling two different
music expressions into one context,
but you've not explicitly instantiated a voice context.
…
Note that when you add
\new Voice = A
you no longer need the #'add-stem-support command.
That's rather
Is it possible to get fingerings aligned the same way when defined in
a separate variable as when defined in a different variable? i.e.:
\include deutsch.ly
\version 2.12.2
musicOne = { c'8 d' e' f' g' a' h' c'' }
musicOneFingerings= { s8-1 s-2 s-3 s-1 s-2 s-3 s-4 s-5}
musicTwo = {c'8-1 d'-2
James E. Bailey-3 wrote:
Or is it just not possible?
with Lilypond everything is possible!!!
try \override Fingering #'add-stem-support = ##t in the Staff context
--
View this message in context:
http://www.nabble.com/fingering-tp22505666p22506489.html
Sent from the Gnu - Lilypond
On 13.03.2009, at 23:56, -Eluze wrote:
James E. Bailey-3 wrote:
Or is it just not possible?
with Lilypond everything is possible!!!
try \override Fingering #'add-stem-support = ##t in the Staff
context
Awesome, thanks.
___
lilypond-user
James,
You're funneling two different
music expressions into one context,
but you've not explicitly instantiated a voice context.
See http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Creating-contexts
and
consider it as a temporary solution. I'm a visually
impaired teacher and I'm about to use LilyPond for providing fingering of
played pieces for my pupils. So as I'm a piano teacher, I'm about to bump
into fingering of chords containing seconds quite often. Every GUI notator
which supports
It would be nice if LilyPond were able to resolve every possible
fingering configuration optimally, but it is a complex problem.
Generally, the options available work pretty well, and when they
don't there is the possibility to tweak the positions of individual
fingerings to your liking. Like
Thanks, that gives me some extra ammunition to solve some fingering
problems.
Nick
-Original Message-
From: lilypond-user-bounces+nick.payne=internode.on@gnu.org
[mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] On
Behalf Of Trevor Daniels
Sent: Friday, 13
extra-offset rocks!
Thanks for the suggestions.
Dave
Trevor Daniels wrote:
It would be nice if LilyPond were able to resolve every possible
fingering configuration optimally, but it is a complex problem.
Generally, the options available work pretty well, and when they
don't
Hello,
thanks for solution. It's great to have any solution. Could anyone
please send it into LSR for future reference?
Nevertheless, I consider it as a temporary solution. I'm a visually
impaired teacher and I'm about to use LilyPond for providing fingering
of played pieces for my pupils
Hello,
let's modify slightly a snippet from NR 1.7.1, section Fingering
Instructions:
\relative c' {
\set fingeringOrientations = #'(left)
c-1 d-2 a'-54
\set fingeringOrientations = #'(down)
c-1 d-2 a'-54
\set fingeringOrientations = #'(down right up)
c-1 d-2 a'-54
\set
involving notes with accidentals, some fingerings are
displayed to the left of the accidental (good) while fingerings on notes
without accidentals are not shifted left (ugly-and sometimes results in
collisions between accidentals and fingering indications). It would be
great to be able to tell
A further problem (seems to me to qualify as a bug) is that if I have two
adjacent notes in a chord, I can't place one fingering indication to the
left and the other to the right. Up/down works ok, but left/right or
right/left places both indications on the right
(if up appears in the list), below
(if down appears), to the left (if left appears, or to the right (if right
appears). Conversely, if a location is not listed, no fingering is placed
there. LilyPond takes these constraints and works out the best placement for
the fingering of the notes
701 - 800 of 1060 matches
Mail list logo
