I had the same problem, but I am using Logic 9.1.1 in 64bit and VEPro 64bit, all 8 cores are being used in Logic. Ok, the first core seems to go overloaded several times, but I think that this problem will be quite solved when VI Pro is being released. They optimize their software with each update, obviously. Everything what I did was to use both DAW's in 64bit and switched on the internal FIREWALL of Snow leopard. After updating to Safari 5.0 I found out that Safari got a big speed down, so I checked the system and saw that only the firewall could solve the problem because Snow Leopard was fully opened in network backdoors after 10.6.4. I am also working with an 8-core Pro with 32 GB RAM.

Try to switch on the firewall under security settings and see that the multithread tasking works better.

Give us an update here, please.

I'm still having this prob, big time.  Mind you, I'm loading up over 5 GB of Kontakt into my VEP 64 (along with another gig on VEP 32 for Play and other stuff)... but still, it shouldn't be behaving like this.

Hello

Did you read those :

http://community.vsl.co.at/forums/p/27029/177079.aspx#177079

if that does not help you can use VE PRO SERVER (I had the same problem and that solved it)

Best

Cyril

here was my question to VSL and the answer I got, just in case it helps anybody to figure out what is going on with  Apple and their Logic pro developers. 

I must say that since then and after been a Logic user for years I am testing Cubase and Protools for a better audio engine overlan eficiency. Read carefully my question to VSL and their answer:

<----------------------------------------

@Another User said:

Hello

@Another User said:

Working in Logic pro on a big orquestral template using several VE-pros instances overlan in the same mac pro, I notice that in my 12 core new Mac pro only the last core is being used and often as the session grows Logic stops and I get the test message: "System overload. Audio engine can not process in time the data..."

@Another User said:

I tested the same orchestral example as in above situation but this time opening each track with a  VI-pro instrument directly in Logic pro (without Ve-pro) and the result is that all the cores in my mac pro are being evenly used as it should be.

@Another User said:

So now I ask myself why is this happening, and what sense does it make then to use a orch. template with many VE-pros overlan in a 12 core mac pro if only one core is being used waisting this way the power of my 12 core mac?

@Another User said:

I have tried all kind of solutions to arrive to the conclusion that maybe using VEpro in a multicore system doen´t work out and maybe is better go to the one VIpro by track solution in Logic pro for a better use of the compùter power processing.

@Another User said:

Please I need some serious technical advice about this. I am working in a professional situation here in my studio and I need to run lots of Vienna and Kontakt instances to accomplish my large orchestral film projects. I have spent many hours creating a template with more than 200 tracks, including group buses etc and now I see that all of it may have been a waist of time. Is hard for me to believe that VEpro can not use all the cores of my mac pro:(

@Another User said:

------------------------

@Another User said:

Please read all my tech stuff:

@Another User said:

Logic Pro (64 bits)

@Another User said:

preferences buffer: 1024 for Playback, 256 for midi imput. 

@Another User said:

each VE-pro is a 16 track multinstrument. I use in Logic thr midi multinstrument for the midi tracks in the organize window  and aux tracks in the mixer for the audio returns from the  VE-pro server.

@Another User said:

VE-pro (64 bits) server preferences

@Another User said:

multiprocessing: 2 threads per instance (I also tryed out with 1 thread, 4 threads etc without noticing any chanches)

@Another User said:

Mac Pro 2 x 2.93 Ghz 6 core intel Xeon

@Another User said:

32 Gb RAM

@Another User said:

OSX Snow Leopard 10.6.4

@Another User said:

RME PCI HDSPe AIO audio card

@Another User said:

SATA 64 bit cache internal RAID  Drives holding the Libraries.

@Another User said:

SATA external  Drives holding the sessions and video.

@Another User said:

VEpro v. 7349

@Another User said:

VI pro v. 7349

@Another User said:

Logic pro 9.1.3

@Another User said:

Sibelius 6.2

@Another User said:

@Another User said:

best

@Another User said:

Tomás San Miguel

@Another User said:

www.musimagic.com<http://www.musimagic.com>

@Another User said:

______________________________________________________

@Another User said:

VSL´s ANSWER HERE:::::::::::::

@Another User said:

I had the same problem with an 8 core Macpro (the 8the core was going on overload, the other where around 10/15 %)

I solve it using VE PRO server

I found that excluding all 32 bit plugs (thus non 32 bit bridge), things works much better. [B]

do you have a lot of effects running in Logic ? reverbs ?

If yes you must uses busses so Logic spread the load across processors

Best

Cyril

it's  a Logic issue [+o(]

Look with activity monitor if the load is balanced ! (mine was, so it was Logic reporting core overload that did not existed)

To track your problem I will disable all FX one after one and see if this cure the problem. (suppressing the reverb should help)

Then I Will read the link given by passenger57 and apply it little by little the FX

Best

Cyril

@Cyril said:

Hello

Did you read those :

http://community.vsl.co.at/forums/p/27029/177079.aspx#177079

if that does not help you can use VE PRO SERVER (I had the same problem and that solved it)

Best

Cyril

I have the same problem. Mixing in the VIframes is possible, yes, but very inconvenient as I'd have to save each VIFrame with each project (I run VEPro decoupled for snappier response in Logic) and would have to reload them for each new project, which defeats the great preserve feature.

I submitted a feature request to Apple with a link to this thread and Martin's explanation. Those who experience this problem, please do the same: http://www.apple.com/feedback/logicpro.html

I'm in the middle of setting up a large template too and have noticed this problem.  VE pro is not playing nice.  I get distributed cores but I'll suddenly get massive stuttering and dropouts when using VE Pro but loading everything as separate VIPros in Logic yields smooth results.  I have Cubase 5 and tried that but the CPU usage was far worse.  I tried to add Vienna Suite eq to the VE Pro but that drove the CPU over the top.  Running them in Logic was much better.  Granted in all of this my machine is an older 2.66 quad Mac Pro.

Chris

Edit: I don't know if you've noticed but the load time with VI has gotten extremely quick practically negating the need for separate hosting.

@passenger57 said:

 Cyril - Could you please elaborate? Do you mean you ran VEP as a server on the same machine as Logic?

yes, 64bit

@Stibi74 said:

Hi, i have the same Problem..(8 Core / Logic 9.1.3 VE Pro latest Version on one Machine) I know that i can fix it when i mix everyhting in VE Pro and return it as one Stereo Output Back to Logic..but that would kill my whole Setup. (SSL Duende won´t work know in the 64Bit VEPro and the Euphonix MC Mix and MC Controls just can Mix a hole Stereo Input of "Strings" "Brass" etc...which make the a kind of "useless" - having all this faders) So my question: Can i fix it when i run VE Pro on a second machine (PC?), or is the moment when the Audio Input is linked to the Logic on the Mac Pro the bottle neck - and is still get this overload, even if all the Vienna stuff is NOT on the same machine? Thanks for your help! greets Stefan

If you run VE Pro on a separate PC life is much better I find.  I only have one PC so far and that runs a competitors string library, but within the VEPro host.  Logic barely notices the incoming load (granted thats just a stereo stream, but more won't bother it).  I gave up trying to host all 32 instruments in VE Pro on my older MacPro 2.66 because my machine just isn't fast enough.  Until I can build a 2nd PC to host all the Vienna stuff it will live inside Logic.  At least that way I can start freezing individual tracks as the load starts to get heavy.  The downside is if I tweak the template and need to apply it to other projects it's a long process.

Chris