musescore / musescore/MuseScore
Sending the MIDI command "Play" simultaneously activates the playback of all open scores in MuseScore.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
When on my iMac I have several musical scores open with MuseScore and I send a midi command (defined via Settings/MIDI mapping) the command thus sent is executed in all open MuseScore sessions. I have noticed this, for example, with the PLAY, REWIND or LOOP PLAYBACK functions.
It seems normal to me that only the active session (active window score) should start playing.
Steps to reproduce
Prepare/Control some MIDI mapping for player functions in MuseScore / Preferences. (see screeshot as exemple)
Open several SCORES/ MuseScore sessions
Send "PLAY" MIDI Command to MuseScore (with keyboard or Elgato StreeamDeck i.e.)
Error : MuseScore starts playing all open music pieces at the same time
Screenshots/Screen recordings
MuseScore Version
MuseScore Studio version (64-bit): 4.3.1-241490902, revision: github-musescore-musescore-026c26b.
Regression
No.
Operating system
OS: macOS 12.7, Arch: x86_64
Additional context
Already Not OK in MS 4.2.0 with same iMac environment.
At the moment I don't have a Windows PC to do the same test on a PC.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with several scores open and a MIDI mapping for Play, Rewind, or Loop Playback. Trace how MIDI-mapped player commands are dispatched across open MuseScore windows, and consider the issue done when the command affects only the active score; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100