Graham Percival writes:
Getting an actual LilyPond score requires calculating
line breaks and there's no way to get rid of the overhead.
Sure there is. Compile each bar individually with the default
spacing (i.e. whatever you get if your entire score is one bar and
you use
Han-Wen Nienhuys writes:
Architecturally it is very difficult. Rather than making lilypond much
more complicated to do incremental rendering, why not invert the
problem: have your editor control line breaks, and use lilypond to
render just one line of music at a time.
This is exactly what
Thanks Shane, this did the trick. The syntax makes a lot more sense, don't
know what I was thinking...
-Ben
On 7 August 2012 13:24, Shane Frasier sfras...@mac.com wrote:
Ben,
I am still a bit of a novice myself, but I think you want to do something
like:
\new StaffGroup
\new Staff {
Jan Nieuwenhuizen jann...@gnu.org writes:
Han-Wen Nienhuys writes:
Architecturally it is very difficult. Rather than making lilypond much
more complicated to do incremental rendering, why not invert the
problem: have your editor control line breaks, and use lilypond to
render just one line
On Tue, Aug 7, 2012 at 9:52 AM, David Kastrup d...@gnu.org wrote:
Since the main problem in that article is to deal with the I can't read
this, even though I (probably) can write it aspect of LaTeX which is
pretty much the same problem space for LilyPond, it might be useful to
go idea-fishing.
The fermata in the bass clef in the attached pdf is too low, it's
right on top of the upper note in the chord. The source follows. If I
put the \fermata command in the leftSecond line, the fermata appears
below the music. Is there a way that I can put the fermata above the
notes, not clashing with
Tim Slattery slatter...@bls.gov writes:
The fermata in the bass clef in the attached pdf is too low, it's
right on top of the upper note in the chord.
Well, you placed the fermata on a _spacer_ rest rather than on a note.
The source follows. If I put the \fermata command in the leftSecond
I would like to put a dot after the barline to show (something like) a
crotchet tied to a quaver - or according to
http://ranumspanat.com/jacquet_dots.htm subtly different(!)
It's more clear in this Beethoven string quartet:
David Kastrup d...@gnu.org wrote:
Tim Slattery slatter...@bls.gov writes:
The fermata in the bass clef in the attached pdf is too low, it's
right on top of the upper note in the chord.
Well, you placed the fermata on a _spacer_ rest rather than on a note.
I know. But when I put it with the
MING TSANG wrote:
I try to code per the png. I don't know what it is call, therefore I
cannot search LSR.
That note is a breve -- the length of two whole notes. You can use
\breve for the length, as in
fis\breve ~ fis1
However, the boxy notehead in your png is not the current style of
On 8/08/2012, at 5:12 am, Tim Roberts wrote:
However, the boxy notehead in your png is not the current style of writing
that note (which is as a whole note with bars left and right). What you have
there is the Petrucci style. You can still achieve the boxy notehead by
overriding the
On Aug 6, 2012, at 12:20 PM, David G wrote:
I would like to put a dot after the barline to show (something like) a
crotchet tied to a quaver - or according to
http://ranumspanat.com/jacquet_dots.htm subtly different(!)
It's more clear in this Beethoven string quartet:
2012/8/8 james james.lilyp...@googlemail.com:
On Aug 6, 2012, at 12:20 PM, David G wrote:
I would like to put a dot after the barline to show (something like) a
crotchet tied to a quaver - or according to
http://ranumspanat.com/jacquet_dots.htm subtly different(!)
It's more clear in this
LP users,
I encounter compile error from init.ly. Can anyone experience this before?
Detail of the error .
Starting lilypond-windows.exe 2.14.2 [definities-1159.ly]...
Processing `D:/mingtsang-2/lied-1159/definities-1159.ly'
Parsing...
MING TSANG tsan...@rogers.com writes:
LP users,
I encounter compile error from init.ly. Can anyone experience this
before?
Detail of the error
.
Starting lilypond-windows.exe 2.14.2 [definities-1159.ly]...
Processing
David Kastrup, Tim Roberts Matthew Collett:
Thank you for all your help. I added \once to your suggestion and it works
perfectly (very similar to the original).
\once\override NoteHead #'style = #'baroque fis\breve(s2*2 s4 fis1)
Blessing in+,
Ming
Am 08.08.2012 02:18, schrieb MING TSANG:
I encounter compile error from init.ly. Can anyone experience this before?
Detail of the error .
Starting lilypond-windows.exe 2.14.2 [definities-1159.ly]...
Processing
17 matches
Mail list logo
