Very cool solution! I tested it this evening and I must say that this is really cool! I love it already. I have a few questions about this that may be pretty dumb, but I imagine a few others will breathe a sigh of relief when I ask them because they didn’t dare.
Is there a location for the files for Aida? If so, I have not found it yet. But this place must be quickly and easily accessible, especially for new buyers of the Dwarf. It additionally would help the mod family (and also the company) a lot if the community shares there diligently. It is an open source product, this spirit must also be felt here, in this hot topic.
In the files that @falkTX had thankfully uploaded to Nextcloud, I found files that model amps, but also files that model pedals. If you use a modeled pedal, do you still have to add an amp simulation and a CabSim behind it, or is that already included in the modeling? For me this point is not clear, sorry for that…
in theory its the sub in the forum - with a more organized website like tonehunt.org (we have been talking to them about options) coming in the future.
Models are sparse right now but I personally have a few I’m working on but this needs a little time. Next week hopefully.
most of the models are without a cab - to keep it as flexible as possible. So you use pedals and amps like you would on any normal board. Be it virtual or the real thing.
I checked Aida and Snapshots. It is working fine as well. I can change the file from one modelling to another per snapshot and there is only a very small but bearable latency when changing. I took one clean model for the rythm and then a gained one for solo. It works fine!
I ve loaded few profiles from https://tonehunt.org and loaded them thru fike manager to my duoX but till now there are no profiles in nerual presets, any idea what am I doing wrong?
Nothing centralized yet to my knowing, but there is a pack of several profiles in this thread to start with -NeuralPi ToobAmp models
Also forum posts with people sharing their profiles seem to be tagged with a “Model sharing” tag and can be found here: Model Sharing - MOD Audio Forum (probably that is the closest we’ve got to “base” at the moment.)
Things are not yet in a good state where we can just have a “good to go” pack.
Some of models I uploaded (none of my authorship, I simply adjusted or converted them) do not work on a MOD Dwarf in a reasonable way as they take too much CPU. They are still useful on desktop.
Once we have better and more performant models I might delete the current links, so people move into the good stuff.
We also need to pay attention to audio levels between these models. For the 2 packs I uploaded I manually roughly matched their volume, but it is within a pack, not globally.
Still, I think some kind of centralized place to download a good starting set of models would be great to have, we just do not have enough good/performant models yet.
If it actually does something that I expect it to do - I think it should be possible to make a step in the colab document, which will take the the full “predicted” track, calculate how much gain we need to normalize it, and save this gain value to the model json.
This way we would get all the profiles created with colab document producing more or less the same volume, at least if all the models are made from the same input file.
It could be awesome - typical problem with all the kinds of the presets for different plugins is that volume is often different, and it is hard to scroll presets without sudden loud guitar screams.
Having all the profiles normalized to the same volume… mmmm… sweet.
Trying to do something like that, at least I was able to convert the whole dry input data to the modelled array, and trying to calculate the gain.
Injected this step after Evaulation step, that’s where we get full_dry variable data to work with.
I do not have much of the understanding of the normalization snippet I’ve borrowed, so I am not sure if it does what it should for this particular array, but if I am lucky - it probably produces the required gain value to normalize output into -3db RMS. This can be later can be used in json. (Yet to be implemented)
Would be nice to add something like that to the colab file, and put gain into produced json so all the trained models would share the same volume.
p.s. repeating the step several times forces my CUDA to run out of RAM , so looks like modeled_full generation RAM usage stacks up, adding 0.5gb of ram on each run.
rms_level = -3 #db
# Apply model to full dry signal
modeled_full = model(full_dry[:, None, None].to(device)).cpu().flatten().detach().numpy()
#https://superkogito.github.io/blog/2020/04/30/rms_normalization.html # linear rms level and scaling factor
sig = modeled_full
r = 10**(rms_level / 10.0)
a = np.sqrt( (len(sig) * r**2) / np.sum(sig**2) )
output_gain_to_normalize = a
print (f"gain to achieve rms_level {rms_level}db is {output_gain_to_normalize}"
gain to achieve rms_level -3db is 2.227024804497091
p.p.s.
Also would like to add, that if volume normalization of the models does make sense to you guys, then the earlier this would be added to colab document, the less models would be generated with random volumes to hurt our ears.
by itself it runs most of the lower-cpu-usage models, but not much CPU left for other things like a cabsim.
a little portal could help, forcing the system to use the 2 Duo cores, but this adds latency…
so yes, it mostly runs. if it is useful enough depends on how many plugins you need to have on a pedalboard.
My current pedalboard setup standard is 1 comp, 1 overdrive, 1 Aida-x (switching 2 heavy profiles) portal, 1 cab sim, 1 delay, 1 reverb, 1 x2 gain, latency is about 7,5 ms at 78/82% CPU.
Before when I used a QC with same profiles/fx and latency was more than 9 ms
Well, better than nothing. I was expecting it to be a no way thing. By the way, why should anyone need a cab sim with Aida? When one samples and models an amp doesn’t the target sound come out of the amp cone and through a mic?
Let’s say at least one could convert a duo in a cab modeler and put it in their effect chain or before or after a Duo and get some use of it.
BTW I’m not sure I understand what portal does and how it’s supposed to be used.
However, I’ve noticed that when adding new models’s json files to the file list, they don’t appear straight away in the list displayed in the plugin’s settings. I had to delete the plugin and stick a new one on my pedalboard to see them being displayed.