Kieran Coulter wrote:
Hello again,
I found the piece and version number in question, it's the 4th ballade by
Chopin, and convert-ly gets it up to version 2.5.18 before it can't get any
further. Am I right in assuming that the last line in the log file is the one
that prevents the file rendering?
You should read the log output from convert-ly, which says:
Not smart enough to convert auto beam settings
Auto beam settings must now specify each interesting moment in a measure
explicitely; 1/4 is no longer multiplied to cover moments 1/2 and 3/4 too.
Please refer to the manual for details, and update manually.
What you should do in this particular case is to replace the line (which
appears twice in the file)
\override Staff.autoBeamSettings #'(end 1 24 6 8) =
#(ly:make-moment 3 24)
with the following lines:
#(override-auto-beam-setting '(end 1 24 6 8) 3 24 'Staff)
#(override-auto-beam-setting '(end 1 24 6 8) 6 24 'Staff)
#(override-auto-beam-setting '(end 1 24 6 8) 9 24 'Staff)
#(override-auto-beam-setting '(end 1 24 6 8) 12 24 'Staff)
#(override-auto-beam-setting '(end 1 24 6 8) 15 24 'Staff)
and similarly to replace the line
#(override-auto-beam-setting '(end 1 24 6 8) 3 24 )
with the following lines:
#(override-auto-beam-setting '(end 1 24 6 8) 3 24)
#(override-auto-beam-setting '(end 1 24 6 8) 6 24)
#(override-auto-beam-setting '(end 1 24 6 8) 9 24)
#(override-auto-beam-setting '(end 1 24 6 8) 12 24)
#(override-auto-beam-setting '(end 1 24 6 8) 15 24)
Once you have done that, you go to the top of the file and replace
\version "2.5.18"
by
\version "2.5.21"
to tell convert-ly that you have manually handled that conversion. Now,
you can
run convert-ly again to update the file from 2.5.21 to your current version.
If you again look at the log output from convert-ly, you will notice
that it says
(among others)
Not smart enough to convert space-function
and
Span_dynamic_performer has been merged into Dynamic_performer
To handle the latter message, just remove the line
\consists "Span_dynamic_performer"
Regarding the "space-function", I would simply start by trying to
comment out
the lines that override the space-function property and compare the
corresponding
bars of the output with the PDF file in Mutopia to see if it's worth
spending time to
find a corresponding tweak or of LilyPond has improved so that the tweak
is no more
necessary.
Now, that you run the file through LilyPond, you will hopefully not get
any serious
error messages (at least I don't when I try it here). However, you will
notice that
the output isn't entirely perfect and that LilyPond spits out a number
of warning
messages, that may be worth investigating. In other words, convert-ly
cannot
handle everything. For example, you may want to fix the following:
- The "più f" indications are wrong. When the original .ly file was
written,
you had to use LaTeX commands to get this accented character, now you
should
instead input the character directly in your editor and save the file
in UTF-8
encoding. Fortunately, these indications are defined as macros at the
top of the
.ly file, so you only have to make the change in these macro
definitions instead
of having to search through the full file.
- Bar 134 has some very funny looking slurs for the acciaccaturas. If
you look
in the .ly file, you will notice that the original editor has included
a number of
extra tweaks to handle some layout problem in LilyPond version 2.1.0.
Again, I propose to simply comment out all these extra \overrides
first and
see if you get an acceptable output.
/Mats
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
