@Christoph-Hart It was a dodgy faust node. I didn't bother to look at the faust code to see what was wrong. I was just going through the nodes one by one and deleting them and recompiling. I didn't need it any more and must have edited the code badly before going on holiday and forgot what I did. 😆

HISE was built with Faust and all paths set correctly to answer your question. Thanks for the help!

@Morphoice

Well maybe. But it'll be so cpu hungry. And fiddly because the routing of a real reverb is a complex matrix with taps coming in and out of all kinds of places

@d-healey Ok. Im playing with it now. Just made all my samplemaps disappear in my main project but I was able to bring it back so I kinda see whats happening. Im gonna have to keep playing with it to fully understand whats going on. I'll get it soon enough.

@hisefilo Just wanted to chime in about this work here:

Building AI Enhanced Audio Plugins by Matthew John Yee-King

https://github.com/yeeking/ai-enhanced-audio-book

I am just finishing the work and its a great starter for training in Torch then building in the JUCE framework. I haven't tried HISE integration yet (I didn't know the API was updated either). I am happy to share the pdf if you are interested!

@d-healey Ok I'll check it out on patreon thanks for your time

@HISEnberg Did you get the patch to work in hise? I get no mix or sound when I insert the patch into hise.

@d-healey Thanks, simultaneously I just found this thread:
https://forum.hise.audio/topic/9830/attaching-text-json-files-to-the-compiled-binary/6

I really assumed that I could load data like this but that's ok - I will do the suggestion in there of checking for a file and falling back to a default object if not found, at least for the resets/presets code. The main data I can definitely move to a .js no problem. The main data of my entire script including samplers came from a JSON file and I was tricked into thinking it was working fine because the samplers are created at compile with the correct data, and so I figure the UI was as well. No wonder absolutely nothing has been working correctly.

@d-healey thanks alot that worked!

@hisefilo cool. I'll do some reading. Might be back. Thank You!

@whoopsydoodle

Here's an example of 'simple and easy'.

anything outside of this, you're definitely making it less simple and easy.

Laf Shadows and a subtle glow are attached to the slider knob body so it seems 'responsive' moving up and down the slider.

Slider made separate then drawn into Laf function.

Screenshot 2025-04-18 at 3.36.25 PM.png

You could LAF some shadows and glows to help the vibe for sure.

Slider Example Shadows.gif

@Straticah
ikr : )
I think it was one of the first questions I asked on the forum, so this is very nostalgic.

@d-healey So, I think the issue had to with the most recent Xcode Update.

I was on 16.3 and reverted back to 16.2, seems to be all good now.

Thanks for the help folks.

@JulesV start here:

const var externalDat = { "Option 1": A, "Option 2": B, "Option 3": C, "Option 4": D }; inline function CheckOnLoad() { local data = Engine.loadFromJSON("../MyFile.dat");); Console.print(trace(data)); //data = externalDat; //Engine.dumpAsJSON(data, "../MyFile.dat"); }; CheckOnLoad();

@aaronventure Thanks, looks interesting :)

When using g.addNoise() the area parameter is still expecting an array.

@HISEnberg Awesome thank you so much!

@DanH https://forum.hise.audio/topic/9618/what-is-errorhandler-state-12?_=1744705170625

@CyberGen you're absolutely right, but this would break backward compatibility. So making your own array seems to be the solution for now.
In the waiting for a HISE_USE_NATURAL_TEMPO_ORDER preprocessor ☺