Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
TeeDeeY opened this issue Jun 14, 2024 · 10 comments
Labels
MusicXML P3 Priority: Low

Comments

@TeeDeeY
Copy link

TeeDeeY commented Jun 14, 2024

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.

@muse-bot muse-bot added the regression MS4 Regression on a prior release label Jun 14, 2024
@bkunda bkunda changed the title Master 4.4 doesn’t export grand piano chords correctly Master 4.4 doesn’t export grand piano chord symbols correctly Jun 14, 2024
@bkunda bkunda added P3 Priority: Low MusicXML MIDI Issues related to MIDI input/export, or MIDI devices labels Jun 14, 2024
@Jojo-Schmitz

This comment was marked as outdated.

@cbjeukendrup

This comment was marked as resolved.

@MarcSabatella
Copy link
Contributor

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
Copy link
Contributor

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

@MarcSabatella
Copy link
Contributor

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

This comment was marked as resolved.

@cbjeukendrup cbjeukendrup changed the title Master 4.4 doesn’t export grand piano chord symbols correctly MusicXML exports chord symbols on grand staves incorrectly, moving them to the top staff Sep 6, 2024
@MarcSabatella

This comment was marked as resolved.

@Jojo-Schmitz

This comment was marked as resolved.

@cbjeukendrup cbjeukendrup removed regression MS4 Regression on a prior release MIDI Issues related to MIDI input/export, or MIDI devices needs review The issue needs review to set priority, fix version or change status etc. labels Sep 6, 2024
@TeeDeeY
Copy link
Author

TeeDeeY commented Sep 6, 2024

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

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MusicXML P3 Priority: Low
Projects
Status: Some release after that
Development

No branches or pull requests

6 participants