Dear list,
while trying to import some scores into lilypond i was given as xml export
from a finale using collegue, i stumbled across some problems...
by far the most common one i tried to reduce into the attached files.
while the xml (correctly) contains a Vivace mark in the first bar, the .ly
When wanting to avoid dangerous hard disk operations, i would recommend
andLinux.
It runs a kernel within windows, and on top of the filesystem. You only need
access to ext3 partition somewhere for compiling (since andLinux does not
know ln -sf on NTFS or the like), running lilypond works
Dear list,
this seems to me a bug:
\version 2.12.2
\score{\relative c'{
\time 3/4
r8
8
r4.
8
}}
results in the augmentation dot printed behind the accidental.
Both in 2.12 an 2.13 on this machine.
Best wishes, Arno http://www.nabble.com/file/p23781165/test3.pdf test3.pdf
Thank you, that git hint was helpful!
Yours, Arno
Joe Neeman-2 wrote:
On Sun, 2009-05-24 at 11:53 -0700, ArnoWaschk wrote:
Werner LEMBERG wrote:
i am using a 2.13 lilypond compiled from today's git repo, and i am
observing - in comparison to a version from around 10th of April
Dear list,
i am using a 2.13 lilypond compiled from today's git repo, and i am
observing - in comparison to a version from around 10th of April - that the
page breaking strategy seems to have changed significantly.
Which leads me in one case of a before 47page piano reduction score (1 to 4
Werner LEMBERG wrote:
i am using a 2.13 lilypond compiled from today's git repo, and i am
observing - in comparison to a version from around 10th of April -
that the page breaking strategy seems to have changed significantly.
Which leads me in one case of a before 47page piano reduction
Arno Waschk wrote:
Werner LEMBERG wrote:
i am using a 2.13 lilypond compiled from today's git repo, and i am
observing - in comparison to a version from around 10th of April -
that the page breaking strategy seems to have changed significantly.
Which leads me in one case of a
dear list,
is there a way to tell lilypond in a bigger score to keep - while generally
using \removeemptystaffcontext - certain staffs unhidden, no matter whether
they actualy contain music or not?
is there a way to tell lilypond to show staffs - while generally using
Hi Kieren, hi Nicolas,
thank you very much for your replies.
I am sure i can interpolate from your information to find what i need!
Best, Arno
Kieren MacMillan wrote:
Hi Arno,
is there a way to tell lilypond in a bigger score to keep - while
generally
using \removeemptystaffcontext
