Re: about musicxml2ly

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Mittwoch, 20. Februar 2008 schrieb Reinhold Kainhofer:
> However, the conversion result triggers lots of error messages in lilypond
> (which even segfaults on the file...), because Sibelius does not put any
> ending marks for beams into the .xml file, so none of the beams in the
> lilypond file are ended with a corresponding ]. 
> musicxml mailinglist to clarify that point about the musicxml
> "specification". So, either Sibelius is wrong and produces wrong files, or
> we need to extend musicxml2ly to take this into account.

Okay, I now got the answer from Michael Good (the guy who is responsible for 
MusicXML and also for the Finale and Sibelius plugins...). Appently, Sibelius 
creates wrong files due to a bug in the scripting interface of Sibelius, so 
in musicxml2ly we'd need to add a compatibility mode that ignores all beaming 
information from the .xml file and simply let lilypond do its job with 
beaming.

On Wednesday, February 20, 2008, Michael Good wrote:
> Each <beam>begin</beam> really should have a corresponding
> <beam>end</beam>.
>
> What you are seeing is a result of a bug in the Dolet 3 for Sibelius
> plug-in caused by directly using beam information provided by the
> ManuScript interface. It turns out that, despite what the ManuScript
> documentation says, ManuScript only returns the begin and continue
> values. This means that the Dolet plug-in should be doing some
> additional processing before exporting these values to the MusicXML
> file, but it is not yet doing that. MusicXML 2.0 adds ways to indicate
> that certain beam values are no supported, but Dolet 3 for Sibelius is
> currently exporting MusicXML 1.1 files.
>
> This is something that we plan to fix in a future version of the Dolet
> for Sibelius plug-in. In the meantime, importing software may just
> want to ignore the beam values from MusicXML 1.1 files produced by
> Sibelius and apply its own automatic beaming instead. Importing
> software may want to just pay attention to the "begin" values to see
> where beams may be broken in unexpected places.

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHvKKPTqjEwhXvPN0RAnUyAJ9bhupKetdZrL2mnGsSphJoQGBqhwCfWTeq
bwJSirYRzIK+vX6JV27OY9s=
=6kCn
-----END PGP SIGNATURE-----