Re: global marks

[Simon Albrecht]

Hello,

I usually don’t write this in the \score block, but instead define a music function like
global = #(define-music-function (parser location mus) (ly:music?)
  #{ << \helper
        \relative { \key as \minor \time 9/16 \partial 8. \autoBeamOff
                      $mus }
         >> #})
with \helper defined as  a stream of silent rests and all kinds of events (\tempo, \time, \override, \bar etc.) which are common to all voices. This really simplifies work for me.
Music is then entered as
soprano = \global { c'8. | f4.~ 8. }

Yours, Simon

Am 13.02.2015 um 01:20 schrieb Flaming Hakama by Elaine:

I am inclined to agree with Kieren. Manually putting the marks in EVERY
staff can be tedious and error prone, depending on how many you plan to use.
The better way is to create another voice that only contains spacer rests
with the marks at the appropriate position(s), then make it simultaneous
with a voice in each staff. That way you only have to define where the marks
are once, but it is replicated perfectly.

I am wondering if folks would mind commenting on their experience using this type of approach:

    new Staff <<
      \new Voice \markVoice
      \new Voice \partI
    >>

In particular, how much can you put in the \markVoice?  Would this approach work for:

    o Marks

    o Tempi
    o Time signatures
    o Key signatures
    o Repeats
    o Double bar lines
    o Symbols like coda, DS, fermata

Also, if you are using tags, is this how you would combine these syntaxes:

new Staff <<
      \new Voice \markVoice
      \new Voice \keepWithTag #'tagPartI \partI
    >>

Thanks,

David Elaine Alt

415 . 341 .4954                                           "Confusion is highly underrated"

address@hidden

self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user