silverhead

I assume you’re using a Helix device? Make sure you select Custom as the Variax tuning parameter, and that you assign all the alternate tuning parameters (strings) to the Snapshot controller.

I suggest you open a support ticket. There may be a lingering issue with the interaction between Workbench HD and Mac OS. EDIT: It would be helpful if other Mac OS and Workbench HD users could report their status here. Are others having the same problem?

If you haven't done so already, download HX Edit from this website. When installing make sure all components are selected for installation. If your Helix firmware is not v2.92 use HX Edit to update the firmware. 1) Don't worry about your guitar just yet. Connect your Helix via USB and run the HX Edit program. If it connects properly to your Helix you will see HX Edit uploading data from the Helix. If this does not happen you will see a 'No Device Connected' error message. Your problem is the USB connection to the computer, not Workbench HD or your JTV. Research threads that discuss fixing USB issues. 2) If HX Edit loads up successfully choose any preset. Make sure the Input block is set to Variax or Multi, and that your JTV is connected via VDI and that JTV modeling is turned on. With the Input block still selected and in Edit mode (not Bypass/Controller Assign), in the bottom right hand pane select Variax (not Input). The top parameter is named Model. Rotate the model knob on your Variax. You should see the parameter changing in HX Edit as you rotate the knob. There two possibilties here: 2a) If you do see the model changing in HX Edit that means that the USB and VDI connections are working properly. The fact that Workbench HD does not recognize the JTV while HX Edit does indicates a problem with the Workbench HD software. Reinstalll Workbench HD. 2b) If you do not see the model changing in HX Edit that indicates a problem with the USB or VDI connections from the computer through the Helix device to the JTV. It's a more general issue than just Workbench HD. Again, Research threads that discuss fixing USB and VDI issues. Let us know which of these three possibilities you observe (1, 2a, or 2b). If something else happens describe whatever is it that you observe.

Does HX Edit control the Variax properly with the VDI connection?

.... moved to proper forum.....

First off, you need to download and install the Line 6 driver. Check that your recording program is using the POD HD and it’s ASIO driver as the audio input and output device. Connect your speakers / headphones to the POD outputs. After arming a stereo track for recording in your recording program, select the POD HD USB channels 1/2 as the Record Input Source. Note: The Line 6 driver is required for Windows computers. If you are using a Mac you may or may not need a driver depending on the age/OS of the Mac.

What computer/OS are you using? What recording program (you only mention a mixer)?

I’m not familiar with the mixer app you are using. When using HX stomp as the audio interface is the app configured to use the Stomp and the Line 6 driver?

Make sure you are using the Line 6 ASIO driver when you use the HX Stomp as your audio interface. You will need to download and install it if you haven’t done so already. It is part of the HX Edit installer package.

Have you tried using the Global EQ to add a bit of a boost to the XLR output signal? I’m not at my Helix at the moment but I expect there’s a Level parameter in the Global EQ.

Have you tried turning down the guitar’s volume knob?

That seems to be a pretty common experience. Best way to create presets that cut through in a band situation is to create them at gig volumes, without using headphones. I know that's not practical in many cases; you may need to set aside some time in a space that can accommodate the volume level.

I doubt that this will change in a future update but you never know. It’s all about DSP. The wah, volume, and EQ blocks are very low DSP consumers. All together their combined total of DSP would probably not allow you even a 5th flex block, let alone 8.

If you have previously been playing and listening to your guitar through a traditional guitar amp you should expect to hear a difference. You are used to listening to an amp in the room with you. A modeller like the POD Go is designed to create the sound in a recording or control room - from placing a microphone in front of an amp that sits in a different room, and listening to the mic’d sound through PA speakers or studio monitors. Like you say you should just start learning and playing. You will be able to ask more specific questions to improve your skills and understanding as you proceed through the learning curve (and there will be one!).

Use a dual path preset. Set the Input block for Path 2 to Variax Mags, and for Path 1 to Variax, with the desired Variax Acoustic model specified. Place a VOL block at the beginning of each Path. Assign both Vol blocks to the same EXP pedal. Define the min/max positions for each pedal in opposite directions (I.e. one pedal has Min=0, Max=100 while the other is the reverse). EDIT: Attached is a preset that I think does exactly what you want. It's designed for a song named Aqualung by Jethro Tull way back in the '70s I think. It switches from electric guitar to acoustic with alternate tuning for Capo 3, based on EXP 2. Credit where due: I believe I downloaded this from Customtone at some point and then tweaked it. Unfortunately I have lost any record of the original designer but he/she deserves credit! Note: I haven't gotten around to it but the attached preset should be edited to either remove the alternate tuning or use a footswitch rather than the expression pedal to move from electric to acoustic guitar. Currently the pedal blends the two guitars, which won't sound good at anything other than full heel/toe position since both guitars are in standard tuning but one is using a capo at the 3rd fret. Aqualung.hlx

I would back up everything and then reinstall the firmware. If the issue persists it is likely a hardware problem.

Depending on the specific IR and guitar I use both different mix settings and different block placement (IR and preamp). I experiment with all arrangements and settings and end up with whatever sounds best to me in any given preset. There’s no right or wrong here - whatever sounds best to you is right for you.

Yes, factory presets are sometimes but not always update in new firmware. The firmware update process does not install the new factory updates; it leaves all presets in the device as they were. Yes you should back up your custom setlists before doing a firmware update. To see any new factory updates you would do as you suggest - perform a factory reset and then import your non-factory custom setlists individually. For reset options see:

Read the thread that @voxman55 referenced at the end of the first paragraph in his response above.

I don’t expect that POD Go presets will ever be compatible with Helix Native presets.

Www.helixhelp.com

Yes, dynamic DSP management does expose the DSP limitations of a device. But that doesn’t mean that static management devices don’t have DSP issues, or are ‘immune’. Far from it. EVERY audio processing device has its DSP limitation. All that static management does is ensure that you never encounter the limitation by placing handcuffs and constraints on the user. Your previous ZOOM, Valvetronix, and Flextone devices placed certain limitations on preset construction. E.g. only one reverb; no distortion and compression block in the same preset - choose one or the other, no stereo FX, no simultaneous mod and delay blocks, can’t have the Spring reverb at all - it’s simply not part of the product, etc. That way you were prevented from ever seeing the limitation. It also ensured that you could virtually NEVER use all the available DSP; there was always some waste. Of course the POD Go has its own limitations but not as constraining. Dynamic management leaves you in control and provides much more flexibility while also permitting you to use virtually ALL available DSP when you want to. But yes, it takes user awareness and responsibility. Until you understand how it works it can leave the impression that the device is underpowered even though it is more powerful than its static management $$ competitors. Enjoy your POD Go. I know you will.

1) You will see Line 6’s notes about Catalina compatibility in a link near the top of this page. 2) The POD X3 series is not compatible with iOS afaik. Others may have more info about this and can report here. 3) This is probably your best bet. Note that the POD X3 is not a full midi device; the implementation does not support all midi commands and features. Here’s a snip from the X3 manual: MIDI – connect POD X3 Live to your MIDI equipment to send and receive Program Change Messages for selecting Presets. POD X3 Live’s MIDI Out connects to another device’s MIDI In; its MIDI In goes to another device’s MIDI Out. Chapter 6 has info on setting your MIDI Channel for communication. Visit www.line6.com/manuals for more comprehensive MIDI CC information. .. and here’s the midi reference manual... .

This sometimes happens due to very slight vibrations in the surface where the unit is resting. This can cause the system to interpret the vibrations as movement of one or more of the knobs, causing unexpected changes in parameter values. To see if this is in fact the issue, try rotating all the knobs to their min or max positions; they are less sensitive to detected movement in these positions. Of course as you do that the sound of the preset will change. Just switch presets without saving the changes and then return to the preset, leaving the knobs at the min/max positions. Then continue to use the device as usual and see if the unexpected changes continue. If so there is a different problem.

Thank you for the chart and all the effort that went into it. During my experiments related to this thread I was amazed at the accuracy. The mere 0.8% discrepancy I noted at one point is essentially a rounding error and not indicative of any inaccuracy in your numbers. I strongly agree with you about how to make best use of the chart. Build your presets without any consideration for DSP until and unless you hit the limit. Then use the chart to determine the most DSP-effective adjustments to the preset.