Too slowly Interface
A differenza della precedente versione 2.0.2
partiture semplici sono diventate impossibili da gestire per l'eccessiva lentezza delle risposte del sistema.
L'inseguimento della partitura rimane indietro anche per piu' di due battute (c.a. 1s) e la finestra dei controlli di riproduzione non aggiorna timer e contatori (che scompaiono) ...
Nell'immagine allegata la riproduzione era gia' alla pagina successiva.
La versione precedente gestiva correttamente questa partiture ed altre anche molto piu' impegnative.
L'occupazione di cpu (anche senza alcuna apparente attività) è schizzata alle stelle in questa versione.
GIT commit: 3c7a69d
| Attachment | Size |
|---|---|
| Screenshot 2016-04-18 06.20.13.png | 149.34 KB |
Comments
Google translate:
Unlike the previous version 2.0.2 simple scores have become impossible to manage the excessive slowness of the system responses.
The pursuit of the score remains back for more two-measure equipment (about 1s) and the window of the playback controls does not update timers and counters (which disappear) ...
In the attached image reproduction it was already on the next page.
The previous version was running properly this and other scores also much more challenging.
The occupation of the cpu (even without any apparent activity) is skyrocketing in this version.
Could you disable the navigator (F12) and see if this has a positive effect on the CPU load, i.e. is it decreasing?
So, i'm sorry .... I red similar comments too late ...
Yes, with navigator disabled, come back normal response (and cpu consumption) ...
... I'm sad, the navigator was very useful for long scores...
it would be possible to think of a simplified version of the navigator?
even a scrollbar without graphics and with only the bars numbers ... or courtesies ... or the clef/key changes ... ?
thanks a lot
sk
p.s.
during the editing phase I use continuous view ... especially in complex parts .. and always during the execution ... .. only in a second time debug the layout with the page view ...
disableling the Navigator was not meant to be a fix, more a troubles hooting step.
yes, I know,
I still have already so happy to have found the prowess... even though instead of the navigator bar I trained to use the slice of the playback controls ...
The performance issue with the navigator will be taken care off with the development of MuseScore 3.
Since 2.3.1 is the last version of 2.X series, the issue will be addressed in 3.0.