Odd parameter automation behavior after Max v2 Upgrade

AmpliTube TONEX, AmpliTube 5, AmpliTube Custom Shop, AmpliTube Joe Satriani, AmpliTube Brian May, MESA/Boogie®,Orange™, Fender™, Hendrix™, Metal, AmpliTube SVX, and more for Mac/PC

Odd parameter automation behavior after Max v2 Upgrade

Postby MainePatr1ot » Tue Jan 28, 2025 11:50 pm

I have several Reaper project files that use envelopes to bypass certain Amplitube FX. Before upgrading to Amplitube Max v2, setting the envelope value high set the bypass state. Bringing it to zero removed the bypass state (effectively turning the FX on).

So, to turn on a given pedal, such as a delay, I would bring the bypass envelope to 0. I have a couple dozen Reaper projects like this and they've worked fine for years.

Then I upgraded to Amplitube MAX v2. Since then, bypass envelopes set to 0 no longer behave reliably. Sometimes it will work, but most of the the time a value of 0 no longer turns the FX pedal on (removes the bypass state). Instead, I have to set it to slightly above 0 to turn the FX on reliably.

This change of behavior happened immediately after upgrading to MAX v2. These Reaper projects files are for live shows and have been behaving reliably for over a year before the upgrade.

I'm curious if this or anything similar has happened to anybody else?

This is all being run on an HP laptop running Win10 and the latest version of Reaper.

Thoughts?
MainePatr1ot
 
Posts: 2
Joined: Sun Mar 20, 2022 8:35 am

Re: Odd parameter automation behavior after Max v2 Upgrade

Postby MainePatr1ot » Wed Jan 29, 2025 5:50 pm

Some images to help explain:

Here, I cheated the envelope value up a little bit to make it a non-zero value. In this case, the "low" state is honored and the bypass state is UNset (FX is switched on):
https://drive.google.com/file/d/13YmpK1_emVv9RiVD2ivRIAXVjLyAXBKk/view?usp=sharing

Here is the way the bypass envelope was for over a year before my upgrade to MAX v2. The full-low value of 0 was always honored as a bypass-UNset state, turning the FX on. Now, a 0 value is ignored and the FX remain off (bypassed):
https://drive.google.com/file/d/1e_Cu1yuZ_1VOyPOZ8vQNuajQmeKgsjsf/view?usp=sharing

This happens in delays and other FX, too, in other Reaper projects, some of which I've been using for years without issue. This issue of ignoring 0-values in envelopes only started after my recent upgrade to MAX v2.
MainePatr1ot
 
Posts: 2
Joined: Sun Mar 20, 2022 8:35 am

Re: Odd parameter automation behavior after Max v2 Upgrade

Postby R0lias-tg » Tue Feb 04, 2025 3:47 am

I would suggest submitting that to tech support.
User avatar
R0lias-tg
 
Posts: 47
Joined: Mon Jan 16, 2023 10:10 pm


Return to AmpliTube & TONEX Guitar Amp & FX