POD Go effect block MIN/MAX stomp switch bug

[zreed]

I've been encountering a bug since updating to v 2.50 with some of my presets. 

 

When assigned to a parameter of an effect block, my understanding of the stomp switches is:

• OFF: Effect block parameter is at MIN value. Switch LED dimmed. LCD screen dimmed. 
• ON: Effect block parameter is at MAX value. Switch LED full brightness. LCD screen full brightness. 

 

However, my POD Go is doing the opposite of what I think it should. When the stomp switch is OFF, the effect block parameters are at MAX value, and when the stomp switch is ON, the effect block parameters are at MIN values. 

I'm wondering if anyone else out there has had the issue as well. 

I have four stomp switches assigned to control parameters in a number of effect blocks:

• FS2: "DELAY", Dual Delay Parameters
• FS3: "VERB", Dynamic Hall Reverb Parameters
• FS5: "DRIVE", Dhyana Drive (on/off)
• FS6: "BOOST", EQ Block Parameter (+3db volume boost)

 

In addition, I'm using Snapshots to save on/off combinations of these four switches:

• Snapshot 1: All off
• Snapshot 2: FS5 on
• Snapshot 3: All on
• Snapshot 4: FS6 on, Reverb decay set to 10.0 sec (normally MIN of 3 sec, MAX of 5.8 sec)

 

What's going on? The Line6 Customer Support rep handling my ticket said, "There isn't anything wrong with your preset or Pod Go." But I can't think of any other device I've ever used where when the light is "on" the effect is "off". 

Bugged Preset.pgp

[silverhead]

Is there any actual performance issue or is it just a display issue for you?

 

This may also be affected by the state the preset was in when last SAVEd. Try experimenting with different saved states.

 

Or, could also be affected by the Global Settings for Snapshot Edits if you happen to turn on/off any FX manually while in any given snapshot..

[zreed]

Here's a video of the bug in action: 

 

 

Quote

Is there any actual performance issue or is it just a display issue for you?

There's an actual performance issue. The device applies the effect parameters, but in the inverse to what's shown on the GUI of the device and the footswitch. The POD Go software correctly shows what current values are being applied.

For example, I've got FS3 set up as follows:

• ON: Big reverb
• OFF: Smaller reverb

When this error starts, the Big reverb effects occur when the footswitch and the GUI show the effect block as OFF, and the small reverb effects occur when the effect block is ON. 

This is a little frustrating when I'm in the middle of a performance and I want to turn on an effect, but the opposite happens. 

 

Quote

This may also be affected by the state the preset was in when last SAVEd. Try experimenting with different saved states.

I have. :( 

It seems that regardless of what I do, once the bug manifests, no amount of resaving or playing with the levels change it. 
 

Quote

Or, could also be affected by the Global Settings for Snapshot Edits if you happen to turn on/off any FX manually while in any given snapshot..

 

I've got the Snapshot Edits setting set to "Recall". I play around with it set to "Discard" and see what happens. 

[zreed]

It looks like I'm not the only one to encounter this. I thought it was a bug with v2.50, but this video is from two years ago. 

[zreed]

This guy has had the same issue and offers a fix by editing the .pgc file. 

Some chain of events leads to the "@fs_enabled" parameters between "block" and "Mix" sections changing from either both being true or false, to one being true while the other is false. He points this out at around 9:49.