194,325 users have contributed to 42,916 threads and 257,955 posts.
In the past 24 hours, we have 2 new thread(s), 14 new post(s) and 83 new user(s).
Hey there.
It is all running on a Gigabit network so I don't know what's to do. Is this the general consensus at the moment, that this configuration will not work very well (yet)? Or are there users running a similar setup without those problems? For now at least, I will have to work around using the VEP slave since I need a pretty solid setup for working and I can't rely on this to function.
I am running the host on a Mac Pro with 9GB RAM, Leopard 10.5.8, Logic 8.0.2.
I tried reducing the number of VEP instances to 2-3 - and changed the other ones to locally running Kontakt in Logic, this seems to have bettered the situation, at least I haven't had a crash in 30 minutes now...:)
The buffer setting in the VEP instances... I have tried both "none" and "2", doesn't seem to make any difference. What about multicore/threads settings in Kontakt/VEP server? How should they be set? I have 2xdual core CPU's. Should I set it to "4 threads" in the VEP server? And "no multicore" in Kontakt or...? Right now VEP is set to "4 threads" and Kontakt to "multiprocessor off".
Not gonna post the complete crashlog here, just the top of it including my config, maybe it can give you some clues (funnily enough, in this crash it can't tell that VEP is in thread 0 - I have an old one that had VEP in thread 0):
(LOG SENT OFF IN MAIL INSTEAD)
What typically happens is that Logic "freezes" for a second, as if it can't keep up, then VEP server crashes and Logic comes up with a "system overload" message. This doesn't even seem to be related to anything being played in the VEP instances or not - and it is not related to having the slave PC running either, I can now conclude since I shut that one down completely and disconnected the instances but I still get very frequent crashes.
Simon,
I'm having similar issues with VE Pro and Logic...
After pressing play sometimes, Logic will "hang" for a second or two, and then VE Pro will crash. Please let me know if you find the culprit.
For what it's worth, I just started using Audio Ease Altiverb in VE Pro instead of in Logic, as that plug-in takes a lot of RAM. IT could possibly be a culprit. Are you using Altiverb v6 in VE Pro as well?
UPDATE:
I am now having very frequent crashes with VE Pro Server and Logic 9.1.1.
This has started happening ever since I started using 3rd party FX plug-ins in VE Pro.
I am going to bring this issue to VSL support via email.
I am using just one instance of Altiverb, which none of the VEP instances are even routed to, so I really doubt that's it, but I'll give it a shot.
I misread your first post regarding Altiverb. I thought you meant I should use it in VEP instead of Logic, but you actually suggested Altiverb could be the culprit - in VEP.
And actually just now, I removed the two instances of Altiverb I had in an instance of VEP, then tried stressing Logic and see if I could make VEP crash. Granted, I only tried for 10 minutes, but it didn't crash, even though I managed to make one of those "hiccups" in Logic where it froze for a couple of seconds.
Then I added Altiverb, and almost immediately after I got this:
Process: Vienna Ensemble Pro [181]
Path: /Applications/Vienna Ensemble Pro/Vienna Ensemble Pro Server.app/Contents/MacOS/Vienna Ensemble Pro
Identifier: com.vsl.viennaensemblepro
Version: 4.0.5436 (4.0.5436)
Code Type: X86 (Native)
Parent Process: launchd [91]
Interval Since Last Report: 85241 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 1351 sec
Per-App Crashes Since Last Report: 1
Date/Time: 2010-05-05 15:34:36.314 +0200
OS Version: Mac OS X 10.5.8 (9L30)
Report Version: 6
Anonymous UUID: DAB932A3-C65A-4D9D-8083-AC1948F527AD
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 ??? 0000000000 0 + 0
1 com.audioease.Altiverb5.AU 0x18e711dc Planet::HandleDrawBefore(AEDrawContext*, AERect*) + 204
2 com.audioease.Altiverb5.AU 0x18e711b9 Planet::HandleDrawBefore(AEDrawContext*, AERect*) + 169
3 com.audioease.Altiverb5.AU 0x18e7194b Planet::RedrawSelf(AEDrawContext*) + 283
4 com.audioease.Altiverb5.AU 0x18e402bf MissionControl::Redraw(AEDrawContext*) + 383
5 com.audioease.Altiverb5.AU 0x18e41270 MissionControl::ReceiveIdle() + 96
6 com.audioease.Altiverb5.AU 0x18ea9e4c MissionControlRefClass::HandleIdle() + 188
7 com.apple.CoreFoundation 0x909148f5 CFRunLoopRunSpecific + 4469
8 com.apple.CoreFoundation 0x90914aa8 CFRunLoopRunInMode + 88
9 com.apple.HIToolbox 0x94fe22ac RunCurrentEventLoopInMode + 283
10 com.apple.HIToolbox 0x94fe20c5 ReceiveNextEventCommon + 374
11 com.apple.HIToolbox 0x94fe1f39 BlockUntilNextEventMatchingListInMode + 106
12 com.apple.AppKit 0x95e176d5 _DPSNextEvent + 657
13 com.apple.AppKit 0x95e16f88 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
14 com.apple.AppKit 0x95e0ff9f -[NSApplication run] + 795
15 QtGui 0x00f888f9 non-virtual thunk to QDesktopWidget::~QDesktopWidget() + 11385
16 QtCore 0x01c97001 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 65
17 QtCore 0x01c9722d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 189
18 QtCore 0x01c9b2be QCoreApplication::exec() + 174
19 com.vsl.viennaensemblepro 0x003d07da main + 12506
20 com.vsl.viennaensemblepro 0x0000a4c6 start + 54
... so maybe Altiverb IS the culprit. That would definitely be something I could work around for the time being (if I can figure out how to send multiple audio outs of a VEP instance, back into Logic - that IS possible, right?), just using Altiverb in Logic instead.
