lilypond-user
[Top][All Lists]
Advanced

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

Re: Problem with \break command


From: Peter Toye
Subject: Re: Problem with \break command
Date: Thu, 9 Apr 2015 16:30:39 +0100

Simon,

Thanks - it gets somewhere.

The reason for the extra braces was that it's a cut-down "tiny" version of a more complex score with polyphony.

Best regards,

Peter
mailto:address@hidden
www.ptoye.com

-------------------------
Thursday, April 9, 2015, 4:15:26 PM, you wrote:


Hello,

the problem seems to be that the Bar_engraver takes part in triggering the clef on the new line, so without it no clef is printed. I tried to come up with a workaround, omitting the bar lines, but it has a major drawback: it still leaves some space for the omitted bar lines, which I can’t explain nor circumvent: all the overrides I tried had no effect. Anybody else?
Some other remarks:
It might make sense to make the context modifications (\remove) in a \layout environment also, such as to get more legible code. For the same reason, always store your music in variables, as explained in the Learning Manual. And: the {} around each music line aren’t necessary.

HTH, Simon

Am 09.04.2015 um 16:49 schrieb Peter Toye:
\version "2.18.2"

\language "english"

\layout {
ragged-right  = ##t
}

\score {

\new Staff \with {
  \remove "Bar_number_engraver"
  \remove "Time_signature_engraver"
  \remove "Bar_engraver"

}

\new Voice \with {
  \remove "Stem_engraver"
}

\relative c {
  \key c \major
  \clef bass
 
  { g4_5 a_4 b_3 c_2 d_1  }
  \break

  {  g,4 a g a b a b a }        
  \break
 
  {g4 af g af bf a bf a }

}

}

reply via email to

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