Lilypad

• Sep 25, 2014 - 19:32

Think I missed this...

What happened to the ".ly" export?

It would really save an AWFUL lot of time for me!

Ken

Comments

• Sep 25, 2014 - 19:42

Do you mean what happened to it for 2.0 Beta 1? The answer is, no one seemed sufficiently interested in the feature to volunteer to maintain the code. Realistically, we can't support every third party program anyone might want to use, so we focus on the one universal standard in music notation: MusicXML. So export to MusicXML, and then use whatever tools are available to convert from MusicXML to LilyPond.

Or, depending on why it is you are using MuseScore and why you are using LilyPond and why you are trying to combine them, you might just be better off using an editor designed from the ground up to work with LilyPond, like Frescobaldi. Or sticking with MuseScore nd not worrying about LilyPond (and you should 2.0 Beta coms a lot closer to LilyPond in quality of output than 1.3 was).

Reply

• Sep 30, 2014 - 22:27

I was using jEdit but it was too much work because your output wasn't even close and I have to learn MusicXML. Looks like a good move to drop it. So I'll give that a try.

That will keep me busy for a couple of weeks!!!

Thanks again.

Reply

• Oct 1, 2014 - 05:18

Not sure what you mean about having to "learn MusicXML". Whether you export ".ly" from MuseScore, or export MusicXML from MuseScore than convert it to ".ly", you need not ever actually look at the contents of MusicXML file or write one yourself.

Also not sure what you mean when you say "your output wasn't even close" - do you meant the quality of the printed score wasn't as good as LilyPond's? It should actually have been *sort of" close before - really, only complicated scores would show much difference - but again, better in 2.0. So do give it a try.

Reply

• Oct 1, 2014 - 17:00

No, sorry. I meant learning Lily code. And the output from MuseScore wasn't even close. Took A LOT of changes to get it to compile and the format was difficult to work with. As I said, all in all a good choice to scrap it and put the effort into your own formatting.

2.0 is looking very nice. I think it might even be easier to understand. Couple of bugs holding me up but seems that formatting is working much better so far as I have got. Nice job.

Reply

• Oct 1, 2014 - 17:20

Again, not sure what you mean by "the output from MuseScore wasn't even close", but now I'm thinking by "output" you mean, the generated ".ly" file and not MuseScore's own printed output, and by "wasn't even close", you mean, the resulting ".ly" file had syntax errors when you ran it into whatever version of LilyPond you had installed. That could have been simply a version compatibility issue. In any case, indeed, kind of moot, because we're not likely to fix whatever errors might have existed now that the feature has been removed :-)

Do be sure to report the bugs in 2.0 Beta that are holding you up if you haven't already - in separate threads in the Technology Preview forum. Once they are confirmed, then you can file them officially to the "Issue tracker".

Reply

Do you still have an unanswered question? Please log in first to post your question.