I'm open to any suggestions. What disk utilities do you recommend?
-
@petethomas said:
I wait for a long time for it to open but nothing.
If I do force quit I see "not responding"
Yes it's the latest version.
Peter, the "not responding" is... ehm... ehm... normal (everytime you launch VI, 'till it gets ready you'll see that... "situation/state")... maybe Paul or cm can explain this better then me! [:O]ops:
How long, did you wait, before "force quitting"...?
Have you Repared Disk Permissions (with Disk Utility... it's in the folder Applications/Utility)...?
A very good Utilitiy is Disk Warrior from Alsoft...
-
I want to second Rino's recommendation of Alsoft's DiskWarrior. In my case, on quite a number of occasions, running DiskWarrior solved For exampleotherwise inexplicable problems that Apple's Disk Utility did not see and could not be corrected by "repairing persmissions."
On one occasion Diskwarrior saved a disk that evey other disk utility reported beyond repair. Rebuilding the directory of this disk took over 12 hours (normally DiskWarrior takes about 15 minutes to rebuild the directory of a 250GB disk), but saved all the data on that disk. One more example: recently, I installed a new version of Altiverb (v.6) but Logic did not recognize its presence. No amount of trashing preferences, repairing permissions or running Apple's Disk Utility changed this behavior. However, rebuilding the directory of the startup disk with DiskWarrior resulted in an immediate cure. Diskwarrior, unfortunately, does not always give a full accounting of what it fixed - - in this case its report stated that it had found problems with custom icon flags affecting four fonts associated with Finale and made no mention of Logic or Altiverb. Nonetheless it fixed something that made it possible for Logic to recognize Altiverb. DiskWarrior is now available in a Universal Binary version that works on Intel Macs as well as PPCs.
-
How long, did you wait, before "force quitting"...?
5 minutes or more
I've also verified and repaired permissions
-
-
How long, did you wait, before "force quitting"...?
5 minutes or more
I've also verified and repaired permissions
Pete,
Do try waiting a few more minutes. The first incarnation of VI took a very long time to launch and though more recent software versions have improved this it can still take a long time to start on the first time you launch.(do check you've downloaded the latest VI software version) The launch time is dependent on the size of your VI Library (how many collections are present in the library manager) and the speed of your system.
As a guide I find on a G5 2.5 Dual with 6.5 MB of RAM and fast SATA raid drives with the Symphonic Cube and 3 other collections that it takes not much short of 3 minutes to launch from cold. When the cbe was first released it took well over 7 minutes.
Julian
-
You're right, it does open eventually, over 5 minutes.
Meanwhile the not responding message makes you think its crashed.
-
OK... my english is AWFUL!!! ...but... I told you so...
Peter, the "not responding" is... ehm... ehm... normal (everytime you launch VI, 'till it gets ready you'll see that... "situation/state")... maybe Paul or cm can explain this better then me!
[[[:D]]] [[[:D]]] [[[:D]]]
R
-
Pete,
Now since I have Syncrosoft 5.0.8.1 the Vienna Instrument opens in under two minutes with the full Symphonic Cube, 3 other VSL VI's, and two licenses from other manufacturers. I have a Dual 2 Gig G5, 6.5 GB RAM, however my VSL hard drive is an ultra-SCSI RAID w/ 10K drives.
But....before I installed 5.0.8.1 it took over seven minutes to open. And this was a common figure with VSL VI owners for quite some time. So I think the main thing is the Syncrosoft version, not so much the drives. A lot of us leave our systems on for days at a time.
-
Peter, the "not responding" is... ehm... ehm... normal (everytime you launch VI, 'till it gets ready you'll see that... "situation/state")... maybe Paul or cm can explain this better then me!
[[[:D]]] [[[:D]]] [[[:D]]]
R
Yes you did tell me so, but I didn't realise you meant as long as 5 minutes!
l never expected an app to take over 5 minutes, it does that the first time I open VI after booting up my computer. If the manual had warned me of that I wouldn't have thought it was a typical "not responding"
-
The longest any of my other apps takes to open - Logic, Final cut, Photoshop, Dreamwevaer, etc, etc is 45 seconds so I was REALLY surprised when I encountered the 7 minute plus boot time.
Though it is now under 3 minutes for me it still is a significant time.
I must admit it has never been explained why (exactly) an empty plug-in should take 300-400% longer tp open than some of the most complicated apps on the planet! (including those protected by copy protection)
Julian
-
Depending on the content assigned in the Directory Manager the initial startup time should take up to 2 minutes (absolute maximum: 3 minutes).
This is where all the file locations you assigned in the Directory Manager are scanned, in order to give you the fastest possible loading time [:)]
Now if you are loading up a project on a freshly booted computer, and this project is filled up with 45.000 samples, the loading time will be the "initial startup time" (scanning) PLUS the loading of 45.000 samples.
Hope that explains what´s happening in the background....
Best,
Paul
Paul Kopf Product Manager VSL -
@Paul said:
Depending on the content assigned in the Directory Manager the initial startup time should take up to 2 minutes (absolute maximum: 3 minutes).
This is where all the file locations you assigned in the Directory Manager are scanned, in order to give you the fastest possible loading time [:)]
Now if you are loading up a project on a freshly booted computer, and this project is filled up with 45.000 samples, the loading time will be the "initial startup time" (scanning) PLUS the loading of 45.000 samples.
Hope that explains what´s happening in the background....
Best,
Paul
Thanks Paul,
and yes your estimates correspond with my experiences - between 2 and 3 minutes to load Vienna Instruments without any samples.
Julian
