Exporting MusicXML for use in other programs using Sibelius' export function introduces some weird and apparently random alterations in note positions. Despite my best efforts to ensure that all live start positions etc are eliminated, Sibelius seems to incorrectly adjust the positions of some notes. This results in errors when the exported file is imported into other programs, such a LilyPond.
After the changing of an instrument on a staff upon the original instrument returning, an exported MusicXML file does not reflect the correct transposition changes. For example. I input Ex 1 into Sibelius. I then export this as a MusicXML file. I then open this MusicXML file back into Sibelius and get Ex 2. The C Clarinet is now transposed incorrectly. There is also a B flat key signature. upon inspection of the MusicXML ...more »
The Sibelius 7 Sounds installer on Mac OS writes the file-system path of the sample library installation into a file called "Sibelius 7 Sounds.xml" in folder "Libraries" at: /Library/Application Support/Avid/Sibelius Sounds/Libraries/ But if the user has chosen an installation location on a file-system volume whose name contains XML reserved characters (such as ampersand), then the sounds installer fails to encode the ...more »
I've reported this as a bug. Exporting simple folk music with 8th note and 16th note clusters with beams into MusicXML causes the beam information to disappear.
Reimporting the XML file back into Sibelius shows separate notes only. So does using the XML file as the input for conversions to ABC notation.
It would be helpful to include an export option for ABC (a notation used especially for folk music). Currently the only path is to export to XML and then find an XML-to-ABC converter.
The reverse direction is less necessary.