Why is L/Mono outputting Left, not Mono? in Helix Posted August 19, 2022 On 8/18/2022 at 10:25 AM, theElevators said: I practice at home and at home I have 2 studio monitors plugged into left and right. Every once in a while I check whether the bug comes back by leaving only left/mono plugged in and rebooting my Helix. After a few days/weeks the issue resurfaces. If I do a system restore, it goes away. The problem is clearly with my Global Settings that I have, and those are pretty standard and nothing out of the ordinary. If this were a hardware problem, then this problem would always be there. However, the problem only comes back after a week when I recreate my specific Global Settings and simply use my Helix like people normally do. So let's please stop referring to it as a mechanical problem -- it clearly is not. Unless well.... a mechanical problem somehow corrupts my Global Settings ... it still would be a software bug. 2 Helixes I own, one was brand-new, Line 6 support recreated it a few years back. So bug bug bug. I bet you a lot of people have the same exact issue, they just don't know they have it. Heck, I only realized it 17!! songs into my set that I was only hearing my left side on stage at a gig. And only because of the prominent ping-pong delay that was simply not there. I can accept that there may be other Helix users out there who may have the same problem and are unaware of it, particularly given how long it can take for the bug to surface. As you indicated, only executing something like the ping-pong test in mono before every use would confirm the absence/presence of the bug for many users who output to summed mono. If I were starting from the premise that the problem has absolutely nothing to do with my hardware, as you assert, I think the next thing I would try would be the following two tests. Targeted towards ensuring it wasn't either a corrupted preset or a preset with just the right combination of variables to cause a bug. My rationale being that since the issue/bug doesn't pop up for days/weeks, perhaps it is an unfortunate intersection of my global settings and one or more of my presets. For someone who is gigging regularly and only had one Helix this might not even be feasible, given how long it takes to produce the bug, but if you still have two devices you could dedicate one to just doing these tests while you use the other one for gigs. Btw, these tests are also based on the premise that the bug does not occur for you using the factory default global settings. If it does, you would need to potentially add two more tests to recreate the bug. One using only the default globals and Factory presets. And the other using using the default globals and the combination of presets you use to perform/practice. Test 1 Use the Helix for a few weeks with only Factory presets and your preferred global settings. Does the bug appear? If it does, start restoring the factory default globals, one at a time, and retest until hopefully the issue no longer surfaces in an effort to nail down the particular global, or perhaps combination of global settings causing the problem. Test 2 Use the Helix for a few weeks with the combination of presets you use to perform/practice, and your preferred global settings. Does the bug appear? If it does, depending on the results from your other tests, you may have to start tracking down the problematic presets. Guess you have already confirmed the bug pops up in this scenario so perhaps you don't have to run Test 2 again. Any way you look at it this is definitely a tedious test process with no guarantee of success.