4.03 OS X VST makes Plogue Bidule crash

Posting here hoping that someone on the
Reaktor team see this and might be
able to help find on which side the
problem is.

We have received several reports that
v4.03 is causing Bidule to crash
at startup (Bidule looks for new and
updated plugins at startup and open/query
them to cache the information so we
don't have to open/query all plugs
at each startup)

Bidule does support Mach-o plugins
and hasn't have a problem (yet) with
the ones that are out.

Relevant crash log excerpt:
#0 0x9014b7d8 in CFBundleCopyBundleURL
#1 0x901315c4 in CFDictionaryGetValue
#2 0x03355ba4 in _Z20componentStartupInitv
#3 0x03355a74 in main_macho

thanks,
seb@plogue

 

I hope you sent an email to support as well.

 

*bump*
(as i don't think that i got read because
it was posted on last friday and
with all the weekend posts...)

From quickly looking at the site, I
only saw an online support form requiring
to be a registered user. I don't own
Reaktor 4 and since there's no
demo, I can't even reproduce the
problem myself to try to find the cause,
that's why I've posted here.

 

Hey Seb,

I've posted a report on reaktor window resize in your forum and have send you some crashlogs, please mail any significant information to kubia@web.de and I'll try to forward them to the reaktor support using my account since I'm very anxious to get the problem solved.

Christian

 

Ive the same problem here=

my post to the plogue forum:

we're os x here

i had the old reaktor vst files installed. i never ran reaktor 4.0 inside of Bidule, but it loaded the plugs fine.

then, i 'upgraded' to reaktor 4.03 and the new mach-o have made life slightly annoying... but more

Bidule now hangs on Reaktor4 FX 2X8.vst

I have removed Reaktor4 FX 2X8.vst from the vst plugs folder... deleted it, deleted bidules prefs, reinstalled bidule.. restarted... whatever... it still hans on this vst plug... even tho i removed it completely from the machine

!!!ACK!!!

 

Yup, same problem here! Just adding one more voice to the pile...

didn't realize you were a plogue man, J! (though it sure makes sense)

best,
-e

 

! Mr. Cook !
lovely-

i will take a more long winded conversation off topic out of here.. but..

i talked to sebastien at plogue and he at least cleared up the problem with bidule hanging on the reaktor .vst files... i had wondered why i had to install the reaktor files myself (ie drag and drop) into my osx vst folder. but the reality was, the installer puts the files into the root /library folder -- they were the ONLY vst files in there... every other one has installed itself (or i put) in the user directory!

so that fixed the multi-crashing bidule issue -- tho i still have to keep the reaktor vst files out so i can run bidule.

and ya.. i really like bidule... its a nice thing to run along with reaktor, tho its a shame there's this conflict...

 

Same situation here. It crashed on me when opening Bidule and the same happened when I tried the Melodyne demo.

 

Has anything happened about this? (Like a bug being logged at the least)

Reaktor 4.0.3 also makes the new public beta of Tracktion crash.
Do these apps (Tracktion and Melodyne and Bidule) have non-standard VST implementations or is it one of the "optimisations"?

I've had to revert back to 4.0.2 which is a shame as 4.0.3 was about 5 to 10% faster (in terms of less CPU usage)

 

I got an e-mail from seb (plogue) the other day in which he stated that they finally received some software from NI so that they can have a closer look at the problem. It seems as if NI is actually the one to blame on this since it took them some time to provide a copy of their software to other VST-Host developers.
Which is a shame since bidule is an excellent piece of software and when it finally works flawlessly with R4 it might become the "excellentest" one of it all.

Christian

 

It has nothing to do with Bidule, Melodyne or other hosts having non-standard VST implementation or the any of the "optimizations".

I've send an email to NI explaining
exactly why it crashes. Still waiting
for the answer.