swanny8777

46 minutes ago, Racknee said:

8)When you switch to snapshot 1 and back to snapshot 2, snapshot 2 is now set to (default) "auto impendance", not 1mil. Going back and forth, snapshot 1 stays saved at 10K as it should, but the one you first arrive at when you load the preset resets to "auto".

 

Helix LT at 2.82.

I don't have my Helix in front of me to know for sure, but I've encountered a similar bug with delays, reverbs, and amp settings:  pretty much anything that I set to utilize snapshot parameters.  I don't have a solution to my problem, nor yours, but I have dug and seemed to see what may be one of the issues.  The .hlx file that presets are saved as are nothing more than text files using JSON formatting, which just means you can open the .hlx file in a simple text editor to view preset information on your computer if you've used HX Edit to save it from your Helix to your computer.  When you look at the file there's quite a bit of information, that can be broken down as follows (picture a tree that branches off into more detailed branches):  a data field which leads to a tone field which has several different fields under it:  dsp0, dsp1, snapshot 0, snapshot1, snapshot 2 (thru snapshot7, which would be your 8th snapshot), global, and controller.  Basically, the information is stored to tell your Helix what the preset should load when you switch to it on the hardware, and there is separate information stored for each snapshot that you have saved in the preset.  

Let's for the sake of argument say that the preset is saved so that when we switch to it, it loads on snapshot 8.  When it loads the preset (and subsequently snapshot 8), it loads everything correctly because the default information for the preset stored under dsp0, dsp1, global, and controller are correct (it stores the information in these fields based on what blocks were on/off, where parameters were, etc. when you hit save), however, even if I change to no other snapshot, but merely hit to go back to snapshot 8, I might find that instead of the channel volume on my amp block being set to a hypothetical [5.0], I might find that it jumps to [0.0] or [10.0].

 When I peeked into some of the preset files that were giving me errors I found that the default figures were correct (as mentioned above), but when I go to the dropdown for snapshot7 (snapshot 8 on the hardware), and cruise down to the block info for my amp (in my case, block6) and look at the ChVol parameter, I see be saved as either 0, or some number greater than 1.  Here's why this last part is important, the .hlx file saves values as very long decimals, so my default preset value for amp channel volume (and also preset7) should be 0.5 to give me the volume of [5.0] I'd expect to see, but it may be something like 0.49999998275 or 0.50000001023 to still yield the same result of the channel volume being at [5.0].  I have found that when I experience errors with snapshot values (for instance, channel volume drops to [0.0] or [10.0] when I switch to the snapshot), the saved value in the .hlx file may be 0.0 (resulting in [0.0] when selecting the snapshot) or something strange like 45 (resulting in [10.0] when selecting the snapshot--remember that to get this value the saved value would only need to be 1.0 or even 0.9999 or something similar).

That is A LOT to say this:  I bet if you open your .hlx file, or share it with me so I can check it out, if "auto" is the minimum or maximum setting you can have for your snapshot value, then you may be experiencing a similar bug.  I have reached out to Line6 about this before and I guess because it didn't happen to them when building presets (even though they could open my preset, either on an actual Helix unit, or by observing the .hlx file internally), they kind of just brushed it off as a corrupt preset, which may be all that it is.  So I have rebuilt presets before when dealing with this issue, but it also makes me VERY leery of using snapshots at times.  You may need to rebuild your preset, or you can manually adjust the level in the .hlx file, save it, and reload it into your Helix (the latter idea makes some people nervous thinking that it might brick their unit, but anyone with any IT background I know say that this is highly unlikely if at all, so if that makes you nervous, just rebuild the preset from a New Preset and save over your trouble preset).  Hope this helps, sorry for the book I gave you to read lol.

If you'd rather see me coming to these conclusions in real time, here's a video:

1 hour ago, vypole said:

In 2.8 when switching between snapshots bass and mid on amp values turned to maximum. On helix display it looks in 2000 and 90000, on HX editor 10.0. Please help!

I've had this issue intermittently since I've had my Helix; it's never been a bug that I've been able to reproduce from scratch, so I was told that perhaps I had presets that were corrupt.  It's interesting that the values on your helix exceed 10, mine never did that.  What I did notice was that if I open the preset file on my computer with a text editor or comparable application, the value for that snapshot state parameter would exceed 10 (for example, it would be 45 [see video link below if interested, but it's a long video]), but it seemed that the Helix never allowed the value to go over 10 and the bar beneath the value would be maxed to the right.  I haven't updated to 2.8 yet due to all the bugs I'm seeing here, but I'm wondering if something was lost in the code that dictates what max value the Helix is displayed.  Interesting problem to see, please keep us posted on your outcomes!

On 12/10/2018 at 5:46 AM, shmaque said:

Haven't found this in a search, but has anybody else had major issues with snapshot based tap tempos not working lately? HX Stomp FW ver 2.71 - tempos set to per snap, snap changes set to discard.

When editing a snap (eg to enable a block) and then saving, the snap will at times arbitrarily adopt (and save) the stored tempo for a different snapahot. This happened to me about 4 times over the weekend when trying to save quick updates to gain structures. 

 

Additionally, tapping manually to override the current snapshot's (eg ss3) tempo, then switching to a different snap and back does *not* restore the snap's (ss3) stored tempo. Instead, it reverts to whatever I tapped while 3 was last selected, regardless of the fact that snapshot changes are set to discard.

 

Seems tap tempos are all squirrelly in this FW version - is this an issue on floor/lt or just stomp?

Played a set last night where we were in the middle of sound check when I saved a change to one of my presets regarding my snapshot based Variax model.  The tempo is preset based and had been saved at 68 BPM.  When I clicked back through my presets after sound check I noticed the tempo light blinking very fast.  When I double tapped the button with my finger to display the tempo I believe it was 255 (it was maxed whatever it was).  Thankfully it was the first song of the set... otherwise that would have thrown me for a quick loop upon starting the song!

On 6/27/2017 at 10:07 AM, silverhead said:

 

That would require a whole new plugin - perhaps called Variax Native. Helix does not do any Variax DSP; it just communicates Variax command and control data over VDI. Perhaps Line 6 will do that someday, but it would be a completely different VST product - not an extension of Helix Native.

I'm late to the convo, but man that would be sweet.  It'd be an awesome in recording and tone shaping scenarios; record your parts and licks and modify everything in post with a click here or there.  Of course Helix Native already makes much of this possible, but it's always nice changing guitar models live to hear the difference you get, it would just be nice to have that option after the fact too.  I'd buy it.  But, it definitely seems like quite the task as mdmayfield pointed out:

On 8/15/2017 at 3:01 PM, mdmayfield said:

 

The modeling depends on having 6 separate audio channels - one for each string. (The modeling as a whole, not just the alternate tunings. Each string must be processed differently due to pickup angle, etc.)

On 9/14/2018 at 5:52 PM, mdmayfield said:

 

To even begin to guess at the source of the problem, someone would need to see the actual error :-)

 

Otherwise, maybe start here: https://opentechschool.github.io/python-beginners/en/getting_started.html

Yes, sorry, I wasn't thinking of adding the error; perhaps when I have some time to read through your resource and troubleshoot I'll be more specific :-) Thanks for the help!

3 hours ago, jonandtice said:

If I had time I'm pretty sure I could get it to look like HX Edit on a web browser, even with my limited skills.  So I'm surprised no one has done it yet.

Yeah, it seems like it would be straightforward enough, just extracting information from the .hlx files (and the fact that you have all the neat little images and such in the package contents of HX Edit)... I just have next to NO working knowledge of doing this stuff... I was able to add buttons though for snapshots that fill in the snapshot names on loading a preset, but that's all I've gotten to work so far (I couldn't get the dropdown menu to work as such).  It's fun playing around with though.  And it makes me wonder why exactly we're still not able to utilize HX Edit without being hooked up to the Helix.  Oh well.  I've recruited my buddy's help for working on this fun little project; he's in IT and is apparently well versed in JSON (or at least more than I am), so we'll see.

test 2.html

On 11/3/2015 at 2:51 PM, thestratmanblues said:

I've made this little Python app to dump the content of a Bundle file called "Bundle_VERSION_1_03.hlb":

I'll come up with another Python to dump in a more formatted fashion way.

Hello there!  I'm trying to run your Python app from Terminal, but I'm having trouble getting syntax errors...  Is there any chance I could get some help with this?  I've never played with Python, but would like to get the readout from the Helix Bundle file.  Thanks in advance!

On 12/17/2017 at 2:06 PM, jonandtice said:

So I whipped up a very basic hlx file viewer as a proof of concept.  I've taken it as far as I can with my limited programming skills so hopefully this generates some interest.

test.html

Wow this is great! I've been looking for a possible way to easily view the details of my .hlx presets and this is an awesome start.  Would it be easy to add to this GUI?  I've not done any real coding or application design, but I'd love to help in any way to add functionality to this file viewer.  Specifics that I'd like to see is possibly buttons to change which snapshot you are viewing, as well as the parameters and values of the different blocks.  What do you think?  I know what sounds easy is not always possible...

By the way the main reason I'd like to have the ability to view the files is because I'm wondering if I'll be having to rebuild many of my presets from scratch;  I've been dealing with some buggy issues with parameters jumping around but after filing a support ticket I'm being told they are user error;  I'm pretty sure it's an issue with my unit, but I'm not sure if simply doing a fresh install of the firmware and a reloading of my presets will help my situations, SO I'm planning on doing a fresh install and rebuilding each preset manually;  my hope is that there will be a convenient way for me to view the information in each of my presets without having to reload them into the Helix and possibly causing "contamination" if that makes sense.  Sorry for the rant!  Regardless, let me know what you think of your GUI--I think it would be an awesome tool to utilize!

4 hours ago, ppoceiro said:

I found a similar behavior but not when synced via MIDI.

With the tempo set manually in the preset and switching to the snapshot with tremolo, the pulse doesn't align with the song.

Why is that happening if I switch snapshots at the exact tempo?

Doesn't bypassing/switching on an effect resets its LFO?

I'll try the step once tip but it's kind of annoying I have to step on another pedal to align the effect. Turning the effect on/off should reset the LFO.

I have found in 2.60 that occasionally when I switch snapshots the time parameter of delay and mod fx blocks switch from say 1/8, 1/4, etc. to ms... If I were you I'd go into your preset, make sure you do not have the fx block in question selected (I've found that hitting the amp button and changing snapshots can cause this problem on my unit), change snapshots a few times, and then go to your fx block and see if the time has changed from a note value to a millisecond value.  Not sure if you're having the same problem as I am, but it's worth checking...

On 8/3/2017 at 9:46 AM, johoffry said:

Firmware 2.21

 

Assigning a CC Toggle to Footswitch setting dim value and lit value

 

Problem:

As I switch through my snapshots the values are reversed.

 

My application:

 

Assigning footswitch to MIDI Mix Control on my Big Sky. When I hit the footswitch it increases the mix. Unfortunately, when I change snapshots the MIX is automatically switched even without the footswitch being pressed. Has anyone else had problems with this? Is there a workaround? Should I submit a bug report?

 

thanks

JeffM

I know it’s been a while since 2.21, but has 2.60 fixed this for you? I still get the random dim/lit switch occasionally when changing snapshots...

13 hours ago, redwanhamzah said:

I've updated to 2.60 and designed a few great sounding patches based around the new Cali Texas Ch.1 Model. However, is anyone else facing this issue I have, where the volume keeps dropping and then completely disappears? 

 

I've tried a few solutions that I've seen provided after searching about this online - such as not leaving the bass control at 0 (I have mine at 0.3, and 3.9 depending on gain structure and snapshot), and also assigning EXP 2 Pedal Position to 'Global' instead of 'Per Preset'. Unfortunately that still does not resolve the issue.

 

It definitely is solved after I go to a different preset and then back again, but that does make it highly worrisome. Just played two relatively big shows where I had a bit of anxiety just making sure my volume wasn't dropping by continually going back and forth between presets, in between songs.

 

Do chime in if you're facing this - and also if there are any solutions!

 

best,

Redwan

Hi Redwan, just curious: when your volume drops out have you been able to stop and check if any parameters have dropped to zero? Perhaps you have your amp’s master volume set via snapshot and it’s bugging out?  Again, just curious-I just posted about some of my parameters in other blocks going haywire; on the amp though it’s usually my presence going up to ten...

So I updated to 2.60, and have been enjoying the update.  There are two things that I have noticed:

1.  MIDI Messages Assigned to Stomp Buttons

I have posted before regarding MIDI bugs in stomp mode and command center; so far the Instant Commands are working better than they were before, but sometimes the stomp CCs can be a bit buggy.  The main thing I've noticed is that if I have a CC message assigned to a stomp button, it will occasionally switch to a lit state in between snapshots; this wouldn't normally be a huge deal for me, but I mainly use the CC messages to utilize transport controls in Ableton Live.  Occasionally when I switch snapshots, the Fast Forward button will be lit, and then I can't stop the fast forward function unless I completely clear the MIDI message from that particular stomp... weird... Anyone else run into this?

2.  Unexpected Parameter Changes In Snapshots

So, I believe I have experienced this before 2.60, but it was never so frequent that I felt the need to post to forums... Since updating, however, it seems to be happening a lot more often.  The unexpected changes occurs on a multitude of blocks--Amp (Presence settings), Modulation (Time), Delay (Time, Feedback, and Mix), and Reverb (Mix).  Two things happen:  First, there are occasions when the time parameter switches from my tempo specific note values (such as 1/4 or 1/8) to milliseconds.  Second, there are times when the snapshot value shifts whatever value I have to 0%, 1%, or 100%.  This is of course a huge shocker to me when I hit a note or chord with delay on and suddenly the note doesn't stop repeating due to the feedback being at 100%.  I've not been able to pinpoint exactly what causes the issue, but I think it may have to do when I plug in my Variax and press the model knob to turn on the Variax (which, by the way, my Variax always turned on automatically [if I'm remembering correctly] when I'd connect to my old HD500, is this the way other peoples' Variax functions with their Helix?).  It may also just happen when I change quickly between snapshots.  One last strange thing in regards to this issue:  It seems like this either affects how the Helix exports or imports the presets as well.  There are times when I know I export the preset with all the right settings, but other times I can load the preset and the issue is evident upon importing it to a new preset.  Again, anyone else run into this problem?

On 8/14/2016 at 9:58 AM, Digital_Igloo said:

 

Yep—works great, but the latency isn't ideal. Perfect for synth pads or bass parts without notable transients.

Any idea on when (if ever) the latency on sending notes might be fixed?  Maybe it has already;  I only ever tried using the MIDI notes on the Helix once to trigger some samples in MainStage 3... ideally they would have synced up with the click the band was playing with if I hit the button relatively near on beat, but sending the MIDI note from the Helix didn’t work too well.  Funny enough, sending the MIDI note from my FCB1010 worked flawlessly and that signal passed through the Helix on its way to the laptop...  so I’ve settled with that routing ever since.  I’d love to one day have the Helix be my sole controller for both sounds and MIDI :-)

On 5/17/2018 at 6:56 PM, Roberttheprole said:

I'd like to give a shout out to having back the ability to send midi messages when changing snapshots!!! Seriously!!! Updates are supposed to be just that! So curious how that wire got crossed! Whatever the case, is this not important to everyone as it is for me?!?!?!?

hahaha

So I was dealing with an issue this past week with my Variax USB interface (probably the 1st of June) and I spoke to a rep via telephone who mentioned the upcoming 2.6 update for Helix would have a massive number of midi bug fixes. Nothing more specific than that, but here’s hoping they live up to their claim that the Helix should be a “world-class master remote control for your entire touring or studio rig” (page 45 from the 2.0 Owner’s Manual).

Ha!  Wow Saxer, that's a ton of info!  I can't really talk though-my video was fifteen minutes long!  Like you, I'm glad (I use that word loosely) to hear someone else shares the same issue.  Like Phil suggested, I did send a support ticket and received this response:

"I'm sorry about the trouble with your gear. Thanks for the detailed info. We are aware of these midi bugs and have them logged. A fix will be implemented in a future release. Thanks for your patience while we sort this out."

Not sure how long the wait will be until the "future release" arrives, but I'm hoping soon :-)  Thanks Phil and Saxer for your input!

On 4/25/2018 at 6:44 PM, phil_m said:

 

Sorry... I have to confess that I didn't watch your video the whole way through the first time. Have you tried running the MIDI monitor without having Ableton open? I kind of suspect that what you're talking about might have to do with MIDI over USB and Ableton mirroring commands it's receiving. I vaguely remember reading about someone else running into this.

No worries, Phil, it was a long video (I added time stamps to try to help with that, lol)!  I wasn’t aware of an issue of Ableton mirroring commands;  I performed many of the same tests while running MIDI messages via USB into MIDI Monitor without Ableton running (an additional difference is that in my video I was running MIDI from the Helix via a MIDI cable into a M-Audio Midisport then from there into the computer via USB; I did this because sometimes when I run the MIDI into Ableton directly via USB it causes some freaking out issues… perhaps this is the mirroring you were discussing).  With the simplified setup I’m still running into the same issues.  I created a backup and tried a couple of factory resets with similar results dealing with what I feel are bugs in the system:

After booting while holding down footswitches 11 + 12:

Still multiple firings of mixed CC data

Adding a Program Change resets my CC values to zero

Adding a CC toggle to footswitch in stomp mode resets my CC values

After performing a factory reset (holding down footswitches 9 + 10):

Still multiple firings of mixed CC data

Occasional re-firings of PC data for snapshots which have PC set to off in command center

Adding a CC toggle to footswitch in stomp mode resets my CC values (one snapshot retained its CC value) and my PC values

Not sure what other steps there are for me to try out, any ideas?  Thanks again for your time and help! :-)

8 hours ago, phil_m said:

 

The thing to realize with assigning CCs to Instant Commands is that when you switch snapshots, the value that you have set in each snapshot for each CC is being shot out. So you mentioned in the video that a certain CC is assigned to a certain snapshot... That's not really how it works. That CC is set for that Instant Command for the entire preset. You need to go set a specific value for that CC in each snapshot then.

Thanks, Phil!  Yeah, I realize that when a CC is created in Instant Command it is present on all snapshots;  one of the big things that isn't functioning as it should (as far as I know) is that when one of my snapshots 1 thru 4 are pressed, CC numbers are firing with values of 127 that should be set to 0 prior to firing the correct CCs and values (this is demonstrated in the last minute of my video), causing tracks in Ableton to restart.  I also documented this via MIDI Monitor.  Any idea of why this might be happening on my unit?

So I haven't run into the issue as of yet with the distortion blocks, but I have been having an issue with the MIDI program changes.  I contacted Line 6 yesterday and I'm waiting to hear back from them.  I'll post a video below demonstrating how it seems that program changes are causing things to bug out.  Did you ever figure out a solution?

One of the weird things I noticed is that when I viewed things through MIDI Monitor: there were times when hitting a snapshot would send a ton more extra data then it looks like it should (around 4:30 in my video).  In my opinion it definitely looks like there is a bug that needs to be worked out of the system.  Let me know how things are working for you :-)

https://youtu.be/i_EUtOd-y60

Not to make a nonsense post, but I just saw that I could select the "Notify me of replies" slider and wanted to make sure that I'm aware of anything any of you might say... Thanks again everyone! :-)

On 3/25/2016 at 10:59 AM, Digital_Igloo said:

To assign block on/off to a footswitch in three seconds:

• Use the joystick to select the desired block.
• Touch (but don't press) the desired footswitch for two seconds and press Knob 6 (OK).

To assign a model parameter to a footswitch in three seconds:

• Press and hold the parameter's knob. Helix jumps to the Controller Assign page for that parameter.
• Press Knob 6 (Learn Controller) and then press the desired footswitch.
• OPTIONAL: Move Knob 4 (Min Value) and Knob 5 (Max Value) to restrict the parameter range and press HOME to exit.

To assign a Command Center command (MIDI, Amp Control, CV, CV Toggle) to a footswitch:

• Press MENU (three lines icon) and then Knob 3 (Command Center).
• Use the joystick to select the desired footswitch.
• Turn Knob 1 (Command) to select the type of command Knobs 2-5 to set the command's values.

Up to 8 of the above items (any combination) can be assigned to a single footswitch. If you want two blocks to toggle back and forth, select one and press BYPASS.

 

Repeatedly touching a footswitch will cycle through all assignments. This is the reason we limited footswitch assignments to 8 items—cycling through any more than 8 would be annoying. In this case, we artificially restricted functionality for UX's sake.

 

The 64 controller assignments per preset is a technical limitation, however.

Howdy!  I'm just making sure I didn't miss anything, but is there a way to assign more than one MIDI command to a footswitch in stomp mode?  So far I haven't figured it out...  I know that instant commands are possible per preset or snapshot (which I haven't played around much with yet), but I was just checking in to see about multiple MIDI commands getting assigned to a single stomp mode footswitch.  Thanks in advance for any direction :-)

That's dedication! Frankly I think your solution is more cumbersome than the problem it's trying to solve, but to each his own. I do know that you run the risk of creating a corrupt preset which will have unpredictable implications, up to and including bricking your Helix. Any small typo that you make could cause significant issues when loaded into Helix.

Thanks! I think the explanation is cumbersome, but the process, imo is actually very simple; simple that is in comparison to going through block by block and noting all of the various [settings] from snapshot to snapshot and re-inputting these settings into a new snapshot of a new preset. Here I simply copy and paste.

Honestly, what I was originally looking for in the text of the .hlx file was maybe a type of csv that would save me the time of transcribing all of my snapshot data, but when I saw the format of one .hlx file compared to another and that it appeared to be apples to apples line for line I figured I'd try the approach I use in the video.

Was it risky? Yeah, and maybe foolish for me to have tried since I was only trying out of frustration of the tediousness of doing what felt like a lot of repeated editing. When I first imported a test I have to admit I was holding my breath (probably afraid of a resulting Helix brick), but hey it worked!

There actually is an example of a syntax error in my video-when renaming the preset the text editor changed the format of a " that the Helix does not like. This error resulted in a URI error (I believe that's what it was), but the only result (to my knowledge so far) was the inability of the Helix to import the new Preset. I still need to export my set lists and bundle to make sure that any attempts to import a bad set list doesn't create any corrupted preset slots or anything, but I feel it would be highly unlikely to do that.

But thanks for bringing up the possibility of a potential brick, it is indeed important to be mindful of the worst case scenario!

The biggest question I have now is whether this could be incorporated into the Editor. Since the code is apples to apples, I see no reason that I couldn't copy a snapshot from one preset into a master clipboard and paste it into another preset if the preset layouts match. I'm not a software designer, but it seems like it would be a simple if/then line of code: if the preset layouts match then the paste is successful, if the preset layouts do not match then the user receives a message noting the paste could not be performed due to layout inconsistencies. I dunno. Is that too much to ask?

Thanks for the suggestions.

The idea is that I want to save the song-specific snapshots and recall them quickly in future, without having to manually input and change every single parameter of each different snapshot (I'm thinking all of us here know how tedious it is to do that).

I actually figured out how to do this and made a video on it:

Once I have the snapshots the way I need them for a song (for example for Song 1 I use Snapshots 1-3), I export the Preset onto my hard drive, and then I open the .hlx file using TextEdit (I'm working on a Mac). From there I can copy and paste from that Preset into a new Preset giving me the option of quickly creating a Preset for any given Sunday without the hassle of tweaking all of the individual snapshot parameters.

Of course for the copying and pasting into a combined Preset to work, the individual songs/presets/snapshots that I'm combining all have to have the same blocks, signal path, etc. but as I said in my OP, I'm okay with that.

No, not possible.

 

I'm curious, though. Why not create a separate preset per song?

Thanks mkornell.  I used to do exactly that, with my POD HD500 that is.  The only problem was that the tiny audio gap between changing presets got a little too deep under my skin (a problem that still exists with the Helix).  The snapshots work for exactly what I need, eliminating that little audio gap.  It was much easier saving one song per snapshot.  So far I've worked around this minor limitation by saving snapshot information to an excel sheet and referencing that when creating a new preset for a new week's set.

Hello All,

I just got my Helix today and I'm trying to customize it to exactly how I'd like to use it, but I've got a question that there may not currently be an answer to:

Is it possible to copy a snapshot from one preset and paste it into a different preset?

Here is why I would like to do this:

I lead worship services that typically consist of somewhere around 4 songs.  I'm planning on having a rig on a single preset in which each snapshot consists of the settings for each song.  If possible, I'd like the ability to store and recall the various songs/snapshots for future instances of doing any one of those particular songs.  I realize I wouldn't be able to change any of the blocks in the rig by doing it this way, but I'm okay with that.

I feel like if (for example) Preset 01A and Preset 01B have everything the same the Snapshots from one to the other should be compatible.  Of course, I realize nothing in software is as simple as it sounds, but is there anything like this, that is to say storing snapshots so they can be pasted into other presets, currently possible on the Helix or maybe something that could happen in the future?

Thanks in advance for input!

I don't find this to be problematic. I create song-specific presets. Depending on the song, I'll set up one amp configuration on one of the 2 available DSP paths, and a second amp setup on the second path. Both paths have what additional fx are needed to support that path. I'll setup a single foot switch to toggle between which amp setup is active and which is bypassed. Other foot switches may be assigned to manage fx in either signal chain.

 

The other added benefit of this approach is that I name my presets by the song name along with including the key signature in the name. I can then assemble a set list of "songs" knowing that when I hit the foot switch for that song, everything I need is immediately under my feet (including having the appropriate BPM tempo loaded given the number of songs we play that utilize click tracks and loops).

Mike, it sounds like the way you create your song-specific patches is a lot the way I do as well, but it isn't clear to me how you avoid the audio gap when switching between song-specific presets; using the 2nd signal path I understand, but can the tempo be adjusted automatically when switching to the second signal path? And if this is possible, what do you do for the rest of your songs?

To be clear, I build a preset for song 1 (at 130 BPM), and then a second preset for song 2 (at 110 BPM), each preset with different amp and effect settings (and then I do the same for song 3, song 4, etc.). The patches sound great (in my opinion), but the problem arises when we ring out song 1 and our in-ear click counts the band off to start song 2. The gap is short, but it's still a gap and in my opinion kills the transition.

So anyways, Mike I quoted you because you're the only person I saw in this thread that posted ANYTHING about song specific tempo (and it's possible I missed a post), so, again, I was wondering wondering, do you don't find the audio gap between song presets problematic?

And for everyone else, doesn't tempo alone merit the idea that using multiple presets that are song specific in a gig is more useful than being stuck on a single preset? It seems to me a song for a guitarist revolves a lot around their created tone, but a song for any musician revolves around a (normally) pretty specific tempo...