[MusicXML] Title, Subtitle, Composer and Lyricist not exported

• Dec 21, 2011 - 20:29
Type
Functional
Severity
S4 - Minor
Status
closed
Project

1. Open attached score.
2. 'Export'.
3. Choose 'MusicXML'.
4. Open MusicXML.

Result: Title, subtitle, composer and lyricist aren't there.

Discussion: Marked critical as it represents a loss of information.

Using MuseScore 2.0 Nightly Build (5133) - Mac 10.6.8.

Attachment Size
Text.mscz 1.88 KB

Comments

Title [MusicXML] [Trunk] Title, Subtitle, Composer and Lyricist not exported [MusicXML] Title, Subtitle, Composer and Lyricist not exported
Status (old) fixed active

Still doesn't export.

Using MuseScore 2.0 Nightly Build (5486) - Mac 10.7.3.

Status (old) active needs info

Well, it does work for me, so I don't understand why it wouldn't work for you. Could you try again with the latest nightly ?

Also please explain exactly what you did, what is not OK and attach the relevant files.

I know why.

If you enter all the information after creating the score (via 'Create>Text'), it doesn't appear.

Using MuseScore 2.0 Nightly Build (5488) - Mac 10.7.3.

Status (old) needs info active

OK, you are right, I stand corrected. This is not caused by the MusicXML exporter, though. When you create the title etcetera in the new score wizard, the text gets styled with style "title" etc. When you use create text, the text gets styled with style "default". As a result, the MusicXML exporter finds the text, but doesn't know the type and cannot export it.

To complicate matters further, when exporting in MuseScore format, the style "title" is added to the text ... After importing the MuseScore file, export to MusicXML does work.

Thanks Leon - it works.

Not sure if there are other methods, but feel free to mark as fixed.

Using MuseScore 2.0 Nightly Build (5494) - Mac 10.7.3.

Why is this set to active again ? Please specify exactly what the issue is.

I am perfectly willing to spend time fixing issues. I am very unwilling to waste time guessing ...

Thanks, Leon.

Just checked, the issue does not occur anymore using the current trunk with any of the attached files. Do you agree with closing the issue ?