Dear Michael,

What I've found is that exporting and importing xml works best for single
parts - so I would recommend exporting each part as an xml file and then
including them in your lilypond score. I've even found that piano parts
generally work better when each hand (and sometimes each voice/layer) is
imported separately. It's a bit of a hassle - but with lilypond's
architecture it actually isn't that bad. It seems to me that there is a lot
of variability in how well different program export and import xml that you
can't yet trust it for automatic transfer between programs. Each programs
seems to miss or mess up certain things. This is true for transferring
files between any two programs (try to load your file in Finale or
MuseScore and you'll probably see what I mean).

Hope this helps.

All the best,
Avner

On Tue, Sep 8, 2015 at 8:48 AM Michael Gerdau <[email protected]> wrote:

> Dear Lilyponder,
>
> a couple of years ago I created a score in Sibelius that I now would
> like to continue to work on with Lilypond. I thus have exported from
> Sibelius (7.1.3) in MusicXML and tried to import in Lilypond using
> musicxml2ly (2.19.26).
>
> Unfortunately I get an error (see attached logfile).
>
> How do I proceed ?
>
> I've attached the compressed MusicXML as well but am happy to reduce
> the size by removing stuff. However I have no experience in debugging
> this sort of problem and would need a few hints as to what I should do.
>
> The command invoked was
> musicxml2ly --nd --nrp --no-beaming -m Machet\ die\ Thore\ weit.xml
> >Machet\
> die\ Thore\ weit.log 2>&1
>
> Kind regards,
> Michael
> --
>  Michael Gerdau       email: [email protected]
>  GPG-keys available on request or at public
> keyserver_______________________________________________
> lilypond-user mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
-- 
All the best,
Avner
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to