Black score view with MacOS Sierra

• Sep 25, 2016 - 22:14
Reported version
2.1
Type
Graphical (UI)
Severity
S3 - Major
Status
closed
Project
Tags
Priority (old)
major
Status (old)
closed
Component (old)
User interface
Category (old)
bug report

Hi, when I open musescore for Mac (2.0.3) the score workspace becomes black so that I cannot see anything.
Hope it could be fixed soon.
Thank you for your work.

Luca
GIT commit: 3c7a69d


Comments

Is this after upgrading your operating system to Sierra? We had a previous report of something similar: https://musescore.org/en/node/125726

As you can read on that thread, reverting to factory settings fixed it. But a preventative solution should still be found.

Note that the "assigned" setting is to indicate when a programmer has taken on the task of fixing the problem, not to indicate who reported it.

It would be really helpful if someone could upload his settings file before resetting to factory. The file located in ~/Library/Preferences/org.musescore.MuseScore2.plist.

Title black screen Black score view with MacOS Sierra

Our current guess is that it's due to the fact that the user used a non standard background for the score. If you encounter this issue, it would help us to investigate if you could share:

1. A screen capture of your screen with the palette and a score opened
2. A screen capture of Preferences > Canvas
3. The file located in ~/Library/Preferences/org.musescore.MuseScore2.plist

Status (old) needs info active

I recently upgraded to Sierra and have this issue all the time. My plist file contains entries such as:

<key>selectColor4</key>
<string>@Variant(</string>

All colors in the plist show up in this way.

Resetting preferences to default only works for the current session in my case. Once preferences are saved, they are again wrong.

Additionally, the highlight color for all voices also turns black, so you can't see the highlight at all. Probably because of the same color to string conversion bug.

I'm attaching a plist file saved from the Guest user after simply opening the preferences dialog and clicking OK. Had to convert it to xml (plutil -convert xml1 *.plist) and rename it for the attach to work.

The nightly build seems to work fine.

Workaround: converting the plist to xml and manually deleting all malformed color key/value combinations solves the problem, until the preferences are saved again.

Attachment Size
org.musescore.MuseScore2.plist_.xml 7.09 KB

Thank you so much for the investigation!

Good that the nightly works. Unfortunately they use a more recent version of Qt. Now I wonder if every single Sierra user will encounter this bug or if it's a special configuration of the system.

A possible workaround would be to save a string representation of the color instead of a QColor Variant.

Given the other reports, it seems that MuseScore 2.0.3 on Sierra cannot write QColor correctly in a plist file. When reading, the color ends up being invalid and render as Black.
Since the problem doesn't appear with a master nightly, it's likely a bug in Qt 5.4.2.

We will release a newer version of MuseScore 2.0.3 for Mac OSX to solve this issue before the release of 2.0.4. FWIW, I'm still considering to rename 2.0.4 to 2.1 since there are several new features (zerberus, select more, probably others)

I am running a fresh install of macOS Sierra on a MacBook Pro. MuseScore 2.0.3.1 fixes the black score issue. Create New Score -> Key Signature is no longer blacked out either. Thank you lasconic.

May I humbly suggest that musescore dot org use the 2.0.3.1 version? Thanks again!

Status (old) active fixed

2.0.3.1 is now the default version for Mac OSX and MuseScore will tell people that there is an update.

I'm also in favour of naming it 2.1 and maintaining full forwards and backwards compatibility. No doubt the 0.0.X increment was intended to avoid raising expectations for major new features, but I think it proved a little too cautious in the end. Some of the recent "patch" releases have actually had quite a few new features, so perhaps it would be more appropriate to consider them "minor" releases. That would enable patch numbers to be reserved for unintentional releases (like this one) which is more in keeping with the standard for Semantic Versioning.

Its better to ask for help on the Support forum. When you do, please say what OS, what browser, what version of MuseScore, and what specifically goes wrong.

I downloaded the 2.0.3.1 dmg which seem to solve the problem when I opened it directly from the software....but when I open the software via a file, it still opens up with a black screen. Are all my files working off the old version? and if so, how do I get rid of it? Does the 2.0.3.1 override the old version?
Jo
macOS Sierra version 10.12.2

Jo, it sounds like you do indeed have two versions of MuseScore on your system. Opening the DMG file should create a drive with MuseScore 2.0.3.1 inside. Did you drag that version of MuseScore to your Applications folder (or wherever you had installed the earlier version)? You should have gotten a prompt to overwrite the older version at that time. If you chose to keep both on accident, you should be able to manually trash the older version, then empty the trash.

Expanding on Marc's suggestion: Open MuseScore, go to the MuseScore menu on the top left of your screen, then click on About MuseScore. Then quit the program, go to one of the files that opens incorrectly, open it, then navigate to About MuseScore in the same fashion as before.

There is a possible workaround if you can't find an older version on your system. In the Finder, navigate to one of the scores that opens incorrectly. Click once to highlight it. Then go File -> Get Info. Go to Open With, choose the other MuseScore 2.0 in the list, then hit the Change All button.