HonestOpinion

Bump, I know the post above is long but it really comes down to what are you seeing for the active/bypass state of the added block in the rest of your snapshots when you add a bypassed block to snapshot#1 and then save. Is anyone else seeing the same bypass/active behavior described above? Trying to confirm if this is a bug or just happening on my Helix. Thanks!

You can assign the 'Threshold' parameter on the noise gate to the snapshots. The more distorted and noisy your snapshot is the more you raise the threshold. Distorted leads get a higher threshold and cleaner sounds a low threshold setting, often to the point where it never engages as it is unnecessary. If for example you have "Clean, Rhythm, Chrunch, Lead", snapshots set up each one gets a progressively higher threshold setting.

As the previous posts here indicated unless you get alternate instructions from Line6 the procedure is ALWAYS to create a backup, then download and run the latest HX Edit "application suite" and NOTHING ELSE! By default "HX Edit" will install not only the editor but also the matching version of the Line6 Updater and the driver. Now do backups again using your freshly installed editor and use the Updater to update to the firmware version that matches your version of the editor. All these files, the editor, updater, and driver must be matched and then the Updater used to flash the matching version of the firmware. Don't download these files individually as this is a perfect storm of a recipe for ending up with a mismatch of these critical software components, particularly editor and firmware, and when that happens it is absolutely guaranteed to cause problems or appear to be missing new features. I still believe Line6 would be well served by changing the downloads page so only HX Edit showed up prominently for the HX line of products. Also, change the name of the "HX Edit" download to something like "HX Application Suite". It can be very confusing to new users to see a group of separate software products (editor, driver, and updater) named after only one of its components - the editor in this case. It causes them to think they need to download and install all the components separately. The separate flash, driver, and Updater files should be buried under an "Archive" or some other such heading on the downloads page so as to reduce the level of confusion generated for new users when these downloads are all listed together along with "HX Edit". Currently and often in the past, the HX Edit download is not even displayed as the first download option. Note: There may be rare occasions where Line6 issues an editor, updater, firmware update, or driver to correct a problem where you will need to install these components individually but this is infrequent and following instructions carefully should allow you to update without a hitch.

I agree this has always been a bit of a pain and I would say quite often a block gets added that you only want active in one or two snapshots. The easiest way to do this I find is to make sure you are in snapshot#1 when you add the block, bypass it, and then save. This should leave it bypassed in the rest of your snapshots. But.... I think there may be a bug, at least on my Helix (firmware 2.60). When I do this in Snap/Stomp mode with for example four snapshots showing on my top row, stomps on the bottom row, the 4th thru 8th snapshots always seems to have the block state active, even if I set and saved it to be bypassed in snapshot#1. Snapshots #1 thru #3 have the block bypassed as I would expect. If I have the global preferences set to show all eight snapshots on the footswitches, then it improperly sets the bypassed block active only in snapshot #8. Kinda weird. Btw, make sure you have the editor dialed up when you test this so you can see what is happening in snapshots #4 thru #8, even if you are using for example a Snap/Stomp setting on the Helix. Important Note: This testing was done with 'Snapshot Edits' = "Discard" In other words, as long as you add the new block in snapshot#1 and set it to bypass, its block state gets saved correctly in every other snapshot except for the last one showing on your footswitches setup thru to the last. In a stomp/snap setup, if you bypassed the block, that means that snapshot#4 thru #8 is always wrong and in all 8 snapshots footswitch mode that means snapshot#8 is always wrong. Anyone else seeing this bug? Summary: I don't think the global settings for footswitch mode('Preset Mode Switches'), and possibly the 'Snapshot Settings' as well, are interacting properly with block active/bypass state when doing preset design. I think there is a bug where the 'Global Settings' --> Footswitches --> 'Preset Mode Switches' setting (Snapshots, Snap/Stomp, etc.) is interacting with how the active/bypass state is being saved in snapshots. The 'Preset Mode Switches' setting should not have any effect on a block's active/bypass state when saving presets or snapshots. Also, although your Preferences --> 'Snapshot Edits' setting(Recall, Discard) setting can and should have an impact on how snapshots are saved as per design, there is a possibility this behavior may also be interacting in unexpected ways with block active/bypass states. I have not run the above tests with 'Snapshot Settings' ="Recall" so I am not sure if results will vary depending on how this global setting interacts with the 'Preset Mode Switches' setting. WORKAROUND: So, at least for right now the workaround if you want all your snapshots to inherit the bypass state of a newly added block is to set 'Global Settings' --> Footswitches --> 'Preset Mode Switches' = "Snaphots", at least for the duration of your preset design session. Make sure you are in snapshot#1 before you add your new block, bypass it, and save. Now go to snapshot #8 and bypass the block and save.

Have you tried a different pair of headphones? Do all headphones behave like these or just your 64 ohm Sennheisers?

Thanks for the settings! Just curious, why do you recommend Trails = "Off"? Does it sound out of control when you switch snapshots?

The fact that you have not really changed your firmware or presets prompts a low-tech solution. Unplug and reseat the Variax's VDI cable on both ends; or even test another one if you have a spare (a spare ethernet cable can be used for the duration of the test). Another thing I would try is moving the controls on the Variax around particularly the model knob. Perhaps something got wonky there.

One thing to check is go to any preset with a Variax set for the Input block and go to the second page of the parameters for the Input block and make sure the 'Variax Settings' parameter is set to "Per Preset". It will affect all of your other Variax settings as it is a global settings despite the fact that it is located within a preset. Restoring a full system backup from January that may or may not have your snapshots seems like a bad plan unless you are talking about individual presets backed up that can be restored to new locations so as not to overwrite the current ones that include your snapshots. In either case I would make current backup(s) before restoring anything. That January backup is not exactly current. Btw, what version of the firmware are you on? One of the behaviors now with the Variax in the 2.6 firmware is that unless you force a new tuning when you switch presets it will stay on the tuning of the last Variax preset you had selected.

Here again is BBE's literature regarding this pedal: It imparts a pre-determined phase correction to the high freqs where most harmonic information exists. It breaks the signal into three sub-bands or groups; Low freq group which is crossed over at 150hz, the mid xover@2500hz and the high freq group that handles everything else up to 20k Low group is delayed 2.5 milliseconds (below 150hz) It has a control to set at flat or boost @50hz Mids are delayed at .5 milliseconds while the highs are passed through a voltage control amp. The high group is used as a point of reference to make dynamic amplitude corrections to the high freqs RMS loudness detectors continuously monitor both the mids and high freqs to compare the relative harmonic content levels of the two bands and apply the appropriate amount of control voltage to the VCA thereby determining the amount of high freq harmonic content present at the final output With the exception perhaps of the " pre-determined phase correction to the high freqs" that the BBE literature quotes, theoretically you could get close to replicating most of what this pedal does on the Helix by using the crossover EQ combined with a 2.5 millisecond delay on lows below 150hz and delaying mids by 0.5 milliseconds. The "dynamic amplitude corrections to the high freqs" could be duplicated to some extent by use of the multi-band compressor. A lot of trouble to got to for a sound many aren't that enthusiastic about to begin with but I think with some expererimentation the Helix could probably get you close even now without a BBE plugin.

Hmm, haven't gotten around to testing a fuzz block yet in the new firmware as I rarely use fuzz. Sounds like you were aware of the impedance requirements for fuzz pedals in the past firmware versions though. You may want to talk to Line6 and see if they have intentionally changed something with the fuzz blocks or establish if you have discovered a bug.

I agree this definitely sounds like the problem. Upgrading to the 2.6 firmware necessitates downloading and installing HX Edit 2.6. As a matter of fact the firmware notes recommend doing a backup with HX Edit 2.6 before upgrading to the 2.6 firmware.

I think some people have gotten around the volume/sound changes when the fuzz is bypassed by assigning the Impedance parameter value to a snapshot or to the same stomp switch as the fuzz such that the impedance changes when the fuzz is engaged and bypassed. You may also find it works better when the Impedance is set to "Auto" and the fuzz is the first effect block in the signal chain.

The italicized text below is from a post attributed to the BBE literature. If that description is accurate this would definitely need to be an effect not an IR. There are BBE maximizer plugins so I imagine Line6 could probably create it as an effect block if there was enough demand. I wouldn't mind seeing one make its way into the Helix although both the pedals and the plugins have been received with mixed reviews, many of them negative. I have managed to get good results out of them both in rackmount form on PAs and in pedal form on a guitar pedalboard. Just one more tool to be used, sure, bring it on. It imparts a pre-determined phase correction to the high freqs where most harmonic information exists. It breaks the signal into three sub-bands or groups; Low freq group which is crossed over at 150hz, the mid xover@2500hz and the high freq group that handles everything else up to 20k Low group is delayed 2.5 milliseconds (below 150hz) It has a control to set at flat or boost @50hz Mids are delayed at .5 milliseconds while the highs are passed through a voltage control amp. The high group is used as a point of reference to make dynamic amplitude corrections to the high freqs RMS loudness detectors continuously monitor both the mids and high freqs to compare the relative harmonic content levels of the two bands and apply the appropriate amount of control voltage to the VCA thereby determining the amount of high freq harmonic content present at the final output

You are looking for the HX Edit 2.60 software. For example if you have Windows 10 you would find it here: https://line6.com/software/readeula.html?rid=8417 Download the HX Edit suite and run it and it will install the Line6 Updater, HX Edit, and driver on your computer. Run HX Edit to backup your presets.

Btw, if you have a hub around try that too. It is more likely to hurt than help but any alternate USB option is worth trying along with Windows updates, disconnecting all other USB externals, and minimizing what programs you are running on the Surface. A fresh boot never hurts either. Good luck!

You make a good and interesting point - "vive la difference". I think many players like to both embrace the difference between for example a Les Paul and a Strat but also modify their settings to take advantage of and optimize the sound of their guitars' individual characteristics as matched to the preset. I often find the two goals, maintaining the guitar's unique character and optimizing the preset aren't mutually exclusive unless you are over-processing the signal to the point of every guitar sounding close to the same. With that said I'm certainly for any hint,quick fix, or setting that allows fundamentally different guitar and pickup variations to sound good on the same preset.

Yep, definitely need the driver. Hopefully it got installed when the OP installed HX Edit 2.6. As the OP mentioned that is the default behavior for an HX Edit install as long as you don't uncheck the box. As pointed out by cruisonon2 experimenting with switching to other USB ports is a good place to start. Btw, make sure that both HX Edit and the Line6 Updater are never active simultaneously; you want to use only one at a time. I also seem to remember some users have trouble with particular, maybe earlier, hardware versions of the Surface Books in the past. There may be certain versions of the hardware that work better than others. Maybe some Surface owners can chime in. Yep, definitely some other users having issues with Surface Books. Looks like one thing to do is to make sure you have all the latest and greatest with Windows Update although there may be some potential issues there as well. A couple of other topics on the issue:

Yep, good call, did not notice that. "Multi" means that the piezo as well as the magnetics was going through the upper path. Sounds like you solved it.

Assuming you have checked the path just with the piezo on to make sure the distortion is not originating on the upper magnetics path. Check the headroom parameter in your delay on the piezo path and try increasing it. A low headroom setting can cause distortion. Also of course the "Drive" setting on the "Pre" could contribute to this as well. Worth checking and could be causing the problem although you should be able to use a "Pre" as this preset does without a cab on piezos and not get distortion. I have done this with acoustic guitars with piezos without issue.

Sounds to me like you may have just activated the capacitance sensitive footswitch capability. Not a bug, a feature. Just don't touch a footswitch while you are changing global options.

You could probably go through either. Sweetwater generally has a two year warranty (same as Line6 currently in the US). They will often replace your unit with a new or repackaged one in short order rather then making you wait for a repair so you could start with them or go through the warranty process with Line6. Most people find the repair turnaround with Line6 to be pretty stellar as well. I would lean towards whichever one offered to pay for return shipping. I have found both Sweetwater and Line6 to be excellent regarding service. Btw, thought it worth mentioning that if you are running out to a monitor or FOH in mono make sure you use the left XLR output as it automatically sums the Helix's stereo path to mono. Also worth getting on a support call with Line6 before sending it back to either to make sure it is not a configuration issue.

Glad to hear it worked! The key to this is looking at how the bypass assignments are set up for the whammy and volume blocks. Amazing how complex assignments can get for the Helix. Cool preset btw.

Good point if everyone is using IEMs, no feedback.

Sure it won't be an exact representation for the soundman because he doesn't have them in his ears, and stating the obvious but this is why running sound requires a pair of headphones and knowledge of the solo function on the mixer. Rudimentary stuff. He should be able to get a pretty good idea what he is sending from the board that way and the musician can help tell him/her what they need to fine tune their monitor mix. I can see where catching feedback issues in the monitors in a timely fashion can be a little trickier if there are no stage monitors for the soundman. Just keep an eye out for the pained look on the face of the player with the IEMs.

Not sure I am entirely clear on what you are trying to set up but I hope this helps. If I did get your intention correctly you were pretty much there, all you had to do essentially was remove the footswitch 11 assignment and assign the bypass for the whammy to the toe switch. Then go in and set the bypass states for the volume and the whammy block to switch back and forth between them (e.g. toe switch on EPX1 - volume bypassed whammy active and the reverse for EXP 2). The attached preset may help get you in the right direction. It is your preset slightly modified. If you don't want to use the expression pedal toe switch to switch on the whammy you could set it to come on using the expression pedal position as well. Another approach would be to set both the volume block and whammy bypass to footswitch 11 and have that footswitch alternate between volume and whammy. WhammySwitch.hlx