because it's been instructed to (either on purpose or because of a bug). that's the only reason any program does anything.Yet the question remains, WHY does T scan the plugs at startup?
and so it shall be... until cyberdyne systems gets their way.
because it's been instructed to (either on purpose or because of a bug). that's the only reason any program does anything.Yet the question remains, WHY does T scan the plugs at startup?
If Tracktion maintained a list of scanned plugs it could possibly bypass previously scanned ones and only scan for new ones (Like it says it will do).AndrewSimon wrote:What would be really nice is to be able to remove plugs one by one from the "disabled list" (for a second chance) without the need to rescan everything from scratch.
i believe the difference is that something like Tracktion does a 'scan and verify' while FL only does that if you select that option.PT wrote:i only used the FL demo for a while, but it scans my vst folder in about 2 seconds if I have added something new. Tracktion takes 5 minutes.
What's the downside to what FL does? If it is just an occassional freeze or crash I think it is a fair trade-off. I dread adding new things to my vst folder.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026