@Sifres I just went and looked... That looks SO great.

@pgroslou That's a great resource. Thank You!!

@David-Healey I know about tracktion engine... But I want to do it this way round till the channel strip is built atleast.

The console style Mixer has been a dream of mine since long. And this is a part I want to experiment with. And I'll learn a lot more about plugin design in the process.

Once the channel strip is built, I do plan on looking at tracktion engine for the implementation of playlist, mixer and such basic features of a DAW.

Oof! Didn't think I'd be writing this one this soon.

So, I had started my search for something like HISE for a very specific thing. I wanted to build my own DAW...

I know... Massive dream. Especially for someone who's genuinely a noob at plugin design. But it has always been a dream of mine... I LOVE the console style designs like UAD LUNA or SSL 360...

But well, it IS a mammoth task, so I am breaking it into achievable chunks. I am first trying to build a channel strip plugin that will in future become the console that sits in my DAW. For that channel strip, my plan is to keep the knobs and faders style of the console era, but provide as much digital freedom as possible. For example, with the pan knobs, I wanted to make a pan knob with a crossover frequency that kept the low frequencies unpanned. I wanted a multiband stereo spreader with mono-compatibility. I made both. In HISE. (Got inspired by Boz Digital and Izotope Ozone. Incredible developers there).

What I want here is help to build my dream. Not help in making the plugins... I wanna do that all on my own (I will ask all my doubts and queries here, tho)... I want ideas on how to make this even cooler...

For now, since I am done with the PAN and STEREO plugins, and the output is just going to be a normal fader, the next thing I want to address is the EQ...

(My console idea is SATURATION->FILTERS->GATE->EQ->COMP->PAN/STEREO SHAPING->OUTPUT)

I want you all to give me ideas on what I can implement in these modules to make them stand out, to make them fun. What functionality do you wish there was in an SSL style 4 band parametric EQ (don't say dynamic or spectral tho... Idk how to do that in HISE)!!

@HISEnberg That sounds like MORE hassle

But yeah, coding blind, exporting and checking PluginDoctor got me pretty far so I'll continue that. Meanwhile a frequency curve analyser would be great!

Is there any way of checking the Frequency/Phase inside of HISE? Like Bertom EQ Curve Analyser or DDMF PluginDoctor?

Having to export vst3 and checking the frequency/phase relationship in PluginDoctor is a hassle, honestly.

@David-Healey In the same conversation there are 2 replies from scottmire and sinewavekid... Do you have any information on those?

Using a script to change between neural networks? Or using clearModel() to load a new network?

Or if not that either, can you help with the timer to silence thing?

@David-Healey Test.zip

Well apparently you can just upload zips straight into this forum. Neat.

@David-Healey Aye aye, cap'n.

@David-Healey Sorry I didn't understand what you mean. Do you want the project where I made that 5 model scriptnode thing? That's in a project called "API", which I made like a few minutes ago after seeing resonant's idea. Meanwhile the neuralNetwork code is from a project called TestPre, which I was working on originally.

@resonant I'm not preventing s#it... I'm just testing out the waters. So 35-40% CPU usage isn't as big of an issue right now. Just trying to see if my idea can actually be realised. Also what's Aida x?

As much as I gathered from other chats in this forum, you can embed models as json scripts. I'm not sure, as a noob, if I'll be able to do it or not... So I am just going the simplest route I can take and kinda brute forcing it to work.

@David-Healey Why is NAM like this... Just give us normies a nice loadModel function in a simple cpp that we can just put in a third party C++ node of our own like

#include "./loader.cpp";
Network.loadModel(index+".nam");

And Boom, job done.

But nooooooo, it has to be convoluted.

(Sorry for the rant I know it's a lot more complex than that)

@David-Healey Not a lot of code, I'm doing this 5-model thing in a new project. Here is the code and the scriptnode.

@resonant This is an acceptable result. Silence is manageable. The white noise bursts are unbearable.

Do you have any place where I can learn how to do this? Is this in the HISE Documentation?

(I'm gonna use this technique to make a Manley Voxbox emulation. There are only 5 gain stages... Well, 10 if you count in the Line and Mic switching... And 20 if you count the xfmr in/out switch... But this can be done... I will make that plugin with this idea. As soon as I can do that silence thing, that is.)

@David-Healey
Interface: F:\Apps\HISE\Projects\API212L\Samples

@David-Healey The same place...? It does fetch the 50.nam file. It saturates in the same way 50.nam would. That part is working. It's the drive knob callback where I try to switch models that isn't working.

Also, I just tried out @resonant 's idea with 5 models at first and it works great, except for when it switches between models there's this white noise burst. As long as that can be removed, I think this project can be completed...

@David-Healey Yes, it does change. However what doesn't change is the object value in the neural network. I did a Console.print(neuralNetwork) inside the else and also just before the inline function. Both print out "Object:2ox7...." something. The same value. Nothing changes.

My nam files are in HISE/Projects/API212L/Samples

@resonant Huh... This sounds simple... Let me try it out with 8 nodes First. If it works well, I'll start on adding more...

@David-Healey I do have the step size set to 1, I put in the rounding thing as a precaution.. Honestly it can be deleted and it wouldn't change anything...

Ik I don't need an else, I just added it after testing it without the else when it didn't work. So I thought maybe I should add it (Ik it isn't logical, but programming Gods might have smiled upon me). Anyway that didn't work either.

I'm not changing the value of index. The index is 50... I just don't want modelIndex == 50 entering the processing so I'm just removing that particular case from the processing.