@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

@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!

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.

@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);

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!

do you need to add anything to the extra preprocessor definitions when building in projucer to get this stuff to work properly? had to rebuild and figured I'd consult you guys before I move on.

@cemeterychips realizing I need to take a few coding classes including Davids because I have no idea where to start with this haha! some people pick up crossword puzzles as they age,I guess I'm choosing coding .

@iamlamprey so incredibly helpful!! it will be work and lots of time but you've helped me get on my path, thank you!! and no luckily i don't plan to swap models. sounds funny but it will be a pass through type of plugin no knobs

@iamlamprey you are king! thank you!!!! do I simply get the git ? soooo new to all of this.

@cemeterychips ive only gotten this far and cant crack this error

Hi everyone,

I’m interested in recreating some of the preamps from my studio so I can access their distortion and saturation characteristics at home. I’ve been browsing the forum and saw that a few people have had success using .NAM files in HISE, but I haven’t been able to figure out how to get this working myself.

My goal is to keep the build very simple: no knobs, just a minimal GUI with a bypass button, where the audio passes directly through a plugin running a NAM model.

I’m still fairly new to HISE and have only built a few plugins so far, so I realize this would be a step up in complexity. That said, I’m eager to learn and would really appreciate some guidance on where to start.

For reference, here’s the forum thread I’ve been reading:
https://forum.hise.audio/topic/11136/neural-amp-modeler-nam-in-hise/23?_=1766879787037

Thanks so much in advance for any help or direction — it’s greatly appreciated.

@David-Healey Just one. whats really funky, is that vst's will compile but not AU's

@ulrik oh very interesting let me give that a shot, thank you!

@David-Healey said in exporting an older plugin i made no matter what i do?:

@cemeterychips did you delete the previous plugin first? And did you copy the new one across from the binaries folder?

I think im closing in on the issue "The source code has a different commit hash than the hise build"

@David-Healey its a completely different plugin, not a newer version of the same plugin. do I still need to do that?

thanks!

Hey everyone,

I took a break from HISE and just came back to it today. I created a new, basic reverb plugin, and it compiles without any errors. However, when I load the AU version of the plugin, it opens an older delay plugin I made instead of the new one I made today.

I’ve tried recompiling multiple times across three different projects, but the issue persists. Has anyone run into this before, or have suggestions on what might be causing this and how to resolve it?

Thanks in advance!

@cemeterychips update it worked ! i had to run it in an older xcode