Closed thaumasiotes closed 1 year ago
thaumasiotes
commented
1 year ago I should note that the MuseScore discord advised me to file this issue. I can't really confirm that the nonstandard install location causes the problem, because I have the same problem when I install to the default location.
iamtesch
commented
1 year ago @thaumasiotes -- I've confirmed that MuseSounds still work after setting a custom folder. Especially as the issue happened with the default location as well, there is something else going on.
A couple questions:
MarcSabatella
commented
1 year ago FWIW, there were at least a dozen reports of this on Discord during the beta, and it was always just assumed it wasn't supported. And quite a few reports since the release as well. So it's definitely not working for a lot of people. Not sure if it's OS-specific or something else.
asheb
commented
1 year ago Have similar issue. Installed to a custom location. The profile in Playback setup is grayed out and there's no Muse Sounds option in sound selection in the mixer.
Check MuseSampler says "Muse Sampler library is not found". OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223472200, revision: github-musescore-musescore-5485621
iamtesch
commented
1 year ago This is definitely supported, however setting that directory to an external drive does not work at this point (we are working on improving the behavior in the case that this fails). I have a feeling this is the root cause of the issue for many people. To filter out issues purely related to custom locations, can you confirm if anyone experiencing this both: (a) is setting the custom folder to an internal system drive and (b) has no problems loading the sounds if they switch back to the default location?
MarcSabatella
commented
1 year ago Excellent information, thanks! And yeah, I suspect that using an external drive - or at least, a non-default internal drive - is the main reason are trying this.
At least some people have reported issues getting sounds working after reinstalling, but in some cases at least things were fine after restarting. I'll follow up as I can with people reporting problems.
thaumasiotes
commented
1 year ago Unfortunately, I won't be able to provide the information requested ("Check MuseSampler" and version number).
But I can offer the alternative information that, after setting the MuseSounds install location back to the original custom folder, and then using MuseHub to uninstall and reinstall MuseScore, the new MuseScore installation detected MuseSounds. It was not necessary to restart my PC.
For the version I was using when I filed the report, you'd have to guess based on the fact that I installed it through MuseHub earlier the same day. The version I have now is 4.0.0.223472200. And the MuseSampler check says "Muse Sampler library is detected, version 0.3.2", though I should reiterate that the new installation is correctly detecting MuseSounds.
asheb
commented
1 year ago For me, just restarting OS fixed the issue. I'm still using the same custom location (it's on my internal SSD, but partition is different from the one with the OS).
I did reinstall MuseScore once, but not sure if that's relevant, since it still couldn't load Muse Sounds until I restarted the system.
plutogenie
commented
1 year ago I confirm the same behaviour when I downloaded to a custom location on an external drive. The other thing I had tried, resulting in no change, was adding the "D:\MuseHub\Muse Hub Downloads\Instruments" folder to the list of folders for SoundFonts under Edit->Preferences->General->Folders.
To test whether the issue is caused specifically by an external drive, I changed back to the Default location in MuseHub and restarted the OS. I copied the "Muse Strings" folder (only one I have downloaded) and ".instruments" file into the "C:\users...\Documents\Musescore4\SoundFonts" folder which is the default under Edit->Preference->General->Folders->SoundFonts. The MuseSounds option was then "active" and selected under View->Playback Setup.
(Please note that my Documents folder is located within OneDrive, in case this is relevant. The Musescore4 folder is set to "Always available on this device", so the files are physically on my main internal hard drive and accessible.)
However, when I access the Mixer on an existing project, the only options provided are:
If I create a new project and add an instrument, there is no indication of any MuseSounds being available either. There is no mention of "MuseSounds" in the list of instruments, so it is unclear if those listed are MuseSounds or MS Basic instruments.
I checked what happens when I install a new MuseSound (Keys) to the default location in MuseHub. The instrument data is stored at "C:\ProgramData\MuseHub\Downloads\Instruments". After downloading I opened MuseScore4 and found that the "Muse Sounds" option had been added to the Mixer list above, and Muse Keys was visible as a submenu.
This appears to suggest that MuseScore4 does not look under the SoundsFont default folder or any other folders added. It only looks under "C:\ProgramData\MuseHub\Downloads\Instruments", regardless of what folders are specified under Edit->Preferences->General->Folders->SoundFonts.
I was looking for a solution that avoided re-downloading Muse Strings.
I firstly copied the Muse Strings folder to the same default instrument folder where Muse Keys installed. MuseScore4 did not see Muse Strings because, I assume, the ".instruments" file (which has SQL query information added from what I can see via Notepad) needs to be updated by MuseHub to reflect that Muse Strings exists and is available to MuseScore4. This is confirmed in MuseHub which shows that Muse Strings has not been downloaded, even though it has been and in the same location as Muse Keys.
I tried a few additional things:
I gave up and started to re-download/install Muse Strings via MuseHub. It started preparing for download and must have checked that Muse Strings was already in the default instrument folder. It then quickly changed Muse Strings from "Get" to "tick". So that was a good outcome. I have checked MuseScore4 and both Muse Strings and Muse Keys shows up.
These tests suggest that the issue is not with the external drive location. Instead, the issue is that MuseScore4 is not checking any of the folders specified in Edit->Preferences->General->Folders->SoundFonts as expected. It only looks at "C:\ProgramData\MuseHub\Downloads\Instruments" for MuseSounds. That includes that MuseScore4 does not appear to know the Custom Location specified in MuseHub, which suggests there is no link between the two systems. Perhaps if MuseScore4 is modified to read the Custom Location correctly, the external drive issue will be solved.
EssyTech
commented
1 year ago I installed the sounds onto a different drive on the computer. Muse4 could not detect the new library. However, I restarted the HUB after the initial install and the sound library was detected. Seemed to fix it for me. Windows 10 user.
cbjeukendrup
commented
1 year ago Closing, since this is rather old and we haven't seen any new reports of this. If anyone is still experiencing this, please create a ticket at https://musehub.zendesk.com/.
BetterOIer
commented
5 months ago I think I know the solution!
According to my test, I reckon MuseScore uses relative position instead of absolute position.
That means If your MuseScore is installed in the default position(C:\Program Files\MuseScore 4), the program will turn to C:\ProgramData\MuseHub\Downloads to detect the library.
However, if you have changed the MuseScore's position during its installation, such as D:\Program Files\MuseScore 4,the program will turn to D:\ProgramData\MuseHub\Downloads instead of the former one.
SO, what you have to do is simply move the MuseSound position to the SAME drive that MuseScore is installed.
Hope it may help you.🌹🌹🌹
Describe the bug Setting an install location for MuseSounds causes MuseScore to be unable to use MuseSounds.
To Reproduce Steps to reproduce the behavior:
Expected behavior MuseScore should recognize the new MuseSounds installation.
Screenshots
Platform information