Re: How to adjust space between ChordNames and Staff?
On 14 January 2017 at 21:12, Trevor Daniels wrote:
>
> Thomas Morley wrote Friday, January 13, 2017 9:05 PM
>
>
> > 2017-01-13 17:05 GMT+01:00 Trevor Daniels :
> >>
> >> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
> >>
> >>> On 13 January 2017 at 01:20, Trevor Daniels
> wrote:
> >>>
> Interesting. Does that mean the ChordNames and Lyrics contexts behave
> differently wrt the vertical spacing controls when these are placed
> within a
> \with { } block, since Lyrics can be spaced out that way?
>
> If so, is this intended for some reason ... or a bug?
> >>>
> >>> Thanks Harm. That did the trick. However, I concur with Trevor about
> the
> >>> confusing difference compared to Lyrics. I assumed that they'd work the
> >>> same way so I did not occur to me to try the \layout block. If it /is/
> an
> >>> intended behaviour, there should probably be a note that the settings
> >>> won't work with \with { }.
> >>
> >> Exactly, but I think we need to understand exactly what the problem is
> before
> >> we can decide (a) whether this _is_ a bug and if so (b) whether it is a
> coding or
> >> a documentation problem.
> >>
> >> Copying to bug list so this doesn't get forgotten.
> >
> > No bug.
> > It's \chords vs \chordmode.
> >
> > \chords (as a shortcut) already created a ChordNames-context, see:
> >
> > chordStuff = \chords { c1 d:m }
> > \void \displayLilyMusic \chordStuff
> >
> > So if you really want to use \chords you need to put overrides, etc
> > into \layout or use
> > \chords \with { ... }
> > at least with newer devel-versions.
> >
> > If you use \chordmode you can do
> > \new ChordNames \with { ... } \chordmode
>
> Excellent explanation! Many thanks!
>
> So no bug, but we should add a paragraph somewhere in the NR to make this
> clear. I'll start on that in a day or two.
>
> Trevor
>
>
Thanks for the explanation. And thanks to Trevor for the NR part.
I had to move from \chords to \chordmode anyway because concatenating two
set of chords did not work ( e.g. \new ChordNames { \chordsPartI
\chordsPartII } ). The second part was thrown under the whole system.
However, at that point I had already moved the padding in the \layout block.
The \chords mechanism might also explain why combining did not work—a
second ChordNames was created and ...
-Risto
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: How to adjust space between ChordNames and Staff?
Thomas Morley wrote Friday, January 13, 2017 9:05 PM
> 2017-01-13 17:05 GMT+01:00 Trevor Daniels :
>>
>> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
>>
>>> On 13 January 2017 at 01:20, Trevor Daniels wrote:
>>>
Interesting. Does that mean the ChordNames and Lyrics contexts behave
differently wrt the vertical spacing controls when these are placed within
a
\with { } block, since Lyrics can be spaced out that way?
If so, is this intended for some reason ... or a bug?
>>>
>>> Thanks Harm. That did the trick. However, I concur with Trevor about the
>>> confusing difference compared to Lyrics. I assumed that they'd work the
>>> same way so I did not occur to me to try the \layout block. If it /is/ an
>>> intended behaviour, there should probably be a note that the settings
>>> won't work with \with { }.
>>
>> Exactly, but I think we need to understand exactly what the problem is before
>> we can decide (a) whether this _is_ a bug and if so (b) whether it is a
>> coding or
>> a documentation problem.
>>
>> Copying to bug list so this doesn't get forgotten.
>
> No bug.
> It's \chords vs \chordmode.
>
> \chords (as a shortcut) already created a ChordNames-context, see:
>
> chordStuff = \chords { c1 d:m }
> \void \displayLilyMusic \chordStuff
>
> So if you really want to use \chords you need to put overrides, etc
> into \layout or use
> \chords \with { ... }
> at least with newer devel-versions.
>
> If you use \chordmode you can do
> \new ChordNames \with { ... } \chordmode
Excellent explanation! Many thanks!
So no bug, but we should add a paragraph somewhere in the NR to make this
clear. I'll start on that in a day or two.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: How to adjust space between ChordNames and Staff?
2017-01-13 17:05 GMT+01:00 Trevor Daniels :
>
> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
>
>> On 13 January 2017 at 01:20, Trevor Daniels wrote:
>>
>>> Thomas Morley wrote Thursday, January 12, 2017 10:26 PM
>>>
2017-01-12 21:13 GMT+01:00 Risto Vääräniemi :
> The spacing between ChordNames and Staff seems a bit tight by default.
> I've
> been trying to adjust it but I haven't figured out the right magic words
Do it in \layout
chordStuff = \chords { c1 d:m }
melody = \relative c'' { c4 c c c | d d d d }
\score {
<<
\new ChordNames { \chordStuff }
\new Staff { \melody }
>>
\layout {
\context {
\ChordNames
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding =
#10
}
}
}
>>>
>>> Interesting. Does that mean the ChordNames and Lyrics contexts behave
>>> differently wrt the vertical spacing controls when these are placed within a
>>> \with { } block, since Lyrics can be spaced out that way?
>>>
>>> If so, is this intended for some reason ... or a bug?
>>
>> Thanks Harm. That did the trick. However, I concur with Trevor about the
>> confusing difference compared to Lyrics. I assumed that they'd work the
>> same way so I did not occur to me to try the \layout block. If it /is/ an
>> intended behaviour, there should probably be a note that the settings
>> won't work with \with { }.
>
> Exactly, but I think we need to understand exactly what the problem is before
> we can decide (a) whether this _is_ a bug and if so (b) whether it is a
> coding or
> a documentation problem.
>
> Copying to bug list so this doesn't get forgotten.
>
> Trevor
>
No bug.
It's \chords vs \chordmode.
\chords (as a shortcut) already created a ChordNames-context, see:
chordStuff = \chords { c1 d:m }
\void \displayLilyMusic \chordStuff
So if you really want to use \chords you need to put overrides, etc
into \layout or use
\chords \with { ... }
at least with newer devel-versions.
If you use \chordmode you can do
\new ChordNames \with { ... } \chordmode
Additional Examples:
melody = \relative c'' { c4 c c c | d d d d }
\score {
<<
\chords
\with {
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #10
}
{ c1 d:m }
\new Staff \melody
>>
}
\score {
<<
\new ChordNames
\with {
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #10
}
\chordmode { c1 d:m }
\new Staff \melody
>>
}
Sorry for late reply, the job ...
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: How to adjust space between ChordNames and Staff?
Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM
> On 13 January 2017 at 01:20, Trevor Daniels wrote:
>
>> Thomas Morley wrote Thursday, January 12, 2017 10:26 PM
>>
>>> 2017-01-12 21:13 GMT+01:00 Risto Vääräniemi :
>>>
The spacing between ChordNames and Staff seems a bit tight by default. I've
been trying to adjust it but I haven't figured out the right magic words
>>>
>>> Do it in \layout
>>>
>>> chordStuff = \chords { c1 d:m }
>>> melody = \relative c'' { c4 c c c | d d d d }
>>> \score {
>>> <<
>>>\new ChordNames { \chordStuff }
>>>\new Staff { \melody }
>>> >>
>>> \layout {
>>> \context {
>>>\ChordNames
>>>\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding =
>>> #10
>>> }
>>> }
>>> }
>>
>> Interesting. Does that mean the ChordNames and Lyrics contexts behave
>> differently wrt the vertical spacing controls when these are placed within a
>> \with { } block, since Lyrics can be spaced out that way?
>>
>> If so, is this intended for some reason ... or a bug?
>
> Thanks Harm. That did the trick. However, I concur with Trevor about the
> confusing difference compared to Lyrics. I assumed that they'd work the
> same way so I did not occur to me to try the \layout block. If it /is/ an
> intended behaviour, there should probably be a note that the settings
> won't work with \with { }.
Exactly, but I think we need to understand exactly what the problem is before
we can decide (a) whether this _is_ a bug and if so (b) whether it is a coding
or
a documentation problem.
Copying to bug list so this doesn't get forgotten.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
