3.6 locked up when Stave parts menu selected
Sadly my current session of Musescore locked up completely when I tried to experiment with the Stave parts feature to see if I could colour staves.
There was no obvious way out. Esc didn't work. Apply didn't work. Cancel didn't work. etc.
I'm not sure if I lost a whole bunch of edits from the last hour or so - hope not!
Is there a recovery feature if I lost data?
PS: Looks like a recovery was done when I restarted Musescore. Most or all of the edits I wanted seem to be OK.
Phew!
Comments
Make sure to have updated to 3.6.2
In reply to Make sure to have updated to… by Jojo-Schmitz
OK - thanks.
In reply to OK - thanks. by dave2020X
Nope - sorry - still locks up. Just downloaded a new copy of 3.6.2 and it still locks up when I try to change the staff colour.
I think I've identified one other thing I was mentioning recently - about the versions not showing up "properly". The new version I just downloaded - 3.6.2 identifies as 3.2, so I'm guessing that since we are I think still in series 3 that the 6 is just being dropped. I'm still using MacOS Catalina.
In reply to Nope - sorry - still locks… by dave2020X
Nope, that naming thing apparently is your fault of having renamed it. Had come up recently (and even by you), see https://musescore.org/en/node/317397. Strange enouhg there you claim it being shown as MuseScore 3.3 and here as MuseScore 3.2...
Reg. that crash please share the score and the exact steps
In reply to Nope, that naming thing… by Jojo-Schmitz
I wonder if the crash was because of the file size. I extracted a very small section - see attached - and managed to get it coloured. I was rather hoping that the gaps between the lines would be coloured, rather than the lines themselves, but this could be manageable.
I don't particularly want to put up the previous file example - which crashes - because it is work in progress. If I find another example which also crashes I'll happily put that up. One issue might be that there is a pop up menu to show the colour palettes. It might be that the menu is not seen and goes underneath other panels or windows, so the program is still actually running, but unresponsive because it is calling for input which never comes - until the user force quits the program.
I can test that hypothesis, and come back later.
In reply to I wonder if the crash was… by dave2020X
Actually now this seems to be working. Perhaps it doesn't matter that the spaces between the lines aren't coloured, as with care the individual staves are clearly identifiable.
However, it would perhaps have been nicer if it had been implemented so that only parts of each stave could be coloured. What appears to happen is that the colour is applied from the first bar right through to the last.