search

musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.36k stars 2.67k forks source link

MusicXML exports chord symbols on grand staves incorrectly, moving them to the top staff #23240

Open TeeDeeY opened 5 months ago

TeeDeeY commented 5 months ago

Issue type

Import/export issue

Bug description

Chord symbols on grand staves are not correctly exported to MusicXML.

  1. Start new score with a grand staff instrument.
  2. Enter multiple chord symbols, some on the upper staff, some on the lower staff.
  3. Export the file to MusicXML.

On importing the file back into MuseScore, all chord symbols have moved to the upper staff. It has been confirmed that this is an export problem rather than an import problem.

MuseScore Version

checked in 4.4.1, but also occurs in 4.3.2; earlier versions have not been checked

Additional context

This issue has been significantly edited by @cbjeukendrup, because previously it discussed not only this MusicXML export problem but also a MIDI export problem that turned out to be unrelated.

Jojo-Schmitz commented 2 months ago

The MIDI part of this issue came up again in https://musescore.org/en/node/368244 and I can confirm it, MuseScore 4.4.1, Windows 11, worked in 4.3.2.

cbjeukendrup commented 2 months ago

I'm not sure whether it was fully intentional to triage this as "in the further future" while this is a plain 4.4 regression.

MarcSabatella commented 2 months ago

FWIW, I don't see any issue with MusicXML export mmissing chord symbols on Linux using 4.4.1), but I can confirm that the playback of the chords is not included MIDI export. It is the case with MusicXML that the chords all end up being attached to the top staff even if originally entered on the bottom. Not sure if that's an import or export issue, or if it's a regression, or if it's at all related.

I do seem to recall there was an issue where chord symbol playback was not exported on Windows or macOS only, but I don't see an issue about this, open or closed. This too might not be related, or I might be remembering incorrectly...

Jojo-Schmitz commented 2 months ago

I can't confirm the MusicXML issue with chord symbols moving to the top staff or getting lost

MarcSabatella commented 2 months ago

For me it is specifically with a grand staff (not multiple instruments) that chords migrated between staves top. I have now verified the problem is on export as opposed to import, and that it also occurs in 4.3.2

Here is the test score I am using - chord-symbol-export.zip

Here is how it looks when loaded:

image

and here is how it looks after export/import:

image

cbjeukendrup commented 2 months ago

It's perhaps getting inconvenient that this issue is both about MIDI and MusicXML while both are independent problems. Since this issue now contains useful discussion about MusicXML, let's rewrite it to focus on MusicXML; then someone else can open a new issue about the MIDI problem.

MarcSabatella commented 2 months ago

On it...

Jojo-Schmitz commented 2 months ago

?? As far as I can tell there is no such MusicXML issue, just a MIDI one

Edit 1 Ah, now I see, not top staff of score, but top staff of Piano part!

Only now https://musescore.org/en/node/368244 hangs mid-air...

Edit 2: see #24515

TeeDeeY commented 2 months ago

When I opened the original issue, the chords were scrambled up between export and subsequent import. That part of the issue seems fixed. I thought the midi export issue could be related so I listed it. My Mxl issue is closed but others can continue to the new issues that have come up. The midi issue continues in the other thread.

cbjeukendrup commented 2 months ago

Ah, good to know. Sorry for "rewriting history" with this issue, but at least all problems are in a suitable place on our to-do list now :)