silverhead

Can you lower the track’s input level in your DAW?

Use the original Variax Workbench software, not Workbench HD. It’s available on the Downloads page; scroll down to the bottom of the middle (software) field to find it. You will need the Variax Workbench interface device to connect your guitar to your computer. https://shop.line6.com/accessories/guitar-accessories/variax-vdi-usb-interface-kit.html

I agree that it’s very practical, right now, to use a Helix preset viewer and manually create the corresponding POD Go preset, within the limitations of the POD Go. Here’s another Helix preset viewer that includes some additional info…. https://hxview.netlify.app

Based on @amsdenj’s info, seems the workaround might be to Save your presets in Snapshot mode. So every time you are presented at startup with Preset mode, immediately switch to Snapshot mode and Save the preset. After a short time all your frequently used presets should appear as you wish.

You can’t download Helix presets onto your HX FX. The link I gave you is a website that allows you to upload any Helix preset and view/inspect it. That allows you to see all FX blocks that are used in the Helix preset as well as their parameter settings. Then you manually add those FX blocks and parameter values in your HX FX preset. That way you can produce the exact same sound of the Helix FX block in your HX FX device.

The above statement suggests you will not benefit from either the POD Go or the Stomp. Your HX Effects already has everything you would plan to use in either of the others. I think you would be better off developing some skills in building tone with your HX Effects. Yes, you might find more song-based offerings in Customtone but I think you will find their value diminishes once you turn off the amp/cab/IR in the downloaded presets. One suggestion: download song-based Helix presets and use this online preset viewer to inspect the FX and their settings: https://hxview.netlify.app

Not sure if this will help, but… https://www.vguitarforums.com/smf/index.php?topic=21957.0

You can assign Looper functions to individual footswitches using the Command Center as described in the manual pg 61. So instead of thinking that you would be able to use the unassigned footswitches while in the Looper view, think of assigning the desired Looper operations to footswitches that you will use in Stomp mode.

Hi. I was away for a couple of days and I’m wondering if this issue persists. I have reread the entire thread and have a few questions/comments that I hope may be helpful: 1) I’m not a Mac guy but I know that many manufacturers, including Line 6, have been struggling to adapt to Apple’s introduction of the M1 chip. There’s a pinned topic at the top of this page that describes the current status of Line 6 products and the M1 chip. In that article is the following statement: “Regarding macOS Monterey 12, we continue to test against it.”. You say that your Mac is running OS Monterey so it’s likely that your Mac has not been designated compatible with HX Edit. Personally, from the descriptions provided, I believe that this is the case. The USB-C to USB cable may be problematic, or the communication over that cable may be unreliable. If it’s the latter, the solution is not yet available; Line 6 will need to identify and resolve the issue as they continue to test. No idea when that may happen. This may be what Line 6 Support meant by saying that you may need to wait for a pending firmware update. An unsatisfying answer, I know, but that may simply be the case. If you haven’t already done so, restart your Mac and try HX Edit again. 2) Find out what firmware is installed on your Helix. The version installed is displayed on the screen immediately when you start your Helix. 3) If you’re Helix firmware is already at v3.15 you may not need to update it. Try the global reset. That alone may resolve the issue (unlikely imho but possible). If your Helix device is NOT running firmware v3.15 (same as HX Edit) then you are running incompatible versions of Helix firmware and HX Exit, and this could explain your problem. If so you definitely need to update the firmware. There should be no need to uninstall and reinstall HX Edit. Register your Helix device in your Line 6 account. Run HX Edit and log in to your Line 6 account using the bottom left portion of the HX edit window. After logging in you should be alerted that an update is available. Follow the instructions presented to you as the update proceeds. It will create a backup file and invoke the Updater when appropriate. You will be strongly advised to perform the factory reset when appropriate. Do so, and then Restore your backup file.

Return it for refund/replacement.

Yes and No. Yes you need to update. No you don’t use the Line 6 Updater program directly. You need to follow the instructions. Start by downloading and installing the HX Edit v3.15 program package. After installing all components run HX Edit, which controls the installation (including invoking the Line 6 Updater program in the background when required).

When you perform the Restore From Backup function you will be presented with a list of all backup files in the default folder. That is where your file will be unless you intentionally redirected the folder when you created the backup. If you did that you will simply need to navigate to that folder and select the file. Don't worry - it works.

This is the complete backup file for your Helix device as of the date specified. You may have created it intentionally using the HX Edit Backup command, but the fact that you have asked the question suggests you did not. That means it was created automatically during your last firmware update (maybe you recall the date that you updated?). The firmware update procedure automatically creates this file before updating. The other file you mention (*.hlb) is a partial backup - ignore it. When you update the firmware again a new backup file will be created, again stamped with the date. After the firmware update is complete run HX Edit and use the Restore from Backup function to restore using the most recent backup file. The backup and restore functions are reliable. Make sure you follow the instructions.

It’s described on pg 7 of the AMPLIFi Remote Pilot’s Guide. No point in my rewriting it here. If you’re already following the described procedure and it’s not working please provide details of where it’s breaking down. You need to use the app to do this. For gigging, prepare the amp in advance with the 4 presets you plan to use.

The microphones are the transmitters and yes, they need battery power. Your existing xd-v35 mic will work. However, I believe that wireless mic systems are not generally interchangeable between manufacturers. You can’t necessarily use, say, a Shure wireless mic with your Line 6 receiver. I’m not sure whether there are certain mic/receiver combinations that are compatible among manufacturers so I hope others will corret me if I’m wrong, but you shouldn’t assume that a non-Line 6 wireless mic will work with your xd-v35 receivers.

From the manual, pg 37 1. Within the Signal Flow window, select the block which includes the parameter you wish to control via snapshots. For this example, we’ll choose the Litigator Amp+Cab block to control its Drive parameter. 2. In the Edit tab, right-click on the Amp’s Drive parameter and choose the Snapshots option. Assigning the Drive parameter to the Snapshots controller 3. You’ll see a little camera icon (at the left), and the parameter’s value (at the right) appear in white with brackets to indicate the snapshots controller assignment. 4. Now you can simply load any snapshot and set this Drive slider to the desired value. The value is independently stored and recalled with each snapshot. Each preset can have up to 64 controller assignments, including parameters con- trolled by snapshots. Remember to save your tone if you want your assignments to be permanently stored with the preset! 5. All existing snapshots assignments appear within the Automation/Controller Assign tab’s Assignment List. If desired, you can right-click on the assignment here and choose Clear Assignment to remove it. Once a snapshots assignment is created, any changes to the assigned parame- ter’s value are instantly stored with the current snapshot. These stored values are recalled when jumping from snapshot to snapshot, and appear as you last left them per snapshot.

I don’t have a Stomp XL to test with, but theoretically there are a couple of options. One is to use Snaspshots with different threshold, attack and/or delay values. Another would be to assign any or all of those parameters to a single expression pedal, and vary the Min/Max values of the parameters in an inverse manner, so that some increase while others decrease as you rock the pedal from heel to toe. Experimenting could give you a smooth transition as you adjust with your foot either slowly or quickly.

The Noise Gate affects the signal as it reaches the Noise Gate FX block at its position in the signal chain, regardless of what amp or other FX have produced the signal up to that point in the chain. For instance, if you are using 4CM and place the Noise Gate after the FX Loop then the signal will include the preamp section of the external amp. If you place it before the FX Loop then it will not affect the amp because the signal has not yet reached the amp. Conversely, if you place one of the internal HX FX distortion blocks before the Noise Gate block it will be affected by the Noise Gate. If you place the distortion block after the Noise Gate then its signal does not pass through the Noise Gate and hence won’t be affected.

Line 6 audio interface devices and drivers use the ASIO protocol and adhere to its technical specifications. ASIO4ALL is a pseudo-ASIO implementation that does not adhere fully to the ASIO technical specifications. ASIO4ALL is known to cause issues with Line 6 devices and is not supported by Line 6. Use the Line 6 driver that is installed with the POD Go Edit download package.

Can you be specific? For instance, have you made sure that the levels are matched (line vs. instrument) for the physical I/O jacks being used? Are you using the external pedal before the POD Go or in its FX Loop?

Make sure you are using the Amp Out from the Pod GO to your amp input. See manual pg 7 item #20. Page 8 (physical setup) will also help.

Are you logged in to your Line 6 account while uploading? Is the rest of the Line 6 website working properly for you? Is POD Go Edit working properly?

You’re right. No chance of that being a global affect. You can choose a non-guitar input for any and all presets but you’d need to do it manually for each. Hope your support ticket yields a good result for you.

Have you checked out the pinned topic at the top of this page re: Apple M1 compatibility?

Pretty sure the answer is yes. Anything specific you want to know? (I have moved this thread to the Helix forum).