Feedback on version 4

• Mar 26, 2023 - 13:04

Works great ! But very annoying is that when you start the app, nothing (and I mean NOTHING) happens for 30 secs or so. Note even a time-glass-cursor. It would be great with a start up-window showing load progress or something.
It is very easy to believe that you missed the start command and after a while a bunch of Musescore windows pops up :)
Regards, Anders


Comments

It shouldn't take that long normally. Are you trying to start by opening a specific large score? Or do you perhaps have a bunch of plugins enabled? Or is your system extremely CPU and/or RAM limited?

In reply to by Marc Sabatella

Hi, I have a rather fast computer so that is not the problem. MuseScore3 starts within 2 seconds. When I start MuseScore4 the splash screen pops up after less than a second. Shown for 2 secs and then disappear. And now starts the 30 seconds without any sign whatsoever. After the 30 secs the UI comes and all works fine.
I don't start with a score, just start the program. Starting via a score file in Explorer, is the same, about 30 secs.
I have not installed any plugins, there are 10 active plugins that were there from the start.

In reply to by _Antån_

The plugins wouldn't normally be enabled by default - did you do so? If so, try disabling them.

What you describe definitely isn't normal, so something is clearly wrong. Try Help / Revert to factory settings, and/or also uninstall reinstall (they do totally different things, so be sure to try both if the first doesn't work).

If you then continue to have trouble, use the Diagnostic menu to collect logs, then open an issue on GitHub and describe the problem and attach the logs there.

In reply to by Marc Sabatella

Looked in the last log file. The 30 sec gap is between
2023-03-29T23:19:13.572 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
2023-03-29T23:19:42.400 | ERROR | main_thread | | operator : Unable to check for update, error: [1701]

Now I try to reinstall... then I do a report as suggested (if the error code above does not help ... )

Attachment Size
MuseScore_230329_231910.txt 10.79 KB

In reply to by Marc Sabatella

I disabled the update check. Still the 30 secs delay but different in the log file (here a few calls before and after the delay)
2023-03-30T22:07:02.892 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
2023-03-30T22:07:02.893 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-03-30T22:07:02.893 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"
2023-03-30T22:07:30.261 | ERROR | main_thread | Qt | QWindowsPipeWriter: asynchronous write failed. (Denna pipe har avslutats.)
2023-03-30T22:07:32.797 | WARN | main_thread | Qt | QQmlComponent: Created graphical object was not placed in the graphics scene.
2

Do you still have an unanswered question? Please log in first to post your question.