When I launch the Vienna Instruments application for the first time it appears to scan the licences after approx 10 seconds then there appears to be nothig happenning. If you open activity monitor it shows vienna Instruments as "not responding" however if you double click on the app and select "open files and ports" you can see in the next line to bottom it is actually scanning the folders selected in directory manager. It is doing this at a rate of 1 folder every 5 seconds. Thew Symphonic Cube and Appassionata Strings have 86 folders so this is equating to the 7 minute start time a number of us are encountering.

Once this scaniing process is complete the standalone opens. I guess the same process is occuring when the VI's are opened in Logic.

My Vienna Instrument File Structure is disc/Vienna Instruments/01 Solo violin...86 Percussion which is i think the default installation of the Vienna Installer.

hope this info can help find a solution to the elongated boot times

Thanks

julian

sorry julian, how do you count 86 folders? there should be 1 folder per collection and the appass can easily go into the same folder as the orch strings I (to keep some order)
christian

err: i should have a look into my own structure before posting .... of course there are subfolders for each instrument ... could you please try to consolidate the dat-files (maybe as example for one collection) to the root-folder (eg. VSL_chamber instead of VSL_chamber/10 striings, ect) and see if something changes?

another thought ... do you have an anti-virus application (eg. buggy norton) and this set to *scan files everytime an application tries to access them* or similar wording?
christian

Sorry -there are actually 63 folders as there are gaps in the numbering. I did not create the folders they were created by the Vienna instrument installer - I just pointed the installer at the first DVD and it did the rest for example the woodwind folders are as follows:
31 Piccolo, 32 Flute, 33 Flute II, 34 Alto flute, 35 Oboe I, 36 French Oboe, 37 English Horn I, 38 English horn II, 39 Clarinet-Eb, 40 Clarinet, 41 Bass Clarinet, 42 Bassoon, 43 Contra Bassoon, 44 FluteEnsemble, 45 OboeEnsemble, 46 ClarinetEnsemble, 47 BassoonEnsemble.

The spellings and layout were all created by the installer.

Julian

@cm said:

another thought ... do you have an anti-virus application (eg. buggy norton) and this set to *scan files everytime an application tries to access them* or similar wording?
christian

No virus stuff or any third party utilities (except disc warrior)

Julian

... same folder structure here as julian described.
built by the installer.

thomas

@cm said:

sorry julian, how do you count 86 folders? there should be 1 folder per collection and the appass can easily go into the same folder as the orch strings I (to keep some order)
christian

err: i should have a look into my own structure before posting .... of course there are subfolders for each instrument ... could you please try to consolidate the dat-files (maybe as example for one collection) to the root-folder (eg. VSL_chamber instead of VSL_chamber/10 striings, ect) and see if something changes?

Hi Christian,

I've tried this - well I actually made 4 folders (Strngs, Brass, Woodwind, Percussion)and put all the respective .dat files in at the top level, cleared the directory manager and then added just these folders and the custom data folder which hadn't benn altered. The boot time is the same. Once again in activity manager you can see the various files being scanned - it shows the penltimate .dat file for each instrument then moves onto the next instrument (in each case showing the penultimate .dat fle) this whole process takes 7 minutes.

I have done the usual re-boot and repaired privileges.

Julian

(repeat of my post in a related thread):

I want to add some lateral thinking to this long load time problem.

I find that when I first launch VI Standalone or the AU plug-in, load time is very long (5-7 mins). If I quit and re-launch, it is quicker. I believe it has something to do with vsl daemon - if this is already running in the background, "re-" launch times are faster. Also, if I launch VI Standalone first, then the AU plugin starts within 30 secs in Logic.

If I log out or shut down my G5, the whole process starts again - 7 mins to launch whatever I launch first. Is it possible that you folks at VSL do not log out or ever shut down and therefore your start times are always fast? If so, please turn off your Mac and try again with your stopwatch in hand.....

Regards - Colin

Bravo musos,

the same here.
There must be something wrong with the initial scanning process.
Please VLS-Guys: Help us.
7 Minute I wait for a good Beer (Pils=7Minutes)
But for a Professional! Software it is not accaptable!!!

Best

Oliver

Gremmy Studios

i take the pils .... ok, back to serious things ...

i've been thinking a while about this issue and discussed it with some guys *in the know* ... and came to a conclusion i've already assumed:
the reason has to be found in the preferences.
if the system (and it _is_ the system, not the Vienna Instruments) doesn't find the path to the folder immediately (*needs 5 seconds per folder*) something needs repair or re-install.

one can think of several origins:
- the system does generally not choose the right path to the preferences and is looking somewhere else first
- the path to the preferences has not been stored correctly during install of ViennaInstruments
- another application *overrules* this path and so bends the order of locations where to look for preferences

normal speed should be about 2 folders per second, actually more. if it needs more time something related to your preferences is wrong.
please think about which applications you (who are facing the long loading times) might have installed which possibly affected the preferences path - there must be a common denominator.

possible solution: uninstall and delete everything related to Vienna Instruments Software, reboot, install from scratch (using default paths), adding paths to VSL data again.
in case this dosn't change anything you might have to consider a clean install (possibly parallel on another partition) to make sure you do not drag along any flaws from somewhere

christian

Christian,

Before we all start fault finding I am a little concerned that we haven't heard from a single person outside the walls of VSL who has achieved 30 seconds to 1 minute load times with a full extended cube installed.

Has anyone at VSL followed the full retail disc instal, set up the licences as a retail customer would have to then achieved the 30 second start times?

VSL support is tops as usual and i appreciate pointers to start fault finding but where we have a situation with everyone who has responded having such long start up times it does indicate the possibility of something amiss rather than individual computer systems.

thanks

Julian

@Another User said:

Before we all start fault finding I am a little concerned that we haven't heard from a single person outside the walls of VSL who has achieved 30 seconds to 1 minute load times with a full extended cube installed.

i'm not sure how to understand this - do you say ...? no - i'm sure, you don't say ...!
christian

@Another User said:

Before we all start fault finding I am a little concerned that we haven't heard from a single person outside the walls of VSL who has achieved 30 seconds to 1 minute load times with a full extended cube installed.

i'm not sure how to understand this - do you say ...? no - i'm sure, you don't say ...!
christian

What I was asking is is there anyone outside VSL achieving boot times under 1 minute for a full collection.

In terms of fault finding i have downloaded new installers directly from Syncrosoft and VSL and installed on a virgin MacBook Pro 2.16.

Boot time is 7 minutes 20 seconds for the standalone

hope this helps.

Julian

I installed the Vienna Instruments on the Windows partition of my MacBook Pro. I then connected a Firewire 800 drive with the vienna Library on - this is a Mac partitioned drive so I used MacDrive 6 to recognise the drive.

First boot time for the standalone was 2 minutes 2 seconds with all 10 collections (extended) and App strings. Yhis compares with 7 miutes plus on the same computer in OSX.

Not sure what this indicates - except perhaps there is a OSX issue?

Julian

cm: you didn't respond to my theory - do you ever log out or reboot your Mac at VSL?

Another theory: When we all got the original Vienna Library, the EXS instruments all had info relating to paths on VSL hard drives (eg "ice cube") as opposed to our own drives. We soon discovered that we had to re-link all the files (using Project Manager in Logic or EXSManager) to configure the instruments to our own systems. In this way, load times became very fast.

Is there perhaps some similar path configured within the VI files that confuses our systems? Or does the Vienna Installer write system-specific paths for every new installation?

I can tell you that since my very first installation of Vienna Instruments, it has taken a long time for any first instance to load. The time is always faster however for subsequent starts, even if I have quit the standalone or Logic.

Could you please tell me the exact names and location of VI pref files so that I can check them.

Regards - Colin

Colin,

I second that with my experience....my load times have ALWAYS been long. I actually first installed the instruments on a slave G5 in my studio...in fact, I didn't have a single sequencer installed on that machine...I don't think I even had ProTools installed...

I wonder if all the folks at VSL are using sequencers in Windows, or at least, loading the libraries in Windows (which would explain a lot I would imagine...especially why we haven't found a fix to this issue yet)...

...and, again, like everyone else, I experience much faster loading times aftedr the initial instance of VSL on my computer before I reboot, even if I quit standalone or Logic (...and...of course, we all know that this is because the VSL Server and the VSL Daemon continue to run in the background even after quitting standalone/sequencer until I either force-quit them or restart my system)

Josh

sorry musos, i thought this would be obvious ... of course the start is faster if some related processes are already running, but this is not the point.

usually (application-)preferences reside in: Home folder – Library – Preferences, but i have no mac here to check the details because maya does the most of VI-on-mac support and my desk is somehow *outsourced* [;)]

christian

Hi Christian,

In the light of no other information what i can gather from the recent posts is as follows:

VI initial start times should be between 30"-60" with a full symphonic cube (extended edition) installed.

A lot of people posting on the forum are encountering 7 minute start times.

This could be a Mac based issue, it could be individual system based but there certainly is something amiss!

I would welcome input from VSL to help bring the start times considered normal to VSL to the systems we are using in the field.

Thanks

Julian

Yes Julian,

I agree totaly, there must be another way than installing everything again from scratch, Christian.
It makes no sense because everything else is running very smoothly...

Best

Oliver

julian, i've already contributed patiently especially to your requests and would expect my replies to be read for not having to reiterate myself continuously.
i did not receive any precise information regarding the affected systems so far, so not very much can be said where to start streamlining your system.

we have installed the VIs on a lot of systems (mostly G5s, but going down to a dual G4 450) and some of them are not really well-tended, some of them heavily used for testings, some with clean installs, some of them even production machines. some had or still have not only one but actually a series of sequencers, host software and various *crap* installed.

so to get an idea where to start searching for the reason we had at least to get any machine in our hands showing this behaviour, all theoretical options are covered.
eg. any video software or plugins we don't have couldn't have be taken into consideration of course, the only surprising result i've read so far is the probook, which looks to be a fairly fresh install (yes, we've also tested intelmacs without noticing this behaviour)

of course i can think on a category of reasons, about which i would never talk publically, too.
christian