MS3 - Insane bug: from-MS2 imported score plays with whatever instrument the last score used!!!
OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.2.20666, revision: 8ca4d2c
This MS2 score I downloaded from another user and changed a couple of chords has a most remarkable property (in MS3). It clearly was written for solo piano. But if you open it, and play some choral score already open in another tab, it acquires choral voices! If you then play a Bach cantata aria you have open whose topmost line is oboe, it becomes all oboes (and sounds better, btw). Something is not initialized somewhere, and I suspect it will reveal the stuttering bug.
I took care to write out this MSCZ, and verify that I could reproduce the problem with it.
| Attachment | Size |
|---|---|
| NoInstrument.mscz | 28.46 KB |
Comments
Interesting! Not sure how this score was created, but your description and filename are accurate - the score contains no instrument definition. Well, it has an instrument tag, but no "program" information (the MIDI patch number) in it. My guess is the user had created a custom instruments.xml file that contains a syntax error. Or maybe he did this on purpose. Anyhow, since the information is not there in the score, MuseScore has no information to go on in selecting sounds, so pretty much anything it chooses to do is fair game.
In reply to Interesting! Not sure how… by Marc Sabatella
The Score Properties suggests that it came through XML. The user has no other scores, and the score is a couple of years old.
In reply to The Score Properties… by [DELETED] 1831606
Score had been created (or rather last saved with) MuseScore 2.0.3 and indeed stems from an xml import.
Plays as Piano (on the Website and in MuseScore when the first score opend in a session), probably because that is the 1st instrument in any GM soundfont.
In reply to Score had been created (or… by Jojo-Schmitz
How fortunate that the composer intended it as piano music.
In reply to How fortunate that the… by [DELETED] 1831606
or unfortunate, as that is why he missed the problem
In reply to or unfortunate, as that is… by Jojo-Schmitz
How on earth did he get in that state? How do you leave it?
In reply to How on earth did he get in… by [DELETED] 1831606
XML import?
In reply to How on earth did he get in… by [DELETED] 1831606
Since XML was mentioned, my guess is that the MusicXML file this was imported from did not contain any instrument information at all, so MuseScore 2 dutifully created a MSCZ file with only limited instrument information as well. Impossible to say without seeing the MsuicXML file this was apparently imported from. Would be nice to see it, so we can see if maybe MuseScore 3 could be changed to do something different. Not sure what the "right" thing to do is if the MusicXML contains literally no information about intended instrument at all, but I guess making it be a piano sound is as good as anything. We could also "fix" files already imported that lack this info to include some, potentially. But again, it would be good to understand what the MusicXML file actually specified.
Meanwhile, to fix this, simply change instrument to whatever you want (piano, presumably).
In reply to Interesting! Not sure how… by Marc Sabatella
From here (MS2 online): https://musescore.com/user/13995576/scores/3951356