Glissando avoid accidental bug?
Regardless of whether I set the end-on-accidental override to true or
false, or omit it completely, the glissandi don't stop short of the
accidental.
\version "2.17.5"
\relative c'' {
\accidentalStyle "modern"
\override Glissando #'(bound-details right end-on-accidental) = ##t
c1\glissando cis\glissando c
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: increase vertical space
2012/10/31 Eluze :
> Thomas Morley wrote
>> or
>>
>> if you want to affect only a single line of the score, use
>>
>> \overrideProperty #"Score.NonMusicalPaperColumn"
>> #'line-break-system-details #'((alignment-distances . (30)))
>>
>> see also:
>> http://lilypond.org/doc/v2.16/Documentation/notation-big-page#explicit-staff-and-system-positioning
>>
>> Please note that the Syntax for that will probably change soonish.
>>
>> Example:
>>
>> \version "2.16.0"
>>
>> musI = \relative c' {
>> \repeat "unfold" 6 { c4 d e f }
>> \break
>> \overrideProperty #"Score.NonMusicalPaperColumn"
>> #'line-break-system-details #'((alignment-distances . (30)))
>> \repeat "unfold" 38 { c4 d e f }
>> \bar "|."
>> }
>>
>> musII = \relative c' {
>> \repeat "unfold" 44 { c4 d e f }
>> }
>>
>> \score {
>> <<
>> \new Staff \musI
>> \new Staff \musII
>> >>
>> }
>
> crazy! I didn't know about that!
>
> great!!! (or + xxx)
>
> Eluze
Well, \overrideProperty is rarely used.
You're able to make some very crazy things with it, but trying to make
the layout of a larger score, is incredible troublesome. I did this
once and I will *_never_* repeat it.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar numbers for broken measures
2012/10/20 Eluze : > Thomas Morley wrote >> how about adding it to the LSR, commenting the 2.16-part? >> Or extend >> http://lsr.dsi.unimi.it/LSR/Item?id=559 >> ? >> >> modulo-bar-number-visible >> works in 2.14.2 already, but is not documented, AFAIK. >> At least it would be nice to have it in the LSR. >> >> first-bar-number-invisible-save-broken-bars >> and >> first-bar-number-invisible-and-no-parenthesized-bar-numbers >> are ofcourse 2.16-stuff, but why not adding them commented? > > done (several procedures to print different bar numbering rules) - I think > one day we'll have to review all the snippets dealing with bar numbering... > > as always I'm not sure if I did the LSR addition correctly - please feel > free to change it in any way! > > Eluze Hi Eluze, approved! Some minor changes added. http://lsr.dsi.unimi.it/LSR/Item?id=854 @Phil This is tagged Doc. Regards, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: increase vertical space
Thomas Morley wrote
> or
>
> if you want to affect only a single line of the score, use
>
> \overrideProperty #"Score.NonMusicalPaperColumn"
> #'line-break-system-details #'((alignment-distances . (30)))
>
> see also:
> http://lilypond.org/doc/v2.16/Documentation/notation-big-page#explicit-staff-and-system-positioning
>
> Please note that the Syntax for that will probably change soonish.
>
> Example:
>
> \version "2.16.0"
>
> musI = \relative c' {
> \repeat "unfold" 6 { c4 d e f }
> \break
> \overrideProperty #"Score.NonMusicalPaperColumn"
> #'line-break-system-details #'((alignment-distances . (30)))
> \repeat "unfold" 38 { c4 d e f }
> \bar "|."
> }
>
> musII = \relative c' {
> \repeat "unfold" 44 { c4 d e f }
> }
>
> \score {
> <<
> \new Staff \musI
> \new Staff \musII
> >>
> }
crazy! I didn't know about that!
great!!! (or + xxx)
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/increase-vertical-space-tp135579p135609.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: increase vertical space
Thomas Morley writes: > if you want to affect only a single line of the score, use > > \overrideProperty #"Score.NonMusicalPaperColumn" > #'line-break-system-details #'((alignment-distances . (30))) > > see also: > http://lilypond.org/doc/v2.16/Documentation/notation-big-page#explicit-staff-and-system-positioning > > Please note that the Syntax for that will probably change soonish. "soonish" meaning in about an hour if you are working with the latest development version checked out from master. The change consists in _having_ to write at least \overrideProperty Score.NonMusicalPaperColumn . #'line-break-system-details #'((alignment-distances . (30))) instead and optionally being able to write \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details.alignment-distances #'(30) which is arguably simpler. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: increase vertical space
Hi Peter,
2012/10/30 Eluze :
> Hi,
>
> Peter O'Doherty-2 wrote
>> Is it possible to increase the space between staves, to avoid clashing,
>> for specific systems, i.e. not the whole piece?
>
> as a general rule you can override the behavior of all specific contexts
> (like Staff, Voice,…) in the \layout section.
>
> to override the behavior in just one staff you can specify eg.
>
> \new Staff \with {\override NoteHead #'color = red } {…your music…}
>
> for your purpose I would think that
>
> \new Staff \with {
> \override VerticalAxisGroup #'staff-staff-spacing = #'(
> (basic-distance . 2)
> (minimum-distance . .5)
> (padding . .5)
> (stretchability . 55)
> )
> }
>
> with adapted numbers could help!
>
> Eluze
or
if you want to affect only a single line of the score, use
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-distances . (30)))
see also:
http://lilypond.org/doc/v2.16/Documentation/notation-big-page#explicit-staff-and-system-positioning
Please note that the Syntax for that will probably change soonish.
Example:
\version "2.16.0"
musI = \relative c' {
\repeat "unfold" 6 { c4 d e f }
\break
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details #'((alignment-distances . (30)))
\repeat "unfold" 38 { c4 d e f }
\bar "|."
}
musII = \relative c' {
\repeat "unfold" 44 { c4 d e f }
}
\score {
<<
\new Staff \musI
\new Staff \musII
>>
}
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Function for rendering key textually in 3 languages
shutterfreak wrote > Hi all, > > I'd like to have a function to translate a key signature into the > textual representation of that key in 3 languages. > > For instance, I'd write this in my score: > > and the rendering would look like this: > > The logic I'm trying to implement, is (in pseudo-code): > 1. key format = > > [ > > ] > 2. IF > > is lowercase THEN key is minor ELSE key is major. > 3. If accidentals are added, they pertain to the key name > > How should I proceed? I guess you should use some scheme code to - create those translations/associations (a table?) - concatenate the 3 translated elements - include them in your LilyPond code if you feel this could be of general interest you should file an enhancement request. hth Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Function-for-rendering-key-textually-in-3-languages-tp135474p135606.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: increase vertical space
Hi,
Peter O'Doherty-2 wrote
> Is it possible to increase the space between staves, to avoid clashing,
> for specific systems, i.e. not the whole piece?
as a general rule you can override the behavior of all specific contexts
(like Staff, Voice,…) in the \layout section.
to override the behavior in just one staff you can specify eg.
\new Staff \with {\override NoteHead #'color = red } {…your music…}
for your purpose I would think that
\new Staff \with {
\override VerticalAxisGroup #'staff-staff-spacing = #'(
(basic-distance . 2)
(minimum-distance . .5)
(padding . .5)
(stretchability . 55)
)
}
with adapted numbers could help!
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/increase-vertical-space-tp135579p135605.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: Lyrics Vertical Alignment
On Tue, 30 Oct 2012 21:07:09 +0100 Reinhold Kainhofer wrote: > On Di., 30. Okt. 2012 19:35:42 CET, Tiresia GIUNO > wrote: > > > But shouldn't be: "The syllable > > should be ranged _right_ under the first notehead"? > > No, ranged left means that the left of the syllable is aligned with > the left of the note (i.e. left-aligned). > http://www.paratype.com/help/term/terms.asp?code=286 > > Cheers, > Reinhold. OK, sorry for my stupid question... I understand now. Thanks a lot, TG ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics Vertical Alignment
On Di., 30. Okt. 2012 19:35:42 CET, Tiresia GIUNO wrote: > But shouldn't be: "The syllable > should be ranged _right_ under the first notehead"? No, ranged left means that the left of the syllable is aligned with the left of the note (i.e. left-aligned). http://www.paratype.com/help/term/terms.asp?code=286 Cheers, Reinhold. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics Vertical Alignment
On Tue, 30 Oct 2012 01:23:30 +0100 Reinhold Kainhofer wrote: > On 2012-10-30 00:46, Tiresia GIUNO wrote: > > is there any reason why Lyrics on the two staves in the attached > > example is not correctly vertical aligned? > > Yes, there is a reason. See e.g. Elaine Gould: Behind Bars -- The > Definitive Guide to Music Notation (published by Faber Music, 2011), > p.439, section "Syllable underlay" > The syllable should be ranged left under the first notehead. This > draws the eye to the right - an important consideration, since the > singer always needs to be looking forward. > Since lilypond cannot determine automatically that your case might be > that very exception mentioned in the last sentence, it simply uses > the default: centering the syllable to the single note in the first > staff and left-aligning with the note in the second staff, since > there the syllable is assigned to more than one note. > > Cheers, > Reinhold Thank you very much for your explanation. I understand the sense of that "misalignment" in order to align the syllable according to the melody more than to the single note. But shouldn't be: "The syllable should be ranged _right_ under the first notehead"? Thank you again, TG ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is it possible to change beaming from the \layout block?
Thomas Morley wrote Tuesday, October 30, 2012 10:16 AM > 2012/10/30 Reinhold Kainhofer : >> On 2012-10-30 02:12, Vaughan McAlley wrote: >>> >>> This code compiles without complaint, but the beams are still in >>> groups of four. What am I doing wrong? >> >> Nothing. The \time 4/4 command implicitly sets all the timing properties, so >> your global values are overwritten and don't have any effect. > Are you sure? The \time command sets only baseMoment and beatStructure; beamExceptions remains unaffected, other than selecting the rules applicable to the time signature, which may earlier have been overridden. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pitch name transpose into numeric per key signature
The code below is a "mix" of the code you gave and this snippet. I forget \include "english.ly" (It's was the original language) -- Gilles ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is it possible to change beaming from the \layout block?
2012/10/30 Reinhold Kainhofer :
> On 2012-10-30 02:12, Vaughan McAlley wrote:
>>
>> This code compiles without complaint, but the beams are still in
>> groups of four. What am I doing wrong?
>
>
> Nothing. The \time 4/4 command implicitly sets all the timing properties, so
> your global values are overwritten and don't have any effect.
>
> Cheers,
> Reinhold
Are you sure?
The following examples seem to work:
% example 1:
\version "2.17.4"
upper = \relative c'' {
\time 4/4
c8 c c c c c c c
}
lower = \relative c' {
\time 4/4
c8 c c c c c c c
}
\score {
\new Staff {
<<
\new Voice { \voiceOne \upper }
\new Voice { \voiceTwo \lower }
>>
}
\layout {
\context {
\Voice
beamExceptions =
#'((end . (((1 . 8) . (2 2 2 2)
}
}
}
% example 2:
\version "2.17.4"
myNotes = \relative c' {
\time 4/4
d8 d d d d d d d
}
\score {
\new Staff = "RH" <<
\context Staff <<
\new Voice { \myNotes }
>>
>>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
\context {
\Voice
baseMoment = #(ly:make-moment 1 8)
beatStructure = #'(2 2 2 2)
beamExceptions = #'()
}
}
}
%
Regards,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
Dear Thomas,
thanks, I think, this will be a good solution for me!
2012/10/30 Thomas Morley
> 2012/10/29 Stefan Thomas :
> [...]
> > The problem is:
> > I would like to have a score with drumstaff and a "normal" staff. And
> only
> > in the normal Staff shall be a wider time signature.
> > I give you an short example:
> [...]
>
> Hi Stefan,
>
> next try:
>
> I defined `customTime´ containing all functionality of \time and
> printing a wider TimeSignature in DrumStaff only.
> Disadvantage:
> It has to be used _in_ the DrumStaff or, if used in a global-variable,
> this \global has to be applied to the DrumStaff.
> This makes the Devnull-context dispensable. If Devnull is part of some
> included template, `customTime´ will produce weird output. To avoid
> it, uncomment the \layout in the code below.
> -> http://lists.gnu.org/archive/html/lilypond-user/2012-10/msg00654.html
>
> \version "2.16.0"
>
> % \layout {
> % \context {
> % \Devnull
> % \alias "DrumStaff"
> % }
> % }
>
> customTime =
> #(define-music-function (parser location baseline-skip beat-structure frac)
> (number? (number-list? '()) fraction?)
> (let* ((num (car frac))
> (denom (cdr frac)))
> #{
> \override DrumStaff.TimeSignature #'stencil =
>#(lambda (grob)
> (grob-interpret-markup grob
> #{
> \markup %\fontsize #5
> \vcenter
> \override #`(baseline-skip .
> ,baseline-skip)
> \column {
> \number
> #(number->string num)
> \number
> #(number->string denom)
> }
> #}))
>$(make-music
>'TimeSignatureMusic
>'beat-structure beat-structure
>'denominator denom
>'numerator num)
> #}))
>
> % test
>
> global = {
> \customTime #3 #'(4 3) 7/8
> s2..
> \customTime #3 #'(2 2 2 3) 9/8
> s8*9
> }
>
> drumnotes = \drummode {
> wbl4 wbl wbh4.
> \repeat "unfold" 3 { wbl4 } wbh4.
> }
> somenotes = \relative c' {
> c4 b c4 d8
> e4 e f e8 d c
> }
> \score {
> <<
> %\new Devnull \global
> \new Staff \somenotes
>
> \new DrumStaff \with {
> \override StaffSymbol #'line-count = #6
> }
> << \global \drumnotes >>
> >>
> }
>
> For now this is the best I can deliver, I didn't manage to find a
> scheme-accessable definition for the formating of the
> default-TimeSignature.
> There _are_ formating-procedures in time-signature-settings.scm, but
> they are used in `compoundMeter´ only.
>
>
> Regards,
> Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: exact dimenions of pdf/png
Peter Van Kranenburg writes:
> On 10/29/12 6:13 PM, David Kastrup wrote:
>> writing
>> \paper { paper-width=110\mm }
>> \score { { c4 c4 c4 c4 } }
>> and using
>> lilypond -dresolution=1200 --png
>> I get an image with 5197 pixels width, which is to a pixel exactly what
>> was demanded. So perhaps you need to check what throws a spanner in
>> your works, starting from a simple paper definition.
>>
>
> Thank you for your suggestion.
>
> Invoking 'lilypond -dresolution=1200 --png' results in the right
> dimensions, indeed. Thanks. I will use this. The image is not cropped
> automatically, so I now have to tune the page-height as well. And I
> have to set a small margin for the curly bracket of the
> PianoStaff. Otherwise it would be off the page.
>
> The usage manual however (section 4.4) tells me to do this:
> lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png
> -dresolution=1200 figure.ly
> That results in a png that is too wide. There seems another mechanism
> at work to determine size of resulting image. Cropping?
I seem to remember some slop added for the sake of the manual or
something. Werner?
I have no idea why the more complex options would be recommended here:
when converting to PNG anyhow, it would seem quite irrelevant to me
which fonts are getting embedded or not in the intermediate EPS file.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: exact dimenions of pdf/png
On 10/29/12 6:13 PM, David Kastrup wrote:
writing
\paper { paper-width=110\mm }
\score { { c4 c4 c4 c4 } }
and using
lilypond -dresolution=1200 --png
I get an image with 5197 pixels width, which is to a pixel exactly what
was demanded. So perhaps you need to check what throws a spanner in
your works, starting from a simple paper definition.
Thank you for your suggestion.
Invoking 'lilypond -dresolution=1200 --png' results in the right
dimensions, indeed. Thanks. I will use this. The image is not cropped
automatically, so I now have to tune the page-height as well. And I have
to set a small margin for the curly bracket of the PianoStaff. Otherwise
it would be off the page.
The usage manual however (section 4.4) tells me to do this:
lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png
-dresolution=1200 figure.ly
That results in a png that is too wide. There seems another mechanism at
work to determine size of resulting image. Cropping?
Thanks,
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
increase vertical space
Hi, Is it possible to increase the space between staves, to avoid clashing, for specific systems, i.e. not the whole piece? If so could you please point me in the direction of the help page? Many thanks, Peter -- //= -> Peter O'Doherty -> http://www.peterodoherty.net -> m...@peterodoherty.net -> https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dynamics positioning
On 10/29/2012 04:52 PM, m...@mikesolomon.org wrote: I had to take a break from LilyPond development for a couple months but I hope to be back on board in a month or so. This was the exact problem that I was working on. The long and short of it is that LilyPond does not know how to handle cross-staff objects in vertical spacing. As a result, there are collisions. There is no good way to get around this save manually overriding things like Y-offset or, if necessary, extra-Y-offset. Cheers, MS Okay. Thanks everyone for your help. Best, Peter -- //= -> Peter O'Doherty -> http://www.peterodoherty.net -> m...@peterodoherty.net -> https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: enlarge vertical distance in time signature
pabuhr writes: >Other than that (same with denom), the code looks fine to me. > > Works! However, (and there is always a however ;-), the font and font > size are not the same as the regular (default) time signature. \number $(number->string num) -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
