jacobmilton Posted January 24, 2017 Share Posted January 24, 2017 Hi! I love this product in almost all aspects. I've had one problem though and I would be so pleased if anyone can help. I have the latest firmware installed and my own settings, nothing wierd at all. The expression pedal on the board is first in my chain, and it's set to controll the volume. The setting for my expression pedals are set to "global". Problem: Sometimes when I play the sound suddenly drops very low or turns of completely. Then I have to move the expression-pedal down and up again (0 to 100), and the sound is back. I mostly use the "phones" outlet right now, as I'm in my home studio but the problem should probably be with the other outputs as well. As you understand this is totally unacceptable since I could be on stage and my sound just dies. Please help! / Jacob M Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted January 24, 2017 Share Posted January 24, 2017 If you have your volume block set to be controlled with EXP1, change it to EXP2. That seemed to do the trick for me. EXP2 is default for volume. EXP1 is default for wahs. Quote Link to comment Share on other sites More sharing options...
jacobmilton Posted January 24, 2017 Author Share Posted January 24, 2017 Thanks for the quick respons! Is there a way to get notifications when someone answers a post? Ok, so that could be it. I'm using one external exp-pedal too. With that one I controll the volume of a separate chain, where I have a delay etc. This one was set to nr. 2. Maybe if i switch places on these babies or what do you think? Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted January 24, 2017 Share Posted January 24, 2017 1. If someone quotes your post, then you should get a notification. If it is not quoted, then no notification. 2. The issue seems to be with the on board expression pedal and volume block assignment. Using the onboard pedals, I set all of my volume blocks to EXP2, and wahs to EXP1. I use an external EXP3 for everything else. I don't have any issues with volume drop after doing this. I am also on v2.12. Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted January 24, 2017 Share Posted January 24, 2017 Thanks for the quick respons! Is there a way to get notifications when someone answers a post? Ok, so that could be it. I'm using one external exp-pedal too. With that one I controll the volume of a separate chain, where I have a delay etc. This one was set to nr. 2. Maybe if i switch places on these babies or what do you think? I just quoted this so you can see if you get a notification. Quote Link to comment Share on other sites More sharing options...
jacobmilton Posted January 24, 2017 Author Share Posted January 24, 2017 1. If someone quotes your post, then you should get a notification. If it is not quoted, then no notification. 2. The issue seems to be with the on board expression pedal and volume block assignment. Using the onboard pedals, I set all of my volume blocks to EXP2, and wahs to EXP1. I use an external EXP3 for everything else. I don't have any issues with volume drop after doing this. I am also on v2.12. Thank you so much for your quick respons! I really appreciate it! Since I'm controlling two volume blocks with two different exp-pedals, as explained above, I will probably have a problem until Line 6 does something about this, right? Did you understand my signal chain? It's the same idea as the one being shown in the official video on Line 6, about wet/dry/wet. Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted January 24, 2017 Share Posted January 24, 2017 Thank you so much for your quick respons! I really appreciate it! Since I'm controlling two volume blocks with two different exp-pedals, as explained above, I will probably have a problem until Line 6 does something about this, right? Did you understand my signal chain? It's the same idea as the one being shown in the official video on Line 6, about wet/dry/wet. Yes, I think so. On board expression pedal set to EXP1 for controlling volume of chain A. External pedal assigned to EXP2 for controlling volume of the other chain. I have the same type of physical set up, but set up on board for EXP1/EXP2 and the external as EXP3. So in your case, change chain A for the on board pedal to EXP2, and the volume for chain B for EXP3. You should be in good shape doing it that way. Quote Link to comment Share on other sites More sharing options...
jacobmilton Posted January 24, 2017 Author Share Posted January 24, 2017 Yes, I think so. On board expression pedal set to EXP1 for controlling volume of chain A. External pedal assigned to EXP2 for controlling volume of the other chain. I have the same type of physical set up, but set up on board for EXP1/EXP2 and the external as EXP3. So in your case, change chain A for the on board pedal to EXP2, and the volume for chain B for EXP3. You should be in good shape doing it that way. I understand, thank you! Hope this will work. How do we make sure that Line 6 gets notified about this bug? Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted January 24, 2017 Share Posted January 24, 2017 I understand, thank you! Hope this will work. How do we make sure that Line 6 gets notified about this bug? They already know about it. We all thought it would have been taken care of in v2.12, but it wasn't. Quote Link to comment Share on other sites More sharing options...
MusicLaw Posted January 24, 2017 Share Posted January 24, 2017 At least we know the pre-announcement of Firmware 2.20 is slated for February. Hopefully, this persisting bug will be resolved with the arrival of 2.20. If not, HELIX NATIVE's rollout was pre-announced for April. And, it is possible that a successor firmware release to 2.20 could occur after February and before April. It is already shaping up to be a feature rich 2017 for HELIX!! Quote Link to comment Share on other sites More sharing options...
MonkeyXT Posted January 25, 2017 Share Posted January 25, 2017 I guess this hasn't happened here, but Line 6's Frank specifically posted on The Gear Page that the Helix Team has indeed truly identified the exact cause of the issue, and it will be addressed. Quote Link to comment Share on other sites More sharing options...
jacobmilton Posted January 25, 2017 Author Share Posted January 25, 2017 They already know about it. We all thought it would have been taken care of in v2.12, but it wasn't. At least we know the pre-announcement of Firmware 2.20 is slated for February. Hopefully, this persisting bug will be resolved with the arrival of 2.20. If not, HELIX NATIVE's rollout was pre-announced for April. And, it is possible that a successor firmware release to 2.20 could occur after February and before April. It is already shaping up to be a feature rich 2017 for HELIX!! I guess this hasn't happened here, but Line 6's Frank specifically posted on The Gear Page that the Helix Team has indeed truly identified the exact cause of the issue, and it will be addressed. Thanks for the follow up everybody! I'm so glad I started to write in this forum! I actually changed my settings after the tips in this thread and haven't had any problems since, but hopefully we can chose this as we please when it's fixed. 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.