Maybe look into MuseScore logging to see if it is reporting anything
helpful?
Try to make the smallest MusicXML file you can that causes the
problem. E.g. one segment, one note? Open a bug report and attach. No
guarantees we'll ever get to it. But if it's something simple that rg
is messing up, it should be easy to spot and hopefully easy to fix.
Might also save the imported file as MusicXML from MuseScore and diff
the two. That might find the problem very quickly.
Ted.
On 1/25/24 7:49 PM, david wrote:
I have RG v23.12. I went to export a project as MusicXML. It gave me the
option to export as MusicXML v1.1 or v2.0. I chose v2.0.
Trying to open the resulting XML file in MuseScore 2 or MuseScore 3
reports the file is corrupt.
I finally figured out how to make RG offer me the MusicXML version
choice again (delete the exported XML file outside of RG). Then I
re-exported it as MusicXML v1.1. That exported file is also reported as
corrupt.
If I click Ignore in MuseScore's warning dialog, it opens fine.
Ideas?
--
David W. Jones
gn...@hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
"My password is the last 8 digits of π."
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
