Following our talks on IRC #lad, I've been investigating a bit more about why it takes ~12 minutes on my computer to make a VST3 scan. Note that I have 2 VST3 plugins: Surge and sfizz in /usr/lib/vst3/, and 226 VST2 plugins in /usr/lib/vst.Here my findings when launching a VST3 scan:
In .config/rncbc.org/Qtractor.conf:
if Vst3Paths=/usr/lib/vst3 and VstPaths=@Invalid(), then my 2 VST3 are found super quickly (~1 second)
if Vst3Paths=/usr/lib/vst3 and VstPaths=/usr/lib/vst, then it takes ~12 minutes to scan and it doesn't find my 2 VST3 plugins
Now, look at this weirdy half-baked hybrid one:
if Vst3Paths=@Invalid() and VstPaths=/usr/lib/vst, /usr/lib/vst3 then it takes ~12 minutes to scan and it finds my 2 VST3 plugins
All of that with a build from master 03aaf92.
I hope you will make sense of that.
Hi Rui.
Following our talks on IRC #lad, I've been investigating a bit more about why it takes ~12 minutes on my computer to make a VST3 scan. Note that I have 2 VST3 plugins: Surge and sfizz in
/usr/lib/vst3/
, and 226 VST2 plugins in/usr/lib/vst.
Here my findings when launching a VST3 scan:In
.config/rncbc.org/Qtractor.conf
:Vst3Paths=/usr/lib/vst3
andVstPaths=@Invalid()
, then my 2 VST3 are found super quickly (~1 second)Vst3Paths=/usr/lib/vst3
andVstPaths=/usr/lib/vst
, then it takes ~12 minutes to scan and it doesn't find my 2 VST3 pluginsNow, look at this weirdy half-baked hybrid one:
Vst3Paths=@Invalid()
andVstPaths=/usr/lib/vst, /usr/lib/vst3
then it takes ~12 minutes to scan and it finds my 2 VST3 pluginsAll of that with a build from master 03aaf92. I hope you will make sense of that.