So I am not alone in this issue then....
I will STOP buying VSL [currently have full solo strings, chamber and Appassionata Strings] and wait until the more stable update is release
VSL is a great collection of libray and great sound but the safety and time for my work are more important,
So far I have to rebounce 12 songs, took me all day because of the real time, each song only have 2 vsl track, 1 custom matrice for 2- patches
Amazingly, no one at Vsl team have not say any thing yet.

Sonny:

I'm sure someone from the VSL team will respond regarding this. It's the weekend right now, so I'd guess they'll respond by the beginning of the week.

dsstudio,
I'm going to play devil's advocate here, and suggest shorter bounces. Even with my entirely modest travel library whilst studying here in Moscow, there are occasions when Logic doesn't bounce correctly, with wrong articulations. That's to do with (for me) CPU and RAM resource and the vagaries of MIDI, and the speed or lack of it within my system. (I'm still waiting for someone to produce an ethernet midi controller keyboard, lol)
It's been a working practise of mine since the days of Cbase 3.5 (never again, hehe) to write and bounce, or record to audio, in short chunks. I've discovered this gives one more control over the entire process, and actually frees up an opportunity to manipulate the 'feel' of an orchestral work to a greater and finer degree. (e.g., Rubato, with any modest time and pitch software, either built in or standalone.)
I'm unconvinced that VSL's player is responsible for incorrect bouncing, and one only has to search other fora, and sources of Logic query to understand that Logic isn't perfect at freezing and bouncing by some degree. This program does have issues.

Everyone has their own workflow and, dsstudio, this method may be unsuitable for you. But if you were to examine objectively the process, and determine the point at which you find an issue, you may discover the fault lies within the DAW, or harware capability.

I wish you success, whatever you may discover,

Alex.

Thanks hermitage59 for a very calmly advise,
I don't know if my Set up and Logic having a problem or not but 1 thing for sure is vsl is the only software that cause me bouncing trouble, while almost other 20+ does not.
Software that I threw away wihout think twice so far is BFD, E-Labs's Obsession and Foundation, some NI powered instruments etc... if they don't work for me, I refuse to work with them, to me time is money and these software just not worth my time.
VSL next? I don't think so because it cost me serious money and I also really love the sound and features of vsl, it's a wonderful tool, so that's why I post the problem here hoping that VSL team can help me.
Someone mentioned a stand-alone, will it work thru rewire and can I record more than 2 Vsl tracks at once?
Thanks
Sonny

Sonny,
You are most welcome and i apologise if my comments seem a little simplistic, but i have discovered in life it's often the simplest things we take for granted that prove to be the last place we look!

Another question is,
do you load VSl first or last?
I'm thinking that if you loaded VSL first then added other plugs until the problem occurs, it may be the case that there is a hidden conflict with only one source that you may have to deal with, and not a 'big overall problem' to tackle. What i mean by this is unloading the other plugs, bounce your VSL, and if that works continually without issues, then load your other plugs and bounce until the problem reoccurs.

Perhaps a methodical process of elimination from a different direction would yield a result, and allow you to wallow more enthusiastically in the luxurious splendour of your VSL investment!

Regards,

Alex.

Dear Sonny,

the problem you mention here is presently being investigated. Unfortunately we still don´t know what causes the errors during bouncing and freezing in Logic and whether it is initiated by Logic or Vienna Instruments. Moreover the problem seems to occur more frequently on older Mac models (PPC). As soon as I have received some further information about this issue, I´ll let you know.

I am sorry that I cannot give you a more favourable reply at the moment. [8-)]

Best regards,

Maya

Maya:

Thanks for responding. Please, if you can, keep us updated regarding this problem and let us know if it is specific to Logic or if it occurs with other hosts such as DP, Cubase, etc.

Thanks again.

This is only a guess, but might help finding the root cause ...

The problem with freezing seems to be related to the speed of the harddisk containing the samples. I have got the impression that while freezng the plugin is only playing the part of the sound that is already in RAM, not "telling" the host application that it needs time to stream the data from disk. Freezing a track is much faster than realtime and with slower disks (i.e. usb) the dropout drop out problem happens more often than with faster disks (firewire 800).

... only a guess, regards,

gudgai

Welcome to the forum, gudgai.

I have a firewire 800 external hard drive, and still plenty of problems freezing. But I think that may be because my RAM is WAY overloaded.

Sorry for being imprecise, I also have big problems although using a firewire 800 external hard drive, but it gets even worse using a slower one (usb). I also have a Core 2 Duo Processor, so I don't think the problem is related to the PPC processor, as Maya hinted.

My guess is that the plugin just doesn't let the host application know that it needs more time to get the data from disk and therefore it drops the part of the sound that is not already loaded to RAM (this would also explain why it get worse the more RAM is filled).

Other plugins (like Native Instruments Akoustik Piano) don't have this problem, they freeze with no problem. So it looks to me like a bug in the VSL plugin and not in the Logic Apllication.

Best regards, gudgai.

I don't think that problems associated with freezing VI tracks or bouncing them offline have to do either with the speed of the disk or with the available RAM - - at least within limits. I say this because I have encountered exatly these problems although my sample libraries are running on a one terabyte SATA RAID 0 comprised of two very fast Seagate SATA II (3GBs) 500 GB drives connected to my G5 via a Firmtek SATA card and I have 7GB of RAM installed. In other words this appears to be a bug in the Vienna Instruments software as gudgai suggests. As a result, I bounce Vienna Instruments tracks in real time - - which is laborious, but works.