NAM Model switching logic
-
I have 101 nam files, 0.nam to 100.nam, I want the Drive knob to switch between those models. But the neural network stays stuck at the default 50.nam... Can someone please help?
(Sorry for tagging you all, idk if this is the right etiquette here or not, but I saw @aaronventure and @Lurch discussing the same topic and I did take inspiration from their code to try this out. Also, @David-Healey and @Christoph-Hart, please help.)
-
@pratitghosh said in NAM Model switching logic:
I have 101 nam files, 0.nam to 100.nam, I want the Drive knob to switch between those models. But the neural network stays stuck at the default 50.nam... Can someone please help?
That's probably not going to give you the result you want. It will not smoothly blend like a drive knob does, and even if it does, it will probably hammer the CPU.
-
@Orvillain said in NAM Model switching logic:
That's probably not going to give you the result you want. It will not smoothly blend like a drive knob does, and even if it does, it will probably hammer the CPU.
Yeah. I know that's a risk, But I want to atleast see if it CAN be done. Because I can look into optimisation later... But honestly I can't even switch the models at all...
On that note, you got any ideas on what I could do? Maybe creating a saturation algorithm from all these nam models? Then I could make the plugin an algorithmic saturation plugin...
-
@pratitghosh Why are you rounding the value of the knob? Can't you change the step size instead?
You don't need an else after a return on the if.
if (modelIndex == index)- where are you changing the value of index? -
@pratitghosh you can just use bypass nodes for each model. And these modes will be connected to a xfader node, so it will switch between models
Edit: 100 models are pretty huge, maybe multiple xfader nodes, each one will switch 8 models
