Hello,
I'm trying to make some notation for guitar with Chords, Chord Rhythms, Melody (Standard Notation), and Melody (Tab). My staves are all over the place.

Originally configured, lilypond ignored the layout indicated in the \score block. Putting contents of \staffClassicalGuitar in a \new Staff block got lilypond to create the staff layout indicated in the \score block, but with an extra, empty stave.

My guess is that lilypond is automatically creating a stave somewhere that I'm not aware of.

Thanks,
Kale

Originally (layout ignored):
\version "2.16.2"

thechords =
    {
    \chords{  a }
    }

melody =
    {
    a
    }

staffClassicalGuitar =
    {
    \relative c'
        {
        \melody
        \bar "|."
        }
    }

staffTabGuitar =
    {
    \new TabStaff
        {
        \clef "moderntab"
        \relative c'
            {
            \melody
            }
        }
    }

rhythm =
    {
    \new Staff
        {
        \improvisationOn
        \relative c'
            {
            a
            }
        }
        }

\score
    {
<< \thechords \\ \rhythm \\ \staffClassicalGuitar \\ \staffTabGuitar >>
    }


"Fixed" (layout followed, but with extra blank stave):

\version "2.16.2"

thechords =
    {
    \chords{  a }
    }

melody =
    {
    a
    }

staffClassicalGuitar =
    {
    \new Staff
        {
        \relative c'
            {
            \melody
            \bar "|."
            }
        }
    }

staffTabGuitar =
    {
    \new TabStaff
        {
        \clef "moderntab"
        \relative c'
            {
            \melody
            }
        }
    }

rhythm =
    {
    \new Staff
        {
        \improvisationOn
        \relative c'
            {
            a
            }
        }
        }

\score
    {
<< \thechords \\ \rhythm \\ \staffClassicalGuitar \\ \staffTabGuitar >>
    }




On 06/21/2013 12:01 PM, [email protected] wrote:
Send lilypond-user mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."


Today's Topics:

    1. Re:Gregorian: modern staff? Lyrics spacing? (Eluze)
    2. Re:Gregorian: modern staff? Lyrics spacing? (Eluze)
    3. SpanBar joining Ossia & main staff no longer printed in 2.17
       (Marc Mouries)
    4. Re:SpanBar joining Ossia & main staff no longer printed in
       2.17 (Nick Payne)
    5. Re:SpanBar joining Ossia & main staff no longer printed in
       2.17 (Thomas Morley)
    6. Re:SpanBar joining Ossia & main staff no longer printed in
       2.17 (Thomas Morley)


----------------------------------------------------------------------

Message: 1
Date: Thu, 20 Jun 2013 23:14:23 +0200
From: Eluze <[email protected]>
To: [email protected]
Subject: Re: Gregorian: modern staff? Lyrics spacing?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

I have no idea which snippet you're talking of, but this might help:

\new Lyrics \with {
% \override VerticalAxisGroup #'minimum-Y-extent = #'(-0 . 0)
\override
VerticalAxisGroup.nonstaff-relatedstaff-spacing.minimum-distance = #2
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.basic-distance
= #2
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #.4
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.stretchability
= #99
}

with numbers you can adapt

Eluze


Am 20.06.2013 22:37, schrieb Frank Steinmetzger:
Dear list

I'm dealing with Gregorian notation for the first time by reproducing a Sch?tz
piece from IMSLP?.  After digging through the docs, I managed to solve most of
the hurdles that I came across by myself.

I'm almost finished and only need your advice for two things. Please see
attached a screenie crop of the original and of what I achieved so far.




2) I applied the docs? snippet on vertical lyrics spacing to get the lyrics
     closer to the staff. The page is rather crowded, every millimetre would
     help. But it doesn?t seem to have any effect. What am I missing?





------------------------------

Message: 2
Date: Thu, 20 Jun 2013 22:58:58 +0200
From: Eluze <[email protected]>
To: [email protected]
Subject: Re: Gregorian: modern staff? Lyrics spacing?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

I have no idea which snippet you're talking of, but this might help:

\new Lyrics \with {
% \override VerticalAxisGroup #'minimum-Y-extent = #'(-0 . 0)
\override
VerticalAxisGroup.nonstaff-relatedstaff-spacing.minimum-distance = #2
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.basic-distance
= #2
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #.4
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.stretchability
= #99
}

with numbers you can adapt

Eluze


Am 20.06.2013 22:37, schrieb Frank Steinmetzger:
Dear list

I'm dealing with Gregorian notation for the first time by reproducing a Sch?tz
piece from IMSLP?.  After digging through the docs, I managed to solve most of
the hurdles that I came across by myself.

I'm almost finished and only need your advice for two things. Please see
attached a screenie crop of the original and of what I achieved so far.




2) I applied the docs? snippet on vertical lyrics spacing to get the lyrics
     closer to the staff. The page is rather crowded, every millimetre would
     help. But it doesn?t seem to have any effect. What am I missing?





------------------------------

Message: 3
Date: Thu, 20 Jun 2013 22:30:46 -0400
From: Marc Mouries <[email protected]>
To: lilypond-user <[email protected]>
Subject: SpanBar joining Ossia & main staff no longer printed in 2.17
Message-ID:
        <capup_ohsg1qsqsyf5o5-5zyqx7ctmox_piduadp9x+fsibc...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi Lilyponders,

I am typesetting a score with an ossia using the snippet:
http://lsr.dsi.unimi.it/LSR/Snippet?id=125

In version 2.16, this snippet print a spanBar joining the ossia and the
main staff.
In 2.17, the following warning is printed in the logs:

warning: No span bar glyph defined for bar glyph ':'; ignoring.


I haven't seen described in the changes page and in the doc how to migrate

        \override SpanBar #'glyph-name = #":"



-- Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.gnu.org/archive/html/lilypond-user/attachments/20130620/49ac91d9/attachment.html>

------------------------------

Message: 4
Date: Fri, 21 Jun 2013 17:30:22 +1000
From: Nick Payne <[email protected]>
To: [email protected]
Subject: Re: SpanBar joining Ossia & main staff no longer printed in
        2.17
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 21/06/13 12:30, Marc Mouries wrote:
Hi Lilyponders,

I am typesetting a score with an ossia using the snippet:
http://lsr.dsi.unimi.it/LSR/Snippet?id=125

In version 2.16, this snippet print a spanBar joining the ossia and the
main staff.
In 2.17, the following warning is printed in the logs:

warning: No span bar glyph defined for bar glyph ':'; ignoring.


I haven't seen described in the changes page and in the doc how to migrate

        \override SpanBar #'glyph-name = #":"
If you replace ":" with "!" you will get a nice set of dashes between
the ossia and main staff. I found this by trial and error a while ago
when following this snippet to create an ossia stave with 2.17.




------------------------------

Message: 5
Date: Fri, 21 Jun 2013 10:36:21 +0200
From: Thomas Morley <[email protected]>
To: Nick Payne <[email protected]>
Cc: [email protected]
Subject: Re: SpanBar joining Ossia & main staff no longer printed in
        2.17
Message-ID:
        <cabsfgyvyd7pd+oxoswcsdo3vbgvnbrcyau18vgrpjg1k7lg...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2013/6/21 Nick Payne <[email protected]>:
On 21/06/13 12:30, Marc Mouries wrote:
Hi Lilyponders,

I am typesetting a score with an ossia using the snippet:
http://lsr.dsi.unimi.it/LSR/Snippet?id=125

In version 2.16, this snippet print a spanBar joining the ossia and the
main staff.
In 2.17, the following warning is printed in the logs:

warning: No span bar glyph defined for bar glyph ':'; ignoring.


I haven't seen described in the changes page and in the doc how to migrate

         \override SpanBar #'glyph-name = #":"

If you replace ":" with "!" you will get a nice set of dashes between the
ossia and main staff. I found this by trial and error a while ago when
following this snippet to create an ossia stave with 2.17.
No need for trial and error.

LSR currently runs 2.14.2

See
http://lsr.dsi.unimi.it/LSR/html/contributing.html
about version-statement.

Obviously, you should run convert-ly.

-Harm



------------------------------

Message: 6
Date: Fri, 21 Jun 2013 11:23:23 +0200
From: Thomas Morley <[email protected]>
To: Nick Payne <[email protected]>
Cc: [email protected]
Subject: Re: SpanBar joining Ossia & main staff no longer printed in
        2.17
Message-ID:
        <cabsfgywttn9vz2rxv8ttufqr1-mse4y9dps5t9idw3uynbp...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2013/6/21 Thomas Morley <[email protected]>:
2013/6/21 Nick Payne <[email protected]>:
On 21/06/13 12:30, Marc Mouries wrote:
Hi Lilyponders,

I am typesetting a score with an ossia using the snippet:
http://lsr.dsi.unimi.it/LSR/Snippet?id=125

In version 2.16, this snippet print a spanBar joining the ossia and the
main staff.
In 2.17, the following warning is printed in the logs:

warning: No span bar glyph defined for bar glyph ':'; ignoring.


I haven't seen described in the changes page and in the doc how to migrate

         \override SpanBar #'glyph-name = #":"

If you replace ":" with "!" you will get a nice set of dashes between the
ossia and main staff. I found this by trial and error a while ago when
following this snippet to create an ossia stave with 2.17.
No need for trial and error.

LSR currently runs 2.14.2

See
http://lsr.dsi.unimi.it/LSR/html/contributing.html
about version-statement.

Obviously, you should run convert-ly.
Ok, trying it myself.

convert-ly _doesn't_ work for \override SpanBar #'glyph-name = #":"

Please file a bug-report.

-Harm



------------------------------

_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user


End of lilypond-user Digest, Vol 127, Issue 75
**********************************************

--
Kale Good: Guitar Instructor
website: phillyguitarlessons.com <http://phillyguitarlessons.com>
email: [email protected]
phone: (215)260-5383
address:

 * mailing & lessons: 4705 Baltimore Ave, Phila, PA 19143
 * lessons: 1867 Frankford Ave. Phila, PA 19125

Read my article "The Seven Secrets to Six String Success <http://www.guitarnoise.com/lesson/seven-secrets-to-six-string-success/>" at GuitarNoise.com <http://guitarnoise.com>
Leading the Journey from No-Skills-Guitarist to Talented Musician!
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to