For example: group all captures of the same device (e.g. Neural DSP “US DLX 58”) and switch between installed variations using a selector — if variation “1” is selected, you can jump to “7” or “32” if they are installed.
Well I do not know if current DSP power would be enough for this but…
It would be nice to have this feature.
I would capture my amp with
Gain 4 Bass 5 Treble 5 Master 5 - and …
Gain 6-7 Bass 5 Treble 5 Master 5
Then somehow sweep in between like derivative..
I think Kemper had something like a liquid profile but I am not sure if it was doing what I suggested above.
Hello, my request is simpler and is purely about organization: grouping together all the captures from the same device, which should therefore not require any additional resources.
But I had also thought of something more advanced as you describe. With multiple captures, we could find something that look like the actual buttons of the device. That, however, should certainly be complex and should be the subject of a separate feature request.
Yes, I agree ![]()
I just could not resist ![]()
What you suggested also is very helpful and like you said, simple.
For instance I bought Amalgam Tone King Capture set.
It is massive. So many captures.
I could not use 95% of it.
If it was grouped however, I might have used more of them.
It would take a lot of dsp and a row, but you could assign the output of 2 captures to an exp, with one capture being reversed (heel is 100%, toe is 0% on one, opposite for the other). The exp would blend from one to the other.
That 's a very nice way of describing it. However, I was talking about “beating the capture system limits”. Meaning you capture an amp and use similar settings and it sounds real unless you change the gain a lot. Then you would have to use another capture for higher gain.
So, what if you do 10 captures for each gain level from 1 to 10 and and mix them as you change the dials. I am not talking about real time changes. Imagine you are at the gig and you want to change your amp’s setting without loading another capture. You just turn the knob and grouped captures do their work.
Maybe they could do this with AI, if 10 captures (or certainly many more) are taken for each button on the device, the AI recalculates the entire device with each button usable. For example, if a device has 3 buttons: you take 30 captures, describe the role of each button, and the AI captures the device with all 3 buttons actually adjustable. But it will become less time/resources-consuming and less expensive to just buy the actual device ![]()