garryedgar Posted January 7 Share Posted January 7 HX One Firmware 3.81 and is set up in insert (4CM) configuration. I have observed the following behaviour for some time and only just now been able to replicate the issue consistently. Scenario 1: When moving from a PolyWham effect preset with the status ‘off’ to Feedbacker effect preset status ‘on’ or ‘off’ results in feedbacker effect not triggering. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario does not correct the feedbacker issue. Scenario 2: When moving from PolyWham effect preset status ‘on’ to Feedbacker effect status ‘on’ or ‘off’ results in results in feedbacker effect working as expected. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario also works as expected. This issue is occurring whether presets are navigated view Prev/Next midi command or by the in-built footswitch preset navigation. The same observations occur when moving from the PolyCapo effect to Feedbacker so it may be related to moving from pitcher shifting effects? This issue does not appear to occur if moving from another effect such as Dynamic Plate, Tube Comp 3 Note Generator to the Feedbacker effect. It also appears that if scrolling past another effect between PolyWham and Feedbacker resolves this issue e.g. if a had 3 presets in the sequential order PolyWham > Dynamic Plate > Feedbacker the issue is not observed when scrolling past between PolyWham to Feedbacker using the preset scroll function. It seems like the pitch shifting (PolyWham/PolyCapo) effect preset status is being passed on the feedbacker effect when navigating directly between the two irrespective of the saved Feedbacker preset status. Has anyone else had the same experience or can replicate this behaviour? Quote Link to comment Share on other sites More sharing options...
silverhead Posted January 7 Share Posted January 7 I don’t own or know much about the HX One so can’t really help with this particular issue. However, in addition to any response you get here I suggest you also open a support to report this. Any reproducible and unexpected behaviour is a potential bug and will only come to the attention of Line 6 for a fix if reported through the ticket system. Quote Link to comment Share on other sites More sharing options...
garryedgar Posted January 7 Author Share Posted January 7 Thanks, will do Quote Link to comment Share on other sites More sharing options...
ElmStreetVictim Posted January 15 Share Posted January 15 On 1/7/2025 at 7:13 AM, garryedgar said: HX One Firmware 3.81 and is set up in insert (4CM) configuration. I have observed the following behaviour for some time and only just now been able to replicate the issue consistently. Scenario 1: When moving from a PolyWham effect preset with the status ‘off’ to Feedbacker effect preset status ‘on’ or ‘off’ results in feedbacker effect not triggering. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario does not correct the feedbacker issue. Scenario 2: When moving from PolyWham effect preset status ‘on’ to Feedbacker effect status ‘on’ or ‘off’ results in results in feedbacker effect working as expected. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario also works as expected. This issue is occurring whether presets are navigated view Prev/Next midi command or by the in-built footswitch preset navigation. The same observations occur when moving from the PolyCapo effect to Feedbacker so it may be related to moving from pitcher shifting effects? This issue does not appear to occur if moving from another effect such as Dynamic Plate, Tube Comp 3 Note Generator to the Feedbacker effect. It also appears that if scrolling past another effect between PolyWham and Feedbacker resolves this issue e.g. if a had 3 presets in the sequential order PolyWham > Dynamic Plate > Feedbacker the issue is not observed when scrolling past between PolyWham to Feedbacker using the preset scroll function. It seems like the pitch shifting (PolyWham/PolyCapo) effect preset status is being passed on the feedbacker effect when navigating directly between the two irrespective of the saved Feedbacker preset status. Has anyone else had the same experience or can replicate this behaviour? Yes, man, YES, YES MAN. This is the issue, nearly word for word exact. Your experimentation has figured it out for me too. I can second OP. I am however on 3.80. At band practice the other night I was going to show the crew some dive bombs as well as some feedback, and neither of them worked right. Turns out, it does indeed look like HX One takes the current Pitch effect On/Off status, and uses this value when you switch to Feedbacker. If you are on a Pitch Capo effect (like -1 semitone) and toggle the effect to Off, just regular standard tuning, and then navigate to Feedbacker, the effect will not activate when using the footswitch to turn the effect on. The light turns bright yellow but no effect. If instead, you are on Pitch Capo, and the effect is ON, with the Pink light, and then you switch to Feedbacker, when you turn the effect on with the switch and the yellow light comes on, the effect now activates and works. I was also able to show this behavior on the Poly Pitch (dive bomb and slide effect). Going from this effect being toggled off, and navigating to Feedbacker, the feedbacker effect will not activate. Going back to Poly pitch and triggering it ON, then navigating to Feedbacker, the feedbacker effect works as expected. For now, I have had to set up the effect library ordering so that Feedbacker is at position 000 (the top), and then my Poly Pitch( slides and bombs) at 001, then -1 Semitone Poly Capo at 002, and -2 Semitone Poly Capo at 003, with both of these saved as ON. Default state for rehearsal is in Feedbacker til I need to turn it on. Scroll to Dive Bomb and I can turn that on or off at will. Next effect half step down, always ON, next full step down, always ON, so that if I go back to default state (feedbacker), that effect will work. Quote Link to comment Share on other sites More sharing options...
garryedgar Posted January 17 Author Share Posted January 17 Glad it's not just me!! I've logged a ticket with the line 6 team which has been acknowledged and I'll share any info I get back. Quote Link to comment Share on other sites More sharing options...
garryedgar Posted January 22 Author Share Posted January 22 My support ticket received the following update so hopefully the issue will be resolved in a future update! Hi, I can reproduce this and have escalated it for further testing Best regards Line 6 /Ampeg Support Europe 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.