Colin Hall <colingh...@gmail.com> writes: > On Sun, Jun 24, 2012 at 02:23:36PM +0000, Ken wrote: >> > So it would appear that your files relied on constructs that convert-ly >> > (of course assuming that you had correct \version headers for the _old_ >> > version so that convert-ly would actually be inclined to try converting) >> > is not able to upgrade. >> > >> > Without an actual example, not more than that can be said or done. >> >> Think I got it. I do appreciate your input and willingness to help. >> >> All my string tunings used numbers (semi-tones); as soon as I went >> to the pre- >> defined "banjo-open-g-tuning" everything worked great. Still, the program's >> response wasn't all that helpful in pointing that out. >> >> Then, documentation says pre-defined tunings are in >> "scm/string-tunings-init.scm" but they're not: >> I found them in ly/string-tunings-init.ly -- and changes made >> there (custom tunings and names) seem to work so far. >> >> Thanks again. > > Glad to hear you got it working, Ken. > > Thanks, David, for helping Ken to figure it out. > > It looks like there is no bug to report here.
It might be a problem with convert-ly, but without an actual example I don't see that it makes sense entering a report. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
