Multiple instances of Spitfire Labs don't work after reload.
I have multiple instruments using Spitfire Audio's LABS virtual instruments in the same score.
While in the score, I can change the sounds in mixer as I please and everything works flawlessly. However, once I reload the project, only one of the labs instruments makes sound, others just kinda... turn off? It's not like they are outputting sound and it can't be heard, it's just they don't work. But if I switch instruments in the mixer to another and back to LABS, it starts working again. Up until the next reload, that is.
Any potential way I can fix this?????
Comments
Try forcing a check of VSTs. See https://musescore.org/en/handbook/4/working-vst-and-vsti#Installing_VSTs
In short, stop MS4, delete the file: %localappdata%\MuseScore\MuseScore4\known_audio_plugins.json and start MS4. This should trigger a check for existing/installed VSTs.
If you actually have duplicate LABS versions installed, you may need to remove 1 of them.
In reply to Try forcing a check of VSTs… by Henk De Groot
Just tried deleting the .json file. After the process, nothing changed.
And, when searching through the LABS versions, it seems that I have only installed 1. At least in Users/[me]/Spitfire there is only one of each instrument and no doubled up files at all. The same in program files.
Anything else I could try?
In reply to Just tried deleting the … by Mimumi372
Which LABS version are you using? Mine is v3.0.26-7fd6880.
Have you installed LABS VST into a custom folder?
In the standard VST3 folder there should also just be one Spitfire Audio folder (C:\Program Files\Common Files\VST3).
Do you have another VST3 folder set in MS4 Preferences->Folders VST3?
When did this issue start? Just after an update of MS4? After a LABS update? Or..???
One more thing you can try is revert to factory settings, but that removes custom settings in MuseScore.
In reply to Which LABS version are you… by Henk De Groot
Oh and one more....perhaps you can open the known_audio_plugins.json file in a text editor and check the LABS versions in that file.
Or attach your file here, and I can check/compare it to mine.
In reply to Which LABS version are you… by Henk De Groot
The version I am using is also 3.0.26, but no extra "7fd6880"
No, when I have installed LABS I selected the standart folders, so it is in fact situated in C:\Program Files\Common Files\VST3.
I don't think I changed the folder in musescore preferences even though right now I can't find the preferences window.
The issue start right after I downloaded LABS. I didn't have an experience without this issue yet.
In the JSON file the only part referring to LABS is this:
{
"enabled": true,
"meta": {
"attributes": {
"categories": "Instrument|Synth"
},
"hasNativeEditorSupport": true,
"id": "LABS",
"type": "VstPlugin",
"vendor": "Spitfire Audio"
},
"path": "C:\/Program Files\/Common Files\/VST3\/Spitfire Audio\/LABS.vst3\/Contents\/x86_64-win\/LABS.vst3"
},
{
"enabled": true,
"meta": {
"attributes": {
"categories": "Fx|Mastering"
},
"hasNativeEditorSupport": true,
"id": "Master",
"type": "VstPlugin",
"vendor": "MuseFX"
},
"path": "C:\/Program Files\/Common Files\/VST3\/MuseFX\/Master.vst3"
},
I guess reverting might help, but if it doesn't, then what?
And btw, thank you for your help in advance, I really appreciate it.
In reply to The version I am using is… by Mimumi372
Guess if you had more than 1 VST3 folder to check, it would show twice in the json file as well.
You json contents looks the same as mine, it is odd. Not sure what else might be causing this.
Have you tried re-installing LABS as well?
In reply to Guess if you had more than 1… by Henk De Groot
No, I haven't tried re-installing LABS just yet. Hopefully it will not break anything completely. I will start by doing that tomorrow, and it that doesn't help either, im gonna try resetting MS to factory defualt.
In reply to Guess if you had more than 1… by Henk De Groot
Also, is there perhaps a debug log for musescore which I can read and check for any errors? Perhaps that will help
In reply to Also, is there perhaps a… by Mimumi372
MuseScore creates a logfile each time it is started at this location: %localappdata%\MuseScore\MuseScore4\logs
Good call, perhaps there is something in it which hints to the issue/problem. Specially when selecting the VST in the mixer and when it does not work.