silverhead

Yes.

In Global settings you can arrange things so that you can switch among the 4 snapshots in a preset using the A-D switches while using the Up/Down switches to move to an adjacent preset where the snapshots for that preset become immediately available (I think) on the A-D switches. Seems to me that would do what you want. For details see the Global Settings -> Switches/Pedals section of the manual, particularly Snapshot Mode (set to Manual) and Up/Down switches (set to Preset).

You should find them under the Delay, Mod, and Reverb FX groupings respectively. Make sure you look under all options in those groups - Mono, Stereo, and Legacy. For instance I would not expect the Ping Pong delay to be listed in the Mono grouping. Are you missing them using the Helix device itself, or with HX Edit, or both?

There's a Global Setting that allows you to use 4 Stomp switches for FX on/off and use the Up/Down switches to navigate among presets without leaving Stomp mode.

Based on the settings in the screenshot it’s not doing anything, but it could be used to set the Path B level and pan, or overall level. I presume that’s why it’s shown. I find it interesting that the Mixer block seems to know it’s not in Path A. It has set that level to zero, unless the OP did that.

Of course, you could always just use an HX Stomp switch to control the Tremolo bypass but I presume there's a reason you don't want to do that.

If you can program the G3S to have the same button send different alternating commands with repeated presses then you can use that. But you may have to use two buttons on the G3S, one programmed to turn the block ON and the other to turn it OFF. The HX Stomp cannot be configured to recognize repeated presses of G3S button 11 to act as a toggle/bypass switch.

That could well be the problem. Have you tried updating without using this adapter?

I suggest you open a new topic for this question. The question you are asking has (almost) nothing to do with the topic of this nearly 10 year old thread.

Weird, but good. Let us know if any hiccups or questions.

Funny. Here’s my screenshot. Note that I have left the Hardware field blank. In any case you can try the Win10 compatible version.

Follow the link to the Downloads area of this website (see top of this page). Use the drop-down menus to select POD GO Edit in the Software field and Windows 11 in the OS field (yes, it’s there - you may need to scroll down to see it). Download and install all components in the Edit installation package. Then run the POD Go Edit program and log into your Line 6 account within the Edit program (bottom left corner of the window). Follow the onscreen prompts to update the firmware.

Take a look at the HX Stomp manual pg 9. The 4CM setup is pictured there. With reference to MGW-Alberta’s picture, the HX Stomp appears immediately before cable#2, as your initial post described: Guitar - > Tuner - > wah - > compressor - > fuzz - > overdrive - > hx stomp As shown in MGW-Alberta’s diagram and also in the manual’s diagram, Cable #2 goes from the Stomp Send output to your amp’s guitar input. Cable #3 goes from your amp Send to the Stomp Return. Finally, Cable #4 goes from the Stomp main output (at Instrument level) to your amp’s Return. All the FX shown in MGW-Alberta’s diagram from Cable #2 onward live in your HX stomp preset, unless you want to add some physical FX pedals like a reverb inline with Cable#4. The structure of the HX stomp preset is critical when using 4CM. Most importantly it requires an FX Loop block. Any additional HX stomp FX blocks that you want included in front of your physical amp (e.g. an EQ or Filter model) must be placed before the FX Loop in your preset. All the FX that appear between Cable3 and Cable 4 in his diagram (mod, delay, reverb) appear in your Stomp preset after the FX Loop. Also critical in terms of using the 4CM with utmost flexibility is that your Stomp preset can contain an amp model but it should not contain a cab model, because your physical amp’s cab is used instead, coming into play after Cable #4. You don’t want to double up on your cab. Similarly you don’t want to double up on your amp so make sure that your preset has either the FX Loop or the amp model active at any time, not both. Assign the same footswitch to control the bypass state of your Stomp’s FX Loop and its amp. Save the preset with one of these blocks active and the other bypassed. Henceforth pressing that footswitch will toggle between using the physical amp or your Stomp’s amp model. Finally, the noise gate in the HX Stomp appears in the preset’s Input block. Configure it as desired on a preset basis.

Yes. Firmware v3.50 completely overhauled the cab engine implementation. But this should not be apparent until you apply the new cabs in a preset. Simply updating the firmware and restoring the earlier presets will not change any of them to the new cabs.

We agree - there should be an easier way to replace an existing set of presets with ‘empty’ ones. But still, I maintain that we’re not deleting its data content - we’re replacing it with different content that occupies the exact same memory space. Go forward with this if you wish. I’m out. I think this horse has been sufficiently beaten.

Try restoring your IRs (impulses) from your backup. There are no factory supplied IRs. The factory reset will have deleted any that were previously installed. This is only applicable if you use IRs, of course.

Yes I did read your post. Again, you can’t actually Delete a preset. You can overwrite/replace it with a modified preset named New Preset, EMPTY, or Jim. But you haven’t deleted it. It’s still there residing happily in the device’s allocated memory occupying the same space as the previous preset. A preset corresponds to a specific piece of allocated permanent storage/memory; you can’t rip it out. Yes, I agree there should be an easy way to replace one or more presets with an ‘empty’ preset. On Helix devices that contain multiple setlists, including your Helix Rack, I described a way to do it using a factory supplied USER setlist. On devices like the HX FX and your HX Stomp you need to take the cumbersome approach that you described. A better approach for a single preset is to use the Clear All Blocks option (available only on the device, not HX Edit) as described on pg. 16 of the manual. But still that only applies to a single preset; replacing them all is cumbersome. You could make a feature suggestion for this improvement using Ideascale. It’s probably already there - just vote it up.

OK - I misunderstood the technology. Thanks for the clarification and education!

OK, so by ‘clear a preset’ you mean ‘replace it with a preset named New Preset that has no blocks’. Is that right? If so, the way to do that would be to export a Setlist containing only New Preset in all preset slots from the original factory presets/setlists. Then anytime you want to clear all presets you import that Setlist. This can be done easily with any Helix that provides more than one Setlist in its factory settings. The HX FX however does not contain multiple Setlists. It provides a single setlist of 128 presets, and it contains factory presets. I don’t know if it contains any New Preset among them. In any case, to do what I described above you would need to first manually create the setlist containing only New Preset. You only need to create and export it once and then you can import it at any later time.

I highly doubt it. It is not mentioned among the bug fixes in the release notes. I suppose I t’s possible that it is among the ‘Other minor fixes and improvements’ but you’d need someone who can test it to tell you. Looking at the description of the WIDI UHost I see it uses MIDI an over Bluetooth. The POD Go is not Bluetooth capable. So I expect there’s an approximately 0% chance that it’s ’fixed’ (which is a misnomer in the first place since it’s not a bug). The POD Go uses MIDI over USB. It makes no claim to handle MIDI over Bluetooth.

Why not contact Line 6 Support and plead your case? You never know…. and it can’t hurt.

Interesting. From the retailer's perspective: Why would I want to sell a single guitar that can sound like many guitars? I'd rather sell more of each of the many. I want guitarists to have to carry 6 guitars with them to every gig - not one. A different guitar for different sounds and tunings. That's what I want to sell! Good observation.

OOPS.... If anyone has been following this for the last few minutes, please ignore two earlier posts i made and have since deleted. I was misinterpreting the display of alternate tunings in HX Edit and on my Helix Rack. Apologies for any confusion. This appears NOT to be a bug. Alternate tunings are working as expected for me with my Helix Rack running v3.71 and my JTV-59. If it were an actual bug I would be seeing it too, and it would probably have been noticed and reported by many others by this time. I strongly suspect there is something wrong with @geordie100's setup or equipment. @geordie100: I would try solving the problem by following these steps in order: 1) Try another VDI cable. If you don't have a spare you can use a standard network cable (RJ-45) temporarily. Test your alternate tunings. If still a problem... 2) Visually inspect the VDI ports on both your Helix and your JTV. If any pins appear bent straighten them using an improvised J-hook from some wire that's thin enough to get in there yet strong enough to straighten the pins. Test your alternate tunings. If still a problem... 3) Reset you Helix device. Restore everything from your v3.70 Backup file (there are no new factory presets in v3.71). After restoring, turn your Helix off/on to force an immediate rebuild of any presets that may require it. Test your alternate tunings. If still a problem... 4) Reinstall the firmware on your JTV-59. Test your alternate tunings. If still a problem... 5) Open a support ticket. There may be a hardware fault in either your Helix or your JTV.

Try fresh strings? Clean the saddles?

It would be good to get that straight but I don’t know if we can. The reality is that many people are able to use USB3 with no issues, while some issues are resolved when USB2 rather than USB3 is used. So some reported issues are somehow caused by USB3 while no reported issues are known to be caused by USB2. Hence the prudent thing for Line 6 to do is to recommend always using USB2, which is what they are doing. Meanwhile, in the background, they may be investigating further to try to identify and resolve any technical issues with using USB3. If they are doing so we don’t know about it. It reminds me of a different yet similar issue with non/partially-ASIO compliant drivers like ASIO4ALL. Some people use it without any issues. For others, their issues disappear when they use the Line 6 ASIO compliant driver. So Line 6 Support simply does not offer support for ASIO4ALL environments. They support only installations that use the Line 6 ASIO driver.