silverhead

Are you recording your guitar using a mic or pickups of some sort? If using a mic you may not want/need any IR because you already have the effect of the guitar body response in the signal.

Is your Firehawk device running the latest firmware? The best way to check and update is to connect your Firehawk to your computer via USB and run the Line 6 Updater program.

There’s no right or wrong. Try both setups and see what you prefer. In terms of preamp I use the Studio Preamp model. I avoid using a guitar preamp model.

You can reduce the replacement expense if this should happen by using Helix Rack plus Control. Replacing the Control unit is about 1/4 the price of Helix Floor (in Canada).

HX Edit remains at v2.90 while firmware is now at v2.91. Run HX Edit. You can update firmware from there.

Very nice preset. Thanks for sharing.

I don’t know if you want to purchase anything but I was very impressed with Glenn DeLaune’s Acoustic Patches package in the Helix Marketplace. It includes some presets specifically for Variax.

Right - no mic input on the LT. I missed that. Good catch, @rd2rk.

The best way to record the sound coming from your amp is to put a mic in front of the amp and record that. Another way is to use your amp’s line out and then compensate for the fact that this signal does not include a cab. Both of these strategies can get complicated if you are wanting to use Helix to both process your guitar signal before it goes to the amp and also to record the amp, either mic’d or direct. You will need to construct your preset carefully. Here are some thoughts on that: - Create a dual path preset. Make sure the paths are completely independent; do not route Path 1 Output to Path 2. - Using the Output blocks, pan Path 1 output hard right and Path 2 output hard left. - Use Path 1 to process your guitar and send the output signal to your amp. Set Path 1 Input to Guitar (or Variax). Add your desired processing blocks. Connect the Helix R audio output to your amp. - Use Path 2 to receive the amp output and send the signal to your DAW for recording. Set the Input to mic if you are mic’ing the amp, or to one of Return jacks where you would connect the amp’s direct output. If using the direct output you should add a cab block to the path. - In your DAW arm a mono track for recording and select USB 1 (not the stereo 1+2) as the track’s record input. This will record only the L half of the Helix stereo output, namely Path 2.

What computer and OS are you using?

Also the Input-Z parameter is irrelevant if you are using the Variax VDI I put.

Have you considered using the Helix LT as your audio interface for recording? It supports simultaneous recording of both wet and dry signals to your DAW. (See LT manual page 56).

If you are using a PC (not Mac) download and install the Line 6 driver for the Firehawk. Then try using a different recording program - not Audacity.

Don’t forget that the tuner comes in 3 flavours. Experiment by turning in knob 3 when the tuner is active to see which flavour you prefer.

Technically the protocol constraint is that only one ASIO driver can be used at any time. The result is that the same device, with its ASIO driver, must be used as both input and output.

ASIO4ALL may be buggy but more importantly it is not an ASIO-compliant driver. It does not conform fully to the ASIO protocol. Most significantly it exists in part to overcome one of the more restrictive aspects of the protocol, namely the requirement that the same audio device be used as both the input and output device. ASIO4ALL does not impose that restriction, which is one reason it is not a fully compliant protocol. When audio interface devices (like Line 6 devices) are designed to be fully ASIO-compliant it's no surprise that issues emerge when used with ASIO4ALL.

Yes I am running v1.1 firmware - the latest and current version. I don’t believe it’s a firmware issue. The fact that you can’t get the sound loud, even without the POD Go connected via USB, indicates that it’s not a driver or recording issue. It’s more general and basic - likely a hardware fault at the input stage imo.

Yes I have a POD Go. I have no problem with volume, speakers or headphones, nor any problems with USB recording level.

I would open a support ticket. It’s possible your POD Go has a hardware fault that is covered under warranty.

Is the POD Go loud enough through the headphones when just playing, not connected to the computer or recording? If so it seems to be a USB issue. Try using a USB 2.0, not 3.0, port. Try different USB ports on your computer and avoid using a USB hub.

Yes. Helix Native patches are fully compatible with the Helix device. You can simply drag/drop a patch from the Helix Native window to the HX Edit window, or use any folder on your computer as an intermediate transfer location for the export and import functions in the respective programs.

What USB channels sent by the POD Go are you recording? It sends USB 1&2 (the processed signal) and USB 3&4 (the dry signal). What have you selected as the Record Input after arming the channel for recording?

4x12 Uber T75 (with 409 Dynamic mic)

Are you using the latest Line 6 driver?

Hit the Support tab at the top of this page. Scroll down to Account Services and select the Register Gear tab where you can remove the registration for any piece of your gear.