Yes, I would have liked to test the Tonex rig beforehand as well—at least for an hour or two.
The only way I found to play around with some of the new rig’s effects was through the new ToneNET presets.
There’s often white noise involved, but I’m used to that by now.
Yes, many features have been removed—which is a real shame—but perhaps they’ll make a comeback.
All the requests from many users, myself included, haven’t been implemented so far. What I miss most is the ability to import a new TXP package directly within the Amp Model Tone Browser; that was really easy in Version 1.
I do understand the reasoning behind it, though, since TXP stands for Preset and TXM for Tone Model.
The problem is that the TXM files aren’t assigned names, just jumbled number combinations that are completely useless to the user.
Perhaps it would be possible to save a named TXM file directly when creating it in the modeler, instead of a TXP file—which isn’t actually a preset yet anyway.
And one important request for future updates:
When opening the Custom IR Browser, the user folders should only display User Cab folders, not every single Tone Model folder that’s been created; the current view is far too cluttered.
There are surely many users like me who need a large number of folders.
Anyway, enough criticism— I really like the new Tonex rig,
and I’m very confident that it will continue to improve.
The only thing is the noise gate: like with so many other providers,
it shouldn’t be part of the rig chain but rather a global setting that can be activated centrally.
That would be great!
Thank you!