Re: Replicating chord slurs
2017-01-06 19:00 GMT+01:00 Joel C. Salomon: > On 2017-01-05 1:04 PM, Thomas Morley wrote: >> setting spanner-id via \=... has still some shortcomings. >> >> In _this_ and only this case I'd go for a complete stencil-rewrite, >> tailored at mass (every bow starts/ends at same height. > > Nice! I can see where this has its weaknesses too: it wouldn’t work if > the two chords weren’t approximately at the same height, Ofcourse, it's a special override for a special, single situation. > but it’s > perfect for this case. Thank you. > > (Now I have to make an editorial decision whether to keep this, or to > use standard LilyPond chord slurs––i.e., just one single slur curve––and > be consistent throughout the project.) > > Question about the code, though: I can kinda-sorta follow what it’s > doing, or at least I can figure out where in the reference manual to > look up the details. But whence the numbers 0, 1, 2.4, & 3.7? Are > these trial-and-error numbers? Yep. One could probably reduce them with reading out the original stencil extent, but still, at least two bows would need correction anyway, so I decided: to much work for one-time-use Btw, I didn't clean things like (- whatever 0). So follow readers have a hint where to insert custom values... And ofcourse it's all fragile like hell, but doable :) If you could friend yourself with the possibities Abraham and Davd demonstrated I'd go for it. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Replicating chord slurs
On Fri 06 Jan 2017 at 13:00:32 (-0500), Joel C. Salomon wrote: > On 2017-01-05 1:04 PM, Thomas Morley wrote: > > setting spanner-id via \=... has still some shortcomings. > > > > In _this_ and only this case I'd go for a complete stencil-rewrite, > > tailored at mass (every bow starts/ends at same height. > > Nice! I can see where this has its weaknesses too: it wouldn’t work if > the two chords weren’t approximately at the same height, but it’s > perfect for this case. Thank you. > > (Now I have to make an editorial decision whether to keep this, or to > use standard LilyPond chord slurs––i.e., just one single slur curve––and > be consistent throughout the project.) Oh, if you don't have to copy it exactly, can't you just write a tie and let LP do its own thing? Cheers, David. \language "english" \score { \relative c' { \time 3/42 4 2 4 2 4 } \layout {} } slurs.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Replicating chord slurs
On 2017-01-05 1:04 PM, Thomas Morley wrote: > setting spanner-id via \=... has still some shortcomings. > > In _this_ and only this case I'd go for a complete stencil-rewrite, > tailored at mass (every bow starts/ends at same height. Nice! I can see where this has its weaknesses too: it wouldn’t work if the two chords weren’t approximately at the same height, but it’s perfect for this case. Thank you. (Now I have to make an editorial decision whether to keep this, or to use standard LilyPond chord slurs––i.e., just one single slur curve––and be consistent throughout the project.) Question about the code, though: I can kinda-sorta follow what it’s doing, or at least I can figure out where in the reference manual to look up the details. But whence the numbers 0, 1, 2.4, & 3.7? Are these trial-and-error numbers? ––Joel C. Salomon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Replicating chord slurs
Hi, Joel! On Thu, Jan 5, 2017 at 8:38 AM, Joel C. Salomon [via Lilypond] < ml-node+s1069038n198891...@n5.nabble.com> wrote: > Neighbors, > > I’m trying to replicate the chord slurs in the attached image. This > shows the closest two versions I’ve managed (image also attached): > > \version "2.19.54" > \language "english" > > \score { > \relative c' { > \time 3/4 > <cs\=1( e!\=2( g\=3^( as\=4^(>2 > <d\=1) g\=2)\=3) b\=4)>4 > > <cs\=1( e!\=2( g\=4^( as\=3^(>2 > <d\=1) g\=2)\=3) b\=4)>4 > } > \layout {} > } > > The first has the right notes slurred together, but looks bad; the > second looks less bad, but still isn’t right. Can anyone suggest another > tweak I might try here? > A couple of thoughts for you (sorry, I'm using absolute pitch in all my examples below). From top to bottom in the original score, here's what I see: 1. as' ( b' ) 2. g' ~ g' 3. e!' ( g' ) 4. cs' ( d' ) Personally, I think this is overkill with the slurs since you really only need one from one chord to the next, two max (is this for piano?). Now that I'm looking at it a little closer, I wonder what the purpose of the slur in e'! ( g' ) is supposed to mean in the first place... You can't play it AND the tie at the same time, unless it's indicating a finger exchange or something like that. So, here's what I'd recommend: 1. If you MUST replicate the original, re-map the curves to include the tie, then adjust shapes as necessary (I think the tie is all you may need to adjust--maybe flip its direction to DOWN?): <cs'\=1_( e'!\=2_( g'^~ as'\=3^(>2 <d'\=1) g'\=2) b'\=3)>4 2. Re-notate the progression with two voices, and combine the tied g' into a single note, like so: << { g'2. } \\ { <cs' e'! as'>2 ( <d' g' b'>4 ) } >> OR << { <cs' e'! as'>2 ( <d' g' b'>4 ) } \\ { g'2. } >> depending on which order appears better to you. 3. If the tie is superfluous, then <cs' e'! g' as'>2 ( <d' g' b'>4 ) 4. If the second g' is really supposed to be sustained, then I'd do #2 and omit the g' from the second slurred chord: << { g'2. } \\ { <cs' e'! as'>2 ( <d' b'>4 } >> If I had to choose one, I'd go with #3 or #4. HTH, Abraham [image: Inline image 2] image.png (25K) <http://lilypond.1069038.n5.nabble.com/attachment/198896/0/image.png> -- View this message in context: http://lilypond.1069038.n5.nabble.com/Replicating-chord-slurs-tp198891p198896.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: Replicating chord slurs
2017-01-05 16:32 GMT+01:00 Joel C. Salomon: > Neighbors, > > I’m trying to replicate the chord slurs in the attached image. This > shows the closest two versions I’ve managed (image also attached): > > \version "2.19.54" > \language "english" > > \score { > \relative c' { > \time 3/4 > 2 > 4 > > 2 > 4 > } > \layout {} > } > > The first has the right notes slurred together, but looks bad; the > second looks less bad, but still isn’t right. Can anyone suggest another > tweak I might try here? > > ––Joel C. Salomon Hi, setting spanner-id via \=... has still some shortcomings. In _this_ and only this case I'd go for a complete stencil-rewrite, tailored at mass (every bow starts/ends at same height. \version "2.19.52" myStil = #(lambda (grob) (let* ((c-ps (ly:slur::calc-control-points grob)) (thick 0.1) (angularity 0.5) (height (/ (ly:grob-property grob 'minimum-length) 10))) (ly:stencil-add (make-bow-stencil (cons (+ (car (car c-ps)) 1) (- (cdr (car c-ps)) 0)) (cons (- (car (fourth c-ps)) 1) (- (cdr (car c-ps)) 0)) thick angularity height UP) (make-bow-stencil (cons (+ (car (car c-ps)) 1) (- (cdr (car c-ps)) 1)) (cons (- (car (fourth c-ps)) 1) (- (cdr (car c-ps)) 1)) thick angularity height UP) (make-bow-stencil (cons (+ (car (car c-ps)) 0) (- (cdr (car c-ps)) 2.4)) (cons (- (car (fourth c-ps)) 1) (- (cdr (car c-ps)) 2.4)) thick angularity height DOWN) (make-bow-stencil (cons (+ (car (car c-ps)) 0) (- (cdr (car c-ps)) 3.7)) (cons (- (car (fourth c-ps)) 1) (- (cdr (car c-ps)) 3.7)) thick angularity height DOWN mySlur = \tweak minimum-length #10 \tweak direction #UP \tweak stencil \myStil \etc \new Staff \relative c' { 2 -\mySlur ( 4) } Hopefully someone comes up with a better idea. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Replicating chord slurs
Neighbors, I’m trying to replicate the chord slurs in the attached image. This shows the closest two versions I’ve managed (image also attached): \version "2.19.54" \language "english" \score { \relative c' { \time 3/42 4 2 4 } \layout {} } The first has the right notes slurred together, but looks bad; the second looks less bad, but still isn’t right. Can anyone suggest another tweak I might try here? ––Joel C. Salomon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user