Re: Automatically shift dynamics horizontally?

[Palmer Ralph]

On Wed, Jan 27, 2016 at 6:57 AM, Malte Meyn  wrote:

>
>
> Am 27.01.2016 um 10:19 schrieb Urs Liska:
> > In such situations one will usually shift the dynamics to the left, and
> > Lily will automatically use the space better. You can see that when you
> > uncomment one of the lines in \off.
> >
> > Would there be a way to approach this problem automatically, presumably
> > controlled by a configuration variable?
>
> In my opinion moving the sf to the left looks like the b of the left
> hand has the accent. In this case I would prefer a positive shift (to
> the right):
>

Thanks, Urs and Malte. This has been added as Issue #4756 :
https://sourceforge.net/p/testlilyissues/issues/4756/
All the best,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

when adding \new Staff to a StaffGroup, ledger lines not rendered if clef is specified.

[Andy Deitrich]

% The example here renders perfectly if \clef bass is removed
% but as is, the ledger lines in the new staff are not rendered.

\version "2.18.2"

\new StaffGroup \relative c {
\time 6/8
\new Staff
c''2. | c2. 
<<
{2.~ | }
\new Staff 
\clef bass 
{ges,,2. | f}
>>
}


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

Re: when adding \new Staff to a StaffGroup, ledger lines not rendered if clef is specified.

[Phil Holmes]

"Andy Deitrich"  wrote in message 
news:loom.20160129t162423-...@post.gmane.org...

% The example here renders perfectly if \clef bass is removed
% but as is, the ledger lines in the new staff are not rendered.

\version "2.18.2"

\new StaffGroup \relative c {
\time 6/8
\new Staff
c''2. | c2.
<<
{2.~ | }
\new Staff
\clef bass
{ges,,2. | f}
>>
}


I've no idea what you're trying to do here, but if you sort out your << >> 
and { } groups, the music starts to look like I'd guess it should:


\version "2.18.2"

\new StaffGroup \relative c {
\time 6/8
<<
\new Staff {
c''2. | c2.
2.~ | 
}
\new Staff
{ \clef bass
ges,,2. | f }



}


--
Phil Holmes



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

Re: when adding \new Staff to a StaffGroup, ledger lines not rendered if clef is specified.

[Andy Deitrich]

Phil Holmes  philholmes.net> writes:

> 
> I've no idea what you're trying to do here, but if you sort out your << >> 
> and { } groups, the music starts to look like I'd guess it should:
> 
>.

Thank you!!!


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

Re: Piano centered dynamics - dealing with bar collisions

[Abraham Lee]

Przemyslaw,

On Thu, Jan 28, 2016 at 6:02 PM, Przemyslaw Pawelczyk [via Lilypond] <
ml-node+s1069038n186599...@n5.nabble.com> wrote:

> Hi!
>
> There is a piano centered dynamics template that was present in
> Lilypond Learning Manual for v2.14, but is not available in recent
> versions:
> http://www.lilypond.org/doc/v2.14/Documentation/learning/piano-templates
>
> If we take it (w/o midi part, which is not needed here) and add s1 in
> everything (i.e. upper, lower, dynamics, pedal) at the beginning, then
> we can see that \fff overlaps the piano staff bar:
> http://paste.przemoc.net/lilypond/piano-centered-dynamics/
>
> How to make dynamic text not overlap the bar, yet shift the note
> column (not sure if I'm using the correct term here) appropriately, so
> the text would remain centered?
>
> (This mostly works when \dynamics are put into particular Staff [only
> mostly, because \fff remains then too close to the bar, almost
> touching it], but I want to have one \dynamics in separate Dynamics
> between upper and lower Staff within PianoStaff.)
>
> My half-workaround is setting DynamicText.X-offset (which in this
> particular example seems ok with value -0.3, but it doesn't work that
> well in general), but then DynamicText stops being centered and
> depending on width of the dynamic text, it may be almost unnoticeable
> or looks awfully wrong.
>
> I hope there are some better solutions.
>

I, too, have been trying to figure this one out and it appears that we now
have a solution (though it appears to not be documented in the IR, for some
reason--CC-ing the bug-list). It turns out that all you need to add the
following to the appropriate context (Dynamics, in your case):

\override DynamicText.extra-spacing-height = #'(-inf.0 . +inf.0)

That should get you on your way! I've always been puzzled that
extra-spacing-width doesn't change this at all (maybe I just don't know how
to use it properly). The LyricText grob does this SpanBar collision
avoidance by default, so I was confused as to why DynamicText couldn't do
the same.

BTW, this does NOT work with 2.18.2, but it does with 2.19.35 at least.
Haven't checked the other devel versions.

Anyway. There you go.

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

Re: when adding \new Staff to a StaffGroup, ledger lines not rendered if clef is specified.

[Simon Albrecht]

On 29.01.2016 16:29, Andy Deitrich wrote:

% The example here renders perfectly if \clef bass is removed
% but as is, the ledger lines in the new staff are not rendered.

\version "2.18.2"

\new StaffGroup \relative c {
\time 6/8
\new Staff
c''2. | c2.
<<
{2.~ | }
\new Staff
\clef bass
{ges,,2. | f}
>>
}


Phil already sorted out the crucial things, but I’d like to make a few 
more recommendations for structuring your code:



\version "2.18.2"

aux = {
  \time 6/8
}
one = \relative {
  c''2. | c2.
  2.~ | q % ‘q’ repeats the previous chord
}
two = \relative {
  \clef bass
  ges,2. | f
}

\new StaffGroup <<
  \aux
  \new Staff \one
  \new Staff \two
>>
%%%

This gives you a more robust, more legible structure.

Best, Simon

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

No warning upon failed ‘align[Above|Below]Context’

[Simon Albrecht]

Hello,

in this example

%%%
\version "2.19.35"
\new StaffGroup <<
  \new Staff = "A" { a'1 a' }
  { \skip 1 \new Staff = "C" \with { alignAboveContext = "B" } { c''1 } }
  { \skip 1 \new Staff = "B" \with { alignAboveContext = "A" } { b'1 } }
>>
%%%

Lily can’t find context "B" when creating "C", so she silently prints 
"C" below "A". There should be a warning about this.


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

Re: Piano centered dynamics - dealing with bar collisions

[Przemyslaw Pawelczyk]

On Fri, Jan 29, 2016 at 11:31 PM, Przemyslaw Pawelczyk
 wrote:
> On Fri, Jan 29, 2016 at 6:49 PM, Abraham Lee  
> wrote:

>> \override DynamicText.extra-spacing-height = #'(-inf.0 . +inf.0)

> \override DynamicText.extra-spacing-width = #'(-0.2 . 0.2)
>
> Here is the PDF with both overrides:
> http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics-workaround.pdf

Here is the PDF w/o overrides:
http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics.pdf

I've noticed another thing just now, after zooming in.
Regardless of the overrides, first half note in the lower staff
actually does not line up with quater note in the upper staff.
Adding \override SpacingSpanner.uniform-stretching = ##t into \layout
{ \context { ... } } does not change anything.

I'm not sure, though, whether this slight displacement can be
considered as a bug or whether it's within acceptable boundaries.

>>
>> BTW, this does NOT work with 2.18.2, but it does with 2.19.35 at least.
>> Haven't checked the other devel versions.
>
> I usually try to use the latest Lilypond available, but good to know
> that such "glueing" is moderately recent feature.

I've checked mentioned earlier overrides with 2.18.2 (on Windows 7 Pro
64-bit), and they actually can work here too, but only if they're used
together! :)

Regards.

-- 
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86

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

Re: Piano centered dynamics - dealing with bar collisions

[Przemyslaw Pawelczyk]

Hi, Abraham!

On Fri, Jan 29, 2016 at 6:49 PM, Abraham Lee  wrote:
> On Thu, Jan 28, 2016 at 6:02 PM, Przemyslaw Pawelczyk [via Lilypond] <
> ml-node+s1069038n186599...@n5.nabble.com> wrote:

>> There is a piano centered dynamics template that was present in
>> Lilypond Learning Manual for v2.14, but is not available in recent
>> versions:
>> http://www.lilypond.org/doc/v2.14/Documentation/learning/piano-templates
>>
>> If we take it (w/o midi part, which is not needed here) and add s1 in
>> everything (i.e. upper, lower, dynamics, pedal) at the beginning, then
>> we can see that \fff overlaps the piano staff bar:
>> http://paste.przemoc.net/lilypond/piano-centered-dynamics/
>>
>> How to make dynamic text not overlap the bar, yet shift the note
>> column (not sure if I'm using the correct term here) appropriately, so
>> the text would remain centered?
>>
>> (This mostly works when \dynamics are put into particular Staff [only
>> mostly, because \fff remains then too close to the bar, almost
>> touching it], but I want to have one \dynamics in separate Dynamics
>> between upper and lower Staff within PianoStaff.)
>>
>> My half-workaround is setting DynamicText.X-offset (which in this
>> particular example seems ok with value -0.3, but it doesn't work that
>> well in general), but then DynamicText stops being centered and
>> depending on width of the dynamic text, it may be almost unnoticeable
>> or looks awfully wrong.
>>
>> I hope there are some better solutions.
>>
>
> I, too, have been trying to figure this one out and it appears that we now
> have a solution (though it appears to not be documented in the IR, for some
> reason--CC-ing the bug-list). It turns out that all you need to add the
> following to the appropriate context (Dynamics, in your case):
>
> \override DynamicText.extra-spacing-height = #'(-inf.0 . +inf.0)

Yeah, it works now like when \dynamics are put in Staff. Great!
This is the magic sauce to "glue" dynamic text in Dynamics with the
notes in Staff.

>
> That should get you on your way! I've always been puzzled that
> extra-spacing-width doesn't change this at all (maybe I just don't know how
> to use it properly). The LyricText grob does this SpanBar collision
> avoidance by default, so I was confused as to why DynamicText couldn't do
> the same.

>From my tests it looks that changing DynamicText.extra-spacing-width
normally works only when dynamics are put on Staff, not if they are on
their separate Dynamics.
But thanks to "glueing" (i.e. using above mentioned infinite
extra-spacing-height trick), extra-spacing-width works too!
So now I can also fix dynamic text touching the bar:

\override DynamicText.extra-spacing-width = #'(-0.2 . 0.2)

Here is the PDF with both overrides:
http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics-workaround.pdf

>
> BTW, this does NOT work with 2.18.2, but it does with 2.19.35 at least.
> Haven't checked the other devel versions.

I usually try to use the latest Lilypond available, but good to know
that such "glueing" is moderately recent feature.

>
> Anyway. There you go.

Thank you very much!

Regards.

-- 
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86

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