HonestOpinion

The Rack Control does not require the DC power for capacitive touch. There is an interesting blurb in the manual though which points potentially to phil_m's advice to try a different Ethernet/Ethercon cable, and one that is not too long according to the manual. Btw, the manual recommends a Cat-5 or Ethercon cable. It might be worth testing the touch feature without any other cables plugged in other than power and Ethernet to make sure there are no grounding or short issues with a cable. From page 10 of the Rev.D manual: DC IN Reserved for potential future use; for very long cable lengths, use a Line 6 DC-3G adapter (purchased separately)

If this has never happened during practice/rehearsal and does not happen again my first suspicion would be poor power or a loose power connection on the device or at the wall at the venue .You can always get a power conditioner as a preventive measure for the future.

If after exhausting your own efforts and others' suggestions you still can't get this to work I would open a ticket with Line6. If there is a way to get this working hopefully support will provide it and if not perhaps it is a bug they can work on resolving.

No. Keep your guitar and vocals feeds from the Helix separate. I would run my guitar out via 1/4" to my FRFR and then send use the XLR output on the Headrush to send a feed for the guitar to the sound man. Use the XLR output on the Helix to send a second and separate XLR feed for the vocals. I would not split the left and right XLRs on the Helix like this. That will force you to cater all your presets to a dual mono approach. Instead use one path on the Helix for guitar and a second path for vocals. Send your guitar from the 1/4" output(s) on the Helix as indicated in my response to point #2 and send your vocals out via XLR and provide separate discrete XLR feeds for respectively vocals and guitar to your soundman. This approach will result in your soundman having an XLR feed direct from the Helix for vocals and a second XLR feed from the output on the back of your Headrush for your guitar. You can monitor your vocals through your sound system's vocal monitors(assuming you have them) with a feed direct from the board and your guitar from your Headrush. Note: If the run is short enough you could send your soundman a 1/4" feed for your guitar directly from your Helix instead of the XLR feed from the output jack on the back of your Headrush. Your choice. This approach will free you from having to worry about left/right routing/panning in your presets, allow you full control over your guitar monitor, and put the vocals in your face the way you want them with a feed from the board to your vocal monitors. The one drawback to this approach may be that changing the volume you send to your Headrush onstage may also change the volume your soundman is receiving for your guitar. This is a compromise you make when you use the Helix for both vocals and guitar in this particular live setup. That requires having your presets leveled properly for the gig and finding a volume for the Headrush that works for you onstage and then leaving it alone so you don't keep changing the level sent to the mixing board. Essentially you want to use your master volume as a "set it and forget it" control. Btw, I would assign the volume only to the 1/4" output which will send the vocals out at unity but allow you to control the guitar's output level to the Headrush. If the restrictions for this proposed setup prove to be too problematic then you could proceed with your approach of sending the guitar out one XLR output and vocals out of the other but you will have to play close attention to your routing/panning in every preset to prevent mixing vocals and guitar into the same XLR out(L or R). What a pain. Just the way I might approach things. Maybe someone else has a different/better recommendation.

The rack is designed to get adequate volume with higher impedance headphones. Not sure what is going on here. Some suggestions might be tor turn up the volume somewhere in the preset, add a headphone preamp(kinda redundant and not the best option), or try another set of headphones. Another more novel approach is to use the Global Settings --> 'Ins/Outs' --> 'Headphones Monitor' setting for a separate feed for your headphones. If you are not for example using your XLR outs you can use this parameter to send only the signal from your XLR out to your headphones and then set the volume level for this path's Output block louder. Not sure whether it is reflected in the headphone feed but you may want to set the output for your selection for the 'Headphones Monitor' setting to "Line". I think I would opt for just trying a different set of headphones though :-)

Cool, just wanted to make that clear as many newer users are not aware that they should have HX Edit shut down when they run the Updater and consequently can't understand why the Updater is not seeing their device when both are up. Generally it is the installation, not the running of HX Edit, that will enable the USB driver as part of the installation of HX Edit is to install the latest driver. It is part of the install package. I find it interesting that you seem to have observed that just running HX Edit changed something on your computer. Not sure why that would have made any difference. Wonder if some process was hung that was able to shutdown properly after you started and stopped HX Edit?

You do NOT want to have HX Edit running while you are using the Updater. It will prevent the Updater from seeing your HX device. Use one or the other but not both. That is why quitting HX Edit is the first step in SaschaFranck's directions.

If you do locate a preset where you can make this issue occur with regularity you may want to upload it so others here can see if we can recreate the behavior you are seeing. Btw, that is a substantial repertoire!

The manual as you say is vague but I read it as essentially saying that every Variax setting on pages 2,3,&4 of the Input block are impacted by the 'Variax Settings' parameter, either globally, or on a per preset level. This setting does not for example have an "Off" option that ensures only the controls on the Variax guitar itself will make changes. You can set the individual Variax parameters in either mode, "Global" or "Per Preset", in such a way that it ensures only the guitar has control. If you for example run this setting in "Per Preset" mode, and most will, each time you change presets the Variax will change to the settings you have in that preset, contingent on which parameters you force, as you would expect. Changing this setting to "Global" causes every other Variax preset to reflect any Variax parametes you change in the current preset but not edit their previously stored Variax settings. Under the covers all your presets will still have the Variax parameters you originally saved them with, you just can't see them at the moment and they are not active. In practice that means now every other Variax preset you go to will have the settings of the preset where you switched "Global" on, for example the same model and tuning. If you jump to another preset(with 'Variax Settings'="Global" still on) you will see for example that preset now has the model and custom tuning from the preset you were in when you turned "Global" on. Here's where things get interesting. If you switch to another preset and change for example the model and the tuning, when you jump back to the one you initially set "Global" on in, it will now reflect the Variax settings from the subsequent preset where you made the changes. Setting 'Variax Settings'="Global" changes every parameter setting from pages 2-4 that is "forced" into a global setting. It doesn't matter which preset you set them in. See caveat in next paragraph. Caveat: The parameter 'Global Variax Tuning' must be set to "Custom" in any preset you jump to for the tuning to reflect the behavior of the parameters you set in the preset where you turned on 'Variax Settings'="Global" . Although I operate in the "Per Preset" mode I always leave 'Global Variax Tuning'="Custom" anyway to ensure predictable tunings. Including all presets with standard tuning. Let's say now you decide to return to 'Variax Settings'="Per Preset". All of your Variax presets will revert back to displaying the parameter values you assigned on the Input block from pages 2-4 when you first designed and saved the preset and before you changed the 'Variax Settings'="Global". In other words, all the Variax parameter changes you made while you were in "Global" mode are ignored in all presets and all presets revert back to the settings you had saved while in "Per Preset" mode. "Global" is in effect a temp mode that does not edit your underlying presets' saved Variax settings. The Variax settings you change while you are in "Global" mode are in effect only while you are in the "Global" setting. Fairly complicated behavior and overall the easiest way to go is just to leave 'Variax Settings'="Per Preset" which gives you maximal "remote" control over the Variax while using the Helix/LT.

Please let us know how it goes. Also curious if this happens on presets created from scratch on the latest firmware or only older presets from previous firmware versions.

Only other things I can think of at the moment is to either export and reimport the presets where this is happening and checking and reseating the Variax cable or even swapping it out. You can use a standard Ethernet cable temporarily(and carefully) for testing if you don't have a second VDI cable. Also important that last time you upgraded you did the recommended backup, global reset, restore.

I find it interesting that you got the -8609 error in the four restore tests you ran only when you tried to restore the Favorites. I can't think of any reason that a Favorite would have a setting exclusive to the Helix Floor that is not shared by the LT. Was that test repeatable? I will be curious to see if others will confirm this error on cross-device restores that include their Favorites. It occurred to me that it looks like you actually found two issues here unless they are somehow related and I can't see how at the moment. One issue with the -8609 error when you tried to do a cross-device restore of Favorites. A second bug that looks like a cross-device translation error where a preset from the Helix Floor hangs upon usage that has been saved with Command Center options not available on the device it was loaded to(LT). Btw, did you do a restart after restore and let that preset rebuild before it hung during testing because as you stated it did seem to translate properly when imported rather than restored? I am curious if the rebuild process after restore/restart would have fixed it and if not why? Glad you opened a ticket on this. Your efforts here will probably save some other users a lot of head-scratching.

Do you have 'Variax Settings' = "Per Preset" on the second page of the Input block's parameters?

Check out this video. Or this one.

Well that sounds like due diligence to me and glad to hear you have a workable solution. Btw, when you say you are on "HX Edit 3.1" are you talking about 3.01 or 3.10? Sorry to ask but they are different versions of the editor and I think some users on the forum have been getting the two versions confused. The latest HX Edit version as you may be aware is 3.10.

Yes the backup/restore should still work although I don't have both units to test this. Have you checked HX Edit's 'Help' --> 'About HX Edit' to make sure you are actually on HX Edit 3.10 and the 3.11 firmware on both units? If not I would take another backup and download and install HX Edit 3.10 manually as well as making sure both devices are on the 3.11 firmware. Also, did you do the factory reset and restore on both devices after upgrading per the release notes? If not that is the first thing I would try after getting fresh backups. It might be advisable to restore each device's(LT and Floor) with their own respective backups before trying the cross-device backup. More tedious but it might get you there in the end. I would then try the cross-device restore again with your fresh backups or even get yet another set of backups after your global reset and restore and try with those. If this doesn't work I would probably do individual setlist exports from the Helix Floor and then try importing them to the LT.

Definitely worth upgrading although you didn't mention what version of Native you are on. If you have been keeping your Helix up to date, not updating Native will be a recipe for having issues if you try to trade presets back and forth between the two. It is generally a best practice to keep your HX Edit, firmware, and Native versions in synch. Hopefully that will eventually become part of the new more comprehensive updating process in HX Edit or be a similar process incorporated into Native. Btw, if you haven't made one before you can backup Native by clicking on the gear icon in the lower left corner of the Native plugin and clicking 'Export Bundle' on the 'Presets/IRs' tab. As you may already be aware there is no 'Create Backup' command in Native. As mentioned in the previous posts though the upgrade should maintain your current setlists. Btw, while you are there , if you have not checked it in a while you may want to take a look at the 'Hardware Compatibility' tab as well which has some interesting options.

Great to hear it is working! Would love to know why or what specific setting got changed. On the other hand you know what they say about gift horses... I would immediately get a fresh backup now that you have it working again, maybe with a note in the comments section like "MIDI working properly".

Looks like you have tried all the usual suspects. Just in the way of clarification, when you say that changing the Joystick Encoder setting has "no effect" did you mean that you are unable to scroll through either models or blocks? Another thing you might try is the Helix's Test Mode to get further into the hardware layer, perhaps helping to eliminate the firmware as a possible cause. Test Mode on the Helix First unplug every cable from the Helix - USB, XLR, Variax(VDI), 1/4", etc.. This might seem unnecessary but for example if I leave my USB cable plugged in the Helix test mode does not operate properly which can be kind of alarming. Maybe different brands or types of cables cause problems where others don't or maybe it is just the USB. Just pull 'em all. Hold down FS 3&4, turn on the Helix, and keep them held down until it enters Test Mode. Note: Strangely enough holding down FS 4&5 will also get you into Test Mode which may have been the case in all the firmware versions but definitely works in HX Edit 3.10, firmware 3.11. The FS 4&5 combination is not documented in Helixhelp.com and I have seen some confusion over which combination to use on the forum in the past and now I know why. Both combinations seem to work. I use FS 3&4 as it seems to be the one that is better documented. After you come up in Test Mode click the joystick down to enter into the '> UI Test' option. Turn the joystick and look to see if the 'ENCJ' entry in the lower right hand corner turns green. The green indicates at least some measure of proper operation. You can also check the number under it to see if it is responding properly. Clicking the joystick up/down and right/left should also cause its corresponding entry in the list to turn green. If that has not been enough fun you can check the rest of your knobs, switches, and expression pedal. Note: There are several other testing options in addition to the '> UI Test' in Test Mode. I find I have to turn the Helix off and come back into Test Mode if I want to use them though after I have run the '> UI Test'. Most(all?) of the other tests allow me to move between them without having to restart in Test Mode. Maybe there is a trick to doing this with the '> UI Test' as well but I have not found it. It might be as simple as checking every single item in the list under the UI Test.

Just one more thing to add. Although there are different opinions on this subject, if you haven't already, try setting your fader at unity and then adjusting the trim. Again, there is a good chance it will have to be set fairly low with perhaps even a pad engaged if your mixer channel has one. The problem with turning the fader way down for example and boosting the level on the trim is that small movements of the fader then result in much larger decibel swings potentially making it more difficult to dial in the correct level and possibly resulting in higher noise levels.

Any chance that a footswitch on the MC-6 has gone bad/sticking? Unlikely if both the up and down switches are not functioning properly. Have you tried switching presets with different footswitches on the MC-6? Probably did this but try switching out MIDI cables or at least reseating them and checking the connections. Also, did you do the factory reset, restore your global settings from when this was last working, and restore a backup? I know everyone is tired of hearing this recommendation but it is just a very good place to start. Also never hurts to doublecheck HX Edit's 'Help' --> 'About HX Edit' to make sure your editor and firmware are indeed on the versions you think they are(HX Edit 3.10, firmware 3.11).

What happens when you plug the Helix directly into an FRFR or amp without the mixer "in the mix"? Do you still get the hiss? The first thing I would eliminate is the possibility that something on my board was causing the hiss like an unused channel being left on accidentally or a bad cable. Have you tried swapping out the XLR cable? Tried different channels on the board? Adjusted the trim/gain level on the mixer's Helix channel(s)? On many mixers you have to set the trim way down to use the Helix, even when it is set to Mic output levels.

Ran the test again and got the same results as rd2rk and music_tech. It locked up on me as well. I missed the fact that music_tech specified that 'Preset Spillover' needed to be on in my initial tests, despite the fact that it was right there in front of me in black and white. I think you have found a legitimate bug and your subsequent posts did an excellent job of laying out the steps to replicate this behavior. A really fine job of troubleshooting. I believe you should open up a ticket with Line6 to hopefully get this addressed in the future. I guess the workaround for now is to not switch to the same preset you are currently on but this is a bug that definitely should be fixed. I don't see this issue when I switch to a different preset and then come back to the preset. Doing this also restores proper snapshot operation if you already locked things up. Do the snapshots continue to work properly for you as long as you don't switch to the preset you are currently on, or as you also reported, a duplicate of the same preset? I'm actually kind of shocked that I have not seen anyone else post this bug before. I have only played around with the 'Preset Spillover' function as I generally need both paths for my presets but it is surprising that others using Return blocks with 'Preset Spillover'="On" have not run into it.

Strictly speaking and I am sure accurately addressing the question as the OP intended the above posts are correct. At the risk of being "that guy" there are three exceptions that I can think of that can be set from HX Edit worth mentioning if for no other reason than as a reminder of their somewhat unique placement or exception as global settings. The global tempo settings can be changed in the upper righthand corner of HX Edit Under the Variax tab on the Input block for a Variax preset under the 'Variax Settings' parameter you can set "Per Preset" or "Global". Although this is set in a preset it actually is a global setting and will be reflected in all other presets set up for the Variax. Under the Powercab tab on the Output block the 'Remote' parameter you can set it to "Off", "Preset", or "Global". Again, every preset will inherit your setting automatically. I also find it interesting that in the case of the Variax and Powercab settings, despite the fact that they are located within a preset instead of the global settings, you don't even have to save the preset for your selection to be persistent and be reflected in every other preset; even when you switch away from the preset without saving. They act just like global settings but just happen to be located within a preset.

Thanks for posting the video, preset, and details. Without a bit of narrative during the video it is still a bit difficult to tell exactly what is triggering the issue for you but I do see that the snapshots appear to stop switching properly at some point(perhaps when you switch to another preset and back), or at least the blocks stop reflecting the proper bypass state. My first question would be did you run the factory reset and restore of your backup after you upgraded per the update release notes? If not that is where I would start. Does this happen on every preset or just the one? I will load up the one you attached and test it. Update: I loaded up and tested your preset and although I don't have everything hooked up 4CM everything appears to be working properly at least as far as the switching goes. I cannot get your preset to fail as it does in your video and the snapshots seem to be working properly on my Helix. You may want to try reloading your preset and testing it with nothing connected to your Helix to eliminate cabling and external hardware as a potential source of the problem. If the above test does not get things working normally I would start with a backup, factory reset, and restore. Make sure you let all your presets rebuild afterwards and do a second restart of your Helix when that completes to ensure you are not getting any additional rebuild messages. That may just fix your problem unless something arcane is going on with your cables or external hardware. I don't think this is a bug but I could always have missed something.