preset tool palettes empty

• Feb 8, 2019 - 07:39
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

Earlier today I reported issue with repeated crashes upon quitting application and the basic and advanced palettes empty upon starting program. After attempting to fix including restoring factory settings with no effect, I removed program and reinstalled. After a few hours, the basic tool palette is empty. Advanced palette is working normally. Again I tried restoring to factory settings. Basic Palette remains empty. Also, I can report that crashing upon quitting program occurred with regularity while USB connection to MIDI keyboard. Upon disconnecting USB. program does not crash when quitting. It is not clear what relationship is, if any, of USB keyboard connection to MacBook to Musescore crashing. I am using MacBook Touch Bar. OS Mojave 10.14.3


Comments

Update. removed program for 2nd time today and reinstalled. The advanced palette presets disappeared immediately after creating a shortcut "option F" for "add fingering". Nothing I'm trying will bring it back.

This seems likely to be a permissions problem on your system then, since no one else seems to see this, and tht's the only thing I can think of that could explain what seems to be happening.

I'm guessing it may turn out that the program was installed as a different user than the one you are currently logged in as, something like that. I'm not a mac expert s I can't tell you exactly what to look for.

In reply to by Marc Sabatella

I am the only user of my machine....I've now removed and installed 4 or 5 times. Same issues. I might end up taking my macbook to apple store...However, Musescore is the only program acting up like this. Maybe it is interacting with some other program that is installed or running in background....don't know.

In reply to by Marc Sabatella

I have the same Problem.- during first launch i choosed the extended palette in the launch Assistant. After that i wanted to change to the standard palette- but it was empty. By the way - also my system crashes when using the "toggle midi button" (but i guess this should been handled under different issue..)
Attached the failure log..

In reply to by Gömmer

Gömmer. I'm curious...Do you have Ableton Live or a Version of Pro Tools installed on your Mac? Those are the two programs I can remember installing lately before I installed Musescore 3. I've been wondering if there might be some kind of conflict going on. Not sure why that would be the case, but I'm not a coder...

In reply to by Marc Sabatella

Mojave OS 10.14.3. The “empty palette” and the “crash upon closing” issues seem like they are unrelated but I have no expertise to determine that. I experienced the empty palettes from the get go, regardless of being connected or not to MIDI. However the MIDI connection and crashing upon closing do correlate. At this point I may just go back to version 2.xx until issues are resolved. My basic palette is permanently empty. Advanced palette seems stable for now but I’ve already experienced both palettes being empty before my most recent reinstall.

Frequency Many  

2nd to last update of few days ago (sorry I don’t have ver. #) seems to have fixed (inadvertently?) the missing palettes issue! Palettes also are retained in The most recent update which I installed yesterday. I’ll know more once I make MIDI connection. Headed in right direction.

In reply to by Marc Sabatella

I’m missing something here. Even if I try to open by double-clicking another file (all of mine are MuseScore 2 since I’ve been unable to use MuseScore 3), I still get the crash. It doesn’t even get as far as the weird little square window in the upper right-hand corner that I get if I open MuseScore by opening the app. Tried with 3 different MuseScore 2 files in case one was corrupted.

@badflautist, you are not the first to report they cannot run 3.0.4 by double clicking a file. Run MuseScore3 from the command line with the -w command lne option and see if that helps. If it does run, change what displays at start up in the preferences to anything but the start center.

macOS has command line capability too; I'm sure Google would be happy to find information about how to do that. But if you're seeing a crash even when you open by double-clicking a score, that might be a different problem.

In reply to by Marc Sabatella

@Marc, as a related side note. I've seen instructions somewhere for running MuseScore from the command line in various OS's, I just can't find them. I think it would be useful to have a how to or handbook entry explaining this so us non-Mac users can point others to the help.

Severity S3 - Major S2 - Critical
Type Graphical (UI) Functional
Reported version 3.0 3.3
Frequency Many

hi,
i upgraded to OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.3.1.8837, revision: 824af4c and all of a sudden the palette buttons are gone. i've tried resetting to factory settings and re-installing. i read this thread but could not glean a clean solution. any one able to help? thanks.

Attachment Size
missing palette buttons musescore 3.png 12.61 KB
Frequency Many Few
Priority P0 - Critical P2 - Medium

If this issue is about some permission errors on some computers and didn't come up for a while then it might eventually be fixed. That needs investigation but right now it doesn't look like a critical and frequent issue, so I downgrade the priority for this.

Not sure what MuseScore-3.5.tar.gz refers to, is that source you compiled yourself? Probably an issue with your build environment if so, like wrong version of Qt or a missing component etc. Try the AppImage instead.

I got MuseScore-3.5.tar.gz from https://github.com/musescore/MuseScore/releases/tag/v3.5

The last time I tried the AppImage it was either too slow or it crashed, I have not attempted to debug what was wrong with it.

I was able to compile and install a debug version from a github clone using a checkout of the v3.5 tag and I get these errors when I run musescore:
$ musescore-43c5553
unknown:unknown: using qt5ct plugin
/home/martin/git/MuseScore/mscore/zoombox.cpp:Ms::ZoomBox::setLogicalZoom: ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
unknown:unknown: D-Bus global menu: no
/home/martin/git/MuseScore/mscore/zoombox.cpp:Ms::ZoomBox::setLogicalZoom: ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
qrc:/qml/palettes/PalettesWidget.qml:unknown: qrc:/qml/palettes/PalettesWidget.qml:21:1: module "QtQuick.Controls" version 2.1 is not installed
qrc:/qml/palettes/PalettesWidget.qml:unknown: qrc:/qml/palettes/PalettesWidget.qml:21:1: module "QtQuick.Controls" version 2.1 is not installed
/home/martin/git/MuseScore/mscore/startcenter.cpp:Ms::MyWebEnginePage::acceptNavigationRequest: acceptNavigationRequest( QUrl("https://connect2.musescore.com/?version=3.5.0.") , QWebEnginePage::NavigationTypeTyped , true )
[1:15:0917/200917.593939:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
libpng error: Read Error

On my system I have:
libqt5quick5 is already the newest version (5.12.8-0ubuntu1).

Ok, so additional libraries need to be installed:
sudo apt-get install qml-module-qtquick-controls2

But that just brings me to the next Qt error:
qrc:/qml/palettes/PalettesWidget.qml:unknown: qrc:/qml/palettes/PalettesWidget.qml:70:5: Type PaletteTree unavailable
qrc:/qml/palettes/PaletteTree.qml:unknown: qrc:/qml/palettes/PaletteTree.qml:22:1: module "QtQml.Models" is not instal

And this error:
qrc:/qml/palettes/PaletteTree.qml:unknown: qrc:/qml/palettes/PaletteTree.qml:22:1: module "QtQml.Models" is not instal

Is solved by:
sudo apt-get install qml-module-qtqml-models2

These appear to be runtime dependencies to me, since I had no problem compiling musescore at the 3.5 tag.

Did you follow all the steps in the developer handbook for compiling on your flavor of Linux?

It's certainly not impossible that you would be able to get a successful build with all the dependencies correct. but I guarantee, if you're not a developer needing to be able to compile it yourself, the AppImage is going to be far easier and far more reliable. Not sure what problem you encountered in the past, but it's worth trying again, it's what most of us on Linux use daily and it's well tested and solid. If you encounter a problem with it, feel free to report that separately.