Tj Shredder wrote:The scanning of plugins seems to be a never ending annoyance in any program which does it. The same is with Resolve. I do have a lot of audio plugins I also need for other hosts. DaVinci Resolve will start scanning each time I start the program. Of course I can kill the vstscan process if it stalls, but that way it never reaches the plugins I need, unless I remove the offending plugins from my plugins folder. But then I would have to put them back again as other host do not have a problem with these plugins.
Also it seems it does not see plugins if they are within a folder...
I can't just drop a plugin into a fx slot either...
There is no technical need to scan all plugins. It could simply build the database on demand. Whenever I load a plugin the first time, scan it, if it passes add it to the database, if not show an error message...
This is not new to the beta, the same problem I had before, just hoped the new version had fixed it...
I have to bump this. The problem remains in version 17. There is no timeout in the process, it will start over from the beginning each time I restart DaVinci, it fails at the same VST plugin to pass on instead having it labeled as failed. A plugin I don't need in DaVinci, but in other hosts I want to use it and it works there without problems. As soon I would need a plugin which start with a higher letter than F it would be a complete show stopper...