@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
