[MusicXML] Partial slash chord
1. Open attached mscz (produced in 2.0 beta).
2. 'File'>'Export…'.
3. Choose 'MusicXML'.
4. 'Save'.
5. Open MusicXML.
Expected result:
Actual result: Chords beginning with a slash and slashes after a chord don't appear.
Notes:
Also attached is the produced MusicXML.
See original discussion
.
Using MuseScore 2.0 Nightly Build 396c44f - Mac 10.7.5.
Attachment | Size |
---|---|
Partial slash chord.mscz | 1.82 KB |
Partial slash chord.xml | 30.7 KB |
Partial slash chord - Expected result.png | 94.53 KB |
Partial slash chord - Actual result.png | 88.99 KB |
Comments
I'm not sure, but it might be part bug.
When importing the MusicXML into 1.3, chords beginning with a slash appear, but without the slash.
I'm not sure if/how MusicXML supports such chords. We could special case these chords to do whatever MusicXML in general recommends, but does anyone know how these should look (or if this is supported at all)?
BTW, the last few chords don't make sense. "F/" is a syntax error in the input as far as I am concerned. MuseScore appears to support it, by treating the "/" as ordinary text. That is, the same as how it would treat the "$" if you typed "F$". But there is no semantic meaning to attach to it, so nothing to export to MusicXML.
I would understand if there's no support for the last chords (perhaps this could have be clarified in the original topic), but I take it you know what they are trying to represent?
No, not really. They look like typos to me.
From the 8th semiquaver in bar 2:
G
F on G
Em on G
etc
The lack of information on one side of the chord means you use the information of the previous one.
OK, hopefully that means something to the oerson reading the char; I've never seen anything like it before.
I don't think I have either, but I should have said as such.
My current thoughts: If there's objection, I'll accept this.
Somewhat related: I have tested whether it works in 2.0, but seen in in scores, something like
C 7 4 3
Apparently meaning
C C7 C4 C3
Here too repeat the missing info from previous chord symbol
Anything not beginning with a recognizable note name should be treated as ordinary text in 2.0, which is to say, it should look OK within MuseScore, but won't export meaningfully.