How to prevent slur from breaking?
Hi.
When it comes to create slur over repeat (volta), I use this trick:
http://lilypond.org/doc/v2.19/Documentation/notation/modifying-shapes#modifying-ties-and-slurs
(see: Specifying control points explicitly)
But when slur is created just before line break, it appears also in the next
line, which of course is not what I want.
{
c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 -\tweak control-points #'((-46
. 7) (-31 . 8) (-9 . 9) (0.75 . 7)) ( ) c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1
c'1 c'1 c'1 c'1 c'1
}
How to prevent this?
--Karol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Draw line between reference point of object and its parent
Hi, this post http://www.sibeliusblog.com/tips/constrain-attachment-points-in-sibelius-and-finale/ lets me think if such a visualization might not be a good thing to have in Frescobaldi's Layout Control Options (and as a snippet in the openLilyLib repository). What this would mean is: - draw a red dot at a grob's ref-point (as we already have available) - draw a red (or different?) dot at a grob's owner's (is that right) ref-point. (I'm not completely sure if it's clear which grobs are applicable for that. It makes sense for objects that are attached to others such as an articulation or dynamic text is to a note. But we don't need note-staff or stem-notehead etc. - draw a dashed (grey) line between them. Does that look possible (OK, it's surely possible. Does that look feasible)? Is anybody interested in giving it a shot? -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Odp: How to prevent slur from breaking?
OK, so I've tried: \alterBroken transparent #'(#f #t) Slur and it works quite well. The only problem is that transparent object is still there, therefore takes space. Better solution would be: \alterBroken stencil #'(#t #f) Slur But It doesn't work... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to prevent slur from breaking?
Hi Karol,
2014-05-03 14:15 GMT+02:00 Karol Majewski karo...@wp.pl:
Hi.
When it comes to create slur over repeat (volta), I use this trick:
hmm, your example shows no repeat ...
http://lilypond.org/doc/v2.19/Documentation/notation/modifying-shapes#modifying-ties-and-slurs
(see: Specifying control points explicitly)
But when slur is created just before line break, it appears also in the next
line, which of course is not what I want.
{
c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1 -\tweak control-points
#'((-46 . 7) (-31 . 8) (-9 . 9) (0.75 . 7)) ( ) c'1 c'1 c'1 c'1 c'1 c'1
c'1 c'1 c'1 c'1 c'1 c'1 c'1 c'1
}
How to prevent this?
--Karol
It's not clear to me what you want.
Do you want the tweak applied only to the Slur form first line?
Or do you want no Slur in second line at all?
In first case use \shape as a tweak.
In second you may want to use 'omitLastBrokenSlur' as defined below.
\version 2.19.4
omitLastBrokenSlur =
\override Slur.after-line-breaking =
#(lambda (grob)
(let* ((orig (ly:grob-original grob))
(siblings (ly:spanner-broken-into orig)))
(if (and (not (null? siblings))
(equal? grob (car (last-pair siblings
(ly:grob-set-property! grob 'stencil #f
{
%\omitLastBrokenSlur
%% some crazy values :)
c'1 -\shape #'((0 . 7) (0 . 10) (0 . 1) (0 . 10))
^( %% set directions with ^ or _
\break
) c'1
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to prevent slur from breaking?
Thanks Harm! \omitLastBrokenSlur is what I need! Anathoer useful command to my collection :-) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to prevent slur from breaking?
2014-05-03 16:57 GMT+02:00 Karol Majewski karo...@wp.pl: Thanks Harm! \omitLastBrokenSlur is what I need! Anathoer useful command to my collection :-) Seems I always forget about alterBroken ... You can make it work with: #(define get-stil (lambda (grob) (let* ((function (assoc-get 'stencil (reverse (ly:grob-basic-properties grob (stil (if (procedure? function) (function grob) #f))) stil))) omitLastBrokenSlur = \alterBroken stencil #`(,get-stil #f) Slur Note a difference between both codings: My suggestion from previous mail will affect the _last_ slur-part, the code above the _second_ slur-part. Thinking of a Slur spread over three or more lines, both codings will cause different output. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Scheme tutorials follow-up
For all who have read the Scheme tutorials http://lilypondblog.org/category/using-lilypond/advanced/scheme-tutorials/ but aren't notified about comments: I have just uploaded a new solution to the task, incorporating and putting together all information and suggestions from several people's comments: http://lilypondblog.org/2014/05/local-variables-in-scheme-lilypond/#comment-37524 Best Urs -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unknown Schumann piece
On Sat, 3 May 2014, Martin Tarenskeen wrote: Hi, I have an edition of Robert Schumann's Album für die Jugend that has some pictures of his handwritten scores inside. One of the pictures shows a small but apparently unapproved pianopiece, before the first tune Melodie starts. The tune is very simple and not very interesting musically. That's probably why Schumann didn't like it and dumped it. But I couldn't resist trying to typeset it with Lilypond anyway. There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. (I will share the tune later.) Sorry, I accidentally attached the complete page, instead of just the title. See attchment. -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fermatas on last bar, snippet emits warnings
(LilyPond version 2.18.2)
This snippet:
http://lsr.di.unimi.it/LSR/Item?id=10
...work as advertized and produces two fermatas over the last bar line.
The only problem is what it emits these warnings:
document.ly:22:7: warning: Two simultaneous mark events, junking this one
\mark \markup { \musicglyph #scripts.dfermata }
document.ly:16:7: warning: Previous mark event here
\mark \markup { \musicglyph #scripts.ufermata }
I am working with the Mutopia Project, so my scripts cannot emit warnings.
Does anyone know why these warnings are printed? Or, since the output is
fine, can we stop the warnings? (I know this violates the spirit of the
no warning policy, but since we know it works...)
Knute Snortum
(via Gmail)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unknown Schumann piece
On 03.05.2014 21:54, Martin Tarenskeen wrote: On Sat, 3 May 2014, Martin Tarenskeen wrote: There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. Hi, the first word is “Für” (English: “for”) an I think the third one could be “Clavier” (“piano”). Oh, maybe “Für zwey Clavier(e)” (“for two pianos”)? That would explain the two hooks/swashes below the line (belonging to the z and y). And could also explain why this text was cancelled. Cheers, Malte ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: whole page rotated
Harm, and what if I don't want to rotate my note head along with stem-dir? How
to modify your code then? Some note heads look beeter when they are not being
rotated.
If you only want noteheads of doThin-type, try:
\version 2.18.0
#(define nhg
(lambda (grob)
(let* ((stil (ly:note-head::print grob))
(dur-log (ly:grob-property grob 'duration-log))
(nh-id-nr (if (= dur-log 2) 2 1))
(stem (ly:grob-object grob 'stem))
(stem-dir (ly:grob-property stem 'direction))
(new-note-head-stil
(grob-interpret-markup grob
(markup #:musicglyph (format #f noteheads.u~adoThin
nh-id-nr)
(ly:stencil-scale new-note-head-stil 1 stem-dir
\layout {
\context {
\Voice
\override NoteHead.stencil = #nhg
}
}
\relative c '' {
c1 c2 \repeat unfold 4 c8
\repeat unfold 64 c4
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fermatas on last bar, snippet emits warnings
Hi Knute,
On Sat, May 3, 2014 at 3:03 PM, Knute Snortum ksnor...@gmail.com wrote:
(LilyPond version 2.18.2)
This snippet:
http://lsr.di.unimi.it/LSR/Item?id=10
...work as advertized and produces two fermatas over the last bar line.
The only problem is what it emits these warnings:
document.ly:22:7: warning: Two simultaneous mark events, junking this one
\mark \markup { \musicglyph #scripts.dfermata }
document.ly:16:7: warning: Previous mark event here
\mark \markup { \musicglyph #scripts.ufermata }
I am working with the Mutopia Project, so my scripts cannot emit warnings.
Does anyone know why these warnings are printed? Or, since the output is
fine, can we stop the warnings? (I know this violates the spirit of the
no warning policy, but since we know it works...)
Well, you can suppress the warnings by including these lines in your file:
#(ly:expect-warning Previous mark event here)
#(ly:expect-warning Two simultaneous mark events, junking this one)
That's pretty awful, of course. And there's another drawback: you need to
suppress all warnings individually. So if you have another simultaneous
mark situation, you'll need to repeat these lines.
Have you seen the following link?
http://www.mail-archive.com/lilypond-user%40gnu.org/msg76333.html
I think this will give you what you need. (I think that this engraver
should be added to the codebase.)
HTH,
David
Knute Snortum
(via Gmail)
___
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: Unknown Schumann piece
Am 03.05.2014 22:20, schrieb Malte Meyn: On 03.05.2014 21:54, Martin Tarenskeen wrote: On Sat, 3 May 2014, Martin Tarenskeen wrote: There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. Hi, the first word is “Für” (English: “for”) I think this is absolutely clear. an I think the third one could be “Clavier” (“piano”). This not. (I mean it's not clear). Oh, maybe “Für zwey Clavier(e)” (“for two pianos”)? That would explain the two hooks/swashes below the line (belonging to the z and y). And could also explain why this text was cancelled. I wouldn't bet my reputation against it, but I am quite sure the second word is ganz Maybe something like Für ganz Kleine:? Would make sense in the context of op. 68, but I really can't read the last word. Urs Cheers, Malte ___ 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: whole page rotated
OK, I made it. I think I begin to understand scheme :-) #(define nhg (lambda (grob) (let* ((stil (ly:note-head::print grob)) (dur-log (ly:grob-property grob 'duration-log)) (nh-id-nr (if (= dur-log 2) 2 1)) (new-note-head-stil (grob-interpret-markup grob (markup #:musicglyph (format #f noteheads.u~adoThin nh-id-nr) new-note-head-stil))) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Odp: Left hand/right hand editorial annotation
Hi, On 2/5/14 12:47 AM, Robin Bannister wrote: Thomas Ruedas wrote: the second a fatal error, I guess that is due to compatibility issues, because the hacks seem to be several years old But the thumbBracket code still works; see the recent http://lists.gnu.org/archive/html/lilypond-user/2014-04/msg00520.html I have finally found time to try it, and yes, after conversion to the up-to-date version of Lilypond that I use it does indeed work as advertised. Thanks, Robin, for pointing me to this post and for this hack; I hope something of that sort will eventually make it into standard Lilypond. Best, Thomas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fermatas on last bar, snippet emits warnings
Wow, that's a lot of code just to get one upside-down fermata! But thanks.
That's going to do it. And I bet it will be useful in the future.
Knute Snortum
(via Gmail)
On Sat, May 3, 2014 at 1:38 PM, David Nalesnik david.nales...@gmail.comwrote:
Hi Knute,
On Sat, May 3, 2014 at 3:03 PM, Knute Snortum ksnor...@gmail.com wrote:
(LilyPond version 2.18.2)
This snippet:
http://lsr.di.unimi.it/LSR/Item?id=10
...work as advertized and produces two fermatas over the last bar line.
The only problem is what it emits these warnings:
document.ly:22:7: warning: Two simultaneous mark events, junking this one
\mark \markup { \musicglyph #scripts.dfermata }
document.ly:16:7: warning: Previous mark event here
\mark \markup { \musicglyph #scripts.ufermata }
I am working with the Mutopia Project, so my scripts cannot emit
warnings. Does anyone know why these warnings are printed? Or, since the
output is fine, can we stop the warnings? (I know this violates the spirit
of the no warning policy, but since we know it works...)
Well, you can suppress the warnings by including these lines in your file:
#(ly:expect-warning Previous mark event here)
#(ly:expect-warning Two simultaneous mark events, junking this one)
That's pretty awful, of course. And there's another drawback: you need to
suppress all warnings individually. So if you have another simultaneous
mark situation, you'll need to repeat these lines.
Have you seen the following link?
http://www.mail-archive.com/lilypond-user%40gnu.org/msg76333.html
I think this will give you what you need. (I think that this engraver
should be added to the codebase.)
HTH,
David
Knute Snortum
(via Gmail)
___
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: Unknown Schumann piece
On Sat, 3 May 2014, Urs Liska wrote:
There is just one important thing that I couldn't read in Schumann's
handwriting. It's overstroken by Schumann and in that typical 19th
century German handwriting. But maybe someone in this group is able
to
read it. See attachment.
Maybe something like Für ganz Kleine:?
Would make sense in the context of op. 68, but I really can't read the last
word.
I like that one. Until someone comes up with a better idea I'll use that one.
I have attached the tune (.pdf and .ly).
--
MT
00-unknown.pdf
Description: Adobe PDF document
\version 2.19.5
%\pointAndClickOff
\header {
title = Für ganz Kleine (?)
composer = Robert Schumann
}
rh = \relative {
c''4-.( c-.) e-.( e-.) | g( f d2) | e4-.( e-.) c-.( c-.) | d1 |
\break
c4-.( c-.) e-.( e-.) | g( f d2) | e4-.( e-.) d-.( d-.) | c1 |
\bar |.
}
lh = \relative {
\new Voice {
\voiceOne
b'2\rest e, g | b'\rest d, g | b'\rest e, g | b'\rest b, d g |
b'\rest e, g | b'\rest d, g | c e g b d g | c e1 |
}
\new Voice {
\voiceTwo
c1 | b | c | g | c | b | s | s |
}
\bar |.
}
\score {
\new PianoStaff
\new Staff \rh
\new Dynamics { s1\mf }
\new Staff \lh
\layout {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unknown Schumann piece
2014-05-04 1:38 GMT+02:00 Martin Tarenskeen m.tarensk...@zonnet.nl: On Sat, 3 May 2014, Urs Liska wrote: There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. Maybe something like Für ganz Kleine:? Would make sense in the context of op. 68, but I really can't read the last word. I like that one. Until someone comes up with a better idea I'll use that one. I have attached the tune (.pdf and .ly). Thanks Martin. I'm pretty sure that the last letter is an r... I've tried to clean your image, see enclosed. Cheers, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unknown Schumann piece
Am 04.05.2014 01:49, schrieb Pierre Perol-Schneider: 2014-05-04 1:38 GMT+02:00 Martin Tarenskeen m.tarensk...@zonnet.nl: On Sat, 3 May 2014, Urs Liska wrote: There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. Maybe something like Für ganz Kleine:? Would make sense in the context of op. 68, but I really can't read the last word. I like that one. Until someone comes up with a better idea I'll use that one. I have attached the tune (.pdf and .ly). Thanks Martin. I'm pretty sure that the last letter is an r... I've tried to clean your image, see enclosed. The second-to-last is most probably an n - compare with the second-to-last character of the second word. Then we have a clear i dot before that. With the r I'm not 100% sure - although I admit this looks quite convincing. The r in Für has a first stroke that is more distinct than in that last character. Believe it or not, I can well imagine that the last and the fourth-to-last characters are both es. I'd like to know what that stroke above/between the first two characters of the last word is. Just an arbitrary stroke? Or an apostrophe separating a letter and a word? Urs Cheers, Pierre ___ 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: Unknown Schumann piece
See http://www.youtube.com/watch?v=HMcrb-sKh5wfeature=youtube_gdata_player Regards, Mogens On 2014-05-03, at 17:26, Urs Liska u...@openlilylib.org wrote: Am 04.05.2014 01:49, schrieb Pierre Perol-Schneider: 2014-05-04 1:38 GMT+02:00 Martin Tarenskeen m.tarensk...@zonnet.nl: On Sat, 3 May 2014, Urs Liska wrote: There is just one important thing that I couldn't read in Schumann's handwriting. It's overstroken by Schumann and in that typical 19th century German handwriting. But maybe someone in this group is able to read it. See attachment. Maybe something like Für ganz Kleine:? Would make sense in the context of op. 68, but I really can't read the last word. I like that one. Until someone comes up with a better idea I'll use that one. I have attached the tune (.pdf and .ly). Thanks Martin. I'm pretty sure that the last letter is an r... I've tried to clean your image, see enclosed. The second-to-last is most probably an n - compare with the second-to-last character of the second word. Then we have a clear i dot before that. With the r I'm not 100% sure - although I admit this looks quite convincing. The r in Für has a first stroke that is more distinct than in that last character. Believe it or not, I can well imagine that the last and the fourth-to-last characters are both es. I'd like to know what that stroke above/between the first two characters of the last word is. Just an arbitrary stroke? Or an apostrophe separating a letter and a word? Urs Cheers, Pierre ___ 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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
