Can't find effects in DLL (Sanity check failed)

[Onik Sisodiya]

Hello everyone, I'm working on exporting a HISE project, but I'm getting an error "Can't find the effect in DLL",
I'm getting some errors when exporting using Compile DSP networks as dll even after adding a script FX with a network. It processes it, but I get a lot of warnings about the .vcxproj when I restart after the DLL compile process, I do not see any networks in HardcodedMaster FX. I also tried some solutions that I found in the forum by other developers, but still having the same issue. I also rebuilt the HISE and also tried it with the ipp. Is there anything that I might be missing to do before exporting because with other projects, it worked fine as it also loaded the network in the HardcodedmasterFX.
I would really appreciate if someone can help me with this.

I am using windows to compile it with "release with Faust" and the visual studio version is 2022.

[Lindon]

@Onik-Sisodiya The warnings you can ignore - you only want to worry about any errors - showing up in red text -

Make sure your dll is preset by looking in:

PlucksAndMallets\Dspnetworks\Binaries\dll\Dynamic Library

Restart HISE, load your project and load a hardCodedMasterFX - and check that the drop-down box there is listing all your FX.

[Onik Sisodiya]

Hey @Lindon, thanks for the reply. Yes, I did that. It loads the effect in the Hardcoded masterFX 1 but not the other after restarting. Also, after choosing the effect manually in the other hardcoded Master FX2 and 3, it doesn't allow me to export it because this sanity check failed, which says it cannot find the effect even after adding it.

[Lindon]

@Onik-Sisodiya I'm not sure what your problem is, perhaps post a snippet

[Lindon]

@Lindon - Okay - well it seems HardCodedFX modules are very sensitive to the version of HISE used to compile the DLL, and (at times) cannot find the effect in the DLL for DLL's compiled on a version of HISE greater than the version for the module so....

• You need to build the DLL, then remove the module(s) and reinstate them- this seems to let them find the correct DLL and its contained effects - and allows you to compile the project.

[Christoph Hart]

@Lindon there‘s a API version check that prevents loading a DLL with a HISE version that has a different API (otherwise the function pointers into the DLL would just crash) but the API didn‘t change in the last two months.

[Lindon]

@Christoph-Hart said in Can't find effects in DLL (Sanity check failed):

@Lindon there‘s a API version check that prevents loading a DLL with a HISE version that has a different API (otherwise the function pointers into the DLL would just crash) but the API didn‘t change in the last two months.

Well - the problem outlined by the OP is resolved by recompiling the DLL and deleting then reinstating the Hardcoded FX units.... so why could that be?

[Christoph Hart]

@Lindon no idea, maybe the IDs of the effect have changed.

[Lindon]

@Christoph-Hart hmm, only seems to be on Windows...

[Onik Sisodiya]

@Lindon Thanks a lot. It worked after removing all the effects that were causing sanity errors.