IK Multimedia TONEX

Considering I care a lot about accuracy (typically because the real amp sounds and feels better to me), I only use the extended training.

I don't know if the difference is big (cause I haven't tried other options) but nonetheless.

And that is a lot easier now with the batch processing. Leave stuff overnight and come next day, can play through what I get.
 
Another small update: now my ETA is broken, just showing ”00:00” but training is progressing.
 

Attachments

  • Image 2025-10-08 at 14.58.jpeg
    Image 2025-10-08 at 14.58.jpeg
    92.2 KB · Views: 10
Considering I care a lot about accuracy (typically because the real amp sounds and feels better to me), I only use the extended training.

I don't know if the difference is big (cause I haven't tried other options) but nonetheless.

And that is a lot easier now with the batch processing. Leave stuff overnight and come next day, can play through what I get.
I'm doing the same thing. The extended time is less of an issue now that we can batch them up and just let it run overnight. The only downside with the batching is that the finalization stage is awkward if you've captured a pool of different channels/settings - you then have to remember (or document) those settings if you want to compare the real amp to the capture in their A/B selector.

I should really just be doing the standard training for now since I'm mostly doing experiments to dial in levels and work out a consistent capture process that translates to the Tonex hardware transparently. I also suspect once I have that all dialed in, I won't care about the finalization stage, I should have a good idea of how the captures are going to turn out.
 
That it does! But I still can’t access the other captures metadata that’s in queue so still can’t copy/paste the info. I’ll edit my post since it’s incorrect.
If you haven’t trained them yet you can edit the metadata in the json file. There was an option to open file location and it’ll be in each sub folder. I had to update a bunch before training and it worked well
 
If you haven’t trained them yet you can edit the metadata in the json file. There was an option to open file location and it’ll be in each sub folder. I had to update a bunch before training and it worked well
Yeah I imagined there was that option, thanks! I’m gonna try to see if I can do it later and otherwise I’ll go on a wild JSON adventure.
 
Btw, on a sidenote: I really always thought I prefered component modeling over captures (for obvious reasons), but for me there's something to be said in favour of captures.

Yeah I’ve come around on captures too. Once you find the captures that you like, it’s a great fuss free option and cool way to get some more unusual/niche amps.
 
My only real problem with captures as far as flexibility is that on some amps I tend to do "odd" settings, e.g. I often run my Fender-style amps fairly flat / "dark", and oftentimes captures don't reflect this. Still, the EQ set to pre can be really powerful and sound very natural, especially with reducing frequencies, so it's not even a huge deal with the Tonex.

They do get me just playing quicker, like I would with an analog amp, which I really appreciate. I don't think I'm as affected by modeler option paralysis as some people (I think maybe my experience with synths helps here..?), but with modelers I often get lost in doing experiments "just because" instead lol. Which is still fun and useful! But a different mindset.
 
but with modelers I often get lost in doing experiments "just because" instead

Absolutely this (at least for me). Just to end up either trashing the patch or sounding as always. With captures, at least without some efforts, that's just not possible, so I simply play with them instead and decide whether I like it.
 
Trying out a plugin capture (using the Blackhole virtual audio cable, which seems to work a treat), switched the GPU acceleration off (I'm on a GPU-weak Macbook Air M3), but switched it back on when there wasn't any progress after 5 minutes. Using optimized training, estimated time is around 40 minutes. Wouldn't mind doing this more often if only it wouldn't clog up the entire machine so much. Anything I'm doing comes with brutal latency, be it tabbing through things, typing or whatsoever.
In case this capture comes out ok, I'll possibly queue some up and batch process them on a day when I'm not at home.
 
Trying out a plugin capture (using the Blackhole virtual audio cable, which seems to work a treat), switched the GPU acceleration off (I'm on a GPU-weak Macbook Air M3), but switched it back on when there wasn't any progress after 5 minutes. Using optimized training, estimated time is around 40 minutes. Wouldn't mind doing this more often if only it wouldn't clog up the entire machine so much. Anything I'm doing comes with brutal latency, be it tabbing through things, typing or whatsoever.
In case this capture comes out ok, I'll possibly queue some up and batch process them on a day when I'm not at home.
Yeah no surprise on the mac. Cloud processing has its pros and cons but definitely shines in scenarios like this. Im surprised IK dont offer it as a bolt on but im sure only a small % are making captures so might not be worth even offering it. Stadium going cloud makes complete sense for the masses.
 
Im an idiot. Ive owned the large pedal since launch and just discovered there’s a tuner in there. I thought I’d read about it in a firmware update and then accidentally triggered it goofing around with the footswitches tonight. Seems pretty good too.

Now I’m considering kicking my tuner off the board and throwing the Tonex on there. A tuner plus nearly infinite dirt/fuzz boxes is hard to beat, especially when it can double as a direct to PA backup if my amp craps out on a gig.
 
Trying out a plugin capture (using the Blackhole virtual audio cable, which seems to work a treat), switched the GPU acceleration off (I'm on a GPU-weak Macbook Air M3), but switched it back on when there wasn't any progress after 5 minutes. Using optimized training, estimated time is around 40 minutes. Wouldn't mind doing this more often if only it wouldn't clog up the entire machine so much. Anything I'm doing comes with brutal latency, be it tabbing through things, typing or whatsoever.
In case this capture comes out ok, I'll possibly queue some up and batch process them on a day when I'm not at home.
Yeah I quickly tried disabling GPU Acceleration yesterday as well and got the same behavior, nothing happened for awhile.

Mines been chugging over the night and still had a few captures left to train. Since I don’t do it often it’s fine to leave on. I had the bonus of quickly checking and finalizing captures every other hour yesterday night which was actually a little fun.

Results thus far are pretty good to me, but on some of the cleaner captures the volume level is way too low. I did compensate for it (I thought) when capturing but I might redo a few of those later.
 
Aaaand now I caved and put in an order for in store pickup of a Tonex One… Haven't played my new captures yet but Sascha and others gushing over it plus the group buy thing made it impossible to resist.

Might load my new captures onto hardware this evening!

Question: is it possible to adjust delay settings on the One at all? Haven’t managed to find that info yet.
 
I'm
Question: is it possible to adjust delay settings on the One at all?

Yes, as long as you have a laptop connected via USB-C! :grin

It is a mini pedal with no screen, so you really don't want to be using the onboard controls much more than you have to. Minor tweaks to preset volume, and the tone stack are easy, everything else starts to get into alt modes and long holds and all sorts of shit you will not remember without a cheat sheet.
 
Back
Top