MuseScore 2.0.3 issue
Hi, gang!!!
I use Ubuntu Studio 15.10, into a 64 bit PC, with 8 GB of RAM and two HDD of 1 TB each one.
As you can see, the PC has all the necessary specifications to run MuseScore so well.
BUT... (I don't know why, but there is always something "rare" with the human things), I installed the last 2.0.3 version of MuseScore (AppImage version) and... After I use the software with 2 or 3 scores (one at a time), the program runs slow (the mouse, the menus, the edition actions, the playback cursor etc.). I repeated this 5 times (at least) and it always is the same, it runs slows after 2 or 3 scores.
If I use the 2.0.2 version, it doesn't happen.
Does somebody have experimented this issue in another installation? ???
Is it a known "bug"? ???
Is there some fix? ???
Greetings & Blessings from Chile!!!!!!!
Juan
Comments
Are you using the exact same score with both 2.0.2 and 2.0.3? Very large scores will indeed slow MuseScore down; this hasn't changed between 2.0.2 and 2.0.3.
If you have a specific you are seeing a slowdown with even though it is not particularly large, please attach it so we can investigate. But I'm not aware of anything that could possibly cause a significant difference in performance betwene 2.0.2 and 2.0.3
In reply to Are you using the exact same by Marc Sabatella
Mmmm. I don't think my scores are too very large.
But... I'm uploading both with 2.0.3 is going slow, after you load and play it more than 2 times.
I insist, it doesn't happen with 2.0.2 (using the same scores).
In reply to Mmmm. I don't think my scores by jotape1960
I've loaded the first score. It's "kind of" long at 148 measures, so it's a little sluggish to work with - on my system, an edit (like changing pitch of a note) has a small delay - like maybe half a second. Are you seeing something different form that? Can you give me specific steps to follow and describe more precisely what sort of slowdown you mean?
In reply to I've loaded the first score. by Marc Sabatella
I don't have experimented any kind of troubles with that score with 2.0.2 version.
The problems are only presents into the 2.0.3 AppImage version.
In reply to I don't have experimented any by jotape1960
Again, without steps to reproduce the problem - and a clearer description - it isimpossible to do more than guess.
In reply to Again, without steps to by Marc Sabatella
Steps?
Simple:
1) Start MusesScore 2.0.3
2) Open one of "my" scores.
3) Play it.
4) Close it.
5) Open it, again.
6) Play it.
The program will go some slow, also the mouse, etc.
That's all, folks!!!
In reply to Steps? Simple: 1) Start by jotape1960
I don't understand what you mean "go some slow, also the mouse". Do you mean the *playback* is slower is not at the right tempo? Or something else? What specifically are you doing with the mouse that is slow? Are you trying to use the mosue *while* the score is still playing? Also, do I have to play the *entire* score start to finish twice in order to see a problem, or is there some way to see the problem in less than the 10 minutes that would take?
When I follow the steps above but only play a few measures I don't notice anything wrong, but I still don't understand what exactly I need to be doing to see the problem.
In reply to I don't understand what you by Marc Sabatella
Oops!!! I'm sorry!!!
Now I see I didn't explain it, well.
I want to say that the mouse movements go slow (as there was some another heavy process into the background), and the MuseScore cursor is "out of synchronizing" with the playback tempo.
BUT... The playback tempo is right. Sound is right, too (not any kind of artifacts).
The "slow down" is about the mouse movement, the menu opening time, and the score cursor.
It looks that MuseScore 2.0.3 is running at the same time with another heavy process which is eating too much CPU resources.
When I use the 2.0.2 version, it doesn't look like this.
In reply to Oops!!! I'm sorry!!! Now I by jotape1960
Can you bring up a task manager to see how much CPU different processes are using to see if there are clues there? Perhaps some OS update is actually the cause for the difference you see. As mentioend, I simply don't see any change - no discernable slowdown on your score no matter what I do. But I do still need to understand if I need to play the score all the way start to finish in order to see the problem. Like I said, just playing the first few measures, nothing goes wrong for me. Which is what makes me think there really *is* some other process on your system using CPU. I'm also still trying to understand if the mouse slowdown you see is only *while* the score is playing, or if it continues when the playback stops.
In reply to Can you bring up a task by Marc Sabatella
Maybe... Perhaps... The following attached images could bring to you some answer about your enquiry.
As you can see, there is a difference between the first screen (MuseScore 2.0.3) and the second screen (MuseScore 2.0.2) of the Task Manager.
I don't know if that difference is important, but... There is a difference!!!
BTW: I used the exact same score, in the exact playback point.
In reply to Mmmm. I don't think my scores by jotape1960
I opened your score 'Ven conmigo a aquel hogar (cuarteto masculino).mscz' and noticed that starting from measure 144, there are dozens of (invisible) tempo texts, written upon each other.
Here shown visible with some separated:
(BTW: I am using MuseScore 2.0.2)
Regards.
I'm experiencing the slowdown, too. I tried to post it, but the file is too large.
In reply to I'm experiencing the by Stefanokud
If it's too big to attach here, it *definitely* an extremely large score, and indeed, MuseScore is slow with enormous scores like that. This hasn't changed from previous releases - it's *always* been slow for large scores.
In reply to If it's too big to attach by Marc Sabatella
I think it was too big because of a digital photo in the front page. I'll up load it without the photo. I noticed that it was only slow when I used the navigator.
In reply to I think it was too big by Stefanokud
The Navigator is definitely known to slow things down - it basically doubles the work required on each operation, because the entire score is being laid out twice. This has not changed since 2.0.2 as far as I know.
Your score *is* quite long at 433 measures, so it is not surpriusiung it would be sluggish in any version of MuseScore. It is quite fast for me as is because it is mostly empty, but I assume you deleted the actual notes before posting? If this is the actual score you see as being slow, please give exact steps to reproduce the problem if possible. But for me, it is quite responsive with or without the Navigator - again, though, slightly worse with the Navigator which has always been the case.
I deleted the extra measures, so it speeded right up. I always add about 320 measures before I compose. Guess I'll need to be careful. Another score that had the problem is working well, now. I'll keep you informed if the problem continues.
The invisible Tempo objects are there "in purpose".
Those scores don't go "slow down" in 2.0.2.
This issue only happen (into my system) with 2.0.3 (AppImage) version.
(Even the fact that I'm not a programmer) I insist that there is something "wrong" into the new 2.0.3 AppImage version (I don't have any clue about this, but it is there).
Greetings and Blessings from Chile!!!!!!!
Juan