@impeteimpete wrote: Wed Jan 05, 2022 4:42 pmHi!mcbpete wrote: Wed Jan 05, 2022 4:40 pm Hi Impete - Is there a way of getting Wotja to not autoscan my VSTi3s on launch? It seems to hit issues just after it hits waves plugins, though I only really intend to use it for generating midi notes so am happy for it to not use any of my vsts...
Yes, this is changed in the next build, which I'm just finalising!
IMPROVED: Host Plug-in scanning:
Documents screen: rather than automatically starting a plug-in scan:
if you've not yet done a plug-in scan, you're prompted to do so
Title: "Scan for Hosted Plug-ins?"
Message: "You have not yet scanned for Hosted Plug-ins. Would you like to do this now?\n\nYou can scan at any time, by going to the Plug-ins screen, and press the top-left button to re-scan\n\nIf the plug-in scan closes Wotja, simply re-start Wotja; any failed plug-ins are listed in the Action menu on the Plug-ins screen."
Buttons: "Start Scan Now", "Ask Me Again Later", "Don't ask me again”
Plug-ins screen (tab): when top-left button pressed, we now display an alert before kicking-off the scan
Title: "Scan for Hosted Plug-ins?"
Message: "If the plug-in scan closes Wotja, simply re-start Wotja; any failed plug-ins are listed in the Action menu on this screen.";
Buttons: "Start Scan Now", “Cancel"
Plug-ins screen (tab): if you have failed plug-ins, you see two menu items at top of menu:
"Show Failed Plug-ins: 1 failed" (or whatever the number is)
shows alert "The following plug-ins have failed while scanning:"
"Reset Failed Plug-ins, and Re-scan"
... these aren't show if there are no failed plug-ins
Verified on Windows with my home-made VST3 failing plug-in![]()
This updated scanning sounds great! I was going to suggest at least a scan log to see which plugin the scan stopped on. But this is better! The scanner info line in the current version sometimes lags and does not always update the actual plugin being scanned in real-time.
