Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playing to MIDI plays all the staves despite the selected staves #18389

Open
lgvr123 opened this issue Jul 4, 2023 · 5 comments · Fixed by #18827 · May be fixed by #21874
Open

Playing to MIDI plays all the staves despite the selected staves #18389

lgvr123 opened this issue Jul 4, 2023 · 5 comments · Fixed by #18827 · May be fixed by #21874
Assignees
Labels
MIDI Issues related to MIDI input/export, or MIDI devices playback General playback issue

Comments

@lgvr123
Copy link

lgvr123 commented Jul 4, 2023

Issue type

General playback bug

Bug description

When I select a part of my score and play it, the normal behaviour is that it plays only the selected part.

selectMidi

This is not the case with MID I output: all the staves are played.

Steps to reproduce

  1. Open a multi-staves score
  2. Configure MU4 to play to a MIDI output
  3. Select a measure from one staff
  4. Play it

Expected:
Only the selected measure/staff is played

Actual;
All the staff are played

Screenshots/Screen recordings

See https://musescore.com/user/36377501/scores/11363188/s/7jiuxK

MuseScore Version

4.0.2

Regression

No.

Operating system

Windows 10

Additional context

OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: github-musescore-musescore-dbe7c6d

@muse-bot muse-bot added the playback General playback issue label Jul 4, 2023
@bkunda bkunda added the needs info More information is required before action can be taken label Jul 7, 2023
@lgvr123
Copy link
Author

lgvr123 commented Jul 7, 2023

Same workflow and use case as in Staves and voices not played to MIDI output correctly.

@zacjansheski

This comment was marked as outdated.

RomanPudashkin added a commit that referenced this issue Jul 31, 2023
Fix #18389: Block output to muted mixer channels
@RomanPudashkin RomanPudashkin removed the needs info More information is required before action can be taken label Jul 31, 2023
@Jojo-Schmitz

This comment was marked as resolved.

@RomanPudashkin RomanPudashkin reopened this Aug 1, 2023
@RomanPudashkin RomanPudashkin added this to To do in 4.x LONGLIST via automation Aug 1, 2023
RomanPudashkin added a commit that referenced this issue Aug 1, 2023
…utput

Revert "Fix #18389: Block output to muted mixer channels"
4.x LONGLIST automation moved this from To do to Done Aug 1, 2023
@RomanPudashkin RomanPudashkin reopened this Aug 1, 2023
4.x LONGLIST automation moved this from Done to In progress Aug 1, 2023
@oktophonie oktophonie added the MIDI Issues related to MIDI input/export, or MIDI devices label Aug 1, 2023
@lgvr123

This comment was marked as resolved.

@cbjeukendrup

This comment was marked as resolved.

@cbjeukendrup cbjeukendrup moved this from In progress to To do in 4.x LONGLIST Aug 1, 2023
adazem009 added a commit to adazem009/MuseScore that referenced this issue Mar 10, 2024
Since the class is called MidiInputOutputController, it makes sense to send events to MIDI devices there.
The track ID is used to get the mute state of the track and avoid sending events of muted mixer channels.
@adazem009 adazem009 linked a pull request Mar 10, 2024 that will close this issue
8 tasks
adazem009 added a commit to adazem009/MuseScore that referenced this issue Apr 26, 2024
Since the class is called MidiInputOutputController, it makes sense to send events to MIDI devices there.
The track ID is used to get the mute state of the track and avoid sending events of muted mixer channels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MIDI Issues related to MIDI input/export, or MIDI devices playback General playback issue
Projects
4.x LONGLIST
  
To do
9 participants