i'd say your DVD drive is loosing track after a while ... so an option would be to copy the files from the DVD to your harddisk ... but allow some time between the DVDs and/or files ... otherwise it will only appear the files are copied ok (no CRC error message will appear)

then run the install from the location on the harddisk (to which you have copied the files) ... possibly again the installer reports *couldn't read - file corrupt* ... look into the installer window at which .cab-file the installer stopped ... copy again this .cab-file from the DVD to the harddisk (the finder will ask you *overwrite yes/no* and of course you like to overwrite ... restart the installation then.

please consider most DVDs are double layer and are holding a huge amount of data. if your DVD shows significant scratches (what of course could happen, but is not very probable) the DVD itself might be the problem - otherwise it is your drive or RAM.

unfortunately this rather ocurres with large files/installs and you won't notice it probly when reading some CD or less data.
christian

After copying the install discs to the hard drive, I tried an install from there.

It also didn't work.

Additionally, the corrupt file(s) is never the same. I have had the install fail at different points, sometimes within the first disc, sometimes the second, the third, or the fourth. So:

- We have already ruled out any problems with the DVD drive, right?

- If it were due to a particular file, wouldn't it always fail at the same file???

This is my fourth day of attempting to install VI S.E.

@Another User said:

After copying the install discs to the hard drive, I tried an install from there. It also didn't work.

What happens? Do you get the same an error message as before?

yes, same message

@interoctave said:

[...]

Additionally, the corrupt file(s) is never the same. I have had the install fail at different points, sometimes within the first disc, sometimes the second, the third, or the fourth. So:

[...]

Failures at different points of installation can be also an indication for I/O failures on one of your memory sticks....

Maya

Hi Bob. This must be very frustrating for you, but I'm sure the VSL team will help you find the solution. Failed installations of this type aren't normally an issue with VSL products.

Just to be clear, you've copied the contents of the four SE DVD's (which are free of scratches and marks) to your Seagate external drive, right? There should be 24 set-up cab files plus the 'package.info' file from DVD #1.

You've run VSL's Library Installer and pointed it at the package.info file on the Seagate drive, but the installation fails at a different point every time. What drive are you trying to install the samples on, and how big is it?

Once you've posted a reply I'll leave it to the VSL folks to fix your problem, but I'll chime in if I read anything that rings any bells. [I]

P.S. As Sherlock Holmes almost said, "when you have eliminated the impossible, whatever remains, however improbable, must be the truth - unless you're trying to fix a computer problem, in which case forget it." (Just joking :lol[:)]

Day 5, 6:30 a.m. Two more failed install processes, making the total of attempts: 6

Responses to your questions:

Just to be clear, you've copied the contents of the four SE DVD's (which are free of scratches and marks) to your Seagate external drive, right?

Yes.

There should be 24 set-up cab files plus the 'package.info' file from DVD #1.

Yes, 24 set-up cab files plus the package.info file

You've run VSL's Library Installer and pointed it at the package.info file on the Seagate drive, but the installation fails at a different point every time. What drive are you trying to install the samples on, and how big is it?

- The installer is the latest version, installed on the Mac's internal drive.
- The package.info file has been copied from DVD and is now located on an external Seagate drive
- The samples are being loaded onto another Seagate external drive, with a total capacity of 300Gb and plenty of room for the files

I have installed many, many programs on this drive, including East-West's Symphonic Orchestra, Symphonic Choirs, Stormdrum, Garritan's Orchestra, Cello, SAM Horns, and more. This VI installation has become a nightmare.

After five days of trying to install VI SE, I finally got it to work. I had to transfer all of the DVD files to a hard drive first, then it took three more attempts before it worked.

HOWEVER, now there are lots of clicks and pops. There is plenty of memory available, so I don't understand what is going on here. I would expect the files to sound very clean. I did notice other forum threads mentioning the same issue. Any clue to why this is happening?

good to hear you could copy the files withour errors finally ... now reading back you mention a G4 1,4 GHz with two external drives.
you don't mention if they are connected via firewire and what your audio interface is.
in case it is also firewire i'm almost sure this could be the reason. does this also appear if output is set to the built in aidio?
christian

> you mention a G4 1,4 GHz with two external drives.

It's a dual processor G4

They are connected via Firewire...what's wrong with Firewire???

And why would I set the output to built-in audio? It's set to the Presonus interface.

Maybe it all happened because of what I had for lunch last Wednesday. [:)]

And what about those clicks and pops???

no, this happens because of what i had lunch last wednesday ...

so i will repeat my question: is your audio interface connected via firewire?
(sorry, but i didn't read any mentioned model or presonus at all before)

if yes: is it connected through the same firewire controller as your harddisks?
(and i mean controller here, not a posibbly additional connector)

if yes: please doublecheck if the clicks and pops appear also if audio is set to internal.
if they dissapear then it is clear the drivers for the presonus don't allow sample streaming over the same bus.

christian

ps: i can understand if you are enervated after your installation procedure, but the first thing i recommended was a new or alternate DVD drive ...

so i will repeat my question: is your audio interface connected via firewire?
(sorry, but i didn't read any mentioned model or presonus at all before)

I said in my previous post that it is connected via Firewire. So, again, it is connected via firewire...and it is a Presonus FirePod.

if yes: is it connected through the same firewire controller as your harddisks?
(and i mean controller here, not a posibbly additional connector)

They are hooked up through the same connector, if that's what you mean.

if yes: please doublecheck if the clicks and pops appear also if audio is set to internal.
if they dissapear then it is clear the drivers for the presonus don't allow sample streaming over the same bus.

I am streaming several East-West libraries, N.I. lilbraries, and more, over the same bus. It's not the bus. It's not Firewire.

ps: i can understand if you are enervated after your installation procedure, but the first thing i recommended was a new or alternate DVD drive ...

I DID use an alternate DVD drive...I have two of them. The second DVD drive did not help. Then I transferred all files to a hard drive. That did not work either, until finally several tries later.

Bob, glad to hear you finally got SE installed. Obviously it shouldn't have been so tortuous. On the clicks and pops front, VSL have repeatedly warned VI users against connecting an audio interface and sample-streaming drives to the same Firewire bus.

@Another User said:

I am streaming several East-West libraries, N.I. libraries, and more, over the same bus.

VI matrices use an exceptionally high number of samples, it could be a case of the straw which broke the camel's back. I'd suggest you try routing the VI to internal audio as cm suggested and see whether the pops and clicks persist. it might also be worth experimenting with increasing your sound card's latency setting.

Okay, I will go ahead and test the firewire bus and latency settings until I can get better results. Odd, though, that the clicks (mostly) go away after awhile.

Thanks to everyone on the VI Forum and also on the support team for their help with this.

VSL isn't compatible with Firewire properly. A client of mine had trouble with a Dual G5 with 6GB RAM. The issue was that there was a Firewire audio interface (we tried MOTU 828 II, m-Audio ProFire). Every other streaming plugin (BFD, EastWest, EXS24, Kontakt, StormDrums etc..) worked perfectly fine [even multiple simultaneously] but not VSL. The solution was to buy a USB2 hard drive for the VSL sounds. We couldn't even play ONE note polyphony without clicks and pops otherwise!

The folks at VSL really need to step up their sofware development (GUI, installing, streaming, authorizaton etc...). It's quite unfinished and unelegant compared to the professionalism of their sampling and recording department.

Interesting.....because since this originally happened, I have not been able to get ONE instance of VI SE to run without clicks n' pops either. Not one, no matter what aspect of the buss or the buffer or anything else is changed.

I would like to see someone from VI to respond to this. Is there an actual problem with using firewire while there is none with USB???

It's been two weeks now since this odyssey began and I'm still hoping someone on the VSL forum will reply to this issue. I have NOT been able to get ONE instrument to play without clicks and pops. I've done everything under the sun, isolating the drive to a single firewire bus, etc. All other libraries that I own -- big ones -- work correctly and don't produce noises.

The reply above suggests that this will only work correctly on USB 2.0. I would like to know if that's the case.

Hi Bob. While you await response from VSL, did you try increasing the latency setting in your 'audio hardware' settings? The VI works fine with Firewire on my PC, but because of the large sample count I've had to increase the sound card latency.

Yes, I not only did that, but every possible remedy under the sun, most of which you can find all over this forum. However, last night I finally dismantled by current setup to allow for a USB connection. Although completely counter-intuitive, that's what worked! Why? I have no idea. But since I'm not the only one who has ever encountered this situation, I'm surprised I have seen this recommendation until now, especially from VSL. At least I can finally start using the product now.

f-erenc, I run VSL with FW interfaces and PCI together all the time. There must be something else wrong.

But you also have to remember that VSL has 50 billion samples loaded, so it's going to be harder on a machine than anything else.