Also with a small company where some highly motivated folk work night and day and are idealistic and inspired, at least I would think twice about having a bit of respect for what they achieved and cut them some slack compared to big company guys with 4 day work weeks, big company cars and 6 figure salaries, who likely care more about their stock portfolio than customer needs or product quality.
let’s not assume that most amp sim developers are like this. Certainly the guys I’ve spoken to are extremely passionate and aren’t doing their job as some kind of cash grab. The industry is full of great talents and characters and the more the merrier.
This is a discussion forum, people are going to discuss whatever thoughts arise. TMT have literally based the defining features of this product based on user feedback about other products - if customers (or potential customers) are giving feedback, it’s very valuable for the company to listen. Without that, Tonocracy wouldn’t have the input calibration system, cloud training, queued captures etc.
There’s plenty of praise for the positive aspects in this thread, and also plenty of valuable feedback about areas to improve. It’s all very useful - this thread would go in the toilet if it’s just high fives and pats on the back.
I think it’s fair that if were to look at Tonocracy as first and foremost about capturing amps accurately, and anything else is a bonus (rather than an all in one solution) then it’s probably best to look at ToneX like that, because they’ve purposefully left out things so it doesn’t tread on Amplitubes toes.
Regarding frequent updates/additions - it’s a lot harder to maintain a stable release across different systems, and without borking old sessions. It’s great to have stuff added, but if it means old sessions sound different, or crashes happen more frequently, then I’d rather have fewer but more reliable updates. Most companies adopt this approach as it can be an absolute drain on resources to be playing cat and mouse with updates/fixes. This is why seeing a product released that doesn’t look finished gives me some pause - beta testers may have an idea of how fast things get added and how stable things have been, but users have no idea. Theres also no guarantee that things will remain that way, so you’re hoping that things eventually sort themselves out without knowing if you’ll be left on a buggy version where you can’t connect to a server and do anything. Products often become quite bloated if things are added as you go, rather than designing it as a complete product from the start. It’s a lot easier to make a slick and focussed product with careful planning and refinement/trimming the fat that adapting as you go.
Hopefully everything goes well, but there’s just so many things that are making me hesitant about diving in.
![[Nathan]](/data/avatars/m/0/613.jpg?1726885163){kind=avatar}
