# Major issues with TONEX 2.1.1 VST3 Plugin Parameter Automation

**URL:** <https://forum.ikmultimedia.com/t/major-issues-with-tonex-2-1-1-vst3-plugin-parameter-automation/1327>\
**Category:** Guitar\
**Tags:** support\
**Created:** [October 8, 2026, 1:12am UTC](https://forum.ikmultimedia.com/t/major-issues-with-tonex-2-1-1-vst3-plugin-parameter-automation/1327 "2026-10-08T01:12:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CSpace\_Sound](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.ikmultimedia.com/cspace_sound/32/650_2.png) [@CSpace\_Sound](https://forum.ikmultimedia.com/u/CSpace_Sound)\
**Post date:** [October 8, 2026, 1:12am UTC](https://forum.ikmultimedia.com/t/major-issues-with-tonex-2-1-1-vst3-plugin-parameter-automation/1327/1 "2026-10-08T01:12:18Z")

</div>

I have already submitted a support request for this, but I wanted to also post here both to vent some steam and in the unlikely event that someone can help.

I have been using TONEX for more than a year, and up until now have been very happy with it. I just updated to 2.X, and have encountered what I consider to be show stopping bugs.

First, and I’ll preface this by saying I’m probably going to hear that this was “by design”, automation compatibility has been completely broken. Parameters such as “Gain” are now gone and in their place we have “Knob01”, “Switch02”, etc. and you have to go into the TONEX GUI to assign the parameter you want to one of the generic parameter names. So if I want “Gain” for example, I would click on the gain knob on the amp model and assign it to “Knob01”, and in my DAW I would automate Knob01.

This is all well and good, and I assume it was revamped like this in order to support the TONEX Rig with the larger number of effects, etc. BUT, for someone like myself who has lots of pre-existing projects which include the automation of various TONEX parameters, it is an absolute nightmare. I have to go through every project and look at every guitar track to see which have automation, then go through the aforementioned workflow before reassigning the automation envelope to the new parameter name. Honestly, I’m amazed that someone thought it was acceptable to break compatibility in this way.

So that was the venting portion, now on to the “real” bug. Even when configuring automation the new way and setting it up in my DAW, it doesn’t work _unless_ the TONEX VST GUI is open. During playback, no automation initially, but as soon as you open the VST GUI it works. Then if you close it it stops working. Obviously not a viable thing when you have multiple guitar tracks. I have not tested to see if it works when bouncing to a mix, but I doubt that it will given what I’ve seen during playback.

Anyway, I am pretty frustrated at this point. I’ve been an enthusiastic TONEX advocate for over a year now, and I was excited to upgrade and even purchased TONEX Rig. I now seriously wish I’d followed better judgement and held off on upgrading.

---

<div class="post-metadata">

**Author:** ![skinnygriftin](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@skinnygriftin](https://forum.ikmultimedia.com/u/skinnygriftin)\
**Post date:** [October 8, 2026, 1:35am UTC](https://forum.ikmultimedia.com/t/major-issues-with-tonex-2-1-1-vst3-plugin-parameter-automation/1327/2 "2026-10-08T01:35:07Z")

</div>

![First Time Meme: Man with Noose](https://canada1.discourse-cdn.com/flex034/uploads/ikmultimedia/original/1X/48e730576d177e4792d319a8b98c4929096848b4.webp)