codamedia Posted May 6, 2018 Share Posted May 6, 2018 I use a toggle to switch between a compressor and a light overdrive (Timmy). They both assign to the toggle no problem, and the toggle works fine. BUT - the LED is inconsistent as to which state I should be in. I give the toggle a custom name of "Light OD" so the thought is when the LED is off the compressor is engaged and when it is on the Overdrive is engaged. The problem is... the HX has a mind of it's own which state it will show. I get it working right, save it. Come back to that patch later and it shows "OFF" yet the overdrive is the one engaged. I know that by touching the toggle I can show the states of the two effects... but I would think after saving the patch it should always RECALL the way I saved it. For the record, I am not using snapshots. Any idea's why it is behaving this way? The HX Effects is up to date with firmware version 2.54 EDIT TO ADD (this is one of my post further down the thread, but may get missed) Quote Just in case anyone else encounters this problem and comes upon this thread... I have already received an update from Line 6 to the ticket I submitted a couple hours ago. It appears this is a bug they are aware of... this is the response. "Hi, I'm sorry about the trouble with your gear. This is a bug we are aware of have logged it for a fix in the next firmware update. Thanks for your patience while we work this one out. Will - Line 6 Support" Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted May 6, 2018 Share Posted May 6, 2018 Not sure if you are encountering some other issue but the key to getting the correct LED to be on(or off) when you recall the preset/snapshot is to make sure you get the two effects in the states you want , then touch (but don't press), repeatedly if necessary, the footswitch until the LED reflects the lit state (on or off) that you want. Then save. If this is not working than maybe something else is going on. 1 Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 7, 2018 Author Share Posted May 7, 2018 Yes - that is exactly what I am doing... glad to know my approach is suppose to be right. The problem is that out of nowhere the patch (during recall) will reflect the state of the comp rather than the overdrive which inverts the meaning of the LED and scribble strip. I will troubleshoot this a little more today and see if I can narrow down the problem. Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 10, 2018 Author Share Posted May 10, 2018 Well - no luck with this at all. Now it never works as I expect... I'm not sure how I ever got it to work to begin with - LOL! To clarify.... I am combining a "Teemah" and a "Red Squeeze" on one footswitch I want the "Teemah" ON, and the "Red Squeeze" OFF when I save the patch. (loading the patch will always have the "Teemah" on) I want the LED to show the state of the "Teemah"... therefore when I recall the patch the LED should LIGHT UP. This is never happening... it always shows the state of the "Red Squeeze" which is LED off. Extras I have tried... I have reversed the order of the two effects in signal flow. I have reversed the states hoping that might help... but the LED still loads showing the "Red Squeeze" state. I have tried this on blank patches, and existing patches I have tried this on a few different footswitches I have tried this with different effects.... it always wants to default to just one of them whether that state is ON or OFF. As a final note... it's minor, just an irritation. I don't want to name the switch "Comp"... I want to name it "Overdrive"... and I want the LED to come on when the overdrive is ON. But it is not working... Any further suggestions? Quote Link to comment Share on other sites More sharing options...
TRENDKILLCFH333 Posted May 10, 2018 Share Posted May 10, 2018 I ran into this issue when I assigned a solo boost to a button which did the following: turned the noise gate off, mid scooped EQ off, added delay and reverb, sent a CC command to my Mesa TC-100 for the solo boost. Switching it again did the opposite, giving me a metal rhythm and lead tone immediately. Use your fingers to lightly tap the metal footswitch button - this will switch between the OD and the compressor effects that are assigned to the one footswitch. One effect should be off and one should be on. When you select the OD and it is on, press the foot switch all the way down (as opposed to the light tap) to turn it off and then save the preset (this should enable the compressor). The next time you recall the preset, the OD should be displayed and read as off, allowing you to turn it on and the compressor off. Hope this helps! 1 Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 10, 2018 Author Share Posted May 10, 2018 Thanks for the tip... I will try this in real time.... 44 minutes ago, TRENDKILLCFH333 said: Use your fingers to lightly tap the metal footswitch button - this will switch between the OD and the compressor effects that are assigned to the one footswitch. One effect should be off and one should be on. For the record, this is what I have been doing to this point. 44 minutes ago, TRENDKILLCFH333 said: When you select the OD and it is on, press the foot switch all the way down (as opposed to the light tap) to turn it off and then save the preset (this should enable the compressor). OK, this is a step I have never tried. 44 minutes ago, TRENDKILLCFH333 said: The next time you recall the preset, the OD should be displayed and read as off, allowing you to turn it on and the compressor off. Reverse of what I want, but let's see what happens. NOPE: Same results. When recalling the patch, the LED is lit up showing the state of the COMP (in this case, lit up)... I would like the patch to recall showing the state of the overdrive. (yes, the overdrive was the block showing when I saved) Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 10, 2018 Author Share Posted May 10, 2018 On further tests.... your solution does work.... sometimes :) But as soon as I save the patch again (change a parameter elsewhere) it reverts....and I have to go through these extra steps one more time to get it to stick - which doesn't always work on the first try. BUT - thank you... it does give me something to work with. Quote Link to comment Share on other sites More sharing options...
TRENDKILLCFH333 Posted May 10, 2018 Share Posted May 10, 2018 I did have to fiddle around with it for some time to get it to work the way I wanted. I do wish there was more information in the manual about this - it did cause some frustration but eventually I was happy with the end result. I'll have some time tonight to dig a little deeper and get you more exact details. Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 10, 2018 Author Share Posted May 10, 2018 37 minutes ago, TRENDKILLCFH333 said: I did have to fiddle around with it for some time to get it to work the way I wanted. I do wish there was more information in the manual about this - it did cause some frustration but eventually I was happy with the end result. I'll have some time tonight to dig a little deeper and get you more exact details. I've got it down to a point now that it is very predictable and has a relatively easy "work around" that works. You additional step of changing the overall state seems to be the key to getting around it. However, since it requires extra steps and is not intuitive I don't believe L6 intended it to work with way. I have opened a support ticket and provided them with a recipe to test... and also a recipe for the workaround. I can live with it as it is, but I hope it ends up being a confirmed bug that gets fixed in a future update. Thanks again for your help. Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 10, 2018 Author Share Posted May 10, 2018 Just in case anyone else encounters this problem and comes upon this thread... I have already received an update from Line 6 to the ticket I submitted a couple hours ago. It appears this is a bug they are aware of... this is the response. "Hi, I'm sorry about the trouble with your gear. This is a bug we are aware of have logged it for a fix in the next firmware update. Thanks for your patience while we work this one out. Will - Line 6 Support" 1 Quote Link to comment Share on other sites More sharing options...
TRENDKILLCFH333 Posted May 10, 2018 Share Posted May 10, 2018 Nice!!! Thanks for heading that up and I look forward to the next update! 1 Quote Link to comment Share on other sites More sharing options...
TRENDKILLCFH333 Posted May 11, 2018 Share Posted May 11, 2018 I'm sitting here with the HX Effects and have some more detailed input. On one of my presets, I created a footswitch to do the same function as described above. To recap, it's a solo boost essentially: CC toggle to Mesa TC-100 for Solo Boost, Turn on Reverb and Delay, Turn off Noise Gate. So in "rhythm" mode, my Noise Gate is on - everything else is off. In "lead" mode, the CC toggle for Solo Boost is on, as well as delay and reverb, noise gate is off. Visually represented here, just like you would see on the HX Effects. Bold is effects on, not bold is effects off: "RHYTHM": Noise Gate - Delay - Reverb - CC Toggle (solo boost) "LEAD": Noise Gate - Delay - Reverb - CC Toggle (solo boost) Pressing the footswitch switches between these modes. Lightly tapping the footswitch scrolls through all these effects, whichever mode is selected. Which ever effect you stop on, determines if the footswitch is lit. That's the key right there! So you need to set up the modes between the Teemah and the Compressor. mode 1: Teemah - Red Squeeze mode 2: Teemah - Red Squeeze You said you wanted mode 1 as the default when opening the preset. Teemah on, LED to display this. Make sure mode 1 is active, then lightly tap the footswitch to display the Teemah in bold. Then select another footswitch and then you can see the preset name in bold and LED lit to indicate it is on. This shows the change held - save the preset and this should do it. Open another preset and then open the one you just saved to confirm it did save for sure. All this worked on mine and I hope this helps your preset done quick! 1 Quote Link to comment Share on other sites More sharing options...
codamedia Posted May 11, 2018 Author Share Posted May 11, 2018 4 hours ago, TRENDKILLCFH333 said: Lightly tapping the footswitch scrolls through all these effects, whichever mode is selected. Which ever effect you stop on, determines if the footswitch is lit. That's the key right there! This is exactly the behavior I was expecting... but it doesn't work with my unit. 4 hours ago, TRENDKILLCFH333 said: Make sure mode 1 is active, then lightly tap the footswitch to display the Teemah in bold. Then select another footswitch and then you can see the preset name in bold and LED lit to indicate it is on. This shows the change held - save the preset and this should do it. Open another preset and then open the one you just saved to confirm it did save for sure. I've tried this dozens of times - exactly as you wrote. When I change presets and come back - the wrong state is shown. Even when I do get the state to work... simply saving the patch again without any changes breaks it. I'm OK with things now. I have found a way to get it to stick, and Line 6 has acknowledged there is a bug they are fixing. I appreciate you taking the time... and I'm glad to hear it seems to work with your setup. Maybe adding a third item (like yours) is the key... I never tried that, but I really don't need that either. Quote Link to comment Share on other sites More sharing options...
TRENDKILLCFH333 Posted May 11, 2018 Share Posted May 11, 2018 Ok - well I just wanted to be more specific - it's easier to explain with the unit in front of me. Glad you got a solution that works for ya! 1 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.