dkijc Posted April 26, 2021 Share Posted April 26, 2021 Hey all! I recently came back to the helix world with the HX stomp xl and been loving it! I'm trying to have one of the up/down footswitches to have 'hold' behaviour to toggle between two snapshots. All the switches from A-D work fine (I press a switch to go to one snapshot, and hold the same switch to go back to another). But the up and down footswitches do not seem to like hold command and does not toggle between two snapshots. Is there some global settings I need to set for custom commands for those switches? Thank you!! EDIT: phil_m suggested to turn on 6 stomp switch mode. This is happening even when that option is enabled :( Quote Link to comment Share on other sites More sharing options...
phil_m Posted April 26, 2021 Share Posted April 26, 2021 You have to have 6 Stomps under Global Settings>Footswitches>Stomp Switches in order to assign commands to those switches in the Command Center. Quote Link to comment Share on other sites More sharing options...
dkijc Posted April 26, 2021 Author Share Posted April 26, 2021 Thanks for the reply! I definitely have that on, already :). Quote Link to comment Share on other sites More sharing options...
phil_m Posted April 26, 2021 Share Posted April 26, 2021 44 minutes ago, dkijc said: Thanks for the reply! I definitely have that on, already :). I don’t know then. Are you running the latest firmware? I’ll have to take a look at it on mine tonight. Quote Link to comment Share on other sites More sharing options...
dkijc Posted April 26, 2021 Author Share Posted April 26, 2021 Yeap. I just updated to 3.1. Yea, I'd love to see what you get! I tried on all the switches (except the mode/tuner) and it's just the arrow switches that don't want to behave... Quote Link to comment Share on other sites More sharing options...
phil_m Posted April 27, 2021 Share Posted April 27, 2021 5 hours ago, dkijc said: Yeap. I just updated to 3.1. Yea, I'd love to see what you get! I tried on all the switches (except the mode/tuner) and it's just the arrow switches that don't want to behave... I'm observing the same thing you reported, so I'd say this is a bug. I'll report it to the people who need to see it. Quote Link to comment Share on other sites More sharing options...
dkijc Posted April 27, 2021 Author Share Posted April 27, 2021 Ah. Glad to be a QA. haha Thank you @phil_m ! (Talked to another person and he also said this is a bug.) Quote Link to comment Share on other sites More sharing options...
dkijc Posted May 3, 2021 Author Share Posted May 3, 2021 Hi @phil_m How often do they release a bug fix? Thank you :) Quote Link to comment Share on other sites More sharing options...
silverhead Posted May 3, 2021 Share Posted May 3, 2021 9 hours ago, dkijc said: Hi @phil_m How often do they release a bug fix? Thank you :) There’s no set schedule. They are continually fixing bugs and bundle them into the next feature release. Sometimes there is a release that is exclusively bug fixes. This usually happens soon after a major feature release when new high priority bugs have been identified and need to be fixed quickly. This happened most recently with release v3.11. It contains nothing but priority bug fixes from release v3.10. Now it’s back to usual practice; the next set of bug fixes will be included in the next feature update, v3.20 or whatever. And there’s no predicting when that may happen. There’s no guarantee that this particular bug will be fixed in the next release but that’s likely the earliest that it can be anticipated. Quote Link to comment Share on other sites More sharing options...
dkijc Posted May 3, 2021 Author Share Posted May 3, 2021 1 hour ago, silverhead said: There’s no set schedule. They are continually fixing bugs and bundle them into the next feature release. Sometimes there is a release that is exclusively bug fixes. This usually happens soon after a major feature release when new high priority bugs have been identified and need to be fixed quickly. This happened most recently with release v3.11. It contains nothing but priority bug fixes from release v3.10. Now it’s back to usual practice; the next set of bug fixes will be included in the next feature update, v3.20 or whatever. And there’s no predicting when that may happen. There’s no guarantee that this particular bug will be fixed in the next release but that’s likely the earliest that it can be anticipated. I DID not even know 3.11 is out haha. and thankyou so much for the detailed insight~ I figured as much it's not a set schedule. Sometimes, I wonder if companies should have a public backlog of the bug items (both found by your qa and users) and allow people to only search and view items that's been reported. Then let people 'vote' on either the bug they've also found or would like to be fixed. Kill two birds with one stone; user feedback and help you prioritize. :D One could dream, right? haha Anyways, really appreciate the response. Have a great week! Quote Link to comment Share on other sites More sharing options...
silverhead Posted May 3, 2021 Share Posted May 3, 2021 There is a feature request site called Ideascale where users can post, review, and vote on their collective ideas. It mostly deals with new feature requests but there's nothing stopping users from using it to report and prioritize bugs. Just not being used that way at the moment. Currently the way to report bugs is to open a support ticket. Line 6 prioritizes bugs based on their severity and also frequency as reported by the ticket system. Essentially a reported bug is a vote for it to be fixed. That's why it's important for users to report any bugs they find, even if they know it's already been reported. The number of times a bug has been reported (i.e. the number of users bothered enough by the bug to report it) is considered by Line 6 in their prioritization. 1 Quote Link to comment Share on other sites More sharing options...
dkijc Posted May 12, 2021 Author Share Posted May 12, 2021 On 5/3/2021 at 9:44 AM, silverhead said: There is a feature request site called Ideascale where users can post, review, and vote on their collective ideas. It mostly deals with new feature requests but there's nothing stopping users from using it to report and prioritize bugs. Just not being used that way at the moment. Currently the way to report bugs is to open a support ticket. Line 6 prioritizes bugs based on their severity and also frequency as reported by the ticket system. Essentially a reported bug is a vote for it to be fixed. That's why it's important for users to report any bugs they find, even if they know it's already been reported. The number of times a bug has been reported (i.e. the number of users bothered enough by the bug to report it) is considered by Line 6 in their prioritization. That's awesome to know!! Sorry for the late reply! Been really busy :) 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.