lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: External \notes Block Acting Odd


From: Mats Bengtsson
Subject: Re: External \notes Block Acting Odd
Date: Wed, 07 Jul 2004 10:43:57 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616



Will Oram wrote:
Usually when I work with multiple staves, I keep time sig, key sig, and tempo changes separate from the music.

I upgraded to 2.2.4, and I started experimenting with the alternative way of defining instruments.

Old:
\context Staff = "flauti" <<
                \set Staff.midiInstrument = #"flute"
\set Staff.instrument = \markup { \center-align < "Flauto I." > }
                \set Staff.instr      = \markup { \center-align < "Fl." > }
                \barlines
                \theFlutes >>

New:
\new Staff {
            \set Staff.instrument = \markup { "Flauti" }
            \set Staff.instr = \markup { Fl. }
            \set Staff.midiInstrument = #"flute"
            \barlines
            \new Voice { \Flute }
        }

\barlines contains key/time/tempo changes, like this:

barlines = \notes {
    \override Score.MetronomeMark   #'transparent = ##t
    \override Score.TupletBracket   #'bracket-visibility = ##f
    \override Score.TextScript   #'font-magnification = #1.25
    \set Score.skipBars = ##t

    \time 3/4
    \key g \major
s2.*17
    \time 6/8
}
Originally, the music and \barlines would tie in perfectly. With the changes in definition, lilypond now puts \barlines in front in the form of white space, and then the music follows normally. Any recommendations as to how to avoid this problem?

I'm sure you can figure it out yourself if you compare the old and
new version.
Hint: <<...>> means simultaneous, {...} means sequential.

   /Mats




reply via email to

[Prev in Thread] Current Thread [Next in Thread]