Zebra VST + Kontakt 2 + Cubase SX = Crash

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hey Urs,

I read that your hand is temporarily out of commision but I thought I'd post anyway. I have an issue that has been very diffucult to pinpoint. I know this is gonna sound obtuse, but here it goes. I am getting Cubase SX 3.1.1 to crash (only on my DP G5, NOT my Powerbook G4) when I do the following:

(1) Load Cubase Project
(2) Load Kontakt 2.11 VST
(3) Load Zebra 2 VST (the March version - 140306 I believe)
(4) Exception Crash.

Here is the Crash Log:
Any and All help would be HUGELY appreciated... :)

Date/Time: 2006-07-03 00:17:05.947 -0500
OS Version: 10.4.6 (Build 8I127)
Report Version: 4

Command: Cubase SX 3
Path: /Applications/Cubase SX 3.app/Contents/MacOS/Cubase SX 3
Parent: WindowServer [66]

Version: 3.1.1.944 (3.1.1.944)

PID: 288
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0 com.steinberg.cubase 0x007b9f8c dyld_stub_binding_helper + 8093092
1 com.steinberg.cubase 0x007b9f4c dyld_stub_binding_helper + 8093028
2 com.steinberg.cubase 0x007b9ffc dyld_stub_binding_helper + 8093204
3 <<00000000>> 0xa0b8e200 _XHNDL_trapback_instruction + 0
4 <<00000000>> 0x02c0f020 0 + 46198816
5 com.apple.CoreFoundation 0x907eb188 CFBundleCopyResourceURL + 44
6 com.UrsFX.Zebra2.vst 0x23d8c0dc AM_VST_Editor::open(void*) + 480 (AM_VST_editor.cpp:266)
7 com.UrsFX.Zebra2.vst 0x23d289d4 AudioEffect::dispatcher(long, long, long, void*, float) + 504 (AudioEffect.cpp:139)
8 com.UrsFX.Zebra2.vst 0x23d29990 AudioEffectX::dispatcher(long, long, long, void*, float) + 1584 (audioeffectx.cpp:327)
9 com.steinberg.cubase 0x0000eef4 dyld_stub_binding_helper + 52492
10 com.steinberg.cubase 0x0061f980 dyld_stub_binding_helper + 6412184
11 com.steinberg.cubase 0x00978dd0 dyld_stub_binding_helper + 9923560
12 com.steinberg.cubase 0x0096b8a8 dyld_stub_binding_helper + 9868992
13 com.steinberg.cubase 0x00978dd0 dyld_stub_binding_helper + 9923560
14 com.steinberg.cubase 0x0097862c dyld_stub_binding_helper + 9921604
15 com.steinberg.cubase 0x009404bc dyld_stub_binding_helper + 9691860
16 com.steinberg.cubase 0x0096d118 dyld_stub_binding_helper + 9875248
17 com.steinberg.cubase 0x0000ecc0 dyld_stub_binding_helper + 51928
18 com.steinberg.cubase 0x0000c748 dyld_stub_binding_helper + 42336
19 com.steinberg.cubase 0x00013c90 dyld_stub_binding_helper + 72360
20 com.steinberg.cubase 0x00048c70 dyld_stub_binding_helper + 289416
21 com.steinberg.cubase 0x00936244 dyld_stub_binding_helper + 9650268
22 com.steinberg.cubase 0x00a681b0 dyld_stub_binding_helper + 10903496
23 com.steinberg.cubase 0x00051c78 dyld_stub_binding_helper + 326288
24 com.steinberg.cubase 0x00936244 dyld_stub_binding_helper + 9650268
25 com.steinberg.cubase 0x0062c7a0 dyld_stub_binding_helper + 6464952
26 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
27 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
28 com.steinberg.cubase 0x0096d2f0 dyld_stub_binding_helper + 9875720
29 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
30 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
31 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
32 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
33 com.steinberg.cubase 0x00917654 dyld_stub_binding_helper + 9524332
34 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
35 com.steinberg.cubase 0x0096d2f0 dyld_stub_binding_helper + 9875720
36 com.steinberg.cubase 0x00977344 dyld_stub_binding_helper + 9916764
37 com.steinberg.cubase 0x0093ed50 dyld_stub_binding_helper + 9685864
38 com.steinberg.cubase 0x00a882c4 dyld_stub_binding_helper + 11034844
39 com.steinberg.cubase 0x00a87d1c dyld_stub_binding_helper + 11033396
40 com.apple.HIToolbox 0x9321c794 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
41 com.apple.HIToolbox 0x9321beec SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
42 com.apple.HIToolbox 0x93222c8c SendEventToEventTarget + 40
43 com.apple.HIToolbox 0x932b0c0c HIView::Click(OpaqueEventRef*) + 280
44 com.apple.HIToolbox 0x932b0ad8 HIViewClick + 56
45 com.apple.HIToolbox 0x932b0a84 HandleClickAsHIView + 156
46 com.apple.HIToolbox 0x932b03f8 HandleWindowClick + 516
47 com.apple.HIToolbox 0x932afe88 HandleMouseEvent + 456
48 com.apple.HIToolbox 0x9325f080 StandardWindowEventHandler + 148
49 com.apple.HIToolbox 0x9321c794 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
50 com.apple.HIToolbox 0x9321beec SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
51 com.apple.HIToolbox 0x93222c8c SendEventToEventTarget + 40
52 com.apple.HIToolbox 0x932aee58 HandleMouseEventForWindow(OpaqueWindowPtr*, OpaqueEventRef*, unsigned short) + 236
53 com.apple.HIToolbox 0x934119c8 HandleMouseEvent(OpaqueEventRef*) + 368
54 com.apple.HIToolbox 0x93222ff8 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 496
55 com.apple.HIToolbox 0x9321c9e4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284
56 com.apple.HIToolbox 0x9321beec SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
57 com.apple.HIToolbox 0x93222c8c SendEventToEventTarget + 40
58 com.steinberg.cubase 0x00a8c168 dyld_stub_binding_helper + 11050880
59 com.steinberg.cubase 0x008d6f30 dyld_stub_binding_helper + 9260360
60 com.steinberg.cubase 0x008d7118 dyld_stub_binding_helper + 9260848
61 com.steinberg.cubase 0x008c3704 dyld_stub_binding_helper + 9180444
62 com.steinberg.cubase 0x00663ce8 dyld_stub_binding_helper + 6691584
63 com.steinberg.cubase 0x007ba0fc dyld_stub_binding_helper + 8093460
64 com.steinberg.cubase 0x0000215c __code_start__ + 512
65 com.steinberg.cubase 0x00001f8c __code_start__ + 48

Thread 0 crashed with PPC Thread State 64:
srr0: 0x00000000007b9f8c srr1: 0x100000000000d030 vrsave: 0x0000000000000000
cr: 0x24022414 xer: 0x0000000000000000 lr: 0x00000000007b9f4c ctr: 0x0000000000000000
r0: 0x0000000002c0f01c r1: 0x00000000bfffccd4 r2: 0x0000000000000000 r3: 0x0000000000000000
r4: 0x0000000023ce9918 r5: 0x00000000bfffcd4c r6: 0x0000000000000000 r7: 0x0000000000000001
r8: 0x000000006261636b r9: 0x000000008fe53070 r10: 0x0000000019d0135f r11: 0x0000000001d4d7d8
r12: 0x000000008fe0f394 r13: 0x0000000000000002 r14: 0x0000000000000000 r15: 0x00000000bfffd700
r16: 0x000000001b502610 r17: 0x0000000023962e40 r18: 0x0000000023963500 r19: 0x0000000000000320
r20: 0x0000000000000400 r21: 0x0000000000000000 r22: 0x000000002395d680 r23: 0x000000001b5ae520
r24: 0x0000000022e90d40 r25: 0x0000000000000000 r26: 0x0000000000000000 r27: 0x0000000000000000
r28: 0x0000000023d9bf08 r29: 0x00000000bfffd420 r30: 0x0000000000000003 r31: 0x00000000bfffcd50


Model: PowerMac7,3, BootROM 5.2.4f1, 2 processors, PowerPC G5 (3.0), 2 GHz, 1.5 GB
Graphics: ATI Radeon 9650, ATY,RV351, AGP, 256 MB
Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM2/J13, 512 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM3/J14, 512 MB, DDR SDRAM, PC3200U-30330

[edit by Urs: shortened the Crash.log for better readability]
Top

Post

Hey, that's interesting, indeed.

Does it also happen when you load Z2 first and then Kontakt?

Is Kontakt *full* of samples when you load Z2?

Does it happen with other plugins, too? (Well, most VSTs probably use a different way to access resources, neverthless my way should be proper)

The crash itself happens in the System when Z2 asks it for its own location on the hard drive. This hints at three possibilities: Either too many files are open, or something corrupts Z2's memory or something closes BundleReferences when it shouldn't (beginners mistake...).

Or, something in the System has changed... is it a new phenomenon since you're on 10.4.6?

Cheers,

;) Urs
Top

Post

Hey Urs, thanks for the speedy reply! :)
Does it also happen when you load Z2 first and then Kontakt?

No, order is important, I can load several Zebra's safely, it isn't until I load a Kontakt. Any Zebra loaded AFTER Kontakt immediately crashes.
Is Kontakt *full* of samples when you load Z2?
No. In fact, it crashes even without any samples loaded.
Does it happen with other plugins, too? (Well, most VSTs probably use a different way to access resources, neverthless my way should be proper)
No, just Zebra. I've checked it with about six other VSTs and they all are okay.
is it a new phenomenon since you're on 10.4.6?
Well, not really. It is only a new phenomenon because I just got Kontakt 2. All signs point to Kontakt not playing nicely since it is the new member of the family, but I can't figure out why only Zebra crashes it. Also, its odd that it works fine on my Powerbook, but not on my G5. Stabbing in the dark, I thought it might be related to the dual processor, so I disabled one proc, but the crash still occured.

Perhaps I should redownload Zebra and install? Thanks again for your help, BTW!
Top

Post

Hmmm... have you tried repairing permissions?

It's obviously related to my way of handling resources (images etc.) as normal files rather than properties of the plugin. So, it's probably either some weird stuff in the file system, or it could be Kontakt closing the Bundle Reference. Latter would be weird if it runs on one system but not on the other... thus repairing permissions sounds like a viable thing.

Also, maybe you could try moving Zebra to the Local (or User, if it's in the Local now) VST folder and see what happens then...

Cheers,

;) Urs
Top

Post

Fixed. My bad, it was a rogue driver that was crashing for a device I no longer use with my system. The driver was crashing and apparently screwing the system. All is perfect now, so no worries...

:)
Top

Post

Phewwwww... glad to hear that!
Top

Post

damn, damn, damn.

My naive test proved incorrect I'm afraid. While I can now load both Zebra and Kontakt, it appears as though I can't use any functions within Zebra. CRASH!

I agree that Kontakt is prolly screwing with something that Zebra needs, but the crash is just killing me. :(

I've ran all the usual Repair Perms again but to no avail. Some things I've noticed:

When I load Kontakt VTS first, then try to launch Zebra VST, it crashes immediately.
When I load Zerba VST first, then Kontakt VST, it is fine until I try to do ANTYTHING within Zebra, then Crash.

I'm just lost. :(
Top

Post

In case it is any value... In Live 5 mac, I have no trouble with Kontakt2.1 and Zebra2
Top

Post

Thanx pdxindy. It seems that they CAN successfully work together because I have no problems using them together on my Powerbook, however, my G5 freaks out. So I *know* that points to a problem with my system, but I can't seem to find it. I don't do ANYTHING else on this machine except Cubase SX. It is my dedicated music machine, so it is ALMOST a fresh install except for a few device drivers (M-Audio & Novation).

I've been doing everything I can to find out what it is, from running "Sampler" (Development debugging tool) to pulling out ALL my other VST's but still no luck...

Poop.

URS: With regard to the location, I've tried putting Z2 in my home dir's plugin folder and then the "global" plugins folder (though not at the same time), but still nothing. I have a drive name "Audio & MIDI" where I store Kontakt samples. Are you aware of any issues (in general) concerning "weird" characters in path names? Perhaps I should NOT use the ampersand in that path name? Not that this related to the path where z2 is installed, but just curious...
Top

Post

Hmmm... weird...

Well, exotic pathnames shouldn't be a problem for me unless you use %, quotes or anything non-ASCII inside. But even if, I've started to switch all file handlings and everything to Unicode, so there shouldn't be any issues...

Hmm. Another user has that problem that Z2 oscillators can't allocate enough memory to play when there's a lot of Kontakt around.

I hope that I can soon try to reproduce some of these weirdnesses, when Z2 goes into its final beta stage (which is imminent, really, this time)

;) Urs
Top

Post

birdFEEDER wrote:Thanx pdxindy. It seems that they CAN successfully work together because I have no problems using them together on my Powerbook, however, my G5 freaks out.

Are your powerbook and your g5 both running the same OS version? same quicktime?

Is core audio configured differently on one than the other?

same cubase version on both of them?
Top

Post

OS X: 10.4.7 (same)
Same quicktime version
Same Cubase SX 3.1.1
No difference in CoreAudio. I thought my Firewire 410 might be a problem, so I've unplugged it and tried again to no avail.

WRT memory, the Powerbook has 1GB and the G5 has 1.5, so I don't think I'm exhausting all the memory. Also, the issue exists even if there are no samples loaded within Kontakt. I think I'm gonna hit up the Kontakt forum as well as see what I can learn over there... Thanks again for the help...
Top

Post

curious...


Do you have the same sample filepath for Kontakt on both machines? different drives? are the applications and os on the same drive on both machines?
Top

Post

Well, the Powerbook uses only the internal drive for everything while the G5 has a dedicated second HD (internal) that I store all projects/samples/audio files on. The application itself is on the OS drive. I see where you are going with this, I might just try to put the WHOLE APP (Kontakt) on ONLY the second drive and see if that makes any difference...
Top

Post

Is there a multi-out and a stereo out version of Kontakt? If so, have you tried using the different versions? Or have you changed the amount of outputs in Kontakt?

I had something like this happen with SampleTank 2.1. I'm just guessing.

Cheers.
Welcome to KVR, where the PC vs. Mac debate never ends.
Top
Post Reply

Return to “u-he”