Problems with LABS plugin
Hello everyone - since yesterday's LABS update, the plugin is no longer working in MuseScore: when I choose the LABS sounds in the mixer view, all I get is an empty LABS window (see attachment), also in the VST3 menu, I see LABS twice. In other programs (e.g. Ableton Live), LABS continues to work properly and all sounds are available.
Any idea what I can do to resolve the issue? (All existing scores that use LABS sounds no longer work and result in MuseScore crashing). I have deleted both LABS and MuseScore and reinstalled them, to no avail.
Avy
Comments
That's a VSTi, not a Plugin in the sense of thie sub-forum
I ran into this issue as well, I havent found a way to get LABS working again, but you can recover the score files (.mscz) by opening them up in a file archiving software (like winzip or 7zip) and deleting the audiosettings.json file inside it. Then when you open the file it wont crash, though you will lose your mixer settings for that score.
Note: When I used 7zip I was not able to actually open the score file from file explorer, but I managed to get into it by launching a separate 7zip application window then navigating to the score file.
Same problem with LABS. This is the first time I tried using. I have not saved any scores that Labs would not work.
In reply to Same problem with LABS. This… by dannsh13
the same for me
the old LABS (x64) works but the new one "LABS" does not.
resetting to factory settings worked
In reply to the old LABS (x64) works but… by glennmstanton
My problem was actually resolved after hitting 'revert to factory settings' in the help menu, maybe that helps in your case as well.
In reply to My problem was actually… by avstaden
where would I find the factory settings for LABS? I can't see it anywhere
In reply to where would I find the… by yannysadness
Have a look at the handbook.
https://musescore.org/en/handbook/4/working-vst-and-vsti
A re-scan of VSTs by deleting
C:\Users\ [your user] \AppData\Local\MuseScore\MuseScore4\known_audio_plugins.json
should fix the problem.
Or (what i would do): edit the file and delete only the Labs entry.
In reply to Have a look at the handbook… by graffesmusic
This worked perfectly, thank you !
In reply to Have a look at the handbook… by graffesmusic
By editing the JSON it doesn't trigger the rescan.
It starts rescanning only by deleting the JSON.
And yes, after the rescan, the LABS new version is now available
In reply to By editing the JSON it doesn… by tormyvancool
Sure it does.
If you delete the LABS block, the (new) LABS vst is detected when MS is restarted.
Maybe/Probably you had more than one LABS block - one for the original and one for the new Vst?
In reply to Sure it does. If you delete… by graffesmusic
Yes I had more than one LABS block but I deleted all of them.
Rescan wasn't triggered at all
The old references in VST3 where still present.
But the JSON file was cleaned but all the LABS
Solution: remove it.
Musescore then rescanned everything, and now it's ok.
In reply to Yes I had more than one LABS… by tormyvancool
Ok. On my systems this works every time i have done this. I tested it just now.
Delete any vst from json, restart => vst is rescanned.
Anyway, deleting the file also works of course. But then all the vst's from your system are visible in MS, also those you do not want to see (because only useful in a Daw) and you have previously disabled in the json file with "enabled": false,
In reply to Well, on my systems this… by graffesmusic
If they don't put any other system to refresh the scan etc, it's not my responsibility.
As user, I shouldn't even think to edit any file. I have to click a button and the system does what it's supposed to do.
What I see, are all plugins I can use in MuseScore. perhaps they are filtering the plugins already when they scan them.
In reply to If they don't put any other… by tormyvancool
There once was a project for a "Audio plugin manager"
https://github.com/musescore/MuseScore/issues/15967
Design ready.
But it was forgotten.