I'm using an switch Trendnet 1000 base T, You mean that if I use my swith connected to the second port of the main mac pro I'll be able to connect several mac to it with the same procedure ? great news !

as for the the HD I agree with you that the fastest the better but I have this drop out problem even with just one sound loaded !

Also I used to work with this setup untill few weeks ago and it was working like a charm with my 300 midi-track template :-)

I'll keep you posted if we find a slution to this issue.

Thanks for your help.

> I'm using an switch Trendnet 1000 base T, You mean that if I use my swith connected to the second port of the main mac pro I'll be able to connect several mac to it with the same procedure ? great news !

I have not try it

> as for the the HD I agree with you that the fastest the better but I have this drop out problem even with just one sound loaded !

look at what I said about pre-load buffer size in my previous post

How much did you increased your buffer size in Kontakt ?

mine is around 90 Kb on the slave and 60Kb on the master

I was speaking of VSL preload buffer size(in Directory manager)

I use Kontakt in the DAW not in VSL

Ok then I get it ;-)

I checkde that, it was on default so I increased it but it just concern the VI Pro and my issue appear aswell with Kontakt 5 inside VEPro and Omnisphere etc... so I doubt this will solve the main issue but it might help the VSL library...

Hi again,

After a short period of time of behaving better, thank to some help from Cyril, thing are again going wrong woth lots of cuts etc...

Marnix tried to help me but apparently couldn't find a solution neither replicate the problem, so my question is : someone else having this kind of issue ?

I really can't use VEPro in my set up so I can work with my large template !!! this is the reason I did buy this product...please I need a fix on this asap.

Regards.

the worse you can do is to put your libs on FW

If you want thing go better you must put your libs on SSD

Also having a FW audio with FW disk IS VERY BAD, you must check they are not on the SAME FW BUS.

I may be getting to the bottom of my problems at last. I think I had two completely separate issues, that just happened to have the same aural results. I went through all my machines, and turned off a bunch of background services - in particular Media Player Network Sharing service, and Acrobat Updater - then turned up my VEPro buffers to 3, and it seems to have dealt with all the dropouts from one machine.

I think my other machine may have some capability issues, since I have a Samsung EVO drive for both the system and my Vienna samples. This one is still causing problems, but I'm hoping the promised firmware update for the EVO drives will help.

@Pingu said:

 I have a Samsung EVO drive for both the system and my Vienna samples.

If I was you I will keep system and Vienna samples of different ssd

You can say why ?

- System files are constantly evoluating/updated and there are the swap files that could make a lot of I/O so this disk will be morcelated !

- VSL files are rarely updated, so your blocks will be continuated, allowing much more file I/O  

The ideal would be to have a separate disk or volume for the swap files, but with MAC OS X 9.x or 10.x I have not found any utility allowing to move the swap files. In MAC OS ?.? there was the "Suisse knife" but it is not supported anymore

The cost is small If you add another 64 GB or 128 GB for the system 

Do you SATA II or SATA III interfaces ?

@Cyril said:

If I was you I will keep system and Vienna samples of different ssd

Sorry, I wasn't clear. They are on separate drives, with SATA III interfaces. But it's just become clear that EVO840 drives have some issues where older files have massively longer retrieval times than new files. So samples that have been stored a while may not stream very well. There is a firmware update coming, which should fix it, and hopefully fix my glitching issues.