Mobi Posted October 16 Share Posted October 16 Hi, I think I have found a bug in the setup of the split A/B block on my Helix stadium floor running latest 1.4 firmware. Let me explain. I created a preset called Fixxxer Digital. I have added a split A/B block to split my clean amp (Jazz Rivet 120) and my dirty amp (Cali 2C+). I use snapshots to switch between my clean and distorted amps. On this split A/B block I can save the route to A or B for each snapshot. my 2 CLEAN snapshots have the value set to A100 (clean amp) and my 3 DISTORTION snapshots have the value set to B100 (dirty amp). When I push the buttons of the snapshots I can see the value change between A100 and B100. Now the problem is with the first split A/B block in my signal path. I have create this split A/B block to enable either the wah pedal or whammy pedal effect to be controlled by my external pedal Mission EP-1. (this is a spring loaded expression pedal without toe button, and connected to my stadium floor via TRS cable.) The problem is that I can not program this split A/B block between A100 and B100! If I turn it to A100 and save the snapshot, then it is changed for ALL snapshots! When I set the value to B100 and save the snapshot, the block remains B for all snwpshots! I tried changing the split block to a split Y block, and then changing it again to split A/B, but the problem remains the same. How is this possible? Again, the 2nd split A/B block just before the 2 amps is working fine. In below image you can see my signal path with 2 A/B split blocks. The split just before both amps works fine, I have the block always enabled and the value changes from A100 to B100 when I press different snapshots. However the first split block before the whammy/wah does not let me save A100 and B100... I did create a support ticket to Line6. Quote Link to comment Share on other sites More sharing options...
bearfacedcow Posted October 16 Share Posted October 16 Based on your screenshot, it doesn’t look like your Route To is Snapshot enabled. i’m using the Split A/B of one of my patches with no issues here. Everything routes as it should and is changing when I switch snapshots. jord Quote Link to comment Share on other sites More sharing options...
Mobi Posted October 19 Author Share Posted October 19 On 10/16/2026 at 7:12 PM, bearfacedcow said: Based on your screenshot, it doesn’t look like your Route To is Snapshot enabled. i’m using the Split A/B of one of my patches with no issues here. Everything routes as it should and is changing when I switch snapshots. jord Hi, you should not look at that screenshot. The problem is what I have explained in the text. When I ENABLE the split block, and set it to A100, then save snapshot1, then this value is applied to ALL snapshots!!! This behaviour is wrong. I want to be able to save A100 or B100 for each snapshot. UPDATE: I have found a workaround! Instead of physically pressing each snapshot switch, then saving the value, I pushed on the touchscreen right top onto the snapshot camera icon. From there I selected each snapshot, then changed the A/B value and saved each snapshot. Now the value is stored correct for each snapshot. This to me is clearly a bug as you should be able to select the snapshot assigned to a switch, and save the A/B value there. I have reported this back to line6. Quote Link to comment Share on other sites More sharing options...
silverhead Posted October 19 Share Posted October 19 On 10/19/2026 at 5:10 AM, Mobi said: …. The problem is what I have explained in the text. When I ENABLE the split block, and set it to A100, then save snapshot1, then this value is applied to ALL snapshots!!! This behaviour is wrong….. No, that behaviour is normal and correct UNLESS you have assigned the routing parameter (the one you set to A100) to the Snapshot controller. If you have made that assignment and still get this behaviour then, yes, it is wrong. Quote Link to comment Share on other sites More sharing options...
Mobi Posted October 19 Author Share Posted October 19 On 10/19/2026 at 5:39 PM, silverhead said: No, that behaviour is normal and correct UNLESS you have assigned the routing parameter (the one you set to A100) to the Snapshot controller. If you have made that assignment and still get this behaviour then, yes, it is wrong. How do I assign the routing parameter to the snapshot controller? I want to understand if I did something wrong? Quote Link to comment Share on other sites More sharing options...
silverhead Posted October 19 Share Posted October 19 See the Snapshot section of the manual. View the video at the top of that section, starting at the 0:50 second mark. Quote Link to comment Share on other sites More sharing options...
Mobi Posted October 21 Author Share Posted October 21 On 10/20/2026 at 12:33 AM, silverhead said: See the Snapshot section of the manual. View the video at the top of that section, starting at the 0:50 second mark. Yes but that's what I already did. It bugs for some reason. Quote Link to comment Share on other sites More sharing options...
silverhead Posted October 21 Share Posted October 21 Open a support ticket. 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.