spanBar und StaffGroup in Partitur

[chf]

Code Auswählen Erweitern


\version "2.18.2"
pOne = \relative c {c1 c }
pTwo = \relative c' {c1 c2 c  }
upper = {c\breve}
lower = {c\breve}
ped = {c\breve}
car = \relative c' {c2 c c2. c4 }


\score {
\new StaffGroup <<
\new StaffGroup <<                                                   
\new Staff    << \pOne     >>
\new Staff    << \pTwo     >>
  >>
\new Staff    << \car    >>

\new StaffGroup \with {
  systemStartDelimiter = #'SystemStartSquare
} <<
  \new PianoStaff \with {
    instrumentName = "ORGEL"
  } <<
    \new Staff = "OrgelRechetHand" {
      \clef treble  \upper
    }
    \new Staff = "OrgelLinkeHand" {
      \clef bass    \lower
    }
  >>
  \new Staff = "OrgelPedal" {
    \clef bass     \ped
  }
   >>
>>
}







Liebe Freunde,

mit  \override StaffGroup.SpanBar #'stencil = ##f  kann ich alle SpanBars entfernen. Ich hätte aber gerne die innerhalb der StaffGroup erhalten
und nur die Trennung der Stimmgruppen sichtbar gemacht. Leider weiß ich nicht, wie das geht.
Könnt ihr bitte mein nicht ganz kleines Beispiel  "aufbereiten"?

Gruß
chf

[harm6]

BarLine.allow-span-bar ist der relevante grob-property-path.

Code Auswählen Erweitern


\version "2.18.2"

pOne = \relative c { c1 c }
pTwo = \relative c' { c1 c2 c }
upper = { c\breve }
lower = { c\breve }
ped = { c\breve }
lkw = \relative c' { c2 c c2. c4 }

\score {
  \new StaffGroup <<

    \new StaffGroup
      <<
        \new Staff
          \pOne
        \new Staff
          \with { \override BarLine.allow-span-bar = ##f }
          \pTwo
      >>

    \new Staff
      \with { \override BarLine.allow-span-bar = ##f }
      \lkw

    \new StaffGroup
      \with { systemStartDelimiter = #'SystemStartSquare }
      <<
        \new PianoStaff
          \with { instrumentName = "ORGEL" }
          <<
            \new Staff = "OrgelRechetHand" {
              \clef treble \upper
            }
            \new Staff = "OrgelLinkeHand" {
              \clef bass \lower
            }
          >>
        \new Staff = "OrgelPedal" {
          \clef bass \ped
        }
      >>
  >>
}


HTH,
  Harm

EDIT
Variable `car' umbenannt

[chf]

Danke, Harm!

[harm6]

Nachtrag:
Nenne eine Variable nie `car'

Ansonsten führt:

Code Auswählen Erweitern


\version "2.18.2"

car = \relative c' { c2. }
{ \time 3/4 \car }

zu:

/home/harm/lilypond/usr/share/lilypond/current/ly/music-functions-init.ly:1379:26: In expression (car fraction):
/home/harm/lilypond/usr/share/lilypond/current/ly/music-functions-init.ly:1379:26: Wrong type to apply: #<Prob: Music C++: Music((origin . #<location atest-65.ly:587:7>) (element . #<Prob: Music C++: Music((origin . #<location atest-65.ly:587:20>) (elements #<Prob: Music C++: Music((duration . #<Duration 2. >) (pitch . #<Pitch c' >) (origin . #<location atest-65.ly:587:22>))((display-methods #<procedure #f (note parser)>) (name . NoteEvent) (iterator-ctor . #<primitive-procedure ly:rhythmic-music-iterator::constructor>) (types general-music event note-event rhythmic-event melodic-event)) >
))((display-methods #<procedure #f (expr parser)> #<procedure #f (seq parser)>) (name . SequentialMusic) (length-callback . #<primitive-procedure ly:music-sequence::cumulative-length-callback>) (start-callback . #<primitive-procedure ly:music-sequence::first-start-callback>) (elements-callback . #<procedure #f (m)>) (iterator-ctor . #<primitive-procedure ly:sequential-iterator::constructor>) (types general-music sequential-music)) >
))((display-methods #<procedure #f (m parser)>) (name . RelativeOctaveMusic) (to-relative-callback . #<primitive-procedure ly:relative-octave-music::relative-callback>) (iterator-ctor . #<primitive-procedure ly:music-wrapper-iterator::constructor>) (length-callback . #<primitive-procedure ly:music-wrapper::length-callback>) (start-callback . #<primitive-procedure ly:music-wrapper::start-callback>) (types music-wrapper-music general-music relative-octave-music)) >

Muss ja nicht sein ...


Gruß,
  Harm

P.S
Tatsächlich gibt es natürlich noch einige Benennungen, die man eher nicht verwenden sollte. Ich kenn allerdings keine gute Methode, diese aufzuzählen, da hilft nur die error-message wirklich zu lesen