Mixer: Solo glitch - singled out instrument using "solo" button now the only sound on playback of the entire score
BUG REPORT
(MuseScore recommended format)
Steps to reproduce bug (requires a score with multiple instruments)
1) Open Mixer
2) Solo out an instrument (for me, it was an acoustic guitar)
3) Playback score with "solo-ed" instrument
4) Turn off solo on instrument
5) Playback score again
Expected behavior: MuseScore should solo out the instrument in the first run through, and then, after turning off the solo, should bring the rest of the instruments back in.
Actual behavior: Solo-ed instrument is stuck as the only sound in the score even after turning solo back on and off
Discussion: The workaround I found was to turn on solo on all of the instruments in the score, and I was able to hear all the instruments again.
Specs:
Version: MuseScore v. 3.0.0.4747
Revision: 96c1f7b
Downloaded from website/Not complied from source
Operating system: Windows 10 v.1803 (OS build: 17134.472)
===============================================
SUMMARY/BREAKDOWN
PROBLEM: I was working with a score, and wanted to solo out one of the instruments so I could catch it up to where the rest of the instruments were in the score without it being covered up by the rest of the instruments. After getting to a stopping point, my plan was to turn off the solo so I could hear all the instruments. The problem was, when I did, no sound from the other instruments came out. The guitar was stuck in "solo" mode.
WORKAROUND: I figured out that by enabling the solo button on all of the instruments, I was able to hear all the instruments again, but it may happen again.
ATTACHED:
-- Steps to hopefully reproduce the process (solo_step1.JPG and solo_step2.JPG)
-- Screenshot of mixer displaying the workaround. (solo_workaround.JPG)
UPDATE (12/25/2018 10:51 CST): Fixed itself, but I don't know how or why. May still be something to look into.
Attachment | Size |
---|---|
solo_step1.JPG | 52.1 KB |
solo_step2.JPG | 51.97 KB |
solo_workaround.JPG | 52.73 KB |
Comments
I don't know what happened, perhaps its the score? I tried it on a few scores both imported from version 2 and created from scratch in version 3 with no problems. I'm using the same windows 10 build you are.
Mine actually started refusing to play anything. I soloed a trombone section, unsoloed them, and suddenly I couldn't hear anything at all, like the whole score was muted. I had to Solo anything I wanted to actually hear.
Wow, it is the greatest bug report I've ever seen! Thank you.
I see you reported the issue using not the recent release build. Could you please download and install the official release and try there? (https://musescore.org/en/download/musescore.msi)
In reply to Mine actually started… by Laurelin
Could you please attach the score? I cannot reproduce with any of mine :(
In reply to (No subject) by Anatoly-os
OP is using the official 3.0 release as am I.
In reply to OP is using the official 3.0… by mike320
The official release has build number 4785, not 4747 (which is most probably a RC)
In reply to The official release has… by Anatoly-os
You are correct, I thought I had downloaded the official release, but I'm still using the RC.