MuseScore 2 and 3 compete for the MIDI input device
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
Project
I have been having a lot of issues with the new install of MS 3 [see my posts regarding these], and I have a couple pieces I really need to get done. Since there are all the issues using MS 3 right now, I decided to just use MS 2 for a while and get these pieces knocked out. I start the piece, get it set up and blocked out, only to find that my midi will not play in MS 2! Only the qwerty will input notes. The input and output settings are totally blank today and there is nothing available in either dropdown. So, basically, I have no program at my disposal to get this work done right now.
How can I get my midi to work once again in MS 2? How do I get the settings in the dropdown boxes?
Scott
Comments
I've fixed in another bug report: #279203: MIDI Input / Output doesn't work
> " I have a couple pieces I really need to get done"
If you have important notation work you need to do, best stick with MuseScore 2.3.2 for the time being. (Don't worry, you can have both MuseScore 2 and MuseScore 3 installed simultaneously).
> "How can I get my midi to work once again in MS 2?"
I don't think you are actually in MuseScore 2.3.2, because that bug was only introduced for 3.0 release. When you run what you think is 2.0, please take a look at Help->About and copy the version string here.
In reply to > "How can I get my midi to… by ericfontainejazz
2.3.2 is what comes up.
for anybody reading this, 2.3.2 failed to receive midi because 3.0 was running when 2.3.2 was started...so make sure to close 3.0 if you experience this glitch before opening 2.3.2.
So MuseScore 2 and 3 do peacefully coexist, as long as they don't fight for the MIDI Input device, right?
In reply to So MuseScore 2 and 3 do… by Jojo-Schmitz
That is what I observe.
Did someone forget to reactivate this? It needs to be addressed from the 3.0 side.
I would think this is by design and not fixable, not by MuseScore at least?
I'd agree it's by design. I should have said this is by design.
What do those of us caught in the competition do?
Quite obviously: Either don't run MuseScore 2 and 3 at the same time on the same computer or configure one to not use MIDI input.
The problem is that I am not running both at the same time, only MS2, and that now doesn't accept midi input. Is it just sensible to dump MS3 until such time as these problems are solved?
That is strange. Just out of curiosity, if you reboot your computer and start MS2, then does midi input still not work???
Strange is about right. Yes, apparently you are exactly right, as it would not work last night, and after the job today, I tried it and it works just fine on MS2.