|
From: | Urs Liska |
Subject: | Re: Export to ????? |
Date: | Thu, 25 May 2017 11:20:39 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Am 25.05.2017 um 10:51 schrieb Andrew
Bernard:
Then maybe I suggest to call it a practical-lock-in. As a user, if you've decided to work with LilyPond and created a project or even a whole library of projects, you're basically locked in to using them with LilyPond. There's currently no viable solution to take an existing project (at least of some complexity) and pass that on to someone who insists on using other software. There's no commercial intent to this, OK. And there's no restriction to create a solution, OK. But for a *user* this doesn't make any difference, he can't reuse his work otherwise. And apart from the usual case of commercial publishers insisting on Sibelius files there *are* other valid reasons why one would like to export LilyPond files. For example getting the music into a DAW to create *good* audio, where MIDI is still very limited. Or exporting to Humdrum files for which there is a plethora of tools for music analysis. And probably a lot more.
I think it *is* a defect that LilyPond hasn't ever really considered export to *any* other encoding formats important (right from the initial conception). Yes, there is no ODF for music. But if LibreOffice wouldn't provide export filters for Word or Excel I think lots of people wouldn't be able to use it. Not being able to export to MusicXML (with all its limitations) is a hard reason not to use LilyPond for many people who might otherwise consider it. BTW: MEI may well become such a universal standard.
But let's face it: for the average user this path is only a theoretical option. Urs
-- address@hidden https://openlilylib.org http://lilypondblog.org |
[Prev in Thread] | Current Thread | [Next in Thread] |