paulgbell

I just had the same problem. I had two cabinets inline on one of my patches. When I selected that patch, it went silent. Switching to other patches doesn't bring the sound back. I tried many different patches. I was able to bring it back by switching to another patch and rebooting. As soon as I went back to the patch with the two cabinets, silence. I removed one of the cabinets on that patch and saved it. Then rebooted again. That seems to have cleared it up for me. Fortunately, I don't normally use two cabinets inline so I'm hoping to avoid this problem in the future. I don't have time to log an issue, but may later when I have time to reproduce the problem.

I have many patches where I assign multiple parameters (bypass, drive, A/B Switching, etc.) to a single footswitch. Often I'm turning on one or more effects and turning off one or more others. For example, "off" might be a compressed clean sound running through a Fender amp, and "on" might turn off compression and turn on a distortion pedal with a chorus, so I might call it "Distorted" or "Chorus". On my old Helix Floor, the last effect assigned to the footswitch determined the color and lit/unlit state. The editor allows me to pick the color if I don't like the default, but not what the lit/unlit state is. It wasn't a big deal because I would just have the label determine what the lit state was so that if I want that state, I need to press the footswitch. On the Helix Stadium XL, the color and lit/unlit state seem to change almost every time I switch to the patch. This makes it impossible to know what state the patch is in. I could define the label to match the lit state, but the next time I use the patch, it could be reversed and the color might be different if I didn't define it. I'm hoping to get a resolution to this issue in an upcoming update. I'd like the footswitch lit/unlit states more consistent as well as the color. Allowing the user to choose when the footswitch is lit or not lit would be nice, but it might be difficult to implement without making things too complicated or confusing for the user. Just making it predictable and consistent should be enough. Thanks, Paul