3.6.2 appimage much slower than 3.2.3 with navigation panel.
On a large score (the Four Seasons https://musescore.com/musikmann/scores/135805)
the latest version 3.6.2 is unusable when navigation panel is on: everything will make the whole interface hang for 30 seconds or more!
On the other hand, the same score works perfectly well and fast on my ubuntu 3.2.3 version, with navigation panel as well.
So there seems to be a large regression here.
Comments
The score stems from MuseScore 2.0.3. Maybe that matters here.
Then again there's no slowness at all in MuseScore 3.6.2 64-bit on Windows 11
In reply to The score stems from… by Jojo-Schmitz
I think I found the ultimate crash test: open 3.6.2 (linux appimage) and create a new score.
Only one page: the navigator works fine. Now insert a page break so you have now two pages.
Activate the navigator ==> the interface hangs for 30 seconds... (but after that is works)
In reply to I think I found the ultimate… by sanettelinux
I can't replicate this running 3.6.2 AppImage on Kubuntu. For me everything works as expected.
in fact the problem persists for much smaller scores: I saved from that file an excerpt of 5 pages, and the problem is exactly the same
In reply to in fact the problem persists… by sanettelinux
Hmm now I realize the problem happens with all my scores (previously I never edited such large score so I never tried the navigator). So it seems there is a problem with the navigator in the linux version of 3.6.2?
In reply to Hmm now I realize the… by sanettelinux
Not in general, no, works perfectly for me, 3.6.2 AppImage on Debian bullseye. Probably something about your specific graphics driver or some other system resource.
In reply to Hmm now I realize the… by sanettelinux
Here too all fine in large or small scores on Linux Mint MuseScore AppImage 3.6.2 (navigator on)
In reply to Here too all fine in large… by Pentatonus
thanks for the feedback. I don't understand what happens then.
I'm using KDE neon, based on ubuntu, so this shouldn't be very different from Mint.
When I select the navigation panel in the menu, I can see in a terminal using 'top' that Musescore uses 100% CPU for about 20 seconds. And most of the times as soon as I try any other action, 100% again for 20 to 30 seconds...
In reply to thanks for the feedback. I… by sanettelinux
neon and plasma have been known to have less good support from the older Qt version we use. Something to do with the Qt-wayland vs weston layers afaik.
In reply to thanks for the feedback. I… by sanettelinux
I've been having the same problem in Kubuntu 20.04 (up-to-date) since MuseScore 3.6.2 was released. The only workaround is not to display the navigator. Try working on a 25-page orchestral score without the navigation bar!
In reply to I've been having the same… by George Khouri
Have you tried updating graphics drivers?
Meanwhile, I think once you realize how many navigation options MuseScore provides, you’ll quickly realize the Navigator is not ever needed. I literally never use it regardless of size of score. Can you be more specific about what you are using it for? Normal scroll gestures line two-finger swipe, plus the Find command, and occasion use of the timeline, should provide better navigation in virtually all cases.
In reply to Have you tried updating… by Marc Sabatella
Hi Marc,
Thanks for getting back. My system stay up-to-date with the system updates, and I have updated my graphics drivers (Mesa/Intel 4000). I do know the other methods of scrolling. I often have 20-30 page orchestral scores that I often use in continuous view. My preferred and most efficient method for moving around in longer scores is usually the mouse and navigation bar, FWIW. My guess is that if there are outdated QT libs that someone mentioned in this thread, then newer graphics drivers aren't going to fix the problem. I know my way around the OS pretty well and have done a lot of sleuthing since 3.6.2 was released, but I have never been able to fix the navigator issues. All works well using MS 3.2.3. I'm open to all/any suggestions!