# Tag Info

4

In order not to complicate the example by adding additional spacing until LilyPond prefers to pick a kneed beam on its own, I am using a voicing change to get this, moving from "first voice" settings in the lower staff to "fourth voice" setting in the higher. Usually \voiceOne/\voiceTwo (can be implied by << ... \\ ... >>) should be used for the ...

3

You use multiple voices. Here is a small example which semi-manually puts beams in the second of two voices in a << {first voice} \\ {second voice} >> construct as the autobeamer does not work across skips or rests. \relative { \key e\major \time 3/4 << \repeat unfold 24 { s16 e'' } \\ << \repeat unfold 2 { ...

4

The answer is "Yes you can, but doing this is a really bad idea". It's a bad idea because you will probably soon want to write C natural or F natural with a D major key signature, and if you make "c" mean "c sharp" you won't have a good way to do that. If the key signature changes during the piece, things will quickly get very confusing. Check out "note ...

0

Well, an \autochange plays its contents in a sandbox in order to calculate the change requests, then does it "for real". But the sandbox does not actually have the staves where a \change could have an effect. So you need to put the \change in the "for real part", and provide a \context Voice where you'll be able to capture the autochange voice produced ...

0

Add the time signature engraver using \consists, and (optionally) set the context to use numeric time signatures: \version "2.18.2" \new ChordNames \with { \override BarLine.bar-extent = #'(-2 . 2) \consists "Bar_engraver" \consists "Time_signature_engraver" \numericTimeSignature }

5

Use /autochange: \new PianoStaff << \new Staff = "up" { \new Voice = "melOne" { \key g \major \autochange \relative c' { g8 b a c b d c e d8 r fis, g a2 } } } \new Staff = "down" { \key g \major \clef bass } >> For more information, see ...

1

It would appear that all that you really want is to render with a higher number of pixels. LilyPond renders its PNG images by default at a comparatively low resolution of 101dpi. It sounds like calling lilypond with the -dresolution=400 option should do the trick for your problem. Note that LilyPond itself has various vector-class output options, like ...

0

I would try to take the encapsulated postscript (.eps) file generated by lilypond, and render it to PNG at the resolution/size you desire, as indicated in this SO question. The 2.19 version has (some) control of the size of the chord diagrams (documentation here, I'm not sure when this feature was introduced), however using \markup { ...

Top 50 recent answers are included