Yes, thats what i meant. Like most (maybe even all) other hosts that record scanned plugins into a file or the registry it merely does a simple compare on startup to see whether anything has changed, i.e. whether all plugins that are recorded in the list are still present in the VSTPlugins dir and/or whether anything new has been added to it. (In which case a full scan will be performed on the newly discovered plugin(s) only. The rest is only checked for presence.)BONES wrote: Orion doesn't scan plugins unless you tell it to, although it does seem to pick up new ones that have been added, so maybe it does it after it starts or it compares the folder(s) to a list it has previously compiled or something.
And it is this comparison-operation that is somehow being cached. Without having done any further checking as to where exactly, my guess would be that we are either talking about the HDDs own cache or perhaps the HDD driver because the caching is volatile, i.e. it eventually gets eliminated when other apps access a lot of files.
(This is also why every host that scans on startup will benefit from another hosts initial scan after OS boot/reboot, because if Host X has already performed the operation, and Host Y then performs the exact same operation on the exact same set of files, the operation will be completed virtually instantaneous because the data will be drawn from the cache rather than being re-queried from scratch.)
Im inclined to believe that.BONES wrote:Whatever it is, it starts about a hundred times faster than Cubase.
Cubase may be a lot of things but lightweight isnt one of them.
