@Christoph-Hart that's superb news! I'm so looking forward to bringing my AMS RMX16 clone to dolby atmos to have that gated reverb in my next album. It was a stupid idea to start making an album in atmos anyways but hey... why not

@David-Healey no they need to ring out. i will probably limit it around 16 voice cards or something like a real synth would have

@Morphoice https://www.thewindowsclub.com/uninstall-windows-defender

@Morphoice Sick dude. Well done! Loving the sound and glad you kept that interface clean. I'll trade you a code for my synth if you are interested 👈

@dannytaurus no nothing changed except the plugin version in project settings. the hise version was around half a year newer from the one i last compiled it with on the develop branch

@Morphoice yeee! Let go! 🙏

@dannytaurus that makes sense

@Morphoice The basics are they are using ML models to analyze and replicate the behavior of analog equipment. They run various test signals through them and use the results to train a model that can predict how the device will respond to any input signal.
The Kemper Profiler uses a different approach. They capture the full response of an amp or effect at different settings. It creates a snapshot of the device and builds a profile. This is closer to convolution than ML.
The real problem you're going to run into with time-based dynamics (like a compressor with slow release) is the model will start to emphasize the non-linear behavior. The result of these ML compressors ends up sounding like saturators rather than compressors.
I'm on the same path as @griffinboy where I'm focusing on making models of specific components and inserting them between other analog models.
If you want to start tinkering with Neural models in HISE, here's a thread of my starting process:
https://forum.hise.audio/topic/8701/simple-ml-neural-network/108?_=1748359797127
@griffinboy also posted a thread about some details to the training scripts.
I haven't had time to fully dig in for the last few months, but plan to soon.

@d-healey I tried that recently just to reflect the bypass state of the DAW to the bypass button of the VST, but it wasn't reliable in the end... Maybe I've done it wrong that been said...

@d-healey

Or c++ / snex 😁

But two samplers is the easy way I'm sure.

@Morphoice scroll down in the export dialog, there's the juice.

@griffinboy I'm not at that point yet tbh. Most of what I'm working on right now is audio analysis in realtime and sample playback. I do really want to do a distortion/saturation effect of my own at some point though!

@Morphoice hmm, weird, anyways, I've added a safe check as well as the option to edit the flags set by the node_properties.json file in the DLL exporter. This should fix most issues related to this subject.

@orange yes some nodes seem to only work on windows and some only on macOS. The source code of my project can be compiled on windows and MacOS the same. Make sure to clear the binaries folder of the dsp networks. Do not delete any other folders.

When compiling make sure you first set all networks to not compile - then compile the dsp networks - open Hise and set your networks with Airwindows nodes to compile.

@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

@Christoph-Hart Thank you for the suggestion, I will try to edit them.