Questions & Answers

Add continuous rescanning of VST directories

–2 votes
483 views
asked Jul 4, 2017 in Studio One Feature Requests by amg56 (1,040 points)
This is a request to improve Studio One by rescanning VST directories continuously. When the application is started up, it spawns a separate nonblocking thread that watches the VST folders.  If a plugin is added or updated, that thread scans the plug and includes it in the browser list in Studio One.  If a plugin is removed, it disappears from the browser.  

The capability would completely remove the need to restart the application to update the plugin scan, or reset the "Scan at startup" user option. It would replicate the implementation of this functionality on a different DAW which currently has by far the best implementation in this area.  It's particularly helpful for users who need to reorganize large plugin libraries, or who need to test several new ones.  

The watch process has negligible CPU overhead.  It's a feature that is commonly found in some other categories of applications like code development environments.  The separate nonblocking thread means that Studio One's audio engine is not affected if a plugin conks out while scanning.  If there is a failure, the scanning thread is recreated and it resumes where it left off, all of it in the background while the user keeps working.

Alternatively, if the proposed implementation takes too much effort, it would be helpful to allow the user to trigger manually a one-time rescan of the plugin directories, without having to set the "Scan at startup" option or restart, to save time.

1 Answer

0 votes
answered Jul 10, 2017 by AlexTinsley (925,230 points)
 
Best answer

Thank you for the feature request. 

If anyone else agrees or disagrees, please VOTE!

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. You can change your vote later if you choose.

(Here's some helpful info on how to use the voting system)

Please vote the original question / feature request. 

Please DO NOT Vote on THIS response!

...