Musescore 4.1 (Mac Os12.6.7) startup blocked in scanning Audio Plug in
At first launch of v. 4.1.0 Musescore started to scan audio plug-in (I have many of them) and the was stuck at 31% on Arturia's VST3 WurlitzerV.
After forced quit and re-launch the plug-in search doesn't even start and is blocked on the same plug-in; but the scan is at 0%. I was searching some pref to trash; but I can't find any and even after replacing the application with a fresh one nothing changes.
Another strange thing is the fact that in the forced quit panel I have 2 instances of Musescore instead of one as it should be.
Any suggestion?
Thanks in advance
Massimo
Comments
Solved. I trashed the whole directory of Musescore 4 in User/.../Library/Application Support and launching trashed one by one the older VST3 Arturia's Synths that caused the scan to stuck. A bit troublesome because I had to go through the process for each incompatible plug-in; but eventually worked. Maybe a Plug-in blacklist could be useful.
Greetings
Massimo
Also having this issue. Musescore4 gets stuck analysing WaveShell-VST3 9.3.vst3 if that info is worth anything.
In reply to Also having this issue… by goncalomarque1
wow. im having that same exact issue with the waveshell vst 9.3
its asking me to locate the plugin folder but i have no clue where it is.
Did you ever end up finding a fix?
Also have this issue. Deleted the VST3 that it was stuck on, but it got stuck on other VST3s. Deleted them one by one until it ran... (which, yes, worked after a long time).
Hey, I'm new to MuseScore (Thanks for this great prog!) and new to this Forum.
I'm running MacOS 12.7.2 and had same problem launching MuseScore.
TEMPORARY solution:
rename VST3 folder in system library!
@developer: please clear this bug.
I now have to rename folder to use MuseScore and then always re-rename to original to use plugins in DAW correctly...
Best regards,
J.
Experiencing this same problem now 07/08/24
Musescore 4.3.2 on Macbook Pro running Venture 13.5.1
Crashes while scanning audio plug ins and won't open any scores, I'm hesistant to try above due to DAW usage has there been any update to this bug fix?
In reply to Experiencing this same… by rossleightonw
There is a command line switch to fix this.
mscore --register-failed-audio-plugin path_to_the_bad_vst
(Linux command) - or equivalent on Windows and Mac
Location of vst3 on Mac: https://helpcenter.steinberg.de/hc/en-us/articles/115000171310-VST-plug…