MS3 soundfonts sound two octaves higher than they are supposed to be

• Apr 29, 2023 - 07:18

When opening MS3 scores in MS4, parts using MS Basic soundfonts come out 2 octaves higher than they are notated as. This is a consistent issue with my scores. I've attached the same score, one in MS3, and the other opened in MS4.

(My specs: i5-7600K, Nvidia GTX 1070, 16GB RAM)

Attachment Size
Strange_to_hear - MS4.mscz 29.89 KB
Strange_to_hear.mscz 21.56 KB

Comments

I'm getting this too, soon after installing the 4.1 update. All instruments sound at a ridiculous pitch. I can't find any setting to correct this. I tried reinstalling but it's still happening. It's giving me a "Musescore Civil War" vibe. I hope that's not what's happening because that would mean me shelling out hundreds of dollars that I don't have for Sibelius or something else.

In reply to by bobjp

No. As a matter of fact, the 4.1 update worked fine until a few days ago. My settings are the same. I uninstalled Musescore 4.1 and Muse Hub, re-installed them and problem remains. I tried several scores and all of them sound bad. All of them were using MS Basic so I switched most instruments to Muse Sounds. What I played back sounded like a cat getting run over by a truck. I don't know what's going on but whatever it is, it is affecting all my scores. Yikes!

UPDATE: I'm using Windows 10 and I have the updates set to automatic, so perhaps one of the Windows updates is causing a problem. But I don't know where to even look for the culprit if there is one. Ay yay yay!

In reply to by FBXOPWKDOIR2

I've never had a Windows update mess up anything. Maybe I've been lucky. Reinstall of MuseScore seldom fixes anything. If you were to go the uninstall route, you would need search your computer for every thing MuseScore related and delete it Including the registry. Still might not work. A system restart might help. Or Not. There are audio devise settings you can try to get good playback. https://musescore.org/en/node/339915
The hub wants to stay open in your hidden task bar. Open it and scroll down to and select QUIT.

In reply to by bobjp

Ok, did all that, uninstalled Musescore again but this time rolled back to Musescore 4.1 Testing. Every score still plays like 2 or 3 octaves higher. This happened not long after installing the 4.1 update. It worked a few days. When I have time I will do a deeper clean in the registry and reinstall. Mind you version 3.6.2 is working just fine. What I would really like to do is roll back to 4, 4.0.1 or 4.0.2 but I don't know where to download that.

In reply to by FBXOPWKDOIR2

UPDATE: Deleted nearly all references in the registry to Musescore 4 and Muse Hub. Deleted these programs and then deleted their containing folders. Restarted the computer and reinstalled 4.1. Still all the instruments are sounding about 2 or three octaves higher using MS Basic, and seriously corrupted using Muse Sounds. I'll continue to use 3.6.2 until there's a resolution to this.

In reply to by bobjp

Yes indeed I did. Deleted it, deleted the Musescore 4 folder, deleted MuseSamplerCoreLib.dll in C:\Windows\System32, and then went on to search and destroy most Musescore 4 related registry keys and values. Even in Administrator mode some keys could not be deleted. This should have been enough to nearly wipe out everything to do with Musescore 4 but it went tango uniform anyway. I have Windows 10 updates on auto, so I'm thinking there is a sound update that my system downloaded up to a week ago that is roiling Musescore 4. A long shot might be Muse Hub and Audacity updates, which I doubt but cannot rule out 100%. Any software having anything to do with sound production on my computer is suspect at this point, even Musescore 3.6.2 which is working fine. There might be Musescore software on the computer still that are not marked as such, and that's how I search for them, by the filename or key. If there's a Musescore file called for example "I81U812.dll" then I will not be able to find it or know what it is. It might be helpful to have a list of files that are installed, or even a dedicated clean uninstall program that will do all the registry and file operations for us but that's another issue for another time.

Generally this is caused by an incompatible sample rate in your audio device/driver - like perhaps it's set way up to 192 kHz? Try turning it dow to a more typical value like 44.1 or 48.

Do you still have an unanswered question? Please log in first to post your question.