Just tried the beta, I must say it’s definitely an improvement in usability, but personally I’d prefer to have the preset/models/collection browsers in the same window.
Any chance to have an option to put those in a (resizeable) sidebar instead of separate windows?
When I have the Tone Model browser open it automatically closes if I make changes to the effect or cab blocks. Not sure if that is a bug but that is a huge downgrade to usability.
Also not having an option in the preset browser to hide not owned amps is a real problem for just playing. I keep getting static when I am trying to browse tones
I’m not sure if the new software is more usable but it definitely looks a lot nicer and seems to have a much easier learning curve.
Are you looking for general feedback and suggestions from us, or are we just reporting issues in this thread?
We’re looking for both.
First, the looks great and it’s a MASSIVE improvement. I was very happy to see the direction you’re going in. I’ll post things one at a time, as I encounter them, but if you’d like me to consolidate my feedback let me know!
In the “Amps Browser,” I found “Manage Tone Models” confusing. As someone with A LOT of models, this is an important one. I followed the steps and found it odd that it brought me to the Finder to manage these. Once I got there, I found a list of files with cryptic names. I have no idea how I’m supposed to manage my tone models here, and I’m guessing others will feel lost as well.
See screenshots for the steps I took. (I’m on an M4 Pro Mac Mini running Sequoia 15.7.7)
The one largest issue with tonex is no scenes with spillover. This makes it unusable in live situations, not being able to click between scenes or presets without 1 sound cutting out and 2 wet effects spilling over. I love the sound of tonex best, but without this it’s unusable live. Thanks for your time.
On the effects chain, I was expecting to click and drag down/up to turn the effects on/off. It would speed up the workflow to have this option.
The “TAP” and manual edit are not updating the tempo for me in Logic Pro (on M4 Pro Mac Mini running Sequoia 15.7.7). I can hear the delay repeats are locking with the host tempo, but it’s not clear that is what’s happening and when I change the tempo in the DAW it stays at “120” in TONEX. Are others experiencing this on PC and other DAWs?
The standalone version tempo works as expected (no issues), though I expected it to select the numbers when I double-clicked and I got a blinking cursor instead.
UPDATE: The tempo mapped to the correct bpm when I restarted Logic, but the tap and numbers do nothing. I would either make it obvious that the tempo is locked in the DAW or have the option to manually override the tempo. As it is now, the tempo function feels broken because I can still click the “TAP” button and edit the numbers (though they don’t stick.)
I’m with you on the ON/OFF function of the fx in the chain diagram.
just thought it would be quicker, not to have to activate it first and then turn it ON/OFF.
What I’m missing is the optical meter on the compressor. i love to have just a little bit of comp before the amp sim…and with the old version i could visualize it, when the comp kicks in and how much.
please bring this back to the comp fx.
I might have missed something but did 2.0 remove the ability to demo with DI tracks? I found that very useful.
I have Tonex Max. I loaded the newly added models and selected some as Favorites. However, when I open Amplitube 5 to load these Tonex models, the new ones don’t show up in the Favorites list - only the previous ones.
How do I get these new models to show up in the Tonex list in Amplitube so I can use them?
The pop up windows for the browser are nice but I would really appreciate having the option to open it on the side as well. Used to be easier. Also HUGE MISS The shorting models by clean drive Hi gain etc without filtering. Also the meter for compression is missing. Also would be a nice opportunity to add some customization like in amplitube for the IRs and Cabs. Also a Low pass High Pass filter would be huge. Missing a bit the ambiance with all the black background, used to add character. The amps though look nice and the full screen mode. Also the tuner being visible was nice on the prior version while playing. Now I have to engage it separately.
Also Subfolders would be nice, Now I have hundreds of folders. Also maybe the option for us to customize all the options. For example sometimes I don’t want to see recently used or favourites. Would be nice to be able to disable and customize the view to our workflow. Maybe also an automatic phase alignment for the cabs. I want to use two amps in cubase and I always get phase issues.
Each effect has a pre/post switch for this. That did not change from v1
This doesn’t work - and it also isn’t very clear. As someone who helps customers all day every day with tech stuff, this is sad.
This is on a Mac.
When you open your “Tone Model,” you want to select “Open Tone Model Amp Browser.” Once you get there, you have to go all the way to the right of an individual model, hover over where there is nothing to indicate that there is anything to click, and you will get the “…” and the star to add the tone model to your favorites. Like Peter-IK said, you click on “Manage Tone Models.”
Then you get an “Info” screen.
“Manage Tone Models and Presets directly in this folder.
After making changes, perform a “Refresh Library” from the TONEX Account panel to update your TONEX Library.”
The “this folder” links you to:
‘/Users/YOURUSERNAMEDocuments/IK Multimedia/TONEX/Library/ToneModels’
.txp files do not go into the ToneModels folder. And you cannot manage “Presets” in the “Tone Models” folder. Which means the “Info” panel is an embarrassing attempt to give users instructions. This is incredibly poor design and the interface is not intuitive.
I did add the *.txp files to the “Presets” folder at:
‘/Users/YOURUSERNAME/Documents/IK Multimedia/TONEX/Library/Presets’
I then refreshed my library; a few were there, but not all of them. Not even remotely close. Just a few new ones were there.
I’m being so hard on this because even if this is a beta, you should at the very least have an integral “Import” workflow process established and intuitive for the user. As of now, I have zero clue how to add purchased tones I’ve downloaded from places like Amalgam Audio or ChopTones or Strange Angles.
Insanely disappointing.
You are supposed to move the .txm files into the “ToneModels” folder. However, from my experience, everyone uses *.txp files (Preset files) to exchange models. The “Presets” are not in “this folder.” They are in their own folder lateral in that hierarchy. And, yes, I know I can find it, but I find it incredibly aggravating that this sort of thing gets past design support. I know it’s a beta, but at the very least have an intuitive “import” function.
Do those third parties provide instructions on how to import their tones into TONEX? Some of those also sell via ToneNET as Tone Partners which wouldn’t require instructions because there’s no manual file transfer required. But any third party should provide instructions.
That said, good note that if the process is changed that third party providers should get the information and those that are Tone Partners are definitely aware of and have used TONEX 2.0 Player but it would be good to make sure they’re informed. Being that they are third parties, though, a lot of that would on their side to make sure their customers do not have a hard time importing.
Your notes are received here as this is the beta feedback thread and I understand your frustration. It is a beta, your feedback will be heard.
Third parties never had to give instructions because it was just drag and drop. I will say I have used a ton of third party captures and I don’t recall a single .txm file, it is always .txp.
Any changes to the import of third party Tone Models/presets in 2.0 Public Beta have been noted as I stated above. I certainly didn’t mean to cause any offense by asking a question that was meant to help. Like I said, it has been noted officially and earlier I had mentioned this to our Testing Manager as well so doubly noted 
