Re: Line break on a subtitle
Am Mo., 18. März 2019 um 17:08 Uhr schrieb SoundsFromSound
:
>
> Thomas Morley-2 wrote
> > 2017-04-08 15:33 GMT+02:00 Son_V
>
> > vincenzo.auer@
>
> > :
> >> I found a lot of interesting things but sorry, I was not able to find an
> >> answer to my humble question.
> >
> >
> >
> > Whats wrong with
> >
> > \header {
> > subtitle =
> > \markup \wordwrap {
> > Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
> > eiusmod
> > tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> > veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex
> > ea
> > commodo consequat. Duis aute irure dolor in reprehenderit in
> > voluptate
> > velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint
> > occaecat
> > cupidatat non proident, sunt in culpa qui officia deserunt mollit
> > anim id
> > est laborum.
> > }
> > }
> >
> > \markup \null
> >
> > -Harm
>
> Hi Harm,
>
> On a related note:
> Can you tell me why the word-wrap works in my second instance but not the
> first? I don't understand what's going on with the markup here with the
> first going off the page. I tried removing the \with-dimensions and that
> doesn't make any difference so I can't see my error otherwise. I do see that
> the first one is enclosed in a { } expression, and *that* (I assumed) was
> part of the reason but...I'm still a bit lost as to the why.
>
> Thank you,
>
> \version "2.19.82"
>
>
> {
>
> c'1
> -\markup \wordwrap {
> \with-dimensions #'(0 . 0) #'(3 . 0)
Here you provide _one_ string, but wordwrap expects a markup-list like below.
We have wordwrap-string, though I would recommend to keep wordwrap and
change the string to a markup-list.
Basically use { ... } instead of "..."
{
c'1
-\markup
%\box for visual checking dimensions
%% adjust to taste:
\with-dimensions #'(0 . 0) #'(-8 . 3)
\override #'(line-width . 60)
\wordwrap {
This is a long text that widens the score because it can't protrude.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
}
}
Further I'd always set the line-width for wordwrap(-string) used in
TextScript, otherwise the basic line-width is used not shortened to
the available space.
Cheers,
Harm
> "This is a long text that widens the score because it can't protrude.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod"
> }
> }
>
>
> %% compared to this
>
>
> \markup \wordwrap {
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
> commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
> est laborum.
> }
>
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Line break on a subtitle
Thomas Morley-2 wrote
> 2017-04-08 15:33 GMT+02:00 Son_V
> vincenzo.auer@
> :
>> I found a lot of interesting things but sorry, I was not able to find an
>> answer to my humble question.
>
>
>
> Whats wrong with
>
> \header {
> subtitle =
> \markup \wordwrap {
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
> eiusmod
> tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
> veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex
> ea
> commodo consequat. Duis aute irure dolor in reprehenderit in
> voluptate
> velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint
> occaecat
> cupidatat non proident, sunt in culpa qui officia deserunt mollit
> anim id
> est laborum.
> }
> }
>
> \markup \null
>
> -Harm
>
> ___
> lilypond-user mailing list
> lilypond-user@
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Harm,
On a related note:
Can you tell me why the word-wrap works in my second instance but not the
first? I don't understand what's going on with the markup here with the
first going off the page. I tried removing the \with-dimensions and that
doesn't make any difference so I can't see my error otherwise. I do see that
the first one is enclosed in a { } expression, and *that* (I assumed) was
part of the reason but...I'm still a bit lost as to the why.
Thank you,
(attachment)
wrap_words_mint.png
\version "2.19.82"
{
c'1
-\markup \wordwrap {
\with-dimensions #'(0 . 0) #'(3 . 0)
"This is a long text that widens the score because it can't protrude.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod"
}
}
%% compared to this
\markup \wordwrap {
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Duis aute irure dolor in reprehenderit in voluptate
velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat
cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id
est laborum.
}
-
composer | sound designer | asmr artist
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On Mon, 18 Mar 2019, Kieren MacMillan wrote: Hi Martin, I am still not sure if this is something LilyPond should handle automatically. In which case I should report it as a bug. Does Gould talk about this situation? I’ve always been fine with the slur/stem crossing (so that the slur ends at the notehead)… but I could be convinced otherwise. I have tried to find something. There is a paragraph about Slurs in the chapter grace notes (p.129) But it does not talk about collision with stems. In the example images no collisions can be seen though. -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
Hi Martin, > I am still not sure if this is something LilyPond should handle > automatically. In which case I should report it as a bug. Does Gould talk about this situation? I’ve always been fine with the slur/stem crossing (so that the slur ends at the notehead)… but I could be convinced otherwise. Best, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
Hi again,
Sorry. The tweak you want in order to solve the problem you were having is this
one:
\repeat unfold 7 { a'8 b' \acciaccatura { c'' } \tweak extra-spacing-width
#'(-0.5 . 0) d'' e'' }
The advantages as listed in the previous email still hold. =)
Hope that helps!
Kieren.
> On Mar 18, 2019, at 9:03 AM, Kieren MacMillan
> wrote:
>
> Hi Martin,
>
>> Following up my own question. I finally found a workaround that
>> 1. prevents the collisions
>> 2. doesn't require me to drastically change my page layout and spacing.
>>
>> The collision between the acciaccatura's slur and the following stem can be
>> prevented by simply adding an invisible rest. The amount of shifting can be
>> regulated by varying the length of the invisible rest.
>
> My preference would be to use a presentation-layer (as opposed to
> content-layer) tweak:
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On Mon, 18 Mar 2019, Kieren MacMillan wrote:
Hi Martin,
% and here is my workaround to prevent the colliding acciaccatura slur:
\repeat unfold 7 { a'8 b' \acciaccatura { \tweak extra-spacing-width #'(0 .
0.5) c'' } d'' e'' }
Thanks Kieren, that's a much better solution!
But I am still not sure if this is something LilyPond should handle
automatically. In which case I should report it as a bug.
--
MT
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
Hi Martin,
> Following up my own question. I finally found a workaround that
> 1. prevents the collisions
> 2. doesn't require me to drastically change my page layout and spacing.
>
> The collision between the acciaccatura's slur and the following stem can be
> prevented by simply adding an invisible rest. The amount of shifting can be
> regulated by varying the length of the invisible rest.
My preference would be to use a presentation-layer (as opposed to
content-layer) tweak:
%%% SNIPPET BEGINS
\version "2.19.80"
\score {
\new Staff {
\override Score.SpacingSpanner.strict-grace-spacing = ##f
\time 2/4
\repeat unfold 2 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 3 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 4 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 5 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 6 { a'8 b' \acciaccatura c'' d'' e'' } \break
% and here is my workaround to prevent the colliding acciaccatura slur:
\repeat unfold 7 { a'8 b' \acciaccatura { \tweak extra-spacing-width #'(0 .
0.5) c'' } d'' e'' }
}
\layout {
indent=0
}
}
%%% SNIPPET ENDS
In addition to not mixing content with presentation (especially if you inject
this via the edition-engraver!), I think it’s more flexible and precise (since
adjustments to the exact spacing require only a numerical adjustment, rather
than a modification of the skip duration which adjusts the spacing by a
far-less-controllable amount).
Hope this helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
Hi,
Following up my own question. I finally found a workaround that
1. prevents the collisions
2. doesn't require me to drastically change my page layout and spacing.
The collision between the acciaccatura's slur and the following stem can
be prevented by simply adding an invisible rest. The amount of shifting
can be regulated by varying the length of the invisible rest.
The following version of my example shows the last line without
collisions, and without changing the number of linebreaks.
I now use this method in my real score and it works nicely.
%%%
\version "2.19.82"
\score {
\new Staff {
\override Score.SpacingSpanner.strict-grace-spacing = ##f
\time 2/4
\repeat unfold 2 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 3 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 4 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 5 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 6 { a'8 b' \acciaccatura c'' d'' e'' } \break
% and here is my workaround to prevent the colliding acciaccatura slur:
\repeat unfold 7 { a'8 b' \acciaccatura { c'' s } d'' e'' }
}
\layout {
indent=0
}
}
%%%
acciacollision2.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On Mon, 18 Mar 2019, Martin Tarenskeen wrote: gives collisions between the acciaccatura's slur and the following stem. Is such a collision OK, is it a bug I should report, and/or is it something I can/should fix with some kind of tweak? If so how? P.S. Also the \acciaccatura example in NR 1.2.6, in the "Grace notes" paragraph, shows such collisions: http://lilypond.org/doc/v2.19/Documentation/notation/special-rhythmic-concerns -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On 3/18/2019 4:38 AM, Martin Tarenskeen wrote:
On Mon, 18 Mar 2019, foxfanfare wrote:
I personally don't see that as a bug, since avoiding the collision
would make
the slur too tiny...
I am copying a score from different sources. Neither of them have
colliding slurs. The following variant of my example shows Lilypond
when a collision starts to occur:
%%%
\version "2.19.82"
\score {
\new Staff {
\time 2/4
\repeat unfold 2 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 3 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 4 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 5 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 6 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 7 { a'8 b' \acciaccatura c'' d'' e'' }
}
\layout {
indent=0
}
}
%%%
Is the collision not related to the layout? For example, what if you
just adjusted the system or measure layout for the section in question, i.e.
(see attached)
%%%
\version "2.19.82"
\score {
\new Staff {
\time 2/4
\repeat unfold 2 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 3 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 4 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 5 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 6 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 7 { a'8 b' \acciaccatura c'' d'' e'' }
}
\layout {
indent=0
system-count = 8
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Simple example with vertical spacing and dynamic contexts
Thank you very much, Ben. If this helps someone, I could use this solution
to adjust the vertical distance of the lyrics:
дꙋй -- \markup { сѧ, \transparent \draw-line #'(0 . -1) }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On Mon, 18 Mar 2019, foxfanfare wrote:
I personally don't see that as a bug, since avoiding the collision would make
the slur too tiny...
I am copying a score from different sources. Neither of them have
colliding slurs. The following variant of my example shows Lilypond when
a collision starts to occur:
%%%
\version "2.19.82"
\score {
\new Staff {
\time 2/4
\repeat unfold 2 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 3 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 4 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 5 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 6 { a'8 b' \acciaccatura c'' d'' e'' } \break
\repeat unfold 7 { a'8 b' \acciaccatura c'' d'' e'' }
}
\layout {
indent=0
}
}
%%%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
On Mon, 18 Mar 2019, Robert Blackstone wrote:
Hi Martin,
The easiest way I can think of is \stemUp for the “main notes”. But maybe this
is undesirable in the context of your score.
That will not work. There are some passages high above the staff (piano
score, upperstaff) in my score.
\version "2.19.82"
\score {
\new Staff {
\repeat unfold 8 { a'8 b' \acciaccatura c'' d'' e'' }
}
\layout {}
}
%%
gives collisions between the acciaccatura's slur and the following stem. Is
such a collision OK, is it a bug I should report, and/or is it something I
can/should fix with some kind of tweak? If so how?
I have numerous such collisions in a score I'm engraving.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
Hi Martin,
The easiest way I can think of is \stemUp for the “main notes”. But maybe this
is undesirable in the context of your score.
Best regards,
Robert Blackstone
> On 18 Mar 2019, at 08:02 , Martin Tarenskeen wrote:
>
>
> Hi,
>
> the following example:
>
>
>
> \version "2.19.82"
>
> \score {
> \new Staff {
> \repeat unfold 8 { a'8 b' \acciaccatura c'' d'' e'' }
> }
> \layout {}
> }
>
> %%
>
> gives collisions between the acciaccatura's slur and the following stem. Is
> such a collision OK, is it a bug I should report, and/or is it something I
> can/should fix with some kind of tweak? If so how?
>
> I have numerous such collisions in a score I'm engraving.
>
> --
>
> MT
>
> ___
> 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: Edition engraver verbosity
Hi Andrew, Urs, Am 17.03.19 um 13:07 schrieb Urs Liska: > Hi Andrew, > > Am 17.03.19 um 12:34 schrieb Andrew Bernard: >> Voluminous output of >> >> trying >> \break >> >> hundreds of lines. yes, this message is annoying ... >> > > OK, now I see what you mean. > > >> I just commented out the ly:message call, but I think a switch would >> be good. > > > I find the message "trying \break" pretty useless without any context > (like measure number, context and input location), so I have the > impression this is just a development debut message randomly forgotten > to be commented out. and yes, I forgot to comment it. I'll push a fix soon. > I think a switch would be good (=> should be implemented using > (getOption '(edition-engraver debug-messages)) (or any other useful > option name list). But only if the produced output is of actual use. > > Another suggestion would be to replace ly:message with oll:debug here. > What do you think, Jan-Peter? For now I'd just leave it commented out. I inserted it while coding and testing the broadcast event part. If we need that information again, it shall be an optional log message containing measure and moment. BTW I noticed some action around the EE and especially around the documentation recently - thank you very much :-) I hope that my schedule allows to take part again and to promote development soon! Best Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura collision
I personally don't see that as a bug, since avoiding the collision would make the slur too tiny... -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\acciaccatura collision
Hi,
the following example:
\version "2.19.82"
\score {
\new Staff {
\repeat unfold 8 { a'8 b' \acciaccatura c'' d'' e'' }
}
\layout {}
}
%%
gives collisions between the acciaccatura's slur and the following stem.
Is such a collision OK, is it a bug I should report, and/or is it
something I can/should fix with some kind of tweak? If so how?
I have numerous such collisions in a score I'm engraving.
--
MT
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
