Hello,
I have difficulty understanding this tiny example, which is a
breakdown of my general problem:
{
%\key a \major
\chords
{
a1 c
}
\relative c''
{
a1 c
}
}
Without the \key command, the chords are shown
On 18 April 2011 10:30, Christian Eitner 7enderh...@gmail.com wrote:
Hello,
I have difficulty understanding this tiny example, which is a
breakdown of my general problem:
{
%\key a \major
\chords
{
a1 c
}
\relative c''
{
Dear Xavier,
On 18 April 2011 10:40, Xavier Scheuer x.sche...@gmail.com wrote:
It is due to implicit context creation.
If you explicit your contexts (Staff, ChordNames) then such problem
would not appear.
As explained in the doc, \chords { ... } is a shortcut notation for
\new ChordNames
On 4/18/2011 9:03 AM, Christian Eitner wrote:
Dear Xavier,
On 18 April 2011 10:40, Xavier Scheuerx.sche...@gmail.com wrote:
It is due to implicit context creation.
If you explicit your contexts (Staff, ChordNames) then such problem
would not appear.
As explained in the doc, \chords { ... }
Dear David,
I would simply use skips:
\version 2.12.3
{
\chords
{
s1*2
a1 c
}
\relative c''
{
a1 c a c
}
}
Isn't this what you mean?
Yes, but there is really a lot of stuff going on before the couple of
bars with chords, and I would
On 18 April 2011 15:58, Christian Eitner 7enderh...@gmail.com wrote:
Yes, but there is really a lot of stuff going on before the couple of
bars with chords, and I would have to adjust the number of skipped
bars each time something changed.
Is there perhaps a way to tell the new chords
Dear Xavier,
Is there perhaps a way to tell the new chords context to be placed
above alread existent ones?
There is the alignAboveContext property.
Cf. NR 1.6.2 Modifying single staves
\version 2.13.60
\score {
\new Staff = main {
\relative c'' {
\key a \major
