silverhead

I'm not sure I understand. Each mic is a mono device; you can't generate a stereo signal on input. It seems correct to me that at the time of input/recording each mic is assigned its own channel, L or R. At the OUTPUT or post-recording stage you should be able to blend the two inputs into a stereo signal.

First, use HX Edit to make backups of everything you want to use again later. You can backup individual presets, or setlists, or create a complete system backup. Then consult the item below to find the specific reset procedures for your Helix device. Sounds like you want to use FS2 and FS3.

Your ears are extremely well developed and sensitive listening devices. The vibrating strings are only a foot or two from your ears. The amp is much farther away and hence needs to be much louder to overpower the sound of the vibrating strings.

Go to the Downloads area of this website (see top of this page). Select HX Edit from the middle (software) field. Hit the Download button at the bottom of the v3.6 info panel. Check to make sure you are selecting the right editor package (Windows/Mac). What you are downloading is an installer package. Execute the installer to install all required programs and drivers. These include the programs HX Edit, Line 6 Updater, and (for Windows) various drivers for communication between your computer and the Helix device. Install all listed components. After installation, run the under HX Edit program. It should prompt you that an update is available. If not, login to your Line 6 account within HX Edit (bottom left area of window). Follow the instructions to install the v3.6 firmware on your Helix device.

Have you ever opened a support ticket? Your situation seems highly unusual to me and I strongly suspect it’s something to do with your particular computing environment. Line 6 Tech Support may have relevant info.

Official or not, this thing is a computer. Like any computer it has a certain amount of 1. processing power based on CPU specifications 2. permanent storage (disk drives) 3. temporary storage (RAM). In Helix terms that’s 1. DSP 2. Static Operating system, Global Settings, IRs, Setlists, Presets… 3. Dynamic Operating system, Preset audition and editing space, looper space, … It’s just a computer with a guitar-player human interface. Edit: As clarified by datacommando below, firmware doesn’t require the OS to be stored on an internal drive.

I’m not familiar with Pro Tools so can’t advise on how HN behaves there. But as a general workaround…. When you are freezing HN can you Save the preset to the HN library and take note of the name and location? Then you’ll at least be able to recover the settings later by recalling the preset. I expect you’re already doing that and are just looking for an answer to your question, but I’m just mentioning it in case. Might be a bug in HN that should be reported through the support ticket mechanism?

Regarding your preset renaming, make sure you hit the Enter (or Return) key to complete the renaming procedure. Unless you do this the name reverts to its previous state. The reset does, indeed, remove your custom setlists. Use HX Edit to Restore the backup file created at the beginning of the update procedure. The reset procedure installed the new factory presets in v3.6. If you want to retain them deselect the factory setlist(s?) during the restore procedure. Click on the triangle beside the Presets list and uncheck these ones.

Well I’m not 100% certain of that but almost. Otherwise, why would the latest version of the Updater program be included in the HX Edit installation package?

Remember, I said you ‘probably’ don’t need it…. ;-)

Yes, offline updating as you describe will resolve situations where Internet connectivity is not robust or stable enough for the connection to persist through the update process. Sounds like that is what’s happening to you. Are you experiencing Internet dropouts in other situations? I think the only technical difference between the HX Edit managed firmware update and the offline update is the Internet connection time required. In both cases Line 6 Updater is operating on the firmware file. In one case the Updater is invoked in the background by HX Edit and the firmware file is dealt with over time using a stable internet connection. In the offline case the firmware file is downloaded manually in advance and the Updater program is invoked manually. End result is the same in both cases - the firmware update is installed in the Helix device.

Ok, good. So tell us exactly what is happening when the procedure fails. How far along do you get? What program(s) are you running? Do you get an error message? What do you see on the screen? We need accurate and meaningful descriptions to help you.

How exactly are you trying to update? You should begin by downloading and installing the HX Edit v3.6 package as described in the release notes. Follow the instructions. If you are doing that please describe the point at which things are failing.

You probably don’t need the ASIO Helix driver as long as you use only the HX Stomp but there’s really no advantage in removing it. It is included in the HX Edit installer for completeness and selected for installation by default. Remember that HX Edit is the editor for all Helix family products (there is no HX Stomp Edit program). In the future you could connect another HX family product to your computer and use HX Edit with both devices connected. In that case you would need the ASIO Helix driver.

Also, HX FX a is not being left by the wayside in v3.6. It receives the applicable parts of the update - the two new FX models.

I suggest you open a support ticket.

I also do not see the USB interface. I see the battery charger (included with a new JTV) and another box which is not included with the JTV. Looks like an A/B switch of some sort that I think used to be used with pre-JTV Variaxes.

afaik that’s not possible outside of the Line 6 development environment.

There is no PM feature in this forum. Post your questions here. I’ll see them and respond. You may get useful info from other community members too.

There are other differences between the HX Stomp and the HX FX but the amp modeling is the main one for your situation. For instance, the HX FX cannot be used as an audio interface device while the HX Stomp can. The HX FX is designed specifically for your situation. Further to grdGo33’s response, adding the HX FX into the POD Go’s FX Loop does not affect the DSP in the POD Go. The FX Loop is included in every POD Go preset so that small amount of DSP is always allocated whether or not you actually connect anything using it.

That’s unusual. I would open a support ticket.

The factory setlists I attached above do indeed contain the new presets in v3.6 as identified in the release notes. You need to be running v3.6 of both the HX Edit program and the device firmware.

While in HX Edit, login to your user account (see bottom left corner of HX Edit). You should be prompted to update your firmware to v3.6. Follow the instructions.

This is highly unusual and may indicate a hardware fault. Have you contacted Sweetwater to request a replacement?

By following the instructions you have the new factory presets briefly and temporarily. The firmware update itself does not install them. They are installed when you perform the factory reset, but then are immediately overwritten when you do a full Restore from Backup. in order to retain the new factory presets you need to deselect them (remove the check mark beside Setlists 1, 2, and 8 in the exploded Presets list) during the Restoration procedure. I considered describing exactly how to do that but it's simpler to just provide them directly.