talwilkins Posted October 23, 2017 Share Posted October 23, 2017 When i use the Wah with auto engage function I notice a problem. I have the wah turn off at heel down position (0%) and engage at 1% The wait parameter is set at 1000ms (1 second) When I rock the footpedal back and forth, never being at heel down position for 1second, the wah still turns off every now and then. This is really annoying. Does anyone else experience this? Is there a way to avoid this? Is it a bug? 1 Quote Link to comment Share on other sites More sharing options...
talwilkins Posted December 9, 2017 Author Share Posted December 9, 2017 Anyone? Quote Link to comment Share on other sites More sharing options...
duncann Posted December 9, 2017 Share Posted December 9, 2017 Just tried with your settings and the onboard pedal. I did notice that if you operate the pedal quickly, going through its range multiple times, starting from the toe position, it takes anywhere from 3 or 4 seconds (with an operating frequency of about 1s per full range and back) before the wah block disengages. What's even weirder is you can be about halfway through the test, stopping at the toe position, come back later and continue the test as if you hadn't stopped at all. So from toe to toe twice (about 2 seconds), stopping at the toe position for however long, then after 1.5 or 2.5 more counts you can see the wah block disable immediately upon hitting the heel postion. This definitely seems like a bug. Quote Link to comment Share on other sites More sharing options...
talwilkins Posted December 9, 2017 Author Share Posted December 9, 2017 Thanks for reacting and testing this. I have opened a ticket. Quote Link to comment Share on other sites More sharing options...
TLF2007 Posted December 10, 2017 Share Posted December 10, 2017 Thought it was me... thanks for the post. Quote Link to comment Share on other sites More sharing options...
Pezza Posted December 12, 2017 Share Posted December 12, 2017 I'm experiencing exactly the same behaviour. It makes the auto engage function all but unusable for me. Hopefully it'll be fixed in the next update. Quote Link to comment Share on other sites More sharing options...
a2dconverterguy Posted December 12, 2017 Share Posted December 12, 2017 Hey Tal, It looks like there is a counter that adds up the time that you hit 0% while playing the wah... When the time that you hit 0% in multiple instances exceeds the Wait time, the Wah is Bypassed momentarily. (i.e. lets say your wait time is 1000mS and, during your wah-ing, you momentarily hit 0% four times for 250mS... on the last time you hit 0% the Wah will bypass momentarily) It should work like this: The counter should reset to zero every time you do not remain at 0% for the bypass Wait time. Hopefully Line 6 will identify this and correct it in the next FW update. @Digital_Igloo Seeya Joe 1 Quote Link to comment Share on other sites More sharing options...
talwilkins Posted December 12, 2017 Author Share Posted December 12, 2017 Hey Tal, It looks like there is a counter that adds up the time that you hit 0% while playing the wah... When the time that you hit 0% in multiple instances exceeds the Wait time, the Wah is Bypassed momentarily. (i.e. lets say your wait time is 1000mS and you momentarily hit 0% four times for 250mS... on the last time you hit 0% the Wah will bypass momentarily) It should work like this....the counter should reset to zero every time you do not remain at 0% for the bypass Wait time. Hopefully Line 6 will identify this and correct it in the next FW update. @Digital_Igloo Seeya Joe Sounds as a plausible programming error. I made a support ticket for it so let's see what Line6 says. I'll keep you all posted Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted December 12, 2017 Share Posted December 12, 2017 Hey Tal, It looks like there is a counter that adds up the time that you hit 0% while playing the wah... When the time that you hit 0% in multiple instances exceeds the Wait time, the Wah is Bypassed momentarily. (i.e. lets say your wait time is 1000mS and you momentarily hit 0% four times for 250mS... on the last time you hit 0% the Wah will bypass momentarily) It should work like this....the counter should reset to zero every time you do not remain at 0% for the bypass Wait time. Hopefully Line 6 will identify this and correct it in the next FW update. @Digital_Igloo Seeya Joe Sounds as a plausible programming error. I made a support ticket for it so let's see what Line6 says. I'll keep you all posted You may want to update your ticket with the observations from a2dconverterguy. They should give Line6 a leg up on identifying the bug more quickly. Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted December 12, 2017 Share Posted December 12, 2017 Hey Tal, It looks like there is a counter that adds up the time that you hit 0% while playing the wah... When the time that you hit 0% in multiple instances exceeds the Wait time, the Wah is Bypassed momentarily. (i.e. lets say your wait time is 1000mS and you momentarily hit 0% four times for 250mS... on the last time you hit 0% the Wah will bypass momentarily) It should work like this....the counter should reset to zero every time you do not remain at 0% for the bypass Wait time. Hopefully Line 6 will identify this and correct it in the next FW update. @Digital_Igloo Seeya Joe This sounds eminently plausible. Did you derive this from Tal's post or was this the result of testing? Quote Link to comment Share on other sites More sharing options...
a2dconverterguy Posted December 13, 2017 Share Posted December 13, 2017 Hey H. O. My testing confirmed the bug.... it is very easy to replicate.... Hopefully this will be fixed in the next update Seeya Joe Quote Link to comment Share on other sites More sharing options...
talwilkins Posted December 14, 2017 Author Share Posted December 14, 2017 You may want to update your ticket with the observations from a2dconverterguy. They should give Line6 a leg up on identifying the bug more quickly. I updated the ticket. Thaks for the suggestion! 1 Quote Link to comment Share on other sites More sharing options...
a2dconverterguy Posted December 14, 2017 Share Posted December 14, 2017 Here is a video showing the problem... Quote Link to comment Share on other sites More sharing options...
a2dconverterguy Posted December 17, 2017 Share Posted December 17, 2017 I opened a ticket as well and I attached a link to the video that explains the problem... Line 6 support responded that they would present this to the team to see if they are aware of it. Seeya Joe Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted December 17, 2017 Share Posted December 17, 2017 Hey Tal, It looks like there is a counter that adds up the time that you hit 0% while playing the wah... When the time that you hit 0% in multiple instances exceeds the Wait time, the Wah is Bypassed momentarily. (i.e. lets say your wait time is 1000mS and, during your wah-ing, you momentarily hit 0% four times for 250mS... on the last time you hit 0% the Wah will bypass momentarily) It should work like this: The counter should reset to zero every time you do not remain at 0% for the bypass Wait time. Hopefully Line 6 will identify this and correct it in the next FW update. @Digital_Igloo Seeya Joe I updated the ticket. Thaks for the suggestion! Thanks for addressing this! Quote Link to comment Share on other sites More sharing options...
ric1966 Posted January 23, 2018 Share Posted January 23, 2018 Any update on the resolution? Quote Link to comment Share on other sites More sharing options...
glombi_72 Posted January 24, 2018 Share Posted January 24, 2018 Thanks, I have this exakt same issue. I use the toe switch at the moment, but would prefer auto engage... Quote Link to comment Share on other sites More sharing options...
talwilkins Posted January 24, 2018 Author Share Posted January 24, 2018 Hey, I totally forgot to update the thread :unsure: This was the response from L6: Hi, Unfortunately this is a bug in the Helix at the moment. It is slated for a fix in the next release. thanks for your patience. I believe the next update is due soon, right? Quote Link to comment Share on other sites More sharing options...
ric1966 Posted January 24, 2018 Share Posted January 24, 2018 Good news! Thanks for the update. Quote Link to comment Share on other sites More sharing options...
spikey Posted January 25, 2018 Share Posted January 25, 2018 Hey, I totally forgot to update the thread :unsure: This was the response from L6: Hi, Unfortunately this is a bug in the Helix at the moment. It is slated for a fix in the next release. thanks for your patience. I believe the next update is due soon, right? Thanks for the info! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.