Deep thinking on simultaneous note and rest

• May 23, 2016 - 09:06

I've just started using MuseScore (v. 2.0.3, rev. 3c7a69d) under Mac OS (10.11.5, 15F34) to write out drum scores.

It seems that, on any score I create, whenever I mistakenly input a rest for a drum element (snare, ride, whatever) in a position where there's already a note for that same element, MuseScore enters an indefinite period of thinking (i.e. the Mac cursor turns into a swirling beachball), which so consumes my Mac that using it becomes practically impossible.

Even calling up the Mac Force Quit menu (using the keyboard shortcut) takes so long, the quickest way to regain control is to power down manually instead (by holding the on/off key for a few seconds).

Is this a known issue? Searching the forums and Googling didn't (immediately) turn up anything.

Any help would be much appreciated.

Attachment Size
Xtal.mscz 9.42 KB

Comments

• May 23, 2016 - 09:14

Can you explain exactly how to reproduce the problem?
I open your file Xtal.mscz and select the very first note on voice 2, press 0 to enter a rest, and it works: the note is replaced by a rest. What do you do exactly to have the problem?

Reply

• May 23, 2016 - 11:38

I forgot to mention explicitly that the problem isn't about replacing a note by a rest (or vice versa) but about (mistakenly) superimposing the one on the other (using shift when adding the second).

It now turns out that when I do this for the first note of the attached score (selecting it at and adding a simultaneous rest using shift+F), MuseScore doesn't, in this case, enter 'deep thinking', but simply crashes instead.

Reply

Do you still have an unanswered question? Please log in first to post your question.