silverhead

Personally I think you should switch from using Audacity. The main reason is that, by default I believe, Audacity uses a non-compliant pseudo-ASIO protocol called ASIO4ALL. It is known to cause problems with ASIO-compliant devices like Helix. Unless you can configure Audacity to use the Line 6 ASIO driver for Helix, switch recording programs.

You could try using Helix Native in your studio. Record the dry guitar track, focusing only on your playing without worrying about FX processing. Then apply the Helix Native plugin to the track during playback. The display will show the entire signal path including all FX blocks. Instead of tapping a footswitch you could click a mouse. Select any stomp block at any time and click it on/off. Seems your hand and mouse could be just as effective as your foot. You can then 'print' the affected track to a new track, including all your real-time processing/preset edits.

We fully understand what you want to do. Again, it can’t currently be done. Not the answer you want, obviously, but there it is. I’m not going to debate why it’s designed that way.

Yes, you can only have independent control of the bypass state of 10 stomps in any preset. Why? By design. You could post your request to increase that number to Ideascale. You can assign bypass control of multiple stomps to the same footswitch so you can turn on/off several stomps using a single foot tap. This can be done using direct footswitch assignments or by using Snapshots.

You’re right that there’s no formal way to mark a question as solved. However, as the person who started this thread you, and only you, can edit the Title of the thread. If users here want to mark a thread as solved they usually just add the word SOLVED to the beginning of the title.

You can uninstall all but the most recent identically named items; a total of 5 items can be uninstalled.

A VDI cable is shielded (a circular housing around the connectors) at both ends to secure the connection and protect the jacks. The cable that comes with a Variax guitar is part of a set that is used to connect the Variax to a computer for use with Workbench. It is not shielded at either end, or sometimes only at one end, and is vulnerable to loose connections and damage over time if used in place of a true VDI cable. Here is the Variax Workbench connector set: https://shop.line6.com/accessories/guitar-accessories/variax-vdi-usb-interface-kit.html And here is the VDI cable: https://shop.line6.com/accessories/guitar-accessories/variax-digital-cable.html

What is Discord? I know, I could google it but we still probably need more details about the exact problem. What equipment are you using? Howe is it connected/configured? Microphone(s)? Speakers?

You can copy/past snapshots within a preset but not across presets. You can copy and paste blocks across presets. You will need to do what you want manually (after starting by copying/pasting the most representative preset). Note that the preset configuration (amp, cab, FX block selection and order) must be specified for the preset overall, including all snapshots. You can't have one snapshot that contains a certain amp/fx block and one that doesn't. They must all contain the same amp/fx blocks. Snapshots allow you to turn a subset of these on and off, but you can't add/remove them.

Why not just use the XT Main output?

A POD XT Live with a VDI cable/connection will power both your Variaxes. It will probably also provide additional control over the 700 Bass, but will not fully support your JTV (no alternate tuning control, perhaps limited model selection control). The XT Live is currently supported by Line 6 as a Legacy product under the following terms: https://line6.com/support/announcement/108-limited-support-of-legacy-products/

You can already do this easily for all snapshots with two foot taps. Select a different preset and then return to the current preset. It will be reloaded in its saved state, including all snapshots. Or do you want this capability for a single snapshot?

There are different sets of factory presets for the various Helix hardware devices. Helix (Floor/LT/Rack), HX Stomp and Stomp XL, and HX FX all have different sets.

By definition, a dedicated Headphones output is not Line level.

As indicated in my Nov 4 post above this may actually be a Cakewalk issue. After contacting their customer support and following their instructions I now have Cakewalk by Bandlab working properly with Line 6 driver v1.97. Caveat: I am using Helix Rack not Stomp, and I encountered my issue with attempting to use Helix Native.

Yes, we should be able to discuss modellers. However, when it comes to a computer OS nobody should ever use anything except Ubuntu. That's a simple fact beyond beyond the scope of any disagreement or discussion.

What Helix device do you have?

Typically the POD Go gets at least some of the new amp and FX models introduced in a Helix update relatively soon after the Helix update is released. This time may be different, at least as far as the amps are concerned. The recent Helix update involved a complete redesign of the implementation of the Helix Cabs, and required changes to the Helix core operating system. I simply don't know whether or not it will be practical to retrofit this new Cab implementation to the POD Go. And if not, I don't know whether it makes sense to release just the amp without the cab. I think the new Helix FX models stand a better chance of being included in a pending POD Go update but there's no saying when that might happen.

No concern about this being out of place. It may devolve into a Fractal vs. Line 6 debate but I hope not. You've made your intentions clear. I note that although you mention the Fractal FM-3 twice, it's not clear whether you already own one or are considering purchasing either Fractal or Line 6 as your upgrade. Can you please clarify that? How do the Line 6 demos sound to you compared to the Fractal? One thing you could do is download the Helix Native plug-in product and take advantage of the trial period. The Helix LT or Floor sounds identical to the HX Native, and you will have the advantage of knowing exactly how it will sound using your equipment in your environment. The Fractal demos don't give you that. Any online demo (including the Line 6 ones) will sound different in your own environment when the demo-ed device is used with your equipment in your environment. There are many reasons for that, but it's true. There are plenty of posts here about people who initially have difficulty getting the marvelous sound of the demos after buying the equipment. The HX Native trial will let you hear exactly what you'll get. The bottom line is that both Fractal and Line 6 will deliver excellent sounds. The differentiators might be your planned usage of the device. Mainly live performance? Mainly studio? How important is the UI to you, and how do you like those after comparing both? What about moving your tones from studio to stage? Is that important to you? If so, does Fractal have anything like Helix Native that will make that seamless?

It’s not worth pursuing. The v2.22 (Windows) and v2.23 (Mac) firmware is only useful for Variax Shuriken models, as noted in the release notes. Your JTV-69 won’t see any benefits from it over the already installed v2.21

I would open a support ticket with Cakewalk. I use the Cakewalk by Bandlab product and don’t know if the instructions I received would work with other Cakewalk products.

Interesting. I had the same problem with Cakewalk during beta testing. I contacted Cakewalk support after determining that the problem was not with HX Native because I could not even properly open a New Project in Cakewalk. They guided me through a complete uninstall of Cakewalk, including some Registry edits, and then a fresh reinstall. It works now.

Yes to the actual question . And the answer is yes they are the same.

You could try setting the Tuner Out parameter to something other than Mute - a setting that allows your XLR (vocal) output to be active. I know you’ve already explored all these options so I assume there’s no Tuner Out setting that enables XLR but mutes 1/4”. But perhaps the signal processing keeps the vocal and guitar paths separate while the Tuner is engaged, and continues to route the paths independently to their respective outputs. I don’t know and am not at my device to check. If so the challenge is to inhibit the guitar signal from reaching the Output block with any volume. There are probably many ways to do this but the simplest might be a Vol block controlled by an expression pedal at the end of the guitar signal processing path. You’d have to use the pedal actively while using the Tuner to set the Vol level to 0. Since the Tuner taps the signal at the Input block it should still work, but the signal will be silent at the 1/4” Output. A pain to manage, I know, but it might work.