silverhead

Glad everything is OK again. I understand your reluctance to try updating to v2.50 again but what happened took you is a real anomaly and I would not expect it to happen again. It’s really important to follow the update instructions exactly, especially the first step of downloading and installing all components of the v2.50 POD Go Edit package.

Yes. In HX Edit choose the Restore from Backup menu item. After selecting a specific backup file you will see a list of items to restore, including IRs. All items are selected by default. De-select the items you do not want to restore. In your case I would suggest you restore only IRs and Global Settings.

You mention an amp and cab in the preset. I do not use any guitar amp or cab. Try using just the studio preamp, compressor, EQ, and a bit of reverb, chorus and/or delay. For best results send the output to FRFR speakers/monitors, not a physical guitar amp/cab.

I’ve never heard of that before. Have you changed anything in your monitoring equipment? Is it possible your presets use IRs but your IR library is empty? The factory reset removes all IRs; did you restore them? Open a support ticket. fyi… POD Go Edit only allows incremental jumps in 1/2” or 1/4” units. I think that on the device itself you can set 1/10” increments but I’m not certain.

You can’t delete a loop other than by recording a new loop to replace it. You can ignore it by not playing it, or if you wish you can record a new, very short, loop that consists of a few milliseconds of silence. What benefit is there to deleting it or recording silence over it? Just ignore it.

What Helix device are you using? You posted this in the HX One subforum but it sounds like you are using a different device. Please clarify.

You need to keep the firmware and POD Go Edit versions in sync. So begin by downloading and installing the v2.0 POD Go Edit installation package. Install all components and notice that the Line 6 Updater program will be reinstalled. Run this program and select the Update from File option, pointing to the v2.0 firmware file that you have already downloaded. After the firmware update perform a factory reset and then restore the most recent working backup file including Global Settings and IRs. Finally, manually import previously saved setlists/presets that you know are not affected. Once you have v2.0 installed and working properly you can try updating to v2.50 again, beginning with downloading and installing POD Go Edit v2.50. Follow the instructions carefully. What you experienced should not have happened. If it happens again open a support ticket.

Open a Support Ticket (see Support link at top of this page.

You need to assign an FX block to a footswitch (FS) in order for the FX name to appear in the display in Stomp mode. Here’s s a snippet from the manual pg43: NOTE: To manually access the Controller Assign menu, press the menu button and then Knob 2 (Controller Assign). Further details in the manual.

You need to assign an FX block to a footswitch (FS) in order for the FX name to appear in the display in Stomp mode.

After updating did you perform the recommended factory reset and then restore your backup file created during the update procedure? If not, try that now.

Return/replace the HX One.

This might simply be a name-length limitation imposed by Helix. If your BANDNAME is lengthy it could occupy most of the max length of a preset name leaving little or nothing left to distinguish among names within the LT. Try abbreviations for your band name and see if it helps. Not likely the issue I admit, but maybe worth a try. Oldtimers like me remember the early days when it was common for name lengths to be restricted to 6 or 8 characters to save expensive and scarce memory space. I might have had to choose the name ‘slvrhd’!

Is your foot switch cable TRS (tip-ring-sleeve)? If not, it needs to be. If so, check your Global Settings -> Preferences for the EXP/FS assignments.

Yes, it’s ‘only’ handling command/control communication to tell the Variax how to behave when a Helix preset is loaded. Well, that’s not quite true. The VDI cable also powers the Variax from Helix. Compared to the legacy Variax guitars the main additional control in Helix is storing alternate tuning information as well as using Variax knobs as controllers for assigned parameters in its presets, e.g. use the Variax Tone knob to control, for instance, the Helix’s Reverb mix. To Helix the Variax is just another guitar in terms of incoming audio data, but also supports the latterly mentioned control data.

Not 100% sure but I believe that indicates digital clipping on the path The signal is too hot for the chosen output. Try adjusting the Global Settings 1/4” output, e.g. from Instrument to Line.

On a PC I would ask if you’re using the Lin6 ASIO driver in your DAW settings. I don’t know if that actually applies on a MAC (core audio??) but check it out. Also I presume you are using the POD Go as the audio interface? The default audio level over USB is adequate. I don’t think there’s any reason other than DAW settings for what you describe.

Yes. Use Snapshots to achieve what you want in the bullet points. If you’re not familiar with snapshots start by reading the associated section in the manual and come here if any follow up questions. I can’t answer your question re: EXP assignment.

Because with Variax the guitar does all the individual string digital processing. Nothing is done within Helix except pass stored preset data to the Variax (e.g. model selection, custom string tunings) using a proprietary protocol over an RJ-45 connection. Helix does not receive individual string-based data; it receives the processed blended 6-string output from the Variax as a standard guitar signal, either analog (1/4” jack) or digital (VDI connector).

You don’t say why your initial upgrade to v2.50 was interrupted. You also don’t mention your update procedure. It is critical that you download and install all components of the v2.50 POD Go Edit installation package before updating. If you didn’t do that your problem is explained. If you did do that and you’re not sure why update failed it was probably a disruption in usb communication. Since this did not happen during your two rollbacks to earlier versions it will probably not happen again. Your decision to remain at v2.0 is yours to make, of course, but there’s no reason to expect that upgrading to v2.50 will fail again. It’s not a firmware problem, nor a general problem with the procedure. It’s worked just fine for almost all users, though some may need to repeat the process due to dynamic and unexpected errors like usb interruptions. For added security against a usb interruption you could download the firmware file first and then choose ‘update from file’ when running Line 6 Updater. This minimizes the time requirement for a stable usb connection since the time required to download the firmware file from the server during the update procedure is removed.

Are you running the latest firmware? I know it fixed a bug involving Flux but I don’t know if it will fix your issue. Worth a try if you’re out up to date.

Is this what you’re looking for? Sip and spit…. Don’t swallow. May be a bit vinegary by now… http://line6.com/getrelease?rid=5634 I suspect that this bank is the same as the Custom1 bank from your recent firmware update but perhaps not. I find the old documentation on this to be a bit ambiguous. As I understand it this bank represents the Workbench HD models that replicate the mag pickups on the JTV89. It’s meant to provide other JTV model users with the sounds of the 89F hi-gain pickups. Use Workbench HD to load this bank into your 89F anywhere except the Custom 1 bank. Then compare the sounds of this bank to the Custom 1 bank as well as to the 89F mag pickups. At least that’s what the ambiguous docs suggest to me. So no, I don’t think you are missing out on anything. JTV59/69/Standard/Shuriken users are the ones who are missing something that they may want to explore, namely the sound of the 89F mags.

Check your Reaper audio device configuration. If the Helix LT is visible for selection choose it. If not visible you may not have the Line 6 ASIO driver installed. The driver was included in the HX Edit installation package. Run it again and select to Install the driver.

Yes, everything you state in your updated post is accurate. For anyone following this thread, the post I made earlier about correcting misinformation is now out of context since it related to now-deleted content.