Partial slash chord disappears upon saving and re-opening

• Oct 25, 2014 - 23:56
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

1. Open attached score (produced in 2.0 beta 1).
2. Enter the chords as indicated in the image of the expected result.
3. 'File'>'Save'.
4. 'File'>'Close'.
5. Open score.

Expected result:
Partial slash chord disappears upon saving and re-opening - Expected result.png

Actual result:
Partial slash chord disappears upon saving and re-opening - Actual result.png

Notes:

See original discussion .

It only applies to chords beginning with slashes.

Using MuseScore 2.0 Nightly Build fc3ea8e - Mac 10.7.5.

Attachment Size
Partial slash chord disappears upon saving and re-opening.mscz 1.6 KB
Partial slash chord disappears upon saving and re-opening - Expected result.png 38.69 KB
Partial slash chord disappears upon saving and re-opening - Actual result.png 35.17 KB

Comments

• Oct 26, 2014 - 00:01
Title Slash of partial slash chord disappears upon saving and re-opening ⇒ Partial slash chord disappears upon saving and re-opening

Reply

• Oct 26, 2014 - 16:03

I tried this in Version fc3ea8e (2014-10-23).
It appears that in my case not a single chord symbol is displayed when a file is opened. Only those added in open files are displayed. The chord symbols are saved correctly, though, as I noticed from viewing the corresponding mscx (uncompressed) files in an editor.
So strictly spoken, there is no loss of data.
Btw, if one tries to add a non-displayed chord symbol again, it is saved a second time, like in

...
<Harmony>
<root>15</root>
</Harmony>
<Harmony>
<root>15</root>
</Harmony>
...

Reply

• Oct 26, 2014 - 16:22

I am not understanding the comment above - could you post a score and steps to reproduce the problem? Most chords are indeed displayed - it is only chords beginning with slashes that are not. I suspect you have tried using a custom chord description file with a syntax error and that is why you are having problems.

Regarding the original problem - there is actually no loss of data. The chord is being saved correctly; it just isn't being displayed properly. My memory was not playing tricks on me - I *did* implement this a while ago, but apparently it partially broke.

Reply