plugin works fine, until hardcoded master is created

[cemeterychips]

I'm experiencing a crash when exporting a plugin with NAM as Hardcoded Master FX.
Setup:

macOS 13.7.4 (Ventura)
iMac 2017 (Intel)
FL Studio 21.2.3
HISE version: 4.1.0 git commit hash 6ba56cca

What works:

Loading NAM model via script in HISE
Exporting plugin WITHOUT hardcoded FX
Plugin loads and processes audio correctly

What crashes:

Exporting with "Hardcoded Master FX" → crashes DAW on plugin load

Crash: __cxa_throw during Neural Network initialization (SIGABRT)

any ideas ?

thanks!

[David Healey]

Could be daw specific. Test in another DAW such as reaper

[cemeterychips]

@cemeterychips Hi David, I spoke with you on you tube and said i would make a video of the issue i was having. ive attached the video here: https://www.youtube.com/watch?v=SW5CvKj_QB8

tried to keep it breif and to the point. thank you so much for your insight!!!

for reference this this is my script

// Include the embedded NAM model data
include("NAMModelData.js");

// Create the neural network and load the embedded model
const neuralNetwork = Engine.createNeuralNetwork("test22");
neuralNetwork.loadNAMModel(EmbeddedNAMModel);

[David Healey]

@cemeterychips Do you get the same issues with a project that uses script fx but doesn't use nam?

[cemeterychips]

im still getting this error when trying to make a simple reverb in script fx when i send the batchcompileOSX.sh to the terminal: error: unable to attach DB: error: accessing build database "/Users/waveygreta/Documents/HISE Projects/hello/DspNetworks/Binaries/Builds/MacOSX/build/XCBuildData/build.db": database is locked Possibly there are two concurrent builds running in the same filesystem location.
** BUILD FAILED **
then after 1 or 2 mins the .dylib file appears in the dll folder.

How ever it does not crash the DAW and works as intended. is it possible that the nam file ive embedded is too big or something? I've read that can cause issues.

[David Healey]

@cemeterychips said in plugin works fine, until hardcoded master is created:

im still getting this error when trying to make a simple reverb in script fx when i send the batchcompileOSX.sh to the terminal: error: unable to attach DB: error: accessing build database "/Users/waveygreta/Documents/HISE Projects/hello/DspNetworks/Binaries/Builds/MacOSX/build/XCBuildData/build.db": database is locked Possibly there are two concurrent builds running in the same filesystem location.

I think the reason you're seeing this is because when you did the initial export from HISE that froze, it didn't freeze but was still going in the background - how long did you wait?

@cemeterychips said in plugin works fine, until hardcoded master is created:

How ever it does not crash the DAW and works as intended. is it possible that the nam file ive embedded is too big or something? I've read that can cause issues.

That's entirely possible. I know nothing about NAM though so can't help with any specifics here.

[cemeterychips]

@David-Healey i tried pretty quickly let me try to do another build but wait 5 mins.

ah ok well good learning potential here. ill post my findings if i can crack it, thanks David!

[cemeterychips]

@David-Healey said in plugin works fine, until hardcoded master is created:

@cemeterychips said in plugin works fine, until hardcoded master is created:

im still getting this error when trying to make a simple reverb in script fx when i send the batchcompileOSX.sh to the terminal: error: unable to attach DB: error: accessing build database "/Users/waveygreta/Documents/HISE Projects/hello/DspNetworks/Binaries/Builds/MacOSX/build/XCBuildData/build.db": database is locked Possibly there are two concurrent builds running in the same filesystem location.

I think the reason you're seeing this is because when you did the initial export from HISE that froze, it didn't freeze but was still going in the background - how long did you wait?

@cemeterychips said in plugin works fine, until hardcoded master is created:

How ever it does not crash the DAW and works as intended. is it possible that the nam file ive embedded is too big or something? I've read that can cause issues.

That's entirely possible. I know nothing about NAM though so can't help with any specifics here.

@David-Healey . It’s an SIGABRT abort trap

edit i figured out the issue and it may not be capable to run nam as a hard coded fx unless anyone else here knows otherwise.

I'm mixing 2 incompatible approaches

In HISE Script Processor: successfully load NAMModelData.js with JavaScript code
But then: i export as HardcodedMasterFX which compiles to C++
The crash: The JavaScript code CANNOT be compiled to C++ - it fails and crashes

THE FUNDAMENTAL ISSUE:
When I export HardcodedMasterFX, HISE tries to compile my scriptnode network (the script_fx1.xml that says Model="test22") into C++ code. But:

my scriptnode is looking for a model called "test22"
There's NO .nam file called "test22" in your /AudioFiles/ folder
The NAMModelData.js file is JavaScript and CANNOT be compiled into the C++ dylib
Result: Crash
:( boohoo