Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:4932] Re: vst4cs not working

Date2004-07-13 03:29
From"Michael Gogins"
Subject[CSOUND-DEV:4932] Re: vst4cs not working
I am testing with 2 plugins: polyiblit and cheeze machine. The first works
and the second does not with my sources. I don't get a crash on the line you
quote though; I get the info on the cheeze machine OK, but then it crashes
when Csound allocates the instrument instance.

Unfortunately this sort of thing is hard to debug -- you pretty much have to
put in message prints to localize the problem.

----- Original Message ----- 
From: "Andres Cabrera" 
To: "Csound Developers Discussion List" 
Sent: Monday, July 12, 2004 10:15 PM
Subject: [CSOUND-DEV:4931] vst4cs not working


> Michael,
>
> I've just checked out your sources for vst4cs, and they produce a crash
> when calling the plug in's main function. This happens on line 317
> (might not match since I get double spaces) that reads:
>
>     aeffect = main((audioMasterCallback) VSTPlugin::Master);
>
> Can you take a look?
>
> Thanks,
> Andres
>

Date2004-07-13 04:05
FromAndres Cabrera
Subject[CSOUND-DEV:4933] Re: vst4cs not working
I don't really know what my sources do different, but they load 
correctly Cheeze Machine, and even bulky commercial plugs like Absynth2. 
I've also tried Crystal, SuperwaveP8, Borderliner and Synth1 succesfully.
I've tracked the problem down to line 159 of  vsthost.cpp that reads:
aeffect = main((audioMasterCallback) VSTPlugin::Master);
If I replace this with the line from my sources, the error still occurs.
Can you think of something? It might be the way the csound API is 
loading the dlls...

Andres

Michael Gogins wrote:

>I am testing with 2 plugins: polyiblit and cheeze machine. The first works
>and the second does not with my sources. I don't get a crash on the line you
>quote though; I get the info on the cheeze machine OK, but then it crashes
>when Csound allocates the instrument instance.
>
>Unfortunately this sort of thing is hard to debug -- you pretty much have to
>put in message prints to localize the problem.
>
>  
>