MuTools

blahbah · Post by **blahbah** » Tue Sep 11, 2018 9:55 am

Hi, I can't get Kirnu-CreamCM to work on Mulab, comes up with 'main' returned invalid aeffect.
Running 32 version of Mulab in Windows 10 64 bit.

Thanks.

MuTools · Post by **MuTools** » Tue Sep 11, 2018 11:32 am

Are you sure it is a VST 2 plugin?

blahbah · Post by **blahbah** » Tue Sep 11, 2018 11:38 am

I installed it from the Computer Music DVD, it says VST2 in the installer.

MuTools · Post by **MuTools** » Tue Sep 11, 2018 12:22 pm

The error means that the VST returned a null aeffect pointer (out of memory?) or that the aeffect object does not have the aeffect 'VstP' magic value. Both reasons are not on MuLab's side. Please forward this info to the plugin developer.

LunaTech · Post by **LunaTech** » Wed Sep 12, 2018 12:06 pm

Have you had any luck with this? I think there is something about running MuTools in admin mode for the CM plugs. Might give that a shot if you have not already.

Edit: Also might want to run in compatibility mode for win 7.

blahbah · Post by **blahbah** » Wed Sep 12, 2018 1:38 pm

Running as administrator worked, thanks.

MuTools · Post by **MuTools** » Wed Sep 12, 2018 2:10 pm

That's odd. I've sent a question about this to Kirnu.

MuTools · Post by **MuTools** » Wed Sep 12, 2018 4:02 pm

Blahblah, could it be that you had installed the Kirnu Cream data to a folder which requires admin privileges?

pekbro · Post by **pekbro** » Wed Sep 12, 2018 8:55 pm

This doesn't work on my problem. Weird that it only happens in MuLab out of all
my DAWs. I will keep after them.

-Cheers

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Wed Sep 12, 2018 9:35 pm

Wow!! can Cream do something that the built in can't do better? Unless you have a bunch of existing presets for Cream. I really like Cream but the sequencer in Mux replaced it for me.

digdug303 · Post by **digdug303** » Thu Sep 13, 2018 4:06 pm

I agree with you Scrubbing Monkeys, however, Cream has a lot of midi controllable parameters , so it can still be useful in some situations.

I use it without problem with Mux, but my version does not come from CM

LunaTech · Post by **LunaTech** » Thu Sep 13, 2018 11:28 pm

Joe, I think you are right about the issue that blah was having.

LunaTech · Post by **LunaTech** » Thu Sep 13, 2018 11:31 pm

@ pekbro, what are the steps that you take for loading the Mutools up? Are you running the 64bit or 32 bit version?

pekbro · Post by **pekbro** » Fri Sep 14, 2018 12:22 am

LunaTech wrote:@ pekbro, what are the steps that you take for loading the Mutools up? Are you running the 64bit or 32 bit version?

It's 64 bit, this is an issue with the plug-ins definitely, it's not just a single plugin. It's every new and
recently updated plug-in from Plugin Alliance, so its multiple developers. PA handles the QA, so we
will see what happens. I only tried the solution listed here to rule it out, I did not expect it
to work actually.

Apparently they are doing something different with new plugins and updates that trigger the error,
where they did not before. MuLab has certainly not changed in the interim. Of course, it could be on
my end as I am on Win 8, where the majority of users are not.

The strange thing is that it's only MuLab, I own and use 11 DAWs. None of the others have the slightest
problem and that error is very specific.

Anyway, the issue remains open and under investigation.

MuTools

KVR Audio

Mulab won't run Kirnu CreamCM