Re: Notes on wrong side of stem in triads

[Pierre Perol-Schneider]

Hi Dan,
One silly question: Does that change anything if you don't force the A
natural sign; e.g.:
8 16  8[ ]  

??
Cheers,
Pierre

2016-10-17 10:09 GMT+02:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Dan,
> At least you'll find a workaround here:
> http://lsr.di.unimi.it/LSR/Item?id=861
>
> HTH.
> Cheers,
> Pierre
>
> 2016-10-17 9:48 GMT+02:00 Davide Liessi :
>
>> 2016-10-17 3:46 GMT+02:00 DJF :
>> > Unfortunately, I can’t reproduce the enclosed problem in a minimal
>> example because the same code works fine in a file by itself.
>>
>> "Minimal example" means that if you remove anything the problem is
>> gone, so if the code works in what you call a minimal example, that
>> was *not* a minimal example for your problem: sometimes bugs are
>> encountered only in long scores.
>>
>> See http://lilypond.org/tiny-examples.html, especially where it says
>> "When trying to create an example, try commenting out (% or %{ … %})
>> sections of your file. If you can comment something while still
>> demonstrating the main idea, then remove the commented-material."
>> It is a tedious process, but it is actually how you can understand
>> where the problem is: preparing minimal examples to post to this lists
>> often leads me to solving problems on my own.
>>
>> Anyway, if you need help with this, at least share your code
>> (privately, if there are copyright issues), since it is impossible to
>> debug an image.
>>
>> Best wishes.
>> Davide
>>
>> ___
>> 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: Why warning: cannot end volta spanner?

[Peter Toye]

This is a forwarded message
From: Peter Toye 
To: Simon Albrecht 
Date: Tuesday, October 11, 2016, 4:07:21 PM
Subject: Why warning: cannot end volta spanner?

===8<==Original message text===
Simon,

Thanks  - that certainly does the trick. Though why there should be a warning 
message there at all is still beyond me (see the title to this thread!).

I can't find any reference in the manuals to the syntax of calling functions 
like this. There's a list of functions in the Notation and Internal reference 
manuals, but I can't see where it tells me how to use them, apart from the odd 
example of specific functions.

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Sunday, October 9, 2016, 7:26:40 PM, you wrote:

Albrecht> On 09.10.2016 19:08, Peter Toye wrote:
>> Re: Why warning: cannot end volta spanner? David,

>> This is what I'd like. But it compiles with the warning message. My 
>> original questions was: why and can I get what I want without the warning?

Albrecht> If everything is fine except for the warning, you can use
Albrecht> #(ly:expect-warning "cannot end volta")
Albrecht> It goes on top-level, once for every instance of the warning. If a 
Albrecht> future compilation issues fewer warnings than expected, there will be 
a
Albrecht> warning about that.

Albrecht> Best, Simon


>> \version "2.18.2"

>> \language "english"

>> \score {
>>  \new Staff {

>>\time 4/4
>>\clef treble

>>\relative c''
>>{
>>  c1
>>  \repeat volta 2 {
>>c d e f
>>  }
>>  \alternative {
>>{
>>  g f e d
>>}
>>{
>>  \set Score.voltaSpannerDuration = #(ly:make-moment 4/4)
>>  \repeat unfold 2 {
>>\repeat unfold 12  {g8 a}
>>g f e d c d e f
>>  }
>>}
>>  }
>>  g1 f e d c
>>}
>>  }
>> }

>> Best regards,

>> Peter
>> mailto:lilyp...@ptoye.com
>> www.ptoye.com 

>> -
>> Friday, October 7, 2016, 7:03:43 PM, you wrote:

>> *Wright> On Fri 07 Oct 2016 at 18:44:28 (+0100), Peter Toye wrote:
>> >> Not exactly! I've modded my example and am getting interesting 
>> results. In my original music (far too long to show here) without the 
>> change to voltaSpannerDuration the 2nd time volta spanner stretches 
>> right over the repeat unfold (over several lines) without any error 
>> message.

>> >> My original had two nested repeat unfolds (I didn't put this into 
>> my snippet an I didn't think it would be relevant), so I've replicated 
>> the correct structure below. With the change to voltaSpannerDuration I 
>> get the desired effect but a warning message. Without it there's no 
>> error message but the 2nd time volta spanner spans 5 bars - to the end 
>> of the line. Which is different from what happens in my original 
>> music. I can try to provide a reduced version which displays the 
>> issue, but it'll probably take some time to work it out.

>> Wright> It might help to tell us exactly what you want to see printed,
>> Wright> and how this differs from what has been posted here.
>> Wright> Otherwise we're all left guessing.

>> Wright> Cheers,
>> Wright> David.


>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>> *

===8<===End of original message text===Title: Re: Why warning: cannot end volta spanner?


Simon,

Thanks  - that certainly does the trick. Though why there should be a warning message there at all is still beyond me (see the title to this thread!).

I can't find any reference in the manuals to the syntax of calling functions like this. There's a list of functions in the Notation and Internal reference manuals, but I can't see where it tells me how to use them, apart from the odd example of specific functions.

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Sunday, October 9, 2016, 7:26:40 PM, you wrote:

Albrecht> On 09.10.2016 19:08, Peter Toye wrote:
>> Re: Why warning: cannot end volta spanner? David,

>> This is what I'd like. But it compiles with the warning message. My 
>> original questions was: why and can I get what I want without the warning?

Albrecht> If everything is fine except for the warning, you can use
Albrecht> #(ly:expect-warning "cannot end volta")
Albrecht> It goes on top-level, once for every instance of the warning. If a 
Albrecht> future compilation issues fewer warnings than expected, there will be a
Albrecht> warning about that.

Albrecht> Best, Simon


>> \version "2.18.2"

>> \language "english"

>> \score {
>>  \new Staff {

>>    \time 4/4
>>    \clef treble

>>    \relative c''
>>    {
>>      c1
>>      \repeat volta 2 {
>>        c d e f
>>      }
>>      \alternative {
>>        {
>>          g f e d
>>        }
>>        {
>>          \set Score.voltaSpannerDuration = #(ly

Re: Trouble Combining Repeats and Closing Bars in tunes

[David Wright]

On Mon 17 Oct 2016 at 23:24:51 (-0400), Ben Beeson wrote:
> I am looking at a 4 - part tune where the first and third parts are
> repeated and the second and fourth parts are not repeated. Try as I
> may, I cannot get Lilypond to put  the repeats and closing bars in the
> right place when engraving the tune. The following is just about as
> simple as I can get it and still show the issue.  
> 
> % BarExample.ly 
> \version "2.19.48"
> 
> example = {   \time 2/4
>   \relative c''{
>  \repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8
> a8 | \break  }  
>   \bar ".|" d8 d8 d8 d8
> |  d8 d8 d8 d8 | \bar "|." \break
>  \repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8
> a8 | \break } 
>   \bar ".|"  d8 d8 d8 d8 |
> d8 d8 d8 d8 | \bar "|." \break }
> }
>  
> 
> \score   
> {
>   \new Staff <<
>   
>   \new Voice {
>   \example
>   }   
>   >>   
> }
> % end BarExample.ly 
> 
> This produces the following which is clearly not what I intended since
> the first and third lines should be repeated and the second and fourth
> lines are not repeated. 
> 
> 
>  What am I doing wrong and what is the best way to fix it short of
> using separate score blocks for each part? 

Just let LP choose the barline types.

Cheers,
David.
{
  \time 2/4
  \relative c''{
\repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8 a8 | \break  }
d8 d8 d8 d8 | d8 d8 d8 d8 | \break
\repeat volta 2 { a8 a8 a8 a8 | a8 a8 a8 a8 | \break }
d8 d8 d8 d8 | d8 d8 d8 d8 | \bar "|." }
}


a.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Trouble Combining Repeats and Closing Bars in tunes

[Ben Beeson]

Thanks David,

This is just what I needed!

Regards,

Ben

On Mon, 2016-10-17 at 23:52 -0500, David Wright wrote:
> On Mon 17 Oct 2016 at 23:24:51 (-0400), Ben Beeson wrote:
> > 
> > I am looking at a 4 - part tune where the first and third parts are
> > repeated and the second and fourth parts are not repeated. Try as I
> > may, I cannot get Lilypond to put  the repeats and closing bars in
> > the
> > right place when engraving the tune. The following is just about as
> > simple as I can get it and still show the issue.  
> > 
> > % BarExample.ly 
> > \version "2.19.48"
> > 
> > example = {   \time 2/4
> >   \relative c''{
> >  \repeat volta 2 { a8 a8 a8 a8 | a8 a8
> > a8
> > a8 | \break  }  
> >   \bar ".|" d8 d8 d8 d8
> > > 
> > >   d8 d8 d8 d8 | \bar "|." \break
> >  \repeat volta 2 { a8 a8 a8 a8 | a8 a8
> > a8
> > a8 | \break } 
> >   \bar ".|"  d8 d8 d8
> > d8 |
> > d8 d8 d8 d8 | \bar "|." \break }
> > }
> >  
> > 
> > \score   
> > {
> > \new Staff <<
> > 
> > \new Voice {
> > \example
> > }   
> > >>   
> > }
> > % end BarExample.ly 
> > 
> > This produces the following which is clearly not what I intended
> > since
> > the first and third lines should be repeated and the second and
> > fourth
> > lines are not repeated. 
> > 
> > 
> >  What am I doing wrong and what is the best way to fix it short of
> > using separate score blocks for each part? 
> 
> Just let LP choose the barline types.
> 
> Cheers,
> David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why warning: cannot end volta spanner?

[David Nalesnik]

On Tue, Oct 18, 2016 at 3:41 AM, Peter Toye  wrote:
> This is a forwarded message
> From: Peter Toye 
> To: Simon Albrecht 
> Date: Tuesday, October 11, 2016, 4:07:21 PM
> Subject: Why warning: cannot end volta spanner?
>
> ===8<==Original message text===
> Simon,
>
> Thanks  - that certainly does the trick. Though why there should be a
> warning message there at all is still beyond me (see the title to this
> thread!).

The warning happens in lily/volta-engraver.cc, where there is a comment:

/* fixme: be more verbose  */

The warning is issued because the program expects to end the spanner
either when the repeat element is over, or when a line break is
encountered, as in your example.  Consequently, you can set
voltaSpannerDuration to Mom 5/1 or Mom 13/1 in your example with no
warning.  (With results identical to the default without the manual
setting, of course.)

I'm not sure of the point of the warning.  Why else would you set
voltaSpannerDuration unless you want something out of the ordinary?

In any case, the warning should be more descriptive.

HTH,
David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[DJF]

> 2016-10-17 10:09 GMT+02:00 Pierre Perol-Schneider 
> mailto:pierre.schneider.pa...@gmail.com>>:
> Hi Dan,
> At least you'll find a workaround here:
> http://lsr.di.unimi.it/LSR/Item?id=861 
> 
> 
> On Oct 18, 2016, at 3:43 AM, Pierre Perol-Schneider 
>  wrote:
> Hi Dan,
> One silly question: Does that change anything if you don't force the A 
> natural sign; e.g.:
> 8 16  8[ ]  
> 
> ??
> Cheers,
> Pierre


Pierre, I appreciate your stab at a work-around. While the LSR you mentioned 
does help get all the note heads in the right spot, the major side effect is 
that the 8th note beams disappear. So that I could “go to press”, I did use 
that code, however, and graphically inserted some beams into the final PDF. Not 
ideal, to be sure … but it was better than the alternative!

And no, removing the forced A natural sign doesn’t change anything.

> 2016-10-17 9:48 GMT+02:00 Davide Liessi  >:
> 2016-10-17 3:46 GMT+02:00 DJF mailto:delf...@me.com>>:
> > Unfortunately, I can’t reproduce the enclosed problem in a minimal example 
> > because the same code works fine in a file by itself.
> 
> "Minimal example" means that if you remove anything the problem is
> gone, so if the code works in what you call a minimal example, that
> was *not* a minimal example for your problem: sometimes bugs are
> encountered only in long scores.


Davide, I do understand the concept of a minimal example … it’s just that I 
couldn’t get to that point. I really had tried myriad things to isolate the 
issue. In the past, I have spent weeks working on some little (but important) 
problems and usually I find the solution before seeking help from the list. I 
just didn’t have weeks to spend this time, and this particular problem seemed 
so random in comparison. If you really want to see the score, send me a private 
note, but, as I’ve mentioned above, I had to finish it so I could move on to 
other things. Unsolved mysteries are irksome, though!

Best wishes,

Dan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Pierre Perol-Schneider]

Hum, well there's another possible workaround, a bad one, but works:

%% Snipp:

\version "2.19"

\relative c' {
  \clef F
  \time 3/4
  \key f\major
  8 16  8[
  <\tweak NoteHead.extra-offset #'(-1.2 . 0)\tweak NoteHead.rotation #90 a
c e>]
   <\tweak NoteHead.extra-offset #'(-1.2 . 0)\tweak
NoteHead.rotation #90 a c e>
}

HTH,
Pierre

2016-10-18 15:37 GMT+02:00 DJF :

> 2016-10-17 10:09 GMT+02:00 Pierre Perol-Schneider  schneider.pa...@gmail.com>:
>
> Hi Dan,
>> At least you'll find a workaround here:
>> http://lsr.di.unimi.it/LSR/Item?id=861
>>
>
>> On Oct 18, 2016, at 3:43 AM, Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com> wrote:
>>
> Hi Dan,
> One silly question: Does that change anything if you don't force the A
> natural sign; e.g.:
> 8 16  8[ ]  
>
> ??
> Cheers,
> Pierre
>
>
> Pierre, I appreciate your stab at a work-around. While the LSR you
> mentioned does help get all the note heads in the right spot, the major
> side effect is that the 8th note beams disappear. So that I could “go to
> press”, I did use that code, however, and graphically inserted some beams
> into the final PDF. Not ideal, to be sure … but it was better than the
> alternative!
>
> And no, removing the forced A natural sign doesn’t change anything.
>
> 2016-10-17 9:48 GMT+02:00 Davide Liessi :
>>
>>> 2016-10-17 3:46 GMT+02:00 DJF :
>>> > Unfortunately, I can’t reproduce the enclosed problem in a minimal
>>> example because the same code works fine in a file by itself.
>>>
>>> "Minimal example" means that if you remove anything the problem is
>>> gone, so if the code works in what you call a minimal example, that
>>> was *not* a minimal example for your problem: sometimes bugs are
>>> encountered only in long scores.
>>
>>
> Davide, I do understand the concept of a minimal example … it’s just that
> I couldn’t get to that point. I really had tried myriad things to isolate
> the issue. In the past, I have spent weeks working on some little (but
> important) problems and usually I find the solution before seeking help
> from the list. I just didn’t have weeks to spend this time, and this
> particular problem seemed so random in comparison. If you really want to
> see the score, send me a private note, but, as I’ve mentioned above, I had
> to finish it so I could move on to other things. Unsolved mysteries are
> irksome, though!
>
> Best wishes,
>
> Dan
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Davide Liessi]

I reproduced the issue with this:

\version "2.19.47"
\layout { #(layout-set-staff-size 19) }
{  }

Using #(set-global-staff-size 19) instead works as expected.
I couldn't find a bug report for this.
Any ideas?

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Pierre Perol-Schneider]

Thank you Davide.
So the workaround (the bad one):

\version "2.19"
\layout { #(layout-set-staff-size 19) }

\relative c' {
  \clef F
  \time 3/4
  \key f\major
  8 16  8[
  <\tweak NoteHead.extra-offset #'(1.3 . 0)\tweak NoteHead.rotation #90 a c
e>]
   <\tweak NoteHead.extra-offset #'(1.3 . 0)\tweak
NoteHead.rotation #90 a c e>
}

Cheers,
Pierre

2016-10-18 17:05 GMT+02:00 Davide Liessi :

> I reproduced the issue with this:
>
> \version "2.19.47"
> \layout { #(layout-set-staff-size 19) }
> {  }
>
> Using #(set-global-staff-size 19) instead works as expected.
> I couldn't find a bug report for this.
> Any ideas?
>
> Best wishes.
> Davide
>
> ___
> 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: Notes on wrong side of stem in triads

[Mark Knoop]

At 17:05 on 18 Oct 2016, Davide Liessi wrote:
>I reproduced the issue with this:
>
>\version "2.19.47"
>\layout { #(layout-set-staff-size 19) }
>{  }
>
>Using #(set-global-staff-size 19) instead works as expected.
>I couldn't find a bug report for this.
>Any ideas?

Very weird, and certainly a bug. This works as expected also:

\version "2.19.47"
\layout { #(layout-set-staff-size 19.0001) }
{  }

-- 
Mark Knoop

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[David Kastrup]

Mark Knoop  writes:

> At 17:05 on 18 Oct 2016, Davide Liessi wrote:
>>I reproduced the issue with this:
>>
>>\version "2.19.47"
>>\layout { #(layout-set-staff-size 19) }
>>{  }
>>
>>Using #(set-global-staff-size 19) instead works as expected.
>>I couldn't find a bug report for this.
>>Any ideas?
>
> Very weird, and certainly a bug. This works as expected also:
>
> \version "2.19.47"
> \layout { #(layout-set-staff-size 19.0001) }
> {  }

Well, _that_ looks like the distance between noteheads is used as a
factor for deciding about the arrangement in a manner that is
numerically fragile.  Like looking whether their distance is smaller
than 1.0 staff line distances.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Paul]

On 10/18/2016 11:20 AM, Mark Knoop wrote:


At 17:05 on 18 Oct 2016, Davide Liessi wrote:

I reproduced the issue with this:

\version "2.19.47"
\layout { #(layout-set-staff-size 19) }
{  }

Using #(set-global-staff-size 19) instead works as expected.
I couldn't find a bug report for this.
Any ideas?

Very weird, and certainly a bug. This works as expected also:

\version "2.19.47"
\layout { #(layout-set-staff-size 19.0001) }
{  }


Davide, you beat me to it! :-)  I tracked down the same cause, see below...

Oddly, thirds are ok, and only some triads are affected.

I suspect it might be related to this commit:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=74bd453cc3da31d047b2611aad5669395fc71447

-Paul


\version "2.19.42"

% this works fine
% #(set-global-staff-size 19)

\score {
  \relative c {





















  }

  % this causes notes on wrong side of stem for some triads above
  % only when set to 19, all is fine at 20, 18, 18.5, 19.5
  \layout {  #(layout-set-staff-size 19) }
}

% these thirds are fine
\score {
  \relative c {





















  }
  \layout {  #(layout-set-staff-size 19) }
}



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[David Kastrup]

Davide Liessi  writes:

> I reproduced the issue with this:
>
> \version "2.19.47"
> \layout { #(layout-set-staff-size 19) }
> {  }
>
> Using #(set-global-staff-size 19) instead works as expected.
> I couldn't find a bug report for this.
> Any ideas?

I don't think layout-set-staff-size works well.  Probably the notehead
size does not fit the line distance then and stacking is problematic?

Can someone figure out which settings are affected differently here?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Why warning: cannot end volta spanner?

[Peter Toye]

David,

Thanks for the explanation. Seems like a buglet in LP, but not worth while 
worrying about. At least it's not giving me any serious problems, but warnings 
when I don't think I'm doing anything wrong worry me :)>

Best regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

-
Tuesday, October 18, 2016, 2:07:26 PM, you wrote:

Nalesnik> On Tue, Oct 18, 2016 at 3:41 AM, Peter Toye  
wrote:
>> This is a forwarded message
>> From: Peter Toye 
>> To: Simon Albrecht 
>> Date: Tuesday, October 11, 2016, 4:07:21 PM
>> Subject: Why warning: cannot end volta spanner?

>> ===8<==Original message text===
>> Simon,

>> Thanks  - that certainly does the trick. Though why there should be a
>> warning message there at all is still beyond me (see the title to this
>> thread!).

Nalesnik> The warning happens in lily/volta-engraver.cc, where there is a 
comment:

Nalesnik> /* fixme: be more verbose  */

Nalesnik> The warning is issued because the program expects to end the spanner
Nalesnik> either when the repeat element is over, or when a line break is
Nalesnik> encountered, as in your example.  Consequently, you can set
Nalesnik> voltaSpannerDuration to Mom 5/1 or Mom 13/1 in your example with no
Nalesnik> warning.  (With results identical to the default without the manual
Nalesnik> setting, of course.)

Nalesnik> I'm not sure of the point of the warning.  Why else would you set
Nalesnik> voltaSpannerDuration unless you want something out of the ordinary?

Nalesnik> In any case, the warning should be more descriptive.

Nalesnik> HTH,
Nalesnik> David___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Pierre Perol-Schneider]

Hi Paul,

2016-10-18 17:55 GMT+02:00 Paul :

> ...
>
>   % this causes notes on wrong side of stem for some triads above
>   % only when set to 19, all is fine at 20, 18, 18.5, 19.5
>   \layout {  #(layout-set-staff-size 19) }
> }
>
> 
>

Test with v2.19.49:
bug comes with sizes: 7, 14, 19, 28, 38, 56 and probably their multiples.
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Pierre Perol-Schneider]

And also: 3.5, 9.5.
Pierre

2016-10-18 20:09 GMT+02:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Paul,
>
> 2016-10-18 17:55 GMT+02:00 Paul :
>
>> ...
>>
>>   % this causes notes on wrong side of stem for some triads above
>>   % only when set to 19, all is fine at 20, 18, 18.5, 19.5
>>   \layout {  #(layout-set-staff-size 19) }
>> }
>>
>> 
>>
>
> Test with v2.19.49:
> bug comes with sizes: 7, 14, 19, 28, 38, 56 and probably their multiples.
> Cheers,
> Pierre
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Notes on wrong side of stem in triads

[Stanton Sanderson]

> On Oct 18, 2016, at 10:05 AM, Davide Liessi  wrote:
> 
> #(set-global-staff-size 19)

The following also works:

\version "2.19.47"
\paper {
  #(layout-set-absolute-staff-size (* 19 pt))
}
{  }


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Phrasing slurs shortened when broken

[Javier Ruiz-Alma]

I've dealt with this by either adding \noBreak's where slurs span beyond a 
measure with end-of-measure clef change, or by forcing the \break and 
correcting the \shape of the 1st segment.
Does this qualify as bug?

Javier

 
  From: David Kastrup 
 To: Javier Ruiz-Alma  
Cc: LilyPond User Group 
 Sent: Sunday, October 16, 2016 11:58 PM
 Subject: Re: Phrasing slurs shortened when broken
   
Javier Ruiz-Alma  writes:

>>> In a piece I'm working on, and only from bar 146 on, slurs which are
>>> broken across systems, the first broken slur will be typeset short for
>>> a reason I can't figure out.What could exclusively affect the length
>>> of the first segment of broken slurs?Changing from PhrasingSlur to
>>> Slur makes no difference.I'm stumped.The version is 2.18.2.
>>Looks like the clef change in the lower system has something to do with
>>it.
>>David Kastrup
>
> I confirm, the offending instances have the clef change in the bass.
> The concern with fixing the first segment via \shape is the correction
> would be useful when the slur is broken, but undesirable when not.  We
> typeset the same source with different paper sizes, so there's a real
> chance fix, or no fix, one of the versions will show an undesirable
> slur shape.  Forcing or preventing a system break is non-ideal either.
> Interestingly enough, I'm updating the piece from LilyPond 2.1.  LP
> v2.1 slur in this situation was not as affected by this (see
> attached).
> Below is a minimal example that causes the issue/bug:
>
> \version "2.18.2"\score {  <<     { c''2 c''4 c''\(  \break c''1\) } 
>   { c''1 \clef bass c' }    >>}

Can it be

 (2.15.21) ?

I also distinctly remember one issue with some overlap due to a key
signature (though in line rather than at a line break) but cannot find
it right now.

-- 
David Kastrup

   
 ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Phrasing slurs shortened when broken

[David Kastrup]

Javier Ruiz-Alma  writes:

> I've dealt with this by either adding \noBreak's where slurs span beyond a 
> measure with end-of-measure clef change, or by forcing the \break and 
> correcting the \shape of the 1st segment.
> Does this qualify as bug?

Most certainly.

>> Below is a minimal example that causes the issue/bug:
>>
>> \version "2.18.2"\score {  <<     { c''2 c''4 c''\(  \break c''1\) } 
>>   { c''1 \clef bass c' }    >>}
>
> Can it be
>
>  (2.15.21) ?
>
> I also distinctly remember one issue with some overlap due to a key
> signature (though in line rather than at a line break) but cannot find
> it right now.


-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Help required with tuplets

[Bernhard Kleine]

Hi,

I do not see what is wrong with the following extract which is
compilable but totally wrong. The structure is fully from what
Frescobaldi offered, however missing voices not yet added are skipped.

Thank you for any help.

Bernhard

--

\version "2.19.33"
\language "deutsch"
\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
  \key c \major
  \numericTimeSignature
  \time 2/4
 
  \tempo "Allegretto"
}
rightOne = \relative c'' {
  \global
  % Die Noten folgen hier.
  \partial 8 \stemDown
  \tuplet 3/8 {d'16 \p c f,} | \omit TupletNumber
  \tuplet 3/8 {d'16  c e,} \tuplet 3/8 {a g c,} \tuplet 3/8 {f e b} |

}
pianoPart = \new PianoStaff \with {
  instrumentName = "Kl."
} <<
  \new Staff = "right" << \rightOne  >>
 
>>

\score {
  <<
  
\pianoPart
  >>
  \layout { }
}

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Help required with tuplets

[Marc Hohl]

Am 19.10.2016 um 08:14 schrieb Bernhard Kleine:

Hi,

I do not see what is wrong with the following extract which is
compilable but totally wrong.


I think you misunderstood the way \tuplet works:

\tuplet 3/2 is the way to go, because you want *3* notes to last as long 
as *2* notes normally do.


HTH,

Marc



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user