Sound Problem - similar

MuseScore 2.0.1 build b25f81d
Mac OS 10.10.3
MacBook, late 2009

I submitted this report a long time ago. The thread became too complex, it's no longer active. The problem remains. This is the very-short version of the previous thread. I've made extensive attempts to replicate it and to develop workarounds. It's still not clear whether it's a MuseScore bug or whether there's something wrong with my machine.

When the machine goes to sleep with MuseScore open, usually, but not always, the problem occurs. MuseScore awakens with a sharp "pop" through the speakers and the sound won't play. Otherwise, MuseScore works normally. Under view:synthesizer, the visual display looks like sound is playing. The problem also occurs under other circumstances. Sometimes MuseScore opens with a sharp pop, and sometimes it happens at apparently random times when I am using MuseScore.i

It's a serious inconvenience. If I am careful not to put the machine to sleep when MuseScore is in use, it occurs about a third of the time on launch, and about once every twenty minutes when MuseScore is in use.

When this occurs, my other applications also won't play sound. Quitting MuseScore does not solve the problem. At this point, other applications that normally play sound make a sharp pop instead of playing sound. If I click on system sound effects, they also pop instead of playing, or play faintly with a pop.

Rebooting the machine usually solves the problem. Sometimes the problem resolves itself spontaneously. Spontaneous resolution is more likely to happen when MuseScore has been closed. This machine is constantly in use with a wide variety of applications and is perfectly stable in every other respect. I've never seen any other application cause this problem. The problem has persisted through all versions of MuseSccore 2.0, starting with beta. It never happened with 1.3.

The basic question is -- Does this happen on your machine, particularly Mac OS, when MuseScore is open, you put the machine to sleep, and then wake it up again? If so, it's probably a MuseScore bug. In that case, on what problems. If not, there's probably something wrong with my machine.