Fuzz, Input Impedance and why the auto setting "must" be fixed! The ultimate thread! in Helix Posted September 12, 2017 What's the problem with Helix? Other devices set the input impedance to match the fist active effect. In the video example, what effectively is happening is that when I have the Fuzz Face first, it does't matter what goes after it, Helix will stick to the same front end. When I turn it off, what's happening is that I have the amp with the front end of a Fuzz Face, that's why it sounds wrong. It's like putting a pig nose on a fish. In the analog world I could build the fish with the pig nose while still making it true bypass. Do you get that? I's "NOT" about bypass. First... I agree with you, or at least your premise. I used the word bypass, cause that's what the little button reads.. here's a little closer to what's really happening. When you pre-compile two subroutines, one with two functions, one with one function. If you have code that doesn't execute the first function, both subroutines should have the same output. This is what you video proves and I agree... It's not right. There's no impedance, bypass or any other ANALOG routine in the code stack. I find it hard to believe they modeled what a fuzz does in bypass. Maybe they did... but it seems silly considering, "turning off" something in the chain should mean that code isn't executing at all. Further it would mean they modelled all of the devices in the off position as well, or that "off" means different things to different devices... that's just seems silly to me. Possible, but a bit silly. In any case... I still agree with you... something is not right.