Musescore4 : "frozen mixer popup window", even after restart
Hello,
I am using a windows 10 (22H2) on a Dell Latitude laptop which has a display with a 1920 X 1080 resolution;
I have recently upgraded Musescore to the last version of Musescore4.
In the middle of editing a score , I chose to open the mixer; the mixer popup window opened, but it igot stuck to the top of my screen, and ... I do not have any control , either to close or move that popup window.
Even if Musescore appears still OK with every other aspect, i.e. the visible menus are still active and clickable, and the score is editable (but only for the parts that are not masked by the popup); I am nevertheless completely stuck:
it is impossible to properly edit the score anymore, nor have access to the menus hidden by the popup window, (and it is impossible to close that mixer popup window.
Moreover, If I restart Musescore, and choose to edit a new score... the new score appears, but the "stuck mixer popup window" is still there !
So it is now impossible for me to work with MuseScore
Help !
| Attachment | Size |
|---|---|
| MuseScore with frozen mixer popup while editing.png | 258.19 KB |
| MuseScore with frozen mixer popup, after restart with new score.png | 245.21 KB |
Comments
You can press F10 to open and close the Mixer panel.
To help us investigate the cause of this problem, please click "Diagnostic > Save diagnostic files" and upload the resulting ZIP file here.
To stop the problem from happening for now, click "View > Restore the default layout:.
In reply to You can press F10 to open… by cbjeukendrup
Hello cbjeukendrup ,
Following your advices:
I could not access the diagnostic menu while the popup window was still stuck-open.
So I used your indication of using F10 to close the popup window of the mixer, and it worked fine :-)
Then I could access the diagnostic menu and prepare a diagnostic file; the corresponding .zip file is attached
Thanks for your help, I can now resume working on MuseScore, and I will use the F10 trick if the problem occurs again !
I hope you will find the origin of the problem encountered,
Best,