Dots are shifted to avoid non-existent ledger lines (with custom ledger line positions)

2014-07-21 Thread Paul Morris
Here's an obscure one: when ledger line positions have been overridden, the 
positions of dots on dotted notes are still shifted to avoid ledger lines that 
are no longer there.  They don't seem to be shifted based on actual ledger line 
positions.

-Paul


\version "2.18.2"

greenNote =  \once \override NoteHead.color = #green

\markup { Dots are shifted to avoid non-existent ledger lines (see green 
notes). }

\new Staff \with {
  \override StaffSymbol.line-positions = #'(-4 0 4)
  \override StaffSymbol.ledger-positions = #'(-4 0 4)
}
\relative f' {
  \time 12/4
  c,4. d e
  \greenNote f
  g a b
  \greenNote c
  g''
  \greenNote a
  b c d
  \greenNote e
  f g
}

\markup { Dots are not being shifted based on actual ledger line positions.}

\new Staff \with {
  \override StaffSymbol.ledger-positions = #'(-3 -1 1 3 5)
}
\relative f' {
  c, d e f g a b c
}

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


Hairpins not aligned/symmetrical

2014-07-21 Thread Aliosha Bielenberg
> I'm not top posting.

% To be aesthetically pleasing, the end of one
% hairpin should line up with the start of the
% next, i.e. be symmetrical, if they're right next to one another.
\version "2.18.2"

\relative c' {
  f8.\< d16\! g4.\> f8\!
}

This produces [this](https://i.imgur.com/0IP29F6.png), whereas in the hand-
engraved score it's like [this](https://i.imgur.com/3ob5H5Z.png).


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


RE: Hairpins not aligned/symmetrical

2014-07-21 Thread Steven Weber
Try:

\relative c' {
  f8.\< d16 g4.\> f8\!
}

(Any dynamic mark or hairpin automatically terminates the previous hairpin).

--Steven

-Original Message-
From: bug-lilypond-bounces+panteck=hotmail@gnu.org
[mailto:bug-lilypond-bounces+panteck=hotmail@gnu.org] On Behalf Of
Aliosha Bielenberg
Sent: Monday, July 21, 2014 12:40 PM
To: bug-lilypond@gnu.org
Subject: Hairpins not aligned/symmetrical

> I'm not top posting.

% To be aesthetically pleasing, the end of one % hairpin should line up with
the start of the % next, i.e. be symmetrical, if they're right next to one
another.
\version "2.18.2"

\relative c' {
  f8.\< d16\! g4.\> f8\!
}

This produces [this](https://i.imgur.com/0IP29F6.png), whereas in the hand-
engraved score it's like [this](https://i.imgur.com/3ob5H5Z.png).


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

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


Re: Hairpins not aligned/symmetrical

2014-07-21 Thread Janek Warchoł
2014-07-21 22:15 GMT+02:00 Steven Weber :
> Try:
>
> \relative c' {
>   f8.\< d16 g4.\> f8\!
> }

Nevertheless, what Aliosha says is a valid feature request (it's not
always desirable to have decrescendo right after crescendo, but they
should still align).  I'd say this is related to
https://code.google.com/p/lilypond/issues/detail?id=2459

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


Re: Hairpins not aligned/symmetrical

2014-07-21 Thread Jay Anderson
On Mon, Jul 21, 2014 at 1:39 PM, Janek Warchoł  wrote:
> 2014-07-21 22:15 GMT+02:00 Steven Weber :
>> Try:
>>
>> \relative c' {
>>   f8.\< d16 g4.\> f8\!
>> }
>
> Nevertheless, what Aliosha says is a valid feature request (it's not
> always desirable to have decrescendo right after crescendo, but they
> should still align).  I'd say this is related to
> https://code.google.com/p/lilypond/issues/detail?id=2459

This is the closest I've got (it should also work in 2.18 though I
haven't tested it):

\version "2.19.8"

invisibleCresc = #(make-music 'CrescendoEvent 'span-direction START
'span-type 'text 'span-text "" 'tweaks '((dash-period . -1)))

\relative c' {
  f8.\< d16\invisibleCresc g4.\> f8\!
}

The hairpins align vertically, but it unfortunately causes the first
hairpin to end early. I'm sure there are a few more tweaks to make it
work.

-Jay

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


Repeated accidentals after ties

2014-07-21 Thread Justus Schümmer
Hi. Here are two small issues:

1. When I repeat a chord with q which contains a reminder accidental,
both notes get the accidental:
\version "2.18.2"
\relative c'' {
2~ q
}
I think (maybe I am wrong) even the reminder should be printed only once.

2. This is a special case so the example explains it better than I can.
\version "2.18.2"
\relative c'' {
\key g \major
f1~ \break
| f2 f2
}
The natural here appears two times in the second bar.

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


Re: Hairpins not aligned/symmetrical

2014-07-21 Thread Aliosha Bielenberg
Thanks! I still don't really understand how or why, but it works.

Sincerely,

Aliosha Bielenberg


On Mon, Jul 21, 2014 at 11:15 PM, Steven Weber  wrote:

> Try:
>
> \relative c' {
>   f8.\< d16 g4.\> f8\!
> }
>
> (Any dynamic mark or hairpin automatically terminates the previous
> hairpin).
>
> --Steven
>
> -Original Message-
> From: bug-lilypond-bounces+panteck=hotmail@gnu.org
> [mailto:bug-lilypond-bounces+panteck=hotmail@gnu.org] On Behalf Of
> Aliosha Bielenberg
> Sent: Monday, July 21, 2014 12:40 PM
> To: bug-lilypond@gnu.org
> Subject: Hairpins not aligned/symmetrical
>
> > I'm not top posting.
>
> % To be aesthetically pleasing, the end of one % hairpin should line up
> with
> the start of the % next, i.e. be symmetrical, if they're right next to one
> another.
> \version "2.18.2"
>
> \relative c' {
>   f8.\< d16\! g4.\> f8\!
> }
>
> This produces [this](https://i.imgur.com/0IP29F6.png), whereas in the
> hand-
> engraved score it's like [this](https://i.imgur.com/3ob5H5Z.png).
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Repeated accidentals after ties

2014-07-21 Thread James
On 21/07/14 18:12, Justus Schümmer wrote:
> Hi. Here are two small issues:
>
> 1. When I repeat a chord with q which contains a reminder accidental,
> both notes get the accidental:
> \version "2.18.2"
> \relative c'' {
>   2~ q
> }
> I think (maybe I am wrong) even the reminder should be printed only once.
>
> 2. This is a special case so the example explains it better than I can.
> \version "2.18.2"
> \relative c'' {
>   \key g \major
>   f1~ \break
>   | f2 f2
> }
> The natural here appears two times in the second bar.
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
https://code.google.com/p/lilypond/issues/detail?id=4010

?

James

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


Re: Repeated accidentals after ties

2014-07-21 Thread David Kastrup
James  writes:

> On 21/07/14 18:12, Justus Schümmer wrote:
>> Hi. Here are two small issues:
>>
>> 1. When I repeat a chord with q which contains a reminder accidental,
>> both notes get the accidental:
>> \version "2.18.2"
>> \relative c'' {
>>  2~ q
>> }
>> I think (maybe I am wrong) even the reminder should be printed only once.
>>
>> 2. This is a special case so the example explains it better than I can.
>> \version "2.18.2"
>> \relative c'' {
>>  \key g \major
>>  f1~ \break
>>  | f2 f2
>> }
>> The natural here appears two times in the second bar.
>>
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
> https://code.google.com/p/lilypond/issues/detail?id=4010

That's the first.  The second is
https://code.google.com/p/lilypond/issues/detail?id=649>

-- 
David Kastrup


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