Re: forced \break or \pageBreak with ragged-right
Hi Michael, try: ragged-last = ##t Cheers Pierre Le mar. 2 juin 2020 à 06:13, Michael Winter via LilyPond user discussion < lilypond-user@gnu.org> a écrit : > Hello, > > Is it possible to have ragged-right = ##f but then allow a single system > to be ragged-right after a forced \break or \pageBreak? > > Any help on how to do this will be much appreciated. > > Thanks in advance. > > Michael >
forced \break or \pageBreak with ragged-right
Hello, Is it possible to have ragged-right = ##f but then allow a single system to be ragged-right after a forced \break or \pageBreak? Any help on how to do this will be much appreciated. Thanks in advance. Michael
Re: Text above a notehead or rest regardless of collisions with staff
Thanks David
On Mon, Jun 1, 2020 at 11:51 PM David Kastrup wrote:
> Paolo Prete writes:
>
> > Hello,
> >
> > is it possible to place "some text" above a notehead (or a rest)
> regardless
> > of collisions with the staff? Maybe a start could be to use the Fingering
> > object, but I don't know how to change "1" to "some text"
> >
> > {
> > \override Fingering.staff-padding = #'()
> > \stemDown
> > c'-1
> > }
>
> Well, the rather artless way of writing
>
>
> actually works.
>
> --
> David Kastrup
>
Re: Text above a notehead or rest regardless of collisions with staff
Paolo Prete writes:
> Hello,
>
> is it possible to place "some text" above a notehead (or a rest) regardless
> of collisions with the staff? Maybe a start could be to use the Fingering
> object, but I don't know how to change "1" to "some text"
>
> {
> \override Fingering.staff-padding = #'()
> \stemDown
> c'-1
> }
Well, the rather artless way of writing
{
\override Fingering.staff-padding = #'()
\stemDown
c'-\tweak text "Some text" -1
}
actually works.
--
David Kastrup
Text above a notehead or rest regardless of collisions with staff
Hello,
is it possible to place "some text" above a notehead (or a rest) regardless
of collisions with the staff? Maybe a start could be to use the Fingering
object, but I don't know how to change "1" to "some text"
{
\override Fingering.staff-padding = #'()
\stemDown
c'-1
}
Thanks!
Best,
P
Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.
On 6/1/20, Rutger Hofman wrote: > And I could contribute a bit on techniques to have >2 voices per staff, > rhythmically homophonic or rhythmically polyphonic, especially in the > context of divisi staves. That would certainly be interesting. As you can see in the patch I posted earlier in this thread, I’ve just been adding some stuff to the Notation Reference: https://gitlab.com/lilypond/lilypond/-/merge_requests/91/diffs?view=parallel There’s no “orchestral music” subsection in NR 2, like there is for guitar music, percussion etc.; I don’t think it would be wise to have one because it’s linked with numerous other sections (I could be convinced otherwise, but I’m really not sure how there’s a reasonable argument to be made here). What I’ve been doing instead is use NR 2.1.6.1 (“References for opera and stage musicals” which is the closest we have to an Orchestra subsection, and I added a link to that at the very top of NR section 2 “Specialist notation”. The other main area where we can document stuff is, obviously, NR 1.6.3 “Writing parts” (that’s where I’ve added a new subsection about \compressMMRests a few months ago). And NR 1.6.2.3 “Hiding staves”, which is what this patch addresses (on top of recent additions by Jean Abou Samra). If you have other ideas that fit well with our current structure and guidelines, don’t hesitate to chip in. > What would be the best venue for this? Lilypond docs? User list? Scores > of Beauty? If it gets into the Lilypond docs, it is there to "stay > forever" which would be nice. Sure; you’d need to take into account the most recent version though, and not what you can find on lilypond.org -- actually, I’ve just uploaded a recent doc build (that includes my patch about divisi staves) on http://lilydoc.villenave.net/Documentation/notation-big-page.html in case you want to check it out. Now, depending on what you have in mind, a blog entry might be preferable, particularly to show off large, beautiful examples. (Jean wanted a Berlioz fragment in the NR; that’s about the maximum we can afford, and even then its source code is not quoted verbatim.) On that note: > One elaborate example of my experiences is found in the score and parts > of "3 Bruchstücke aus Wozzeck" by Alban Berg, see > https://imslp.org/wiki/Wozzeck%2C_Op.7_(Berg%2C_Alban) I appreciate that you’re making available your source code, but you could simply embed it within the PDF files (LilyPond can do that now!). See for example https://imslp.org/wiki/Oboe_Concerto_No.1_in_E-flat_major_(Herschel%2C_William) (btw, I generally prefer publishing all individual parts as a single PDF; people can then print whatever they want within it, but it makes it *much* easier for ensembles out there in my experience, particularly when IMSLP starts imposing a 15-second delay for all downloads.) Cheers, -- V.
Re: Orchestral strings, how to organise score and parts for divisi, solos, desks etc.
I am thinking of sharing my experiences as a user in this field by contributing a tutorial or a practical experiences story (or whatever) on this topic. It would make a distinction between: 1) temporary staves 2) divisi allocation over groups of staves since these are different concepts, and they are handled differently by the Lilypond user, although both depend on keepAliveInterfaces. And I could contribute a bit on techniques to have >2 voices per staff, rhythmically homophonic or rhythmically polyphonic, especially in the context of divisi staves. What would be the best venue for this? Lilypond docs? User list? Scores of Beauty? If it gets into the Lilypond docs, it is there to "stay forever" which would be nice. One elaborate example of my experiences is found in the score and parts of "3 Bruchstücke aus Wozzeck" by Alban Berg, see https://imslp.org/wiki/Wozzeck%2C_Op.7_(Berg%2C_Alban) (travel to the tab [Arrangements and Transcriptions]). One can have a look at e.g. the Violins I part, mvt. 1, Bars 396-404; there is a 5-fold divisi which is folded into one staff in the full score. Or practically any instrument group, for that matter. Rutger On 5/28/20 10:33 AM, Lib Lists wrote: On Wed, 27 May 2020 at 18:10, Valentin Villenave wrote: On 5/27/20, Lib Lists wrote: merge the stems so that the final result looks like one voice. In that case, what you want clearly is \partcombine (\partCombine since 2.21). If you have more than two voices, then you can always apply another \partCombine on top of the first two voices, or use other tricks to deal with the more complex situations. I understand. Unfortunately I cannot find a way to use the remove-layer technique with \partcombine (see attached file). I'd like to hide the top staff while maintaining the staff group between bar 19-24 for the difficult passage. Is there a way to achieve this? In other words there are four notations that I'd need to achieve for divisi: unisono, divisi (a2, a3, etc.) on same voice & same staff, divisi on different voices & same staff, divisi on different staves. Finally, adding a \shortInstrumentName in the StaffGroup gives an error, but the resulting pdf is otherwise correct. instrumentName and shortInstrumentName are both siple property definitions, not variables or functions so the \ is not needed; just instrumentName = "something". That worked, thank you! Cheers, -- V.
Re: Line breaks in polymetric music
Thank you very much! A great solution! Many thanks! -S.A. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Re: Arpeggio by Dieupart
Hi Urs, hi Andrew, Thank You for Your help. The solution with openlilylib works really great! Regards Franz-Rudolf https://www.kuhnen-musik.de https://noten.kuhnen-musik.de http://www.alte-musik-am-mittelrhein.de
Re: Line breaks in polymetric music
Am Mo., 1. Juni 2020 um 12:32 Uhr schrieb Sami Amiris :
>
> A great thank you to all!
>
> I will implement these solutions to my piece. Thank you all once again!
>
> -S.A.
Hi,
here my own take of it, using David K's \at
\layout {
indent = 0\cm
ragged-last = ##f
\context {
\Score
\remove "Timing_translator"
\remove "Default_bar_line_engraver"
\remove "Metronome_mark_engraver"
}
\context {
\StaffGroup
\consists "Timing_translator"
\consists "Default_bar_line_engraver"
\consists "Metronome_mark_engraver"
}
\context {
\Voice
% Permit line breaks within tuplets
\remove "Forbid_line_break_engraver"
% Allow beams to be broken at line breaks
\override Beam.breakable = ##t
}
}
at =
#(define-music-function (time event music)
(ly:duration? ly:music? ly:music?)
"Place @var{event} at a relative duration @var{time} in relation
to @var{music}."
#{ \context Bottom << { \skip $time <>$event } $music >> #})
<<
\new StaffGroup {
\new RhythmicStaff \with { \remove "Forbid_line_break_engraver" }
{
\override TupletNumber.text = #tuplet-number::calc-fraction-text
\override TextSpanner.style = #'line
\override TextSpanner.bound-details.left.text =
\markup { \draw-line #'(0 . -1) }
\override TextSpanner.bound-details.right.text =
\markup { \draw-line #'(0 . -1) }
\override TextSpanner.bound-details.right-broken.text = ##f
\override TextSpanner.bound-details.left-broken.text = ##f
\override TextSpanner.bound-details.right.padding = #-2
\override TextSpanner.bound-details.left.padding = #-1
\override TextSpanner.bound-details.right-broken.padding = #0
\override TextSpanner.bound-details.left-broken.padding = #0
\at 2 { \break \once \set Staff.whichBar = "" }
{
\time 2/5
\scaleDurations 4/5 {
c4^\markup \tiny \italic "2 of 5:4"\startTextSpan c\stopTextSpan
}
|
\time 5/7
\scaleDurations 4/7 {
c4\startTextSpan c c^\markup \tiny \italic "5 of 7:4"
c c\stopTextSpan
}
|
}
}
}
\new StaffGroup
\new RhythmicStaff \with {\remove "Forbid_line_break_engraver"}
{
\time 4/8
\at 2*4/5 { \break \once \set Staff.whichBar = "" }
{
c16[ c16] c16[ c16] c16[ c16] c16[ c16] |
c16[ c16] c16[ c16] c16[ c16] c16[ c16] |
}
}
>>
Cheers,
Harm
Re: Line breaks in polymetric music
A great thank you to all! I will implement these solutions to my piece. Thank you all once again! -S.A. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Re: Cautionary clef collision with rest
Maybe another solution could be to reduce the clef size, e.g.:
\version "2.20.0"
\paper {
line-width = 50
}
\layout {
indent = 0
system-count = 1
}
<<
\new Staff { R2.*3 c''8 8 8 8 8 8 8 8 8 8 8 8 }
\new Staff { R2. c''4 r r c'' r r r e'' r r d'' r }
\new Staff {
\clef F \time 3/4 R2.*3
\clef G g4 r r g r r
\once\override Staff.Clef.X-extent = #'(-2 . 1)
%\once\override Staff.Clef.space-alist = #'((staff-bar extra-space . 5))
%% or:
\once\override Staff.Clef.space-alist = #'((staff-bar minimum-space .
2))
\once\set Staff.fontSize = #-1
\clef F
}
>>
Pierre
Re: Cautionary clef collision with rest
Le lun. 1 juin 2020 à 08:10, Josiah Boothby a écrit :
> Well, now at least I know of a way to move it around, but I have no
> idea what the pair of numbers for x-extent mean (and #'(-5 . 5) puts
> the clef in an even stranger place).
...
Maybe playing with other settings wil help for a better place:
http://lilypond.org/doc/v2.19/Documentation/internals/clef
E.g. :
\version "2.20.0"
\paper {
line-width = 50
}
\layout {
indent = 0
system-count = 1
}
<<
\new Staff { R2.*4 c''8 8 8 8 8 8 }
\new Staff { R2. c''4 r r c'' r r r e'' r r d'' r }
\new Staff {
\clef F \time 3/4 R2.*3
\clef G g4 r r g r r
\once\override Staff.Clef.X-extent = #'(-2 . 0)
%\once\override Staff.Clef.space-alist = #'((staff-bar extra-space . 5))
%% or:
\once\override Staff.Clef.space-alist = #'((staff-bar minimum-space .
2.2))
\clef F
}
>>
HTH
Cheers,
Pierre
Re: Line breaks in polymetric music
Hi Mark and Sami,
Basically, there can only be a line-break on a note or rest boundary. So the
approach is:
1. Decide where you want the break, say in this example halfway through the
second 4/8 bar
2. Split the note at that point into two, you will have to do the maths to make
this work. It might look like { c4*3/7 c4*4/7 }
3. Hide the second of these notes { c4*3/7 \once \hideNotes c4*4/7 }
I think it might be better to use a spacing rest instead of \hideNotes
(since the \hidden note will take up space):
c4*3/7 s4*4/7
This also has the advantage not to kill \tie's etc., and the break point
does not have to be at the exact correct position since spacer rests are
breakable.
This might even be turned into a music function:
\version "2.20.0"
brkbl =
#(define-music-function (pitch dur) (ly:pitch? ly:duration?)
(let* ((len (ly:duration-log dur))
(dotcount (ly:duration-dot-count dur))
(factor (ly:duration-scale dur))
(spacer-dur (ly:make-duration len dotcount (- 1 factor
#{
$pitch $dur
s $spacer-dur
#}))
<<
\new Staff {
% Total duration will be 4, split in two parts:
% a4*1/7 s4*6/7
\brkbl a4*1/7
a4 a
}
\new Staff \transpose c c' {
\override Beam.breakable = ##t
c8*2/7[ d e f g \bar "" \break a b]
c[ d e f g a b]
c[ d e f g a b]
}
>>
But note that this function is very primitive and does not accept chords
(it could be made to if necessary).
Re: Line breaks in polymetric music
At 07:49 on 01 Jun 2020, Sami Amiris wrote:
> Thank you for your response.
>
> I did research it and found nothing. Would you have a suggestion for
> me to look at?
Hi Sami,
Basically, there can only be a line-break on a note or rest boundary. So the
approach is:
1. Decide where you want the break, say in this example halfway through the
second 4/8 bar
2. Split the note at that point into two, you will have to do the maths to make
this work. It might look like { c4*3/7 c4*4/7 }
3. Hide the second of these notes { c4*3/7 \once \hideNotes c4*4/7 }
--
Mark Knoop
Re: Line breaks in polymetric music
Thank you for your response. I did research it and found nothing. Would you have a suggestion for me to look at? Thank you S.A. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Re: Cautionary clef collision with rest
Basically, X-extent will define the X space dimension used by the clef.
1 is the height between two lines in a staff.
Here, #'(-5 . 5) stays for 5 spaces on the left side of the clef and 5
spaces on the right side.
Too much, of course; you'll have to find the right figures according to
your score.
Cheers,
Pierre
Le lun. 1 juin 2020 à 08:10, Josiah Boothby a écrit :
> Well, now at least I know of a way to move it around, but I have no
> idea what the pair of numbers for x-extent mean (and #'(-5 . 5) puts
> the clef in an even stranger place). Looking through the documentation
> only tells me that X-extent takes two numbers, but doesn't actually
> inform me of what those numbers *do*. *headdesk*
>
> I'll tinker until I figure it out, but thanks for the pointer.
>
> On Sun, May 31, 2020 at 10:53 PM Pierre Perol-Schneider
> wrote:
> >
> > Hi Josiah,
> >
> > Maybe try:
> >
> > \version "2.20.0"
> >
> > {
> > \clef F \time 3/4
> > R2.*3
> > \clef G
> > g4 r r g r r
> > \once\override Staff.Clef.X-extent = #'(-5 . 5)
> > \clef F
> > }
> >
> > and properly set the extent.
> > HTH.
> > Cheers,
> > Pierre
> >
> > Le lun. 1 juin 2020 à 07:32, Josiah Boothby a écrit
> :
> >>
> >> I'm struggling to increase the padding for a cautionary clef in a
> >> slightly crowded line, since it's colliding with rests when there are
> >> notes on other lines. Attached is an image of the score I'm working
> >> with as I'm struggling to come up with a concise test snippet that
> >> doesn't have other problems. Should I instead adjust the measure
> >> width? I'm using 2.20.0.
> >>
> >> Thank you,
> >>
> >> Josiah
>
>
Re: Cautionary clef collision with rest
Well, now at least I know of a way to move it around, but I have no
idea what the pair of numbers for x-extent mean (and #'(-5 . 5) puts
the clef in an even stranger place). Looking through the documentation
only tells me that X-extent takes two numbers, but doesn't actually
inform me of what those numbers *do*. *headdesk*
I'll tinker until I figure it out, but thanks for the pointer.
On Sun, May 31, 2020 at 10:53 PM Pierre Perol-Schneider
wrote:
>
> Hi Josiah,
>
> Maybe try:
>
> \version "2.20.0"
>
> {
> \clef F \time 3/4
> R2.*3
> \clef G
> g4 r r g r r
> \once\override Staff.Clef.X-extent = #'(-5 . 5)
> \clef F
> }
>
> and properly set the extent.
> HTH.
> Cheers,
> Pierre
>
> Le lun. 1 juin 2020 à 07:32, Josiah Boothby a écrit :
>>
>> I'm struggling to increase the padding for a cautionary clef in a
>> slightly crowded line, since it's colliding with rests when there are
>> notes on other lines. Attached is an image of the score I'm working
>> with as I'm struggling to come up with a concise test snippet that
>> doesn't have other problems. Should I instead adjust the measure
>> width? I'm using 2.20.0.
>>
>> Thank you,
>>
>> Josiah
