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? If so, the the line in question is
error: unknown translator: 'span_dynamic_performer' Here is the entire log: -compilation-*- Changing working directory to `J:/Mutopia Piano Database/Chopin/Ballades' Processing `J:/Mutopia Piano Database/Chopin/Ballades/ballade-4.ly' Parsing... error: Incorrect lilypond version: 2.5.18 (2.7.38, 2.10.20) error: Consider updating the input with the convert-ly script error: unknown translator: `Span_dynamic_performer' I tried simply removing that log, but then I get a win32 exception that triggers my Visual Studio debugger, so it doesn't seem to work. What can I use to manually update the file so I can convert it all the way to 2.10.20? And after I do the manual adjustment, would I then manually update the version number to 2.5.19? Thanks so much for the assistance. >------- Original Message Follows ------- >From: "Mats Bengtsson" >To: "Kieran Coulter" >Cc: >Subject: Re: gap(s) in versions for convert-ly >Date: Wed, 18 Apr 2007 08:39:53 +0200 > >As you have noticed, there are a few constructs that convert-ly isn't >smart enough >to handle automatically. These happen for a number of LilyPond versions, >but >this doesn't mean that convert-ly isn't able to handle any scores that >are older than >so, it just means that convert-ly fails to handle the small percentage >of scores that >happened to use that particular feature. >Also, it's often very easy to do the corresponding changes manually, so >there's >no reason to dump the file even if convert-ly can't handle all the >conversion steps >automatically. The typical procedure is: >1. Figure out from the convert-ly error message at which LilyPond >version the > problem appears, let's say in the conversion to version 2.5.18. >2. Run convert-ly up to the version number before the problem appears: >convert-ly --to=2.5.17 myfile.ly >3. Manually update the file and manually update the version number in >the file > by one step (i.e. to 2.5.18 in this case) >4. use convert-ly to upgrade the file to the current version. > >Of course, step 3 may require some detective work. The good news is that >many of the more obscure constructs in .ly files that convert-ly can have a >problem with, were originally introduced in order to handle some bug or >shortcoming in that particular LilyPond version and there's a good >chance that >the lines can simply be removed. Also, if you get stuck figuring out >what to do >with the file, just send an email to the mailing list and there's a good >chance that >someone can assist. > > /Mats > >Kieran Coulter wrote: >> Hello, >> >> I was wondering, upon attempting to update .ly scripts from Mutopia >> that had various original version #s, is there a few version gaps that >> make .ly files written using a certain version or earlier "obsolete", >> meaning they can't be updated all the way to the current version? >> >> I noticed one around either 1.5 or 2.5, I forget which, that said "not >> smart enough to update autobeam settings" or something like that. >> Anyways, I am just trying to see at what version or earlier a file has >> to be for me to know that I shouldn't bother working on modifying it >> if it can't produce an output. >> >> Also, if there is a workaround for this gap, or any other gaps I am >> not yet aware of, please let me know! >> >> Thanks! >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> lilypond-user mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/lilypond-user >> _______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
