Migrating sound libraries
I want to restructure the sound libraries I have for MuseScore 4, mainly because space on some of my external SSDs is running out.
I have been able to copy the files from several onto a much larger SSD and in some cases I may have to re-register the files in their new locations with the provider [e.g. Spitfire, for some VSTs].
Is there anything special which must be done for Muse Sounds, or the libraries downloaded via Muse Hub?
It looks as though there is a path in the Preferences file which can be used to point to external VSTs - maybe that should just be updated to reflect the new locations - but does anything else have to be changed? New permissions? etc.....
Comments
In reply to Muse Sounds would not be in… by Asher S.
I've made partial progress, but there is a problem.
The original SSD was about 256 Gbytes. The target SSD is 2 Terabytes.
To get the migration I downloaded the latest version of MuseHub.
From MuseHub I specified the new SSD as the target for the libraries.
It now looks as though that has copied most or all of the libraries to the new target SSD.
However MuseScore is only picking up the basic Muse Sounds libraries but the additional libraries, such as Berlin Strings, Woodwind etc., and Cinesamples, Spitfire and Audio Imperia and also the Antique Keys libraries are not being discovered, even though the folders for those resources are non empty on the drive. The folders appear to have SFZ files.
I deleted the Muse Sounds fodlers from the original SSD - which hasn't affected the basic Muse Sounds - but currently I can't play any of the other libraries.
However the VST libraries are still on the original SSD, and they still work. That was one of the things I wanted to achieve, to allow installation of a few new libraries. Eventually I'd like to move the VST libraries as well, either to the larger SSD which now contains the Muse Sounds libraries [even if some aren't working yet], or to another larger SSD. There should now be enough space on the original SSD to get the addtional VST libraries installed, even without trying to migrate them to another drive.
With a fairly substantial investment in those additional libraries I do need to get them working, and I don't want to have to pay for them again!
I may have got this fixed. I put in a bug report to MuseHub pointing out that I suspected the libraries hadn't all been authorised, though relevant files seemed to have arrived on the new external SSD. Now the interface in MU4 seems to have menus for all the libraries I bought, and although I've not tested all the 3rd party instruments, the few I have checked seem to work OK.
I set the automatic update option in MuseHub, and today it does seem as though all the libraries are now working.