musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.39k stars 2.68k forks source link

[MU4 Issue] Opening MuseScore 4 and then MuseScore 3 makes Playback stop working (Windows only) #10957

Open Darkspeen opened 2 years ago

Darkspeen commented 2 years ago

Describe the bug Opening any version of MuseScore and then another version makes the playback system stop working. Furthermore. There's no option to change the audio device which I presume to be the problem when system tries to access the audio device assigned to a host that most likely appears like the same.

To Reproduce Steps to reproduce the behavior:

  1. Open MuseScore
  2. Make it play something to check playback system
  3. Open other version of MuseScore while keeping the other one opened
  4. Try to play something on either of them.
  5. See error: The playback line does not move from the beginning

Expected behavior The system should be able to identify both as a different host and therefore let both versions play something accordingly.

Platform information

Additional context This happened when trying to also check for behaviour of MIDI files opening in both MuseScore 3 and MuseScore 4. This is also perhaps another topic to look into: as the MIDI file interpretation of MuseScore is not clean: Does not interpret BPM information correctly and thus, the MIDI quantization comes out as poorly.

Workaround Start MuseScore 3 and then MuseScore 4

RobFog commented 2 years ago

"as the MIDI file interpretation of MuseScore is not clean: Does not interpret BPM information correctly and thus, the MIDI quantization comes out as poorly."

That seems to warrant a separate report.

Darkspeen commented 2 years ago

I thought so as much, but it is not MuseScore 4 exclusive. I'll check further into it and see what I can find before I submit it as an issue to know exactly what to post in more detail.

DmitryArefiev commented 2 years ago

That's Windows only issue. I guess it's related how MU3 allocates audio device (signal)

The workaround is to start MuseScore 3 and then MuseScore 4 (working for me). I'll update the description.

Thanks for logging this!