Request: Blacklisting individual plug-in files.
- KVRAF
- Topic Starter
- 2033 posts since 15 Mar, 2002 from Seattle, WA - USA
Thank you for developing KSM. It's off to a great start and already a tool I'm using regularly, but a feature update I'd like to see is the ability to prevent it from scanning certain files.
Good examples are "shell" plugins like WaveShells which always tend to be in a permanent state of versioning flux or Presonus AU/VST Shell, but also older versions of plugins that will probably never see another future update and are only kept for project compatibility reasons. Even if a newer v2 version exists in the same folder they're still being permanently flagged as out-of-date. I'd love to just skip them altogether during the scanning process.
Good examples are "shell" plugins like WaveShells which always tend to be in a permanent state of versioning flux or Presonus AU/VST Shell, but also older versions of plugins that will probably never see another future update and are only kept for project compatibility reasons. Even if a newer v2 version exists in the same folder they're still being permanently flagged as out-of-date. I'd love to just skip them altogether during the scanning process.
- KVRian
- 571 posts since 19 Aug, 2020 from the top of the charts
You can hide them (right click).
If you plan on purchasing your first Universal Audio hardware, you can get a free additional plugin. Just send a PM.
- KVRAF
- Topic Starter
- 2033 posts since 15 Mar, 2002 from Seattle, WA - USA
-
- KVRist
- 48 posts since 24 Jul, 2016
I guess you could move the plugins you dont want to be scanned into a separate folder and the location to your DAW startup scan (obv not to KVR).
Bit of a workaround but it would probably do the job!
Bit of a workaround but it would probably do the job!
- KVRian
- 571 posts since 19 Aug, 2020 from the top of the charts
True. That would be better.
If you plan on purchasing your first Universal Audio hardware, you can get a free additional plugin. Just send a PM.