Thanks Herb for your quick answer!!

Its great to experience that the mastermind of a company himself offers help to the users!!!
As a user it's great to feel that the developers also invest their enthusiasm in a product. It's surely one of the reasons (in addition to know-how, money and others) why the VIs became so earthshaking!!

As an AppleLogic user i know why i'm saying that... [[;)]]


Greets:
HTF

please note the *scan tool* should be labeled *directory manager* in your VSL section of the start menu
christian

sorry for the wrong wording [:O]ops:

best
Herb

@herb said:

I think the startup time is primary not depending on the amount of used samples, initializing the very first plugin takes the time, because it scans the whole database.


best
Herb

Hi Herb,

My VI's are due any day now .. can you tell me, on a Mac/Logic platform does the primary scan happen when a VI is inserted as an AU in Logic for the first time or when Logic is first launched without any plug-ins inserted. Also if you have a song open using VI's which is closed to open another song (also using VI's) is the primary scan invoked again.

I ask this as a lot of projects I am involved with require frequent switching between songs and load time is an important issue!

Thanks

Julian

I think it's scanned if you open the first Plug in, but I'm not 100% sure. Our OSX tech guys should jump here for clarifying.

best
Herb

@julian said:

on a Mac/Logic platform does the primary scan happen when a VI is inserted as an AU in Logic for the first time or when Logic is first launched without any plug-ins inserted. Also if you have a song open using VI's which is closed to open another song (also using VI's) is the primary scan invoked again.

I ask this as a lot of projects I am involved with require frequent switching between songs and load time is an important issue!

Hi Julian,
as far as i experience, VIs take the whole time to scan everytime you close and open a song; even if you reopen the same one or one with the same instruments.
Its about 4 minutes on my system (see above).


@Christian:

Which startup menu do you exactly mean?



PS: i have to mention that actually i have the whole available content to scan.
That means all the 5 libraries, and all the folders of them.
As there are 22 folders, i guess that the time you win by deactivating the unused ones, can be pretty much, but i didn't try that out so far.

Greets:
HTF

PS:
there's no extra loading time if you open a song that contain no VIs.
That means the scan takes only place if there are used VIs in that specific song.

Greets:
HTF

Hi Julian,
as far as i experience, VIs take the whole time to scan everytime you close and open a song; even if you reopen the same one or one with the same instruments.
Its about 4 minutes on my system (see above).


Greets:
HTF[/quote]

Thanks HTP,

I have the same computer as you with a fast Raid set up and will ultimately be using the whole cube. Please please please don't tell me this could give a potential minimum load time of 8 minutes per song (well next 5 VI releases will probably double the size)

The last time I had a client visit we went through his project which by necessity was on 10 songs. Does this mean 80 minutes of his valuable time would have been watching VI's scan!

As I'm sure any one in the pro business would agree... this would be an impossible scenario.

Julian

hi,

the primary scan is done after starting host after a cold start ie booting the machine.

tasks done are: license check and patch/lib resolution - this takes the most time and thus we have separated it from AU PlugIn. This is also dependent from the actual content being pointed to by Directory Manager (aka scanTool)

when opening a plugin several things happen depending on "load state" of VI
1) empty VI: just initializing GUI (this is _constant_ time and takes a bit longer than on PC, but version 1.1 should adress (and speed up) this issue.
2) loaded VI: loading of cache (variable time) and GUI loading

Cache loading will be significantly improved with an utility you can expect to d/l in approx 2 weeks.

Other suggestions as seen in this forum like splitting the loaded lib further into parts has to be pondered and no comment (or promises) can be made at this time.

Thanks

christian teuscher
development

Christian,

Thanks for the response.

It's good to hear that load time features prominently in VSL's development plans.

Yes if you're only working on a string quartet for example, seperating the library would make sense but for the majority of my work it is good to have the complete palette of VSL sounds at my fingertips so a total scan scenario is what I will be working with as regards song switching and loading.

Julian