Re: subito dynamic after hairpin
On Aug 21, 2012, at 10:47 PM, Nick Payne wrote:
On 22/08/12 14:41, Curt Siffert wrote:
Hi, I am trying to make a decrescendo end in a subito dynamic
for the next note. Not sure how to make it align. I found lots
of examples online on how to shift over subito mf, but in my
case they make the decrescendo too small. I'm not actually sure
I'm going for the right solution here because I'm not 100% sure
what would be the best way to notate this. Any suggestions?
Three tries appended below.
Thanks :)
Curt
Have you had a look at
http://lsr.dsi.unimi.it/LSR/Item?id=739
or
http://lsr.dsi.unimi.it/LSR/Item?id=393
Nick
Yes. Enclosed is a much longer snippet that applies my examples and all of the above examples to my two-measure snippet. I suppose my first example, and the sixth one ("Solution #2" from the second snippet above) are closest, but none are ideal. Makes me wonder if I'm overlooking a far easier way to accomplish this?Thanks again :)Curt
Test.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: subito dynamic after hairpin
On 22/08/12 14:41, Curt Siffert wrote:
Hi, I am trying to make a decrescendo end in a subito dynamic for the
next note. Not sure how to make it align. I found lots of examples
online on how to shift over subito mf, but in my case they make the
decrescendo too small. I'm not actually sure I'm going for the right
solution here because I'm not 100% sure what would be the best way to
notate this. Any suggestions? Three tries appended below.
Thanks :)
Curt
\relativec'' {
\time3/4
d2.\mf\> |
a2-\markup{ \italic \tiny subito } d8\!\mf( e) |
R2.
d2.\mf\> |
a2 d8\!-\markup{ \italic \tiny subito } \mf( e) |
R2.
\textLengthOn
d2.\mf\> |
a2d8\!-\markup{ \italic\tinysubito \dynamicmf}( e) |
}
Have you had a look at http://lsr.dsi.unimi.it/LSR/Item?id=739 or
http://lsr.dsi.unimi.it/LSR/Item?id=393
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unwanted notation appearing on TabStaff after glissando
Which version are you using?
This problem has been fixed in the 2.15.x.
Search 'hideNotes TabStaff' in the google issue tracker (make sure to
search all issues, not just the open ones) and you'll find all the details.
hideNotes is much more handy than tags, so I think it's worth upgrading to
the latest development version (which is also a release candidate, BTW).
Il giorno 22/ago/2012 05:26, "Ben Eichler" ha
scritto:
> Hi everyone,
>
>
> I have a song I'm tabbing out using a normal staff and a TabStaff which
> has a glissando appearing in it. The glissando looks great, but on the
> TabStaff every note after it has some sort of weird dot or line over the
> top of it. This is what my code for the glissando currently looks like:
>
> \hideNotes \grace { dis32\5\glissando } \unHideNotes fis16\5 ...
>
> My StaffGroup is very simple:
>
> \new StaffGroup <<
> \new Staff {
> \clef "G_8"
> \symbols
> }
> \new TabStaff {
> \clef "moderntab"
> \symbols
> }
> >>
>
> I couldn't work out the name of the dots and lines, so I didn't know what
> to search for. Can somebody help me fix this?
>
>
> -Ben
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unwanted notation appearing on TabStaff after glissando
Ben Eichler writes:
> Hi everyone,
>
> I have a song I'm tabbing out using a normal staff and a TabStaff
> which has a glissando appearing in it. The glissando looks great, but
> on the TabStaff every note after it has some sort of weird dot or line
> over the top of it. This is what my code for the glissando currently
> looks like:
>
> \hideNotes \grace { dis32\5\glissando } \unHideNotes fis16\5 ...
The combination of \grace with property changing commands is unreliable.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unwanted notation appearing on TabStaff after glissando
You are just to good Nathan! Or maybe I'm way too novice... :S ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
subito dynamic after hairpin
Hi, I am trying to make a decrescendo end in a subito dynamic for the next
note. Not sure how to make it align. I found lots of examples online on how
to shift over subito mf, but in my case they make the decrescendo too small.
I'm not actually sure I'm going for the right solution here because I'm not
100% sure what would be the best way to notate this. Any suggestions? Three
tries appended below.
Thanks :)
Curt
\relative c'' {
\time 3/4
d2.\mf\> |
a2-\markup{ \italic \tiny subito } d8\!\mf( e) |
R2.
d2.\mf\> |
a2 d8\!-\markup{ \italic \tiny subito } \mf( e) |
R2.
\textLengthOn
d2.\mf\> |
a2 d8\!-\markup{ \italic \tiny subito \dynamic mf}( e) |
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unwanted notation appearing on TabStaff after glissando
On Tue, Aug 21, 2012 at 7:26 PM, Ben Eichler wrote:
> Hi everyone,
>
>
> I have a song I'm tabbing out using a normal staff and a TabStaff which has
> a glissando appearing in it. The glissando looks great, but on the TabStaff
> every note after it has some sort of weird dot or line over the top of it.
> This is what my code for the glissando currently looks like:
>
> \hideNotes \grace { dis32\5\glissando } \unHideNotes fis16\5 ...
>
> My StaffGroup is very simple:
>
> \new StaffGroup <<
> \new Staff {
> \clef "G_8"
> \symbols
> }
> \new TabStaff {
> \clef "moderntab"
> \symbols
> }
>>>
>
> I couldn't work out the name of the dots and lines, so I didn't know what to
> search for. Can somebody help me fix this?
>
>
> -Ben
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
I have worked very little with tablature, but it looks like \hideNotes
and \unHideNotes are causing the problem. The weirdness goes away if I
remove them. Fixing the problem is just a matter of removing these
commands from the tablature staff without removing them from the
normal one.
Tags are probably the most efficient way to do this.
%%%
symbols = {
% ...
\tag #'normal \hideNotes \grace { dis32\5\glissando } \tag #'normal
\unHideNotes fis16\5
% ...
}
\new StaffGroup <<
\keepWithTag #'normal \new Staff {
\clef "G_8"
\symbols
}
\removeWithTag #'normal \new TabStaff {
\clef "moderntab"
\symbols
}
>>
%%%
Hope this helps,
Nathan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Unwanted notation appearing on TabStaff after glissando
Hi everyone,
I have a song I'm tabbing out using a normal staff and a TabStaff which has
a glissando appearing in it. The glissando looks great, but on the TabStaff
every note after it has some sort of weird dot or line over the top of it.
This is what my code for the glissando currently looks like:
\hideNotes \grace { dis32\5\glissando } \unHideNotes fis16\5 ...
My StaffGroup is very simple:
\new StaffGroup <<
\new Staff {
\clef "G_8"
\symbols
}
\new TabStaff {
\clef "moderntab"
\symbols
}
>>
I couldn't work out the name of the dots and lines, so I didn't know what
to search for. Can somebody help me fix this?
-Ben
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: guide finger
Hi pabuhr, On Tue, Aug 21, 2012 at 4:58 PM, pabuhr wrote: >I suppose you're thinking of ly:stencil-rotate. > > Brilliant! > > Now let me see if I can reward your patience by showing you I have learned > something. :) > > The rotation needs to be along the right centre (center) so the character > appears to rotate in the middle of the finger number, which I figured out. > Also, I put in some documentation. And I generalize one step further by > allowing the ornamentation character to be passed as an argument. However, I > don't know how to write "gsc" (see below) to pass in a character or unicode to > "gx". So I still need help. That was a puzzler :) Turns out, the markup command \char takes an integer (seems obvious in retrospect...). You can see its definition in the file `define-markup-commands.scm'. So you just need to change the type predicate in gsc: % guide slope character gsc = #(define-music-function (parser location slope character fingering) (number? integer? ly:music?) (gx slope character fingering)) In order to pass the '+' character with \gsc you have to convert it to an integer: c4^\gsc #15 #(char->integer #\+) ^2 > > Also, does scheme have optional positional parameters and/or named parameters > to possibly allow more generalization, such as the padding size or putting the > ornamentation before or after the finger symbol? (Yea, I'm probably getting > carried away here. ;-) Well, you could easily pass the direction in (and whatever else) by adding another argument. You could use conditionals within the function--do this if the direction is -1, etc. (You might also be able to use the direction as a multiplier.) If you decide exactly what extras you want with the function, I'll be glad to help! Best, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Programming errors if closing beaming brace omitted
Not sure if this indicates an error in Lilypond, but if I forget the
terminating brace when using manual beaming, then the log contains
several "programming error" lines and the output contains noteheads
without stems. Here I've commented out the closing brace:
\version "2.15.43"
\relative c'' {
a8[ \grace { g16[ a] } g8 g c%]
}
and the log contains:
===
Interpreting music...
/home/nick/lilypond/examples/test.ly:4:10: warning: unterminated beam
a8
[ \grace { g16[ a] } g8 g c%]
Preprocessing graphical objects...
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
programming error: Grob direction requested while calculation in progress.
continuing, cross fingers
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
programming error: stem::length called but will not be used for beamed stem.
continuing, cross fingers
programming error: stem::length called but will not be used for beamed stem.
continuing, cross fingers
programming error: stem::length called but will not be used for beamed stem.
continuing, cross fingers
programming error: stem::length called but will not be used for beamed stem.
continuing, cross fingers
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
===
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: guide finger
I suppose you're thinking of ly:stencil-rotate.
Brilliant!
Now let me see if I can reward your patience by showing you I have learned
something.
The rotation needs to be along the right centre (center) so the character
appears to rotate in the middle of the finger number, which I figured out.
Also, I put in some documentation. And I generalize one step further by
allowing the ornamentation character to be passed as an argument. However, I
don't know how to write "gsc" (see below) to pass in a character or unicode to
"gx". So I still need help.
Also, does scheme have optional positional parameters and/or named parameters
to possibly allow more generalization, such as the padding size or putting the
ornamentation before or after the finger symbol? (Yea, I'm probably getting
carried away here. ;-)
==
\version "2.14.2"
#(define (gx slope character fingering)
;; Purpose
;; add ornamentation character before fingering symbol
;; Parameters
;; slope : angle of rotation around right centre
;; character : ornamentation character before fingering
;; fingering : fingering designation for note
;; Examples
;; (gx 0 #x2013 fingering)
;;unicode #x2011 <-> #x2015 are different length "-" punctuation
(let ((music (make-music 'FingeringEvent))
(finger (ly:music-property fingering 'digit))
(guide-char character))
(set! (ly:music-property music 'tweaks)
(acons 'stencil
(lambda (grob)
(ly:stencil-combine-at-edge
(ly:stencil-rotate (grob-interpret-markup grob (markup #:char
guide-char))
slope 1 0);; rotate "slope" around right centre
X 1;; combine stencils along X-axis on right
(grob-interpret-markup grob (number->string finger))
0.2)) ;; add padding to move guide slightly left
from finger number
(ly:music-property music 'tweaks)))
music))
% guide-neutral
gn = #(define-music-function (parser location fingering) (ly:music?)
(gx 0 #x2013 fingering))
% guide-down
gd = #(define-music-function (parser location fingering) (ly:music?)
(gx 30 #x2013 fingering))
% guide-up
gu = #(define-music-function (parser location fingering) (ly:music?)
(gx -30 #x2013 fingering))
% guide slope
gs = #(define-music-function (parser location slope fingering) (number?
ly:music?)
(gx slope #x2013 fingering))
% guide slope character
gsc = #(define-music-function (parser location slope character fingering)
(number? char? ly:music?)
(gx slope character fingering))
\relative c' {
\override Fingering #'font-size = #-2
\override Fingering #'color = #red
\set fingeringOrientations = #'(left)
4
c4^\gn^2
c4-\gn-3
c4_\gn_4
\set fingeringOrientations = #'(right)
4
r4
4
r4
c4^\gu^2
c4-\gd-3
c4_\gd_4
r4
4
r4
c4^\gs #15 ^2
c4-\gs #45 -3
c4_\gs #-45 _4
% these don't work
% r4
% 4
% r4
% c4^\gsc #15 ##x2012 ^2
% c4-\gsc #45 ##x2013 -3
% c4_\gsc #-4 ##x2014 _4
% r4
% 4
% r4
% c4^\gsc #15 '+' ^2
% c4-\gsc #45 '+' -3
% c4_\gsc #-4 '+' _4
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Waltrop meeting outline
Rodolfo Zitellini writes:
> I can confirm I will arrive from Fribourg Friday 24th at 15:21 in
> Dortmund, I still have figure out the time it will take with the U41.
See the previous posting with the travel details. You'll need a type B
local transport ticket.
> I will leave sometime in the morning of tuesday, as my plane in
> Cologne leaves at 14.44. I will be arriving by train, so if someone is
> based in Swiss or near we can arrange for the trip (or to share a car,
> as David proposed)
> I will bring my sleeping bag, should I bring a sleeping pad too?
Makes things more flexible if it has a reasonable size.
> I would like to be present all day the 24th, but I am not sure I can
> make it the 23th. One topic I think would also be nice to touch is
> promoting LilyPond and how we can valorize all the music that is in
> Mutopia (I saw, for example, that there are much of Bach's organ
> works). Also we can continue to discuss on how to speed up compiling
> music - as this is one of the first things everyone notices ("but it
> takes 40 minutes to create the book!").
People are spoiled rotten. I've had moderate success promoting
text-critical typesetting taking about that amount of time on an average
computer for a thousand-page book. The "established" process I had
problems competing with took about 8 weeks of outsourced manual labor
(people working with scissor and paper) per iteration. With
aesthetically inferior results (admittedly, at the time I did the
presentation it was more of a toss-up). What are 40 minutes?
> At last, how are we organized for the food? I love cooking, so if
> needed I will gladly give a hand.
There is not much of organization ahead. I'll start buying basic stuff
soonish. The basic provisions I'll organize in advance will likely
include substandard amounts of meat as my own expertise dealing with
meat is quite limited. I expect to haggle out the details as more
people arrive. It is a reasonable expectation that we'll order out at
some date (Sunday noonish?), barbeque, do pizza (it's rather low effort
to do dough/sauce), have noodles at one point of time.
I'll certainly be glad for people pitching in with cooking/shopping, but
one has to match the taken efforts to the number of eaters, so really
complex food preparation is likely not feasible.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Waltrop travel details
The last travel details in a nutshell: Landline is +49-2309-782756, my mobile phone +49-16092087547. Address is Im Knäppen 63, Waltrop. OpenStreetMap does not even show it while Google Maps is quite accurate. If that is a concern to you, bring your own GPS device and fix it. If you are using public transport all the way to Waltrop Elmenhorst (bus station), you'll need fares from the local transport organization VRR, available in ticket vending machines (not in advance). >From Dortmund Hbf: Einzelticket Preisstufe B, €4.90 >From Düsseldorf: Einzelticket Preisstufe D, €12.00 Those tickets are _not_ valid for high-speed trains (ICE, IC, EC, Thalys). High-speed trains don't offer relevant time savings for those connections, tickets cost about double, and _don't_ include local transport like subways and buses. Train tickets from outside of the VRR area (like from Cologne) also don't include local transport. If you are looking at the train departure tables, make sure that they are yellow (the white ones are only for arrivals usually), and don't sport a large "S" watermark (large railroad stations tend to have separate departure tables for the glacially slow S-Bahn local transport). Usable trains from Düsseldorf to Dortmund tend to be called "Regionalexpress" or "Stadtexpress" and take about an hour. Inside of Dortmund Hbf, you enter the subway U41 direction "Brambauer" and take it to its end point "Brambauer Verkehrshof", travel time 23 minutes (now is the time to call when you are arriving late or on the weekend when the bus service is spotty). >From the subway end station, you can take the Bus 284 direction "Waltrop, Am Moselbach", exiting it at "Waltrop Elmenhorst". It does not come all that often: check the schedule in case it makes more sense to get yourself picked up in Brambauer already. If the bus _is_ handy, and you consider walking after taking the bus, those last 900m will be hard to find without a map printout. Basically you walk through the street that has its dead end at the bus station, then continue right until you come to a wooden horse. You take the path there and follow it until getting to the second farm house. The wooden horse is also the waymark for people arriving by car. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: easyHeadsOn
pabuhr wrote > > > > Yes, it is possible to indirectly change the relative size of the notehead > for > easyHeadsOn by increasing the global-staff-size. However, to get the > notehead > large enough to read the letters, I had to use a value of 50, which means > there > is almost no music on a page. > > So go big or go home with easyHeadsOn! ;-) > > this link may help: http://lilypond.1069038.n5.nabble.com/Re-To-improve-lilypond-score-sheet-output-td20724.html Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/easyHeadsOn-tp131002p131036.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RH separation mark
Edward Neeman wrote
>
>
>
> How would I combine the two commands, noteText and RH, into a single
> command?
>
>
maybe with \tweak:
RH = #'((moveto -0.5 0) (lineto -1 0) (lineto -1 2))
myTweak = {
\tweak #'Y-extent #'(3 . -3)
\tweak #'padding #-0.5
\tweak #'staff-padding ##f
- \markup { \path #0.1 #RH }
}
\relative c' {
<<
{ b'4 \myTweak }
\\
{ e,2 }
>>
}
I reckon there are still other ways…
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/RH-separation-mark-tp130970p131033.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: i have a question about size
- Original Message -
From: "fabio gabbianelli"
To:
Sent: Tuesday, August 21, 2012 1:00 PM
Subject: i have a question about size
hi, i want to write a piano accompaniment. i write 2 scores, melody and
the piano score but i want the melody's size smalleri have searched in
the manual but i didn't find it
i have set the lyl file so:
\header {...
}
melody = {...
}
upper = \relative c'' {...
}
lower = \relative c {...
}
\score {
<<
\new Voice = "mel" { \autoBeamOff \melody }
\new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
>>
}
thanx!
fabio
ps: i didin't write the notes, i write just the file's structure
This should do what you want:
melody = \relative c'' { c4 d e f }
upper = \relative c'' { f4 e d c }
lower = \relative c { \clef "bass" g a b c }
\score {
<<
\new Staff \with {
fontSize = #-2
\override StaffSymbol #'staff-space = #(magstep -2)
}
\new Voice = "mel" { \autoBeamOff \melody }
\new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
>>
}
See
http://lilypond.org/doc/v2.14/Documentation/learning/length-and-thickness-of-objects
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
i have a question about size
hi, i want to write a piano accompaniment. i write 2 scores, melody and the
piano score but i want the melody's size smalleri have searched in the
manual but i didn't find it
i have set the lyl file so:
\header {...
}
melody = {...
}
upper = \relative c'' {...
}
lower = \relative c {...
}
\score {
<<
\new Voice = "mel" { \autoBeamOff \melody }
\new PianoStaff <<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
>>
}
thanx!
fabio
ps: i didin't write the notes, i write just the file's structure
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: guide finger
Hi pabuhr, On Mon, Aug 20, 2012 at 11:45 PM, pabuhr wrote: > Thank you so much. However, because "rotate" performs its rotation around the > center of the character I need to make a small adjustment. There is a > "rotation" routine allowing rotation at an arbitrary point but it appears to > be > solely for music not markups. I suppose you're thinking of ly:stencil-rotate. You can use this in the function, since the result of grob-interpret-markup is a stencil: #(define (gx rotate-guide fingering) (let ((music (make-music 'FingeringEvent)) (finger (ly:music-property fingering 'digit)) (guide-char #x2013)) (set! (ly:music-property music 'tweaks) (acons 'stencil (lambda (grob) (ly:stencil-combine-at-edge (ly:stencil-rotate (grob-interpret-markup grob (markup #:char guide-char)) rotate-guide -1 1) X 1 (grob-interpret-markup grob (number->string finger)) 0)) (ly:music-property music 'tweaks))) music)) >I tried the following change using "translate" > but there is no "translate-guide" routine, which was a guess on my part after > looking at the way "rotate" is used. I have attempted to locate a list of > these > Scheme routines but been unsuccessful. I even downloaded the GIT source for > lilypond and tried to find them there. So I have done due diligence, but I may > have done the wrong things. Can someone show me how to make translate move the > character? I can do the fine tuning of the position after that. I don't find a list of the make-...-markup formulations, and I just created make-rotate-markup as you made make-translate-markup. To express markups in Scheme in a way that is closer to ordinary input you can use the syntax detailed here (I show this below as an alternative): http://www.lilypond.org/doc/v2.15/Documentation/extending/markup-construction-in-scheme This is how to get the translation to work: #(define (gx rotate-guide fingering) (let ((music (make-music 'FingeringEvent)) (finger (ly:music-property fingering 'digit)) (guide-char #x2013)) (set! (ly:music-property music 'tweaks) (acons 'stencil (lambda (grob) (grob-interpret-markup grob ; EITHER: ;(make-concat-markup ; (list ;(make-translate-markup '(2 . 3) ;(make-rotate-markup rotate-guide (make-char-markup guide-char))) ;(number->string finger) ; OR: (markup #:concat (#:translate '(2 . 3) (#:rotate rotate-guide (#:char guide-char))) (number->string finger (ly:music-property music 'tweaks))) music)) > == > > >You might consider upgrading to one of the current development versions if >you're interested in writing functions like this. There is now quite a bit >more flexibility and power to music functions (thanks to David Kastrup). > > I am using GNU LilyPond 2.15.41 even though my files still have "\version > "2.14.2"" at the start. Again, I spent some time trying to locate scheme music > functions but was wholly unsuccessful. But I may just be searching with the > wrong magic phrases. Well, here I was meaning that it was a simple matter to keep your original formulation as a music function and call it from another music function. (See attached. This will cause errors if you try it with 2.14.2.) HTH, David finger-slide.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fingering placement problem
On Mon, Aug 20, 2012 at 08:22:53AM +1000, Nick Payne wrote:
> On 19/08/12 16:46, Nick Payne wrote:
> >In a chord containing a second, if I place the fingering above the
> >notes to avoid having the fingering numerals overlapping each
> >other (see
> >https://code.google.com/p/lilypond/issues/detail?id=2541), then
> >the numerals default to being placed much higher above the
> >noteheads than is normal or if either of the notes in the second
> >is omitted from the chord:
> >
> >\version "2.15.43"
> >
> >\relative c'' {
> >\set fingeringOrientations = #'(left)
> >\override Fingering #'staff-padding = #'()
> >\override Fingering #'add-stem-support = ##f
> >4
> >}
> >
> A similar problem happens with fingerings where the same note is
> played simultaneously on two different strings. This happens quite
> frequently when transcribing the lute music of Silvius Leopold Weiss
> for guitar:
>
> \version "2.15.43"
>
> \relative c' {
> \set fingeringOrientations = #'(down)
> \override Fingering #'staff-padding = #'()
> \override Fingering #'add-stem-support = ##f
> 4
> }
>
Thanks for the bug report, Nick.
There are several open issue trackers for fingering already but this
does seem to be a distinct problem, so I have created a new tracker:
http://code.google.com/p/lilypond/issues/detail?id=2764
Perhaps you could check the title for accuracy?
Cheers,
Colin.
--
Colin Hall
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
