Snapshot Bypass Help

[DewyGoodwood]

Hoping someone can help with this problem.  I'll try to explain so it makes sense...

 

I have a preset with a transistor tape delay block. It is set to snapshot bypass=off and is always enabled. I have the time parameter assigned to footswitch 3, min value of 70 and max value of 200. This works as expected. Pressing footswitch 3 changes the time parameter back and forth from 70 to 200.

 

I also have 3 snapshots in this preset that change the amp block settings (clean, dirty and crunch). None of the delay block settings are assigned to snapshots.  But when I have footswitch 3 enabled (time=200) and change snapshots, it disables footswitch 3 and changes the delay time setting back to 70.  I have to press footswitch 3 again to change back to 200. I would like the snapshots to leave the delay setting where I have it  based on the footswitch (enabled=200, disabled=70).  I've tried removing the footswitch assignment and recreating but I keep getting the same results.

 

Any suggestions would be appreciated.

[phil_m]

Snapshots recall the values of any parameters that are assigned to any controller, not just the snapshots controller. This is unrelated to the Snapshot Bypass parameter - that only affects the block’s bypass state. So, yeah, this is the expected behavior. The only exception to this is the EXP controllers, where you can choose whether they react to the actual position of the expression or not by selecting the Per Snapshot, Per Preset or Global setting in the Global Settings menu.

[PaulTBaker]

ok, that explains things.  I have the same (sort of) problem.  On some presets, I have amp vol and drive parameters tied to a stomp button(not snapshot).  The amp has the snapshot bypass = off.  When I change snapshots, the amp drive/vol change back to whatever they were the last time I was in the snapshot.

 

That does explain things, however, I don't like it :)

 

[HonestOpinion]

14 hours ago, DewyGoodwood said:

Hoping someone can help with this problem.  I'll try to explain so it makes sense...

 

I have a preset with a transistor tape delay block. It is set to snapshot bypass=off and is always enabled. I have the time parameter assigned to footswitch 3, min value of 70 and max value of 200. This works as expected. Pressing footswitch 3 changes the time parameter back and forth from 70 to 200.

 

I also have 3 snapshots in this preset that change the amp block settings (clean, dirty and crunch). None of the delay block settings are assigned to snapshots.  But when I have footswitch 3 enabled (time=200) and change snapshots, it disables footswitch 3 and changes the delay time setting back to 70.  I have to press footswitch 3 again to change back to 200. I would like the snapshots to leave the delay setting where I have it  based on the footswitch (enabled=200, disabled=70).  I've tried removing the footswitch assignment and recreating but I keep getting the same results.

 

Any suggestions would be appreciated.

 

Another approach is to leverage the 'Snapshot Edit' parameter in global settings. Since your preferred behavior is to always have the delay enabled do the following. Do NOT set FS3 to always have Bypass=Off. Instead assign the Delay block's 'Time' parameter to FS3 as you have been with the Min/Max set to your preferred values(200ms & 600ms). Now go set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".  Make sure you save the preset with the delay block active in all snapshots.

 

Now when you switch snapshots whatever 'Time' value you last selected for your delay with FS3 for that snapshot will be remembered; even if you switch snapshots, change the 'Time' value in the new snapshot, and then switch back to your last one. I have attached a simple sample preset below that should be behaving the way you would like it to if I understood your post correctly.

 

You can check out the assignments once you have loaded the attached sample preset. Select the delay block and 'Bypass/Controller Assign' tab in HX Edit and look at the left hand column to see the assignments for the delay. There should only be the one assignment for the delay 'Time' parameter on FS3 with your Min value set to 200 and your Max value set to 600.  If for some reason your 'Bypass' parameter gets assigned to FS3 as well just use the 'Bypass/Controller Assign' tab to clear it.  You can also do this by right clicking on the Delay block and selecting "None" for the 'Bypass Assign' entry in the pulldown menu. Make sure you have all your snapshots saved with the delay block active.

Delay Example.hlx

[jeffreyke]

Hello, looking for some help please with a similar issue (I think). I’m new to stomp so forgive me if my terminology isn’t correct. I’m using an external midi controller to switch between snapshots. I have Footswitch 1 on the stomp to bypass a dual pitch and I have disabled snapshots so basically I can switch between snapshots 1, 2 and 3 and Footswitch 1 stays on. Equally if I turn it off when on snapshot 2 it stays off when I move to snapshot 1 and 3 - happy days! Unfortunately I cannot get the same thing to happen for foot switches 2 and 3 on the stomp. The only difference I can see is that Footswitch 1 is solely in bypass mode, whereas Footswitches 2 and 3 are changing multiple parameters (fs2 does delay and fa 3 doing reverb). Is there a way I can get fs2 and fs3 to behave the same way as FS1? Maybe I’m doing something wrong?  I should say, the delays and reverbs are always on and the footswitches are set to increase some parameters. Hope that helps. Any advice would be great. Seems strange why I can do it for fs1 but not the others. 

[DewyGoodwood]

Thanks for responses folks. Sounds like this behavior is by design. Unfortunate but I guess it makes sense.

 

Thanks for the suggestion HonestOpinion but no joy. I still get the same results.

 

I found a workaround by adding a second delay block. I have one with time set at 70 and the other with time set at 200. I assign both to the same footswitch so pressing turns one on and the other off. That way I can have the snapshots ignore the bypass and get the results I want. Takes a little more DSP but it works.

 

Cheers.

[HonestOpinion]

1 hour ago, DewyGoodwood said:

Thanks for responses folks. Sounds like this behavior is by design. Unfortunate but I guess it makes sense.

 

Thanks for the suggestion HonestOpinion but no joy. I still get the same results.

 

I found a workaround by adding a second delay block. I have one with time set at 70 and the other with time set at 200. I assign both to the same footswitch so pressing turns one on and the other off. That way I can have the snapshots ignore the bypass and get the results I want. Takes a little more DSP but it works.

 

Cheers.

 

Glad you found a workaround that works for you but that should not be necessary. If this did not work with the preset I uploaded it must be related to some Global Setting we have not hit upon. It works perfectly on my end. Did you check the assignments tab as I suggested to make sure your bypass state was not also assigned to that footswitch? What did my preset do specifically when you uploaded it? Might also help if you upload one of your presets that was not working as expected. Would love to get to the bottom of this.

 

Btw, are you on the 3.0.1 firmware?

[jeffreyke]

6 hours ago, HonestOpinion said:

 

Glad you found a workaround that works for you but that should not be necessary. If this did not work with the preset I uploaded it must be related to some Global Setting we have not hit upon. It works perfectly on my end. Did you check the assignments tab as I suggested to make sure your bypass state was not also assigned to that footswitch? What did my preset do specifically when you uploaded it? Might also help if you upload one of your presets that was not working as expected. Would love to get to the bottom of this.

 

Btw, are you on the 3.0.1 firmware?

Sorry it I’m piggybacking on someone else’s questions. Seems like we have same issue. Yes I’m using 3.0.1. I will download your patch and let u know how it works for me. Happy to share my preset with you if I can’t get it sorted. Thanks for your support. Will be back in touch later on. 

[HonestOpinion]

8 hours ago, jeffreyke said:

Sorry it I’m piggybacking on someone else’s questions. Seems like we have same issue. Yes I’m using 3.0.1. I will download your patch and let u know how it works for me. Happy to share my preset with you if I can’t get it sorted. Thanks for your support. Will be back in touch later on. 

 

Would be happy to look at it although with the added element of you using MIDI for switching your issue may be different than the OPs.

[HonestOpinion]

15 hours ago, DewyGoodwood said:

Thanks for responses folks. Sounds like this behavior is by design. Unfortunate but I guess it makes sense.

 

Thanks for the suggestion HonestOpinion but no joy. I still get the same results.

 

I found a workaround by adding a second delay block. I have one with time set at 70 and the other with time set at 200. I assign both to the same footswitch so pressing turns one on and the other off. That way I can have the snapshots ignore the bypass and get the results I want. Takes a little more DSP but it works.

 

Cheers.

 

14 hours ago, HonestOpinion said:

 

Glad you found a workaround that works for you but that should not be necessary. If this did not work with the preset I uploaded it must be related to some Global Setting we have not hit upon. It works perfectly on my end. Did you check the assignments tab as I suggested to make sure your bypass state was not also assigned to that footswitch? What did my preset do specifically when you uploaded it? Might also help if you upload one of your presets that was not working as expected. Would love to get to the bottom of this.

 

Btw, are you on the 3.0.1 firmware?

 

I should also ask, what HX device are you using?

[HonestOpinion]

On 2/26/2021 at 12:37 PM, PaulTBaker said:

ok, that explains things.  I have the same (sort of) problem.  On some presets, I have amp vol and drive parameters tied to a stomp button(not snapshot).  The amp has the snapshot bypass = off.  When I change snapshots, the amp drive/vol change back to whatever they were the last time I was in the snapshot.

 

That does explain things, however, I don't like it :)

 

 

On 2/26/2021 at 1:54 PM, HonestOpinion said:

 

Another approach is to leverage the 'Snapshot Edit' parameter in global settings. Since your preferred behavior is to always have the delay enabled do the following. Do NOT set FS3 to always have Bypass=Off. Instead assign the Delay block's 'Time' parameter to FS3 as you have been with the Min/Max set to your preferred values(200ms & 600ms). Now go set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".  Make sure you save the preset with the delay block active in all snapshots.

 

Now when you switch snapshots whatever 'Time' value you last selected for your delay with FS3 for that snapshot will be remembered; even if you switch snapshots, change the 'Time' value in the new snapshot, and then switch back to your last one. I have attached a simple sample preset below that should be behaving the way you would like it to if I understood your post correctly.

 

You can check out the assignments once you have loaded the attached sample preset. Select the delay block and 'Bypass/Controller Assign' tab in HX Edit and look at the left hand column to see the assignments for the delay. There should only be the one assignment for the delay 'Time' parameter on FS3 with your Min value set to 200 and your Max value set to 600.  If for some reason your 'Bypass' parameter gets assigned to FS3 as well just use the 'Bypass/Controller Assign' tab to clear it.  You can also do this by right clicking on the Delay block and selecting "None" for the 'Bypass Assign' entry in the pulldown menu. Make sure you have all your snapshots saved with the delay block active.

Delay Example.hlx 8.83 kB · 2 downloads

 

Have you tried setting things up the way I suggest above? The key is that if you want the snapshot to always have the block in the state you last left it in, no matter how many snapshots you roll through, set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".  One note, maybe obvious but worth mentioning, once you change presets(not snapshots), all snapshots values in that preset will revert to the state they were saved in.

 

If you want the snapshot to always revert to a specific state when you go back to it, set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Discard".  If you use this global setting because you prefer this behavior make sure you save each snapshot in the state you want when you are creating the preset.

[jeffreyke]

3 hours ago, HonestOpinion said:

 

Would be happy to look at it although with the added element of you using MIDI for switching your issue may be different than the OPs.

Hello,  here is my preset that I'm having issues with.  You will see that if you engage FS1 on the stomp it will turn on the Dual Pitch and if you switch between snapshots it will stay on, and if you turn off on any of the snapshots it will turn off on all of them.  If you then look at FS2 and FS3 these do not behave in the same way.  Only logic I can come up with is that its because FS2 and FS3 are parameter changes rather than on/off.  Any help would be great, thank you for helping and looking into this.

HX Stomp Snapshot issue.hls

[HonestOpinion]

25 minutes ago, jeffreyke said:

Hello,  here is my preset that I'm having issues with.  You will see that if you engage FS1 on the stomp it will turn on the Dual Pitch and if you switch between snapshots it will stay on, and if you turn off on any of the snapshots it will turn off on all of them.  If you then look at FS2 and FS3 these do not behave in the same way.  Only logic I can come up with is that its because FS2 and FS3 are parameter changes rather than on/off.  Any help would be great, thank you for helping and looking into this.

HX Stomp Snapshot issue.hls 50.97 kB · 0 downloads

 

Looks like you exported your entire setlist. Can you upload just the preset. You can right click on the preset in HX Edit and click 'Export'.

[jeffreyke]

18 minutes ago, HonestOpinion said:

 

Looks like you exported your entire setlist. Can you upload just the preset. You can right click on the preset in HX Edit and click 'Export'.

Oh sorry - new to this.  Thanks.  Here you do (I hope).  Thanks again.

Morgan + D&R.hlx

[HonestOpinion]

21 hours ago, jeffreyke said:

Oh sorry - new to this.  Thanks.  Here you do (I hope).  Thanks again.

Morgan + D&R.hlx 14.7 kB · 1 download

 

Maybe I am unsure of exactly what behavior you are looking for, if so please let me know. Loaded up and examined your preset. The instructions from my prior post should work for you, e.g. Set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".   When I test your preset it works as it is, unmodified by me, to retain the last selected state of both the parameter settings and the bypass state(in the case of FS2 with its two assigned delay blocks)across snapshot changes as long as I have the global setting set to "Recall" as described. When I click through the other snapshots and return to the one I made a change in, it is exactly as I left it. Disclaimer: I have the Helix not the Stomp.

 

Btw, that is a fairly slick use of the Stomp for a new user. If I could make one suggestion. Rather than having your multiple footswitch assignments read "Multiple(*) which is rather nebulous, take advantage of the 'Customize' button under either the 'Bypass Assign' or 'Command Center' menus on the device or click the 'Bypass/Controller Assign' tab in HX Edit and use the 'Customize' field there to rename them to something more meaningful.  Maybe you just didn't get around to it yet.

 

If the suggestion in the first paragraph does not work for you I will assume much like the case of the OP that I have yet to identify some other global setting that is set on my Helix that is required for the proper behavior, or that the Stomp is working differently than the Helix on this feature. Makes me wonder which HX device the OP is using as well? The only other global setting I know of that can disrupt the behavior described above is if you set Global Settings --> Preferences --> 'Snapshot Reselect' = "Toggle Previous" (don't do that). Another possibility is that because I am using the Helix's footswitches to switch snapshots rather than an external MIDI controller as you are that the Helix is changing snapshots somehow differently. Seems unlikely but I suppose it is possible. I would need to maybe have both a Helix and a Stomp and sniff the MIDI commands on the PC with something like MIDI-OX to be sure that they are operating identically; assuming all the internal messages pass through.

 

Let me know if just changing the setting above works for you.

[HonestOpinion]

Btw, for newer users of snapshots and in the interest of beating the details on this setting into the ground(Global Settings --> 'Preferences' --> 'Snapshot Edits'), it not only impacts how the snapshots behave while performing but also while editing a preset. If you have it set to "Discard" it is not a bad idea to save each snapshot before moving on to design the next one. Otherwise it is pretty easy to inadvertently lose the snapshots settings when you start switching around to edit other snapshots. With it is set to "Recall" you can save just once when you have completed editing the entire preset.

[jeffreyke]

On 3/6/2021 at 2:00 AM, HonestOpinion said:

 

Maybe I am unsure of exactly what behavior you are looking for, if so please let me know. Loaded up and examined your preset. The instructions from my prior post should work for you, e.g. Set Global Settings --> 'Preferences' --> 'Snapshot Edits' = "Recall".   When I test your preset it works as it is, unmodified by me, to retain the last selected state of both the parameter settings and the bypass state(in the case of FS2 with its two assigned delay blocks)across snapshot changes as long as I have the global setting set to "Recall" as described. When I click through the other snapshots and return to the one I made a change in, it is exactly as I left it. Disclaimer: I have the Helix not the Stomp.

 

Btw, that is a fairly slick use of the Stomp for a new user. If I could make one suggestion. Rather than having your multiple footswitch assignments read "Multiple(*) which is rather nebulous, take advantage of the 'Customize' button under either the 'Bypass Assign' or 'Command Center' menus on the device or click the 'Bypass/Controller Assign' tab in HX Edit and use the 'Customize' field there to rename them to something more meaningful.  Maybe you just didn't get around to it yet.

 

If the suggestion in the first paragraph does not work for you I will assume much like the case of the OP that I have yet to identify some other global setting that is set on my Helix that is required for the proper behavior, or that the Stomp is working differently than the Helix on this feature. Makes me wonder which HX device the OP is using as well? The only other global setting I know of that can disrupt the behavior described above is if you set Global Settings --> Preferences --> 'Snapshot Reselect' = "Toggle Previous" (don't do that). Another possibility is that because I am using the Helix's footswitches to switch snapshots rather than an external MIDI controller as you are that the Helix is changing snapshots somehow differently. Seems unlikely but I suppose it is possible. I would need to maybe have both a Helix and a Stomp and sniff the MIDI commands on the PC with something like MIDI-OX to be sure that they are operating identically; assuming all the internal messages pass through.

 

Let me know if just changing the setting above works for you.

Ok great thanks for this advice. I’ll get a look shortly and let u know how I get on. Thanks again for looking into this. I didn’t realise I could rename footswitches so I’ll defo do that. I’d also like to add a colour so hopefully can do that too. Will let u know how I get on with snapshots. Thanks again. 

[silverhead]

On 3/5/2021 at 10:17 PM, HonestOpinion said:

Btw, for newer users of snapshots and in the interest of beating the details on this setting into the ground(Global Settings --> 'Preferences' --> 'Snapshot Edits'), it not only impacts how the snapshots behave while performing but also while editing a preset. If you have it set to "Discard" it is not a bad idea to save each snapshot before moving on to design the next one. Otherwise it is pretty easy to inadvertently lose the snapshots settings when you start switching around to edit other snapshots. With it is set to "Recall" you can save just once when you have completed editing the entire preset.

Yes, this setting is often the cause of some confusion when users are learning how to use snapshots effectively. I find it useful to change this setting depending on my activity. Mostly I have the setting at Discard because I want to be sure that a snapshot is always recalled in a known state, regardless of whether or not I might have turned a specific FX on or off using a footswitch while I was last in that snapshot.
 

However, when I start an editing session knowing that I will be spending some time tweaking my snapshots in a given preset I will set it to Recall to save time and prevent lost edits. The downside is, of course, that I have to remember to set it back to Discard before playing normally again.

[jeffreyke]

5 hours ago, silverhead said:

Yes, this setting is often the cause of some confusion when users are learning how to use snapshots effectively. I find it useful to change this setting depending on my activity. Mostly I have the setting at Discard because I want to be sure that a snapshot is always recalled in a known state, regardless of whether or not I might have turned a specific FX on or off using a footswitch while I was last in that snapshot.
 

However, when I start an editing session knowing that I will be spending some time tweaking my snapshots in a given preset I will set it to Recall to save time and prevent lost edits. The downside is, of course, that I have to remember to set it back to Discard before playing normally again.

Hi all, sorry for this but I’m having no luck at all. Perhaps I’m not explaining myself properly. If you look at the preset I uploaded, Footswitch 1 works like a normal stomp pedal (independent from the stomp). When I turn it on it stays on regardless of the snapshot I’m in or if I can snapshots it stays on until I turn it off. This is the behaviour I want for footswitches 2 and 3, however this is not what happens in my preset and I cannot get them to behave this way. If I turn on Footswitch 2 (regardless of the snapshot I am in) I want it to say on even if I move through snapshots until I decide to turn it off. This is the behaviour of Footswitch 1. Can you help me understand what I’m doing wrong? 
 

Also, the comment about renaming Footswitch is really interesting - can you explain how please? I do not see an option to edit in “bypass/controller assign” in hx edit and I don’t know which options to select on “command center”. Any advice would be great as I would love to rename the footswitches to something more meaningful and also select a colour?

 

Thanks again for your help and apologies for going over old ground - id like to get this resolved. 

[HonestOpinion]

6 hours ago, jeffreyke said:

Hi all, sorry for this but I’m having no luck at all. Perhaps I’m not explaining myself properly. If you look at the preset I uploaded, Footswitch 1 works like a normal stomp pedal (independent from the stomp). When I turn it on it stays on regardless of the snapshot I’m in or if I can snapshots it stays on until I turn it off. This is the behaviour I want for footswitches 2 and 3, however this is not what happens in my preset and I cannot get them to behave this way. If I turn on Footswitch 2 (regardless of the snapshot I am in) I want it to say on even if I move through snapshots until I decide to turn it off. This is the behaviour of Footswitch 1. Can you help me understand what I’m doing wrong? 
 

Also, the comment about renaming Footswitch is really interesting - can you explain how please? I do not see an option to edit in “bypass/controller assign” in hx edit and I don’t know which options to select on “command center”. Any advice would be great as I would love to rename the footswitches to something more meaningful and also select a colour?

 

Thanks again for your help and apologies for going over old ground - id like to get this resolved. 

 

Ok, great explanation, I think I understand you now. Apologize if I was slow on that. If you turn on FS2 or FS3 in for example Snapshot1, you want the parameters as well as the bypass state to be/stay as you set them in all the other snapshots as well; not just the snapshot you activated it in. Let me see if there is any way to get it functioning that way.

 

Regarding using the "Customize" function for renaming. In the case of FS2 which has two blocks assigned to it, you will need to select the correct block to be able to see the "Customize" field under the “Bypass/Controller Assign”. HX Edit does NOT display the customize field for every block in a multiple assignment, only one. I believe HX devices default to displaying that field only for the first block you assigned to that footswitch when you initially set up the preset; even though the rename obviously involves the other blocks as well. So if you have multiple blocks simply roll through the blocks for that FS one by one until you find the block with the 'Customize' field. In the case of FS2 in your preset that would mean selecting the "Ping Pong" delay block in HX Edit, selecting the “Bypass/Controller Assign” tab, and then clicking on the "Multiple(*)" name in the 'Customize' field and changing it. 

 

This same behavior of only showing the 'Customize' field on one of the blocks in a multiple block assignment is also reflected when you customize the name on the device directly. That means that again, in the example of FS2, you will need to highlight the 'Ping Pong' delay block first, then bring up the 'Bypass Assign' options(on the device) menu. You should now see the 'Customize' option, at least on the Helix. Don't know if you have to maybe page over to see it on the Stomp. If you decide to modify the name in 'Command Center' instead, select the FS you are renaming and select 'Customize'.  Probably easier to use Command Center when multiple blocks are assigned to a footswitch as you only need to know which footswitch you are renaming.

[HonestOpinion]

Going to play around with it some more but I have to admit that short of perhaps some complicated MIDI solution to this I don't currently see a way to get the preset to behave the way you want. Maybe someone else has a solution?

 

I think unfortunately that phil_m's answer waaaaay up at the top of this topic cuts to the core of it. As he initially stated, at least right now, the parameters for a block cannot be "fixed" across snapshots in the same fashion that the bypass state can.  He clearly had a better grasp right from jump of what the OP and you were trying to do.

 

To summarize it would seem to me that footswitch(not snapshot) assignments for parameters could essentially have an option to have the same "fixed" or isolated behavior available that can currently be established(via the Action switch), only for bypass state. I believe this change would address what you and the OP are attempting to accomplish. I suppose this could be implemented by perhaps adding the same sort of 'Snapshot Bypass'="Off" option for a block's parameters(again, currently only available for the block's bypass state). Seems like a prime candidate for an IdeaScale suggestion. I would vote it up. 

[jeffreyke]

4 hours ago, HonestOpinion said:

Going to play around with it some more but I have to admit that short of perhaps some complicated MIDI solution to this I don't currently see a way to get the preset to behave the way you want. Maybe someone else has a solution?

 

I think unfortunately that phil_m's answer waaaaay up at the top of this topic cuts to the core of it. As he initially stated, at least right now, the parameters for a block cannot be "fixed" in the same fashion that the bypass state can.  He clearly had a better grasp right from jump of what the OP and you were trying to do.

 

To summarize it would seem to me that footswitch(not snapshot) assignments for parameters could essentially have an option to have the same "fixed" or isolated behavior available that can currently be established(via the Action switch), only for bypass state. I believe this change would address what you and the OP are attempting to accomplish. I suppose this could be implemented by perhaps adding the same sort of 'Snapshot Bypass'="Off" option for a block's parameters(again, currently only available for the block's bypass state). Seems like a prime candidate for an IdeaScale suggestion. I would vote it up. 

Hi, this reply is really helpful and confirms what I thought was happening. I can use presets in the current setup no problem. Thanks again for your time with this. I’m interested in the IdeaScale suggestion thing - is this something I do?? I also still need to look into the customise setting mentioned earlier. Thanks again for your help. 

[HonestOpinion]

13 minutes ago, jeffreyke said:

Hi, this reply is really helpful and confirms what I thought was happening. I can use presets in the current setup no problem. Thanks again for your time with this. I’m interested in the IdeaScale suggestion thing - is this something I do?? I also still need to look into the customise setting mentioned earlier. Thanks again for your help. 

 

Ideas submitted to IdeaScale is the method by which an idea for a mod or feature has the best chance of getting implemented.  You just have to create an IdeaScale ID and submit an idea. Don't be shocked if an idea such as this which is a little specialized or esoteric doesn't garner as many votes as you might expect. It is still worth getting it into the conversation over at Line6 though. Some ideas pop up in the firmware in fairly short order after being submitted and some take years to never. You never know.

 

https://line6.ideascale.com/

[zappazapper]

https://line6.ideascale.com/a/dtd/Controller-Assign-independent-of-Snapshots/1000019-23508

 

I created this ideascale a few months back in an attempt to improve the use of Snapshots with blocks that the user wishes to control independently of Snapshots (not just bypass state but also parameter control). Please review it and if you think it might be a solution to your issue, upvote it.

 

Thank you.

[jeffreyke]

22 hours ago, HonestOpinion said:

 

Ideas submitted to IdeaScale is the method by which an idea for a mod or feature has the best chance of getting implemented.  You just have to create an IdeaScale ID and submit an idea. Don't be shocked if an idea such as this which is a little specialized or esoteric doesn't garner as many votes as you might expect. It is still worth getting it into the conversation over at Line6 though. Some ideas pop up in the firmware in fairly short order after being submitted and some take years to never. You never know.

 

https://line6.ideascale.com/

Ok great thanks. I’ve registered for an account so once active I’ll get on this. Thanks again. 

[jeffreyke]

On 3/7/2021 at 6:23 PM, HonestOpinion said:

 

Ok, great explanation, I think I understand you now. Apologize if I was slow on that. If you turn on FS2 or FS3 in for example Snapshot1, you want the parameters as well as the bypass state to be/stay as you set them in all the other snapshots as well; not just the snapshot you activated it in. Let me see if there is any way to get it functioning that way.

 

Regarding using the "Customize" function for renaming. In the case of FS2 which has two blocks assigned to it, you will need to select the correct block to be able to see the "Customize" field under the “Bypass/Controller Assign”. HX Edit does NOT display the customize field for every block in a multiple assignment, only one. I believe HX devices default to displaying that field only for the first block you assigned to that footswitch when you initially set up the preset; even though the rename obviously involves the other blocks as well. So if you have multiple blocks simply roll through the blocks for that FS one by one until you find the block with the 'Customize' field. In the case of FS2 in your preset that would mean selecting the "Ping Pong" delay block in HX Edit, selecting the “Bypass/Controller Assign” tab, and then clicking on the "Multiple(*)" name in the 'Customize' field and changing it. 

 

This same behavior of only showing the 'Customize' field on one of the blocks in a multiple block assignment is also reflected when you customize the name on the device directly. That means that again, in the example of FS2, you will need to highlight the 'Ping Pong' delay block first, then bring up the 'Bypass Assign' options(on the device) menu. You should now see the 'Customize' option, at least on the Helix. Don't know if you have to maybe page over to see it on the Stomp. If you decide to modify the name in 'Command Center' instead, select the FS you are renaming and select 'Customize'.  Probably easier to use Command Center when multiple blocks are assigned to a footswitch as you only need to know which footswitch you are renaming.

Hi again, thanks for your advice. As it looks like Hx stomp won’t behave the way I was hoping it would I’ve decided to set my delay sound to come on when I engage snapshots 2 and 3 automatically. It’s not ideal but it will work. Thanks for your help and fingers crossed this can be included in a future update. 
 

I cannot get your advice to work on the customise function - sorry for being a pain. I cannot see any reference to customise anywhere on the stomp. Perhaps not a feature it has? I can’t see any relevant reference to this in the manual either. Perhaps something not available? Happy to send a pic/video of what I can see on HX edit and in command centre. On reading the hx edit pilot guide it appears to say “Footswitch labels are not available on hx stomp devices”.  Similar wording for Footswitch colour. 

[HonestOpinion]

2 hours ago, jeffreyke said:

Hi again, thanks for your advice. As it looks like Hx stomp won’t behave the way I was hoping it would I’ve decided to set my delay sound to come on when I engage snapshots 2 and 3 automatically. It’s not ideal but it will work. Thanks for your help and fingers crossed this can be included in a future update. 
 

I cannot get your advice to work on the customise function - sorry for being a pain. I cannot see any reference to customise anywhere on the stomp. Perhaps not a feature it has? I can’t see any relevant reference to this in the manual either. Perhaps something not available? Happy to send a pic/video of what I can see on HX edit and in command centre. On reading the hx edit pilot guide it appears to say “Footswitch labels are not available on hx stomp devices”.  Similar wording for Footswitch colour. 

 

Wow bummer! Was not aware this was not available on the Stomp as I don't own one. Would have expected to at least see it in HX Edit.  It is there for the Helix. Hopefully it will get added for the HX Stomp in a future update.  Thanks for the courteous responses. Sorry I couldn't be of more assistance.

[HonestOpinion]

On 3/8/2021 at 1:13 PM, zappazapper said:

https://line6.ideascale.com/a/dtd/Controller-Assign-independent-of-Snapshots/1000019-23508

 

I created this ideascale a few months back in an attempt to improve the use of Snapshots with blocks that the user wishes to control independently of Snapshots (not just bypass state but also parameter control). Please review it and if you think it might be a solution to your issue, upvote it.

 

Thank you.

 

Looks like there is a suggestion on Ideascale for this already. Voted!

[zappazapper]

22 minutes ago, HonestOpinion said:

 

Looks like there is a suggestion on Ideascale for this already. Voted!

Excellent. Thank you. 

[jeffreyke]

20 hours ago, HonestOpinion said:

 

Wow bummer! Was not aware this was not available on the Stomp as I don't own one. Would have expected to at least see it in HX Edit.  It is there for the Helix. Hopefully it will get added for the HX Stomp in a future update.  Thanks for the courteous responses. Sorry I couldn't be of more assistance.

Quite the contrary. I have answers to all my questions - perhaps not the answers I had hoped for but I got what I was looking for. Really appreciate your input over the last few day - thank you!