Rosegarden creates bad XML files when exporting

Bug #205474 reported by Vivien Taillandier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rosegarden (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hello !

When using the export to MusicXML function in rosegarden, the generated file is corrupted.
I have to change manually "</attributes>" to "<attributes/>" (minus the quotes) when there's no "<attributes>" element.
It must be a regression because I didn't have that bug in gutsy.

version : 1.6.1 (hardy)

Revision history for this message
Vivien Taillandier (vivien) wrote :

I tried the 1.7.0 on intrepid and the bug is still there.
I guess it should be fixed because many softwares, and specialy score editors, are using the MusicXML format for importing / exporting (like noteedit / canorus, Print Music, Sibelius ...).
This issue is annoying because you only have two choices :
   - To fix the xml file manually (it can be long)
   - To export in the midi format, but you lose a huge amount of informations.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 9.04?

Changed in rosegarden:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in rosegarden:
status: Incomplete → Invalid
Revision history for this message
John Galbraith (john-maxwellsdemon) wrote :

I have duplicated this bug on Gentoo Linux, Rosegarden 10.02.1.

In the file, there is one segment in one track. There is only one note in the segment, and nothing else. The bug occurs when the segment does not start at measure 1. In this example, it starts at measure 2 and exhibits the bug. If you move it to measure 1, the bug goes away.

Apparently, I can only attach one file, so I will paste the relevant XML here, for measure 2. The bug is that the </attributes> tag is unmatched.

  <measure number="2">
    <key>
    <fifths>1</fifths>
    <mode>minor</mode>
    </key>
    <time>
    <beats>4</beats>
    <beat-type>4</beat-type>
    </time>
    <clef>
    <sign>G</sign>
    <line>2</line>
    </clef>
   </attributes>
   <note>
    <pitch>
     <step>C</step>
     <octave>5</octave>
    </pitch>
    <duration>3840</duration>
    <voice>1</voice>
    <type>whole</type>
   </note>
  </measure>

Changed in rosegarden (Ubuntu):
status: Invalid → New
Changed in rosegarden (Ubuntu):
status: New → Confirmed
Revision history for this message
Ted Felix (tedfelix) wrote :

This bug was fixed with the rewrite of MusicXmlExportHelper that was done 2011-09-25 (r12505):

https://sourceforge.net/p/rosegarden/code/12505/

The fix was shipped in version 11.11 of Rosegarden. This bug report can be closed.

Changed in rosegarden (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.