I have found a strange corner case which partCombine doesn't handle
correctly. I ran into it setting a complex orchestral score, but I've
narrowed down the demonstration to something more reasonably sized.
In this example, I have to do the known workaround in bar 2 of adding
invisible grace notes
Hello Thomas,
in your case using a with block is definitely the best option. One can also
solve such issues by adding a skip column before the main beat like this
\new Staff << {\set Staff.instrumentName = #"abc" \grace s} \new Voice \grace c
c >>
which can be useful with stuff like tempo in a
Thank you David for this lesson, I appreciate it a lot.
Thomas
> Am 16.02.2022 um 18:50 schrieb David Kastrup :
>
> Thomas Scharkowski writes:
>
>> Grace note at the beginning makes instrumentName disappear:
>> macOs 12.1
>> LilyPond 2.23.6
>>
>> --
>> \version "2.23.6"
>>
>> GraceVoice = \n
Thomas Scharkowski writes:
> Grace note at the beginning makes instrumentName disappear:
> macOs 12.1
> LilyPond 2.23.6
>
> --
> \version "2.23.6"
>
> GraceVoice = \new Voice
> {
> \grace
> c'8 b4
> }
>
> GraceStaff = \new Staff
> <<
> \set Staff.instrumentName = "Grace"
> \GraceVoice
Greetings Thomas,
In the case of grace notes, the instrumentName must be placed in a \with block.
GraceStaff = \new Staff \with {
instrumentName = #"Grace"
}
<<
\GraceVoice
>>
Not sure if the curly and angled braces work exactly the same way,
because I haven't done this with variables, but
Grace note at the beginning makes instrumentName disappear:
macOs 12.1
LilyPond 2.23.6
--
\version "2.23.6"
GraceVoice = \new Voice
{
\grace
c'8 b4
}
GraceStaff = \new Staff
<<
\set Staff.instrumentName = "Grace"
\GraceVoice
>>
\score {
\GraceStaff
}
NoGraceVoice = \new Voice
{
Hello Erik,
As I said, this is not a solution but just a demonstration, and it abuses the
Accidental grob to place the embellishment. This means you’ll need to force an
Accidental on the embellished note by doing a!.
@Lukas: As I said, this is just a demonstration, and it is doing very shady
t
in Petzel"
Aan: "Lukas-Fabian Moser" ; "lilypond-user@gnu.org"
CC: "E Appeldoorn"
Verzonden: 26-12-2021 20:35:28
Onderwerp: Re: possible bug?
Hello Erik,
I think the behaviour you want is for some sort of embellishment which
basically is handled similar
Am 26.12.21 um 20:35 schrieb Valentin Petzel:
Hello Erik,
I think the behaviour you want is for some sort of embellishment which
basically is handled similar to some sort of articulation.
The appended file is in an extremely hacky demonstration of how one could
implement something like, thoug
Moser"
> Aan: "E Appeldoorn" ; "lilypond-user@gnu.org"
>
> Verzonden: 25-12-2021 20:44:22
> Onderwerp: Re: possible bug?
>
> >And one addition:
> >>I did try the options you then gave me. (context \score \override
> >>SpacingSpanner.
For what it's worth, strict-note-spacing et al. are
known to have some quirks. The corresponding issues are
https://gitlab.com/lilypond/lilypond/-/issues/2630
https://gitlab.com/lilypond/lilypond/-/issues/4493
https://gitlab.com/lilypond/lilypond/-/issues/4499
Regards,
Jean
t;Lukas-Fabian Moser"
Aan: "E Appeldoorn" ; "Hans Aikema"
; "lilypond-user@gnu.org"
Verzonden: 25-12-2021 21:14:18
Onderwerp: Re: possible bug?
Hi Erik,
Just showing one other bar that looks suddenly awfull with strict
spacing
<<
\new Staff \relat
Hi Erik,
Just showing one other bar that looks suddenly awfull with strict spacing
<<
\new Staff \relative c'' {
es4-- r8
\tuplet 5/4 {f32([ ges as ges f)]}
es8^.[ \acciaccatura {a} bes^!] es,4-- |
}
>>
Thanks, that really is not desirable.
The \newSpacingSection command also introducing
being a bug.
PS I did not expect to get stuck, but it seems that the end result in
this score leaves to be desired.
-- Origineel bericht --
Van: "Lukas-Fabian Moser"
Aan: "E Appeldoorn" ; "lilypond-user@gnu.org"
Verzonden: 25-12-2021 20:44:22
Onderwer
And one addition:
I did try the options you then gave me. (context \score \override
SpacingSpanner.strict-note-spacing = ##t and also \override
Score.SpacingSpanner.strict-grace-spacing = ##t)
The relationship between those two settings is not at all obvious from
the documentation:
https:/
While the strict note spacing does solve the problems lilypond throws up
during this bar it does create a load more along the way in other bars.
Just showing one other bar that looks suddenly awfull with strict
spacing
<<
\new Staff \relative c'' {
es4-- r8
\tuplet 5/4 {f32([ ges as ges f)]
> On 25 Dec 2021, at 18:59, E Appeldoorn wrote:
>
> HI all and merry christmas
>
> A couple of weeks ago I had a question about a spacing problem I have in a
> score. After many trials that did not solve anything I'm coming to the
> conclusion that there might be a bug with the \appoggiatura
What would be the correct way to engrave this? Space the 4 16ths
evenly, put the two 8ths above their corresponding 16ths and squeezing
the appoggiatura notes in? What if there's not enough place left for
them - should the 16ths then be spaced further apart (evenly) until it
fits? Even if th
Hi Erik,
Am 25.12.21 um 18:59 schrieb E Appeldoorn:
I have created a complete bare minimum of a trial, one bar, two voices.
While that's much closer to a minimal example than your previous
examples, it's still far from being a bare minimum. That would be
something like:
\version "2.22"
<<
HI all and merry christmas
A couple of weeks ago I had a question about a spacing problem I have in
a score. After many trials that did not solve anything I'm coming to the
conclusion that there might be a bug with the \appoggiatura and the
\acciaccatura. I did try the options you then gave me
Am So., 31. Jan. 2021 um 16:38 Uhr schrieb Davide Bonetti
:
> Thanks again (and sorry for the bad english)
I'm not aware of any bad english, well, apart from my own ...
Cheers,
Harm
Thomas Morley writes:
> Am So., 31. Jan. 2021 um 13:59 Uhr schrieb Davide Bonetti
> :
>> we know that accordion register symbols works as markup and also as a
>> music function.
>>
>> One can put accordion symbols everywhere in a markup block, but if you
>> try to put accordion symbol in a title
Thanks Harm for the workaround.
As you pointed it works only putting
#(use-modules (scm accreg))
in every header where is needed, so in a book with multiple scores it's
a quite tedious.
I think accordion registers is the only markup that need use-modules.
Is there a way to get rid of use-modu
Am So., 31. Jan. 2021 um 13:59 Uhr schrieb Davide Bonetti
:
>
> Hi!
>
> we know that accordion register symbols works as markup and also as a
> music function.
>
> One can put accordion symbols everywhere in a markup block, but if you
> try to put accordion symbol in a title section this leads to
Hi!
we know that accordion register symbols works as markup and also as a
music function.
One can put accordion symbols everywhere in a markup block, but if you
try to put accordion symbol in a title section this leads to an error:
\version "2.22.0"
#(use-modules (scm accreg))
\score {
If any of the interfaces for MultiMeasureRests (e.g. rest-interface,
spanner-interface, multi-measure-rest-interface) are included in
keepAliveInterfaces (useful if you want to condense some systems in a
score, but not others), then when an MMR occurs on either side of a system
break it can cause s
Hi Malte,
> That sounds like a really special case: MarkLine context AND hidden Staff AND
> this staff contains notes (why is it hidden then?) AND Y-offset is set AND
> extra-spacing-width is set …
That "really special case" includes >50% of my choral writing, which comprises
>50% of my compos
It's not that special of a case. Hiding a staff containing notes and using
a MarkLine are normal techniques for managing a large ensemble score.
>From property-init.ly:
markLengthOn = {
\override Score.MetronomeMark.extra-spacing-width = #'(0 . 1.0)
\override Score.RehearsalMark.extra-spacing
Am 28.12.18 um 04:54 schrieb Saul Tobin:
When using a context like MarkLine for tempo marks, if the staff
immediately below the MarkLine is hidden but contains rhythmic activity,
and if BOTH Y-offset and extra-spacing-width are overridden for
MetronomeMark, the first rhythmic column will st
Happy holidays all,
Below is a demonstration of an odd behavior I noticed.
When using a context like MarkLine for tempo marks, if the staff
immediately below the MarkLine is hidden but contains rhythmic activity,
and if BOTH Y-offset and extra-spacing-width are overridden for
MetronomeMark, the f
As it happens, I'm doing a 200 page string quartet at the moment and every
page and every part is full of slurs like this, that end and start on a
single note. In this case it is to indicate the pulsing of the phrase and
repeated notes in particular - and in case this is obscure, it is mentioned
in
Sorry for chiming in:
I can't see that it this can really be regarded as a bug. Ending one
slur and beginning another on the same note is not normal usage - in
fact, I don't really know what it is supposed to mean. How does this
meaning differ from having a single slur over all 5 notes? Will the
Hi Aaron,
> Would something like the following be of any help?
Oh! Almost certainly. Looking forward to testing it out.
Thanks!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
__
On 2018-11-16 4:24 pm, Kieren MacMillan wrote:
[ . . . ]
Kieren,
Would something like the following be of any help?
\version "2.19.82"
#(define (contract-control-points coords amount)
(let* ((x-coords (map (lambda (coord) (car coord)) coords))
(orig-left (apply min x-coords))
Hi David,
> I am irritated that \shape applies \once automatically.
I seem to recall there are a couple of other functions which do so as well
(though I don’t currently recall what they are).
Would it be a good idea to standardize the codebase such that functions never
apply \once automaticall
Kieren MacMillan writes:
> Hi,
>
>> On Nov 16, 2018, at 6:29 PM, Flaming Hakama by Elaine
>> wrote:
>> % I'm not sure how to do this globally, but the normal \shape
>> command can be made to work.
>> slurTweak = { \shape #'((0.3 . 0) (0 . 0) (0 . 0) (-0.3 . 0)) Slur }
>
> Yes, this (with 0.2 in
Hi David,
> Seems like I have been overselling what is there.
> […] Sorry for the confusion.
No worries.
It’s a bit of a relief, actually: I would have been disappointed to find I’ve
been reinventing wheels!
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website:
Hi,
> On Nov 16, 2018, at 6:29 PM, Flaming Hakama by Elaine
> wrote:
> % I'm not sure how to do this globally, but the normal \shape command can be
> made to work.
> slurTweak = { \shape #'((0.3 . 0) (0 . 0) (0 . 0) (-0.3 . 0)) Slur }
Yes, this (with 0.2 instead of 0.3) is perfect for my use
Kieren MacMillan writes:
> Hi David,
>
>>> Well, in this case, I’m engraving a Schenker graph… so I doubt
>>> anyone will be playing it. ;)
>> LilyPond has its own functions for Schenker graphs.
>
> To which functions in particular are you referring?
>
> I’ve slowly been building a SchenkerLily
Hi David,
>> Well, in this case, I’m engraving a Schenker graph… so I doubt anyone will
>> be playing it. ;)
> LilyPond has its own functions for Schenker graphs.
To which functions in particular are you referring?
I’ve slowly been building a SchenkerLily framework over the last few years, and
Kieren MacMillan writes:
> Hi David,
>
>> I can't see that it this can really be regarded as a bug. Ending one
>> slur and beginning another on the same note is not normal usage - in
>> fact, I don't really know what it is supposed to mean. How does this
>> meaning differ from having a single slu
> -- Forwarded message --
> From: Kieren MacMillan
> To: Lilypond-User Mailing List
> Date: Fri, 16 Nov 2018 16:55:36 -0500
> Subject: controlling the tie "gap" [and a possible bug?]
> Hi all,
>
> On my setup (Mac OS X, Lilypond 2.19.80), the cod
Hi David,
> I can't see that it this can really be regarded as a bug. Ending one slur and
> beginning another on the same note is not normal usage - in fact, I don't
> really know what it is supposed to mean. How does this meaning differ from
> having a single slur over all 5 notes? Will the me
-Original Message-
From: Kieren MacMillan
To: David Kastrup
CC: Lilypond-User Mailing List
Subject: Re: controlling the tie "gap" [and a possible bug?]
Date: Fri, 16 Nov 2018 17:11:17 -0500
Hi David,
> No, it doesn't. The image shows the same kind of symptomas the
Hi David,
> As I did say: the image shows the same kind of sympton as the code does
> but is clearly from different code, having a bar line between fourth and
> fifth note.
Ah. Must have had the old code (with barline) in my clipboard when I pasted it.
Sorry/thanks.
> It does beg the question w
Kieren MacMillan writes:
> Hi David,
>
> No, it doesn't. The image shows the same kind of symptom
>
> as the code does but is clearly from different code.
>
> Hmmm… I just compiled it again, and it gave the same thing. Here’s a
> screenshot from Frescobaldi with the code on the left and compil
Hi David,
> No, it doesn't. The image shows the same kind of symptom
> as the code does but is clearly from different code.
Hmmm… I just compiled it again, and it gave the same thing. Here’s a screenshot
from Frescobaldi with the code on the left and compiled image on the right:
What am I sa
Kieren MacMillan writes:
> Hi all,
>
> On my setup (Mac OS X, Lilypond 2.19.80), the code
>
> \version "2.18.2"
> \fixed c'' { e4*4/5( d c)( d e) }
>
> gives
>
> *
No, it doesn't. The image shows the same kind of symptom as the code
does but is clearly from different code.
> 1. Is the crossing
Hi all,
On my setup (Mac OS X, Lilypond 2.19.80), the code
\version "2.18.2"
\fixed c'' { e4*4/5( d c)( d e) }
gives
1. Is the crossing of the ties a bug?
2. Regardless, is there a way I can make all ties to begin a little bit further
to the right and end a little further to the left of the
Thanks Thomas and Kieran,
That work-around works perfectly, without uncommenting the " %\override
Dynamics.PianoPedalBracket #'shorten-pair = #'(0 . -1) " line
(then, there's no need of the trial-and-error method mentioned by Kieran).
I tested it on 2.21.0
I don't understand yet if the default be
Hello Kieren,
sorry to insist again but IMHO this is a bug. Look at the snippet below:
all the objects are aligned to the shifted NoteColumn. Only the pedal is
not aligned.
There's no reason for which it has not to be aligned, and this forces to
apply work-arounds in order to put the end of the br
2018-03-24 17:19 GMT+01:00 paolo prete :
> Hello,
>
> as you can see from the below snippet, the bracket of the sustain pedal is
> not properly extended when the last note is shifted.
> Is this a bug? Is there a way to fix it or a work-around ?
Iiuc, the PianoPedalBracket is left/right bound by Pa
Hi Paolo,
> IMHO this is a bug.
Feel free to submit it to the bug list!
Best regards,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailin
Hi Paolo,
> Sorry to insist: there's no way to put the end of the bracket at the wanted
> note.
%%% SNIPPET BEGINS
\version "2.19.80"
\language "english"
\score {
{
\once \override Score.PianoPedalBracket.shorten-pair = #'(0 . -11.1)
c'\sustainOn c' \once \override NoteColumn #'X-offse
(possible bug?)
Mark,
unfortunately, using \new Dynamics for the pedal line doesn't seem to solve the
issue...
2018-03-24 18:37 GMT+01:00 Mark Stephen Mrotek mailto:carsonm...@ca.rr.com> >:
Paolo,
It is possible to input pedal markings with \new Dynamics. This is what I
gt; I am trying to see how it would work with you example.
>
>
>
> Mark
>
>
>
> *From:* paolo prete [mailto:paoloprete...@gmail.com]
> *Sent:* Saturday, March 24, 2018 10:25 AM
> *To:* Mark Stephen Mrotek
> *Cc:* lilypond-user Mailinglist
> *Subject:* Re: Sust
Cc: lilypond-user Mailinglist
Subject: Re: SustainPedal on shifted notes (possible bug?)
Sorry to insist: there's no way to put the end of the bracket at the wanted
note.
In the snippet below, I want to end the bracket at the note " f' &
Sorry to insist: there's no way to put the end of the bracket at the wanted
note.
In the snippet below, I want to end the bracket at the note " f' "
Is this a bug?
%%
\score {
{
c'\sustainOn c' \once \override NoteColumn #'X-offset = 10
f'\sustainOff
r4\break
I suspect this is a bug. Please see my previous snippet...
2018-03-24 18:22 GMT+01:00 Mark Stephen Mrotek :
> Welcome, Paolo
>
>
>
> “overriding” is out of my knowledge.
>
> Someone else might.
>
>
>
> Mark
>
>
>
>
>
___
lilypond-user mailing list
lilyp
Welcome, Paolo
“overriding” is out of my knowledge.
Someone else might.
Mark
From: paolo prete [mailto:paoloprete...@gmail.com]
Sent: Saturday, March 24, 2018 10:06 AM
To: Mark Stephen Mrotek
Cc: lilypond-user Mailinglist
Subject: Re: SustainPedal on shifted notes (possible bug
Mark,
I would like to override the default behviour of the pedal bracket.
is it possible to end that bracket at the position of the note's column,
instead of extending it for the whole note's duration?
Thanks.
2018-03-24 17:32 GMT+01:00 Mark Stephen Mrotek :
> Paolo,
>
>
>
> Put the \sustainO
on shifted notes (possible bug?)
Hello,
as you can see from the below snippet, the bracket of the sustain pedal is not
properly extended when the last note is shifted.
Is this a bug? Is there a way to fix it or a work-around ?
Thanks
%
\score {
\tuplet 3/2
Hello,
as you can see from the below snippet, the bracket of the sustain pedal is
not properly extended when the last note is shifted.
Is this a bug? Is there a way to fix it or a work-around ?
Thanks
%
\score {
\tuplet 3/2 {c'\sustainOn f' \once \override NoteColumn #'X-offset
Thank you so simple
On 26 October 2017 14:55:40 BST, Pierre Perol-Schneider
wrote:
>Hi Peter,
>
>\override Beam.breakable = ##t
>
>should solve your problem.
>See :
>http://lilypond.org/doc/v2.19/Documentation/notation/writing-rhythms
>
>Cheers,
>Pierre
>
>2017-10-26 11:43 GMT+02:00 :
>
>>
You are on the right track! If you Google for "lilypond beam line
break", you will quickly find the explanation and the solution:
\override Beam.breakable = ##t
/Mats
On 2017-10-26 12:10, peter.gen...@sunscales.co.uk wrote:
Is it me ?
The following script when run via Frescobaldi produc
Hi Peter,
\override Beam.breakable = ##t
should solve your problem.
See : http://lilypond.org/doc/v2.19/Documentation/notation/writing-rhythms
Cheers,
Pierre
2017-10-26 11:43 GMT+02:00 :
> Is it me ?
>
>
>
> The following script when run via Frescobaldi produces correct notation
> but does not
Is it me ?
The following script when run via Frescobaldi produces correct notation but
does not introduce a new line where expected. I ran into this in a larger
score. I have racked my brains for a reason but cannot see any error in the
data. That does not mean there isn't one I accept.
Ca
Is it me ?
The following script when run via Frescobaldi produces correct notation but
does not introduce a new line where expected. I ran into this in a larger
score. I have racked my brains for a reason but cannot see any error in the
data. That does not mean there isn't one I accept.
Ca
On 26/05/2015 17:31, Colin Jesse Kinlund wrote:
\version "2.18.2"
firstVoice = \lyricmode {
I -- av -- na -- na, }
pirveliEkhma = \lyricmode {
ი -- ავ -- ნა -- ნა, }
melody = \relative c'' {
\time 5/4 c4 d e e8( d4.)}
\score {
\new ChoirStaff
<<
\new Voice = "pirveli"
{ \melody }
\new Lyrics
2015-05-26 12:36 GMT+02:00 Michael Gerdau :
> Hi Colin,
>
> after replacing \lyricsto "melody" with \lyricsto "pirveli" this worked
Argh, sure, I forgot to mention this in my previous mail
> for me under 2.19.20 running on ArchLinux.
>
> Not sure what the problem is but I have a few small example
Hi Colin,
after replacing \lyricsto "melody" with \lyricsto "pirveli" this worked
for me under 2.19.20 running on ArchLinux.
Not sure what the problem is but I have a few small examples that work
nicely under Linux and create problems on both Windows 8.1 and OS X 10.10.3
Best wishes,
Michael
--
2015-05-26 9:31 GMT+02:00 Colin Jesse Kinlund :
> Hi LilyPonders, I have a possible bug I’m trying to work around/figure out.
> I have a number of Georgian songs where I’ve set a latin transliteration as
> “verse 1” and the Georgian alphabet for “verse 2”.
> With Lilypond 2.18.2 (or 2.
Hi LilyPonders, I have a possible bug I’m trying to work around/figure out. I
have a number of Georgian songs where I’ve set a latin transliteration as
“verse 1” and the Georgian alphabet for “verse 2”.
With Lilypond 2.18.2 (or 2.19.20) on OS X 10.10.3, compiling now fails with the
error
At 00:03 on 25 Mar 2015, Thomas Morley wrote:
>I disagree.
>\set Score.skipBars = ##t _is_ intended to affect notes _and_ useful!
>Don't limit your thoughts to modern music.
>
>Below I retyped (quick'n dirty) the last bar from Missa Papae
>Marcelli, Sanctus by Palestrina taken from an edition which
2015-03-24 17:06 GMT+01:00 Mark Knoop :
> At 15:43 on 24 Mar 2015, Kevin Barry wrote:
>>On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
>>
>>> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>>>
>>> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>>>
>>
>>At best I would
At 15:43 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
>
>> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>>
>> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>>
>
>At best I would consider these to be non-standard notation. At wo
endEmail.jtp?type=node&node=173568&i=1>
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lily
On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>
> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>
At best I would consider these to be non-standard notation. At worst I'd
say it's incorrect. It's possible to write a
At 12:31 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 9:01 AM, Mark Knoop wrote:
At 18:16 on 23 Mar 2015, Mark Knoop wrote:
>>>Barlines disappear when skipBars is true and a note duration
>>>continues over the bar. I don't think this should happen.
>>>
>>>\version "2.18.2"
>>>
>
On Tue, Mar 24, 2015 at 9:01 AM, Mark Knoop wrote:
> Tuplets across barlines are a relatively common notational practice and
> work perfectly well in LilyPond. It is undesirable that they should
> require a workaround for use in parts with skipBars.
>
If I understand you correctly it seems that
At 23:42 on 23 Mar 2015, Kevin Barry wrote:
>On Mon, Mar 23, 2015 at 6:16 PM, Mark Knoop wrote:
>> Barlines disappear when skipBars is true and a note duration
>> continues over the bar. I don't think this should happen.
>
>It is consistent with the IR definition of the property: `If set to
>true,
On Mon, Mar 23, 2015 at 6:16 PM, Mark Knoop wrote:
> Barlines disappear when skipBars is true and a note duration continues
> over the bar. I don't think this should happen.
>
It is consistent with the IR definition of the property: `If set to true,
then skip the empty bars that are produced by
Joshua Nichols gmail.com> writes:
> Is there talk about improving this feature?
Yes.
Someone recently gave \partcombine an option to double-stem unisons
http://code.google.com/p/lilypond/issues/detail?id=4112
The example at the top of this follow-up might make more sense
http://code.google.com
> The simplest solution here is to keep the voices separate through the
slurs...
Thanks, this is helpful.
Is there talk about improving this feature? Or do you know of a hack for
getting the desired output?
Your solution will be a solid work around from here on out. Thanks.
Josh
__
Joshua Nichols gmail.com> writes:
> I was recently typesetting a song, using part combine, from a hymnal. I ran
into a problem: everytime I ran \partcombine, I found that "unterminated
slur" and "cannot end slur," were common warnings. I was confused, and so I
created this small snippet that s
I was recently typesetting a song, using part combine, from a hymnal. I ran
into a problem: everytime I ran \partcombine, I found that "unterminated
slur" and "cannot end slur," were common warnings. I was confused, and so I
created this small snippet that should reproduce the same issues.
\versio
lypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168337.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
Gilberto Agostinho gmail.com> writes:
> but when changing staff the ottava position
> gets lower (!) and collides with the beam.
LilyPond allows you to beam to any other staff, so in general that
beam might have to go up and cross the ottava bracket, while the
bracket must stay with the staff.
069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168329.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
> On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho
> wrote:
>
> Hello all,
>
> Please have a look on the following code:
>
> \version "2.19.15"
>
> \new PianoStaff <<
> \new Staff = up {
> \override Score.Beam.damping = 3
> \stemUp a'8
> \ottava #1 a'''
> \ottava #0 a'
> a,
> }
> \new S
> On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho
> wrote:
>
> Hello all,
>
> Please have a look on the following code:
>
> \version "2.19.15"
>
> \new PianoStaff <<
> \new Staff = up {
> \override Score.Beam.damping = 3
> \stemUp a'8
> \ottava #1 a'''
> \ottava #0 a'
> a,
> }
> \
> On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho
> wrote:
>
> Hello all,
>
> Please have a look on the following code:
>
> \version "2.19.15"
>
> \new PianoStaff <<
> \new Staff = up {
>\override Score.Beam.damping = 3
>\stemUp a'8
>\ottava #1 a'''
>\ottava #0 a'
>a,
>
problem?
Best,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324.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
Keith OHara writes:
> Joshua Nichols gmail.com> writes:
>
>> global = {
>> \key c \major
>> \numericTimeSignature
>
> It is a bug, but you can fix this one yourself if you like.
>
> In 'property-init.ly' the definition is
> numericTimeSignature = \override Staff.TimeSignature.style = #'numbe
Am 13.05.2014 04:56, schrieb Keith OHara:
Whenever you write a grace note in LilyPond, you need grace
n
Fortunately that's not _whenever_ but only in situations at events like
time signature (changes).
Urs
___
lilypond-user mailing list
lilypond-u
Joshua Nichols gmail.com> writes:
> I've never experienced this before now...
Oops, I just realized you mean the grace-note bug.
Whenever you write a grace note in LilyPond, you need grace
notes or skips of the same duration in every other staff.
So here in the upper staff you need \grace {s8}
Joshua Nichols gmail.com> writes:
> global = {
> \key c \major
> \numericTimeSignature
It is a bug, but you can fix this one yourself if you like.
In 'property-init.ly' the definition is
numericTimeSignature = \override Staff.TimeSignature.style = #'numbered
but we want it to apply to the e
I've never experienced this before now...
I go to use the following settings:
global = {
\key c \major
\numericTimeSignature
\time 4/4
\tempo 4=100
}
and I got the attached picture. I have no idea what I'm doing wrong, or if
this is a bug worth noting.
I was using absolute pitch mode. Than
Wow, i ran into a good one my first try! Thanks for the replies. Yes, can
see a little bit of the slur from the silent grace note, but it's a work
around.
Knute Snortum
(via Gmail)
On Tue, Apr 22, 2014 at 11:57 AM, Urs Liska wrote:
> Am 22.04.2014 20:38, schrieb Paul Morris:
>
> Urs Liska
Am 22.04.2014 20:38, schrieb Paul Morris:
Urs Liska wrote
This is what I wanted to suggest too, but this will leave an ugly slur
fragment (see attached image) in the upper voice.
Clicking on that (point-and-click) will lead to
startAcciaccaturaMusic
in grace-init.ly
Anyone know how to remove
1 - 100 of 163 matches
Mail list logo
