Panama Amp not functioning properly

[jhamilton85]

This issue arose with the most recent 1.22 firmware update.

 

If I boot up my Pod Go on a preset other than my two primary rhythm tones that use the PANAMA amp, and then switch to the PANAMA, the gain is all sorts of messed up. It sounds like I have everything set to 0. However, if I boot the Pod Go up with one of these two already being selected they sound exactly as they should. BUT, if I switch off of one of these two presets and then go back to them, it will do the weird no gain tone.

 

I haven't found a solid answer online about how to roll back a firmware update, or if it is even possible. Hoping someone here has an answer. Otherwise, I guess I will be opening a support ticket with Line 6.

[spaceatl]

are you sure you haven't somehow saved a scene and it's recalling that weird set scene....It sorta sounds like there is a scene in there you are not expecting? Not sure but that is all that comes to mind.

[voxman55]

I'm with @spaceatl - it sounds like your settings may possibly have gone awry somewhere eg you may have set up snapshots and/or made certain assignments that might not be quite right to achieve what you need.  If your patches are simpler with no snaps or assignments, then I'd suggest recreating these (but don't use the 'copy' facility in case you recreate the problem) and allocating these to different patch numbers - if those work correctly, delete the other patches. 

 

If you were using snaps/assignments you could still try to recreate these but there may be no benefit doing this as you might inadvertently simply repeat a possible error (not saying you have, but it's probably the most reasonable possibility at the moment). 

 

If you are positive you have set up your patches correctly and it's only since v1.22 that you've had the problem on patches that were otherwise working fine, you might have a software glitch.  I recommend you back up your patches and try a system reboot back to factory & then reload your patches.  If you still can't solve the issue, then I'd back up your patches and reload v1.22 to see if that solves the problem.  If that doesn't work, then raise a ticket with Line 6 Support and give them a full description of your problem and the actions you've already tried, with a full backup file, to see if they can replicate the problem or spot where your patch settings might possibly have gone awry.   

 

Are you using Pod Go Edit?  If yes, great but if not I'd strongly urge you to use this as it makes creating patches and troubleshooting much easier. 

 

One last thing - we are expecting v1.30 'imminently' (see here for the latest & greatest info: https://line6.com/support/topic/61582-pod-go-130-update-nearly-there-26-sep-sweetwater-v130-video-and-some-info-on-upgrades/ )