silverhead

Wives come with a womanual. They're unreadable.

Yes - the problem is ASIO4ALL, not necessarily Audacity.

Various and unpredictable problems as I understand it - but serious as in it makes the system unreliable. Not just stuttering or some other thing that can be easily fixed by adjusting buffers or optimizing CPU usage. I've never used Audacity/ASIO4ALL myself - just reporting what I've read from others. The basic problem is that it's not a true ASIO implementation, hence there can be communication hiccups between the audio interface and the DAW. You might be lucky and have no problems - but if you do you're on your own.

Need to be careful with Audacity. I believe its default driver is called ASIO4ALL which is not a fully compliant ASIO driver and is known to cause problems with Line 6 products in some cases. Some people seem to use it without problems while others have problems. It is not supported by Line 6; if you do have problems Line 6 support will tell you to use their supported driver.

You're not crazy, but what you are observing is correct. There is no consistency about footswitch assignments among presets other than whatever conventions you choose to impose and adhere to. There is no global setting that says anything like "FS1 is always assigned to a Stomp FX, FS2 to EQ,...., FS8 to Reverb". You impose your own personal preference and define it consistently in each preset. You then adapt any other downloaded presets to your style if you wish.

See Global Settings -> Preferences -> Joystick Encoder. Choose Model or Selection. The former changes the model when the joystick is rotated; the latter selects the adjacent FX block in the chain.

There's a global setting (as of v2.8 I believe) that allows you to specify that rotating the joystick knob will let you navigate left/right along the signal chain and select the adjacent block rather than changing the model selection of the current block.

Actually I believe the tuner is placed at the very beginning of the signal chain, for best accuracy, and can't be changed. I don't believe the manual specifies this but it makes most sense. Why try to tune at the end of the signal chain and have to contend with various FX like Stomp, filter, and mod? Best to deal with the raw input signal. I believe the problem you are having is with the tuner's Output setting - specifically Mute. This setting prevents the signal from leaving the tuner block, whether it is at the beginning or end of the chain.

The JTV59 comes with 'jumbo' frets. I found them very high/large, accounting for the high action and also an out-of-tune behaviour when playing with a heavy hand. Depressing any string so that it touches the fretboard (not just the high fret) added enough tension to the string that the resulting note was sharp. I ended up replacing the frets with a standard size set and I also replaced the nut; both issues were resolved. I used a local guitar tech for this, not a Line 6 service center.

The symptoms point to one of several things to check out: - a JTV firmware corruption. Try reinstalling the latest JTV firmware - the VDI jack on the JTV. Visually inspect it and look for damaged or bent wires. If necessary straighten them carefully using a J-hook you can fashion from a thin plastic wire. - a hardware problem in the internal circuitry of the JTV. It may need servicing.

Yes.

There is a manual although it is very brief. If you haven't seen it yet here's a link: https://line6.com/data/6/0a06439c13b82573b4a40dbbe1/application/pdf/FBV3 Pilot's Guide - English .pdf Note that there is reference to a control app that you can download.

Nothing special to keep in mind - just follow the instructions carefully. You can update directly to the latest version.

The POD communicates with your computer over USB using the industry standard ASIO protocol. This protocol requires that the same audio device is used for both input (recording) and output (playback). Hence you can't assign the Playback device to be your PC speakers while continuing to use the POD as the recording device for your DAW. There are some drivers (e.g. ASIO4ALL) that simulate an ASIO protocoal and allow you to assign different input and output devices but they are known to cause problems when used with fully ASIO compliant audio devices such as the POD.

One solution is to purchase a product called a hum eliminator. A google search will give you many options. A simpler solution might be, as you've already discovered, to experiment with different electrical outlets. For instance, if your current setup has both your computer and your Helix connected to the same power bar you might try plugging each directly into two different electrical outlets.

You also need to install the driver. The best thing to do is download the most recent version of HX Edit. This is an installer package (exe file). Running this installer will install the most recent compatible versions of the HX Edit program, the Line 6 Updater program, and all associated drivers. Install them all. Then connect your LT and run the Line 6 Updater program to update the firmware to the most recent and compatible version. Do not have the HX Edit program running while doing this. For further details see the installation instructions that appear on the HX Edit download page.

There may be one other possible way to retrieve your patch - but it's quite unlikely given that your initial post is now 8 hrs old. IF you are still running the same HX Edit session, and IF you have made very few changes since the accidental import, and IF the UNDO feature can act on preset imports, it may be possible to use the UNDO feature of HX Edit to go back to the state Helix was in before the import. However, as I said, this is very unlikely at this point.

If you connect the backline instruments to the M20d you can get a full recording. That's what I do.

My guess is that you're experiencing a ground loop - electrical interference between your laptop computer and your HX Stomp. Try unplugging your laptop and running it on battery. If the noise disappears then this is the problem. There are solutions available but we don't need to go there until/unless you confirm the issue with the above test.

You can't control anything but the Helix Rack device with the Helix Control. You would need to use the Helix Rack to control your Engl.

Take a look at the last banner item at the top of this page.

I think so but not 100% sure about IRs. I'd leave them as is until/unless you have evidence that they are problematic.

You're welcome. With respect to my final paragraph above (recreating the offending presets) you can try to copy/paste individual blocks from the original preset rather than manually recreating each block from scratch but I can't guarantee that this willl work. If it does it can save you some effort. Try it with one preset first - it will either work (not be rebuilt again on startup) or not.

You likely already know that it is normal for presets to be rebuilt once, on the startup following their first import into new firmware. So I'm assuming you mean that the same preset(s) are being rebuilt repeatedly at each startup. This is not normal and usually indicates that these presets are somehow considered by the new firmware to be structurally corrupt and unable to be properly rebuilt although they may continue to work properly. This will continue to happen until the offending presets are identified and removed or until new firmware is able to rebuild them correctly. You can do something about the former but not the latter. To identify the offending presets watch carefully as the rebuild process happens. The display will show a number between 1 and 1024 for each preset being rebuilt. This number can help you identify the preset location in terms of its setlist/bank/preset location. Divide the number by 128 (the number of presets in a setlist) to determine the setlist number, 1-8. Then divide the remainder by 32 (the number of banks in a setlist) to determine its bank number 1-32. The final remainder will be a number between 1 and 3, which corresponds to the preset location A-C within the bank. (Note: if there is no final remainder that means the preset is in location D of the already identified Bank). For instance if the display shows preset 746 being rebuilt that specific preset is in Setlist 6 (since setlist 5 ends at 5*128=640). It is in Bank 27 (since the remainder from the first division, 106, is greater than 26 *4=104). It is preset B since the final remainder is 2. Often the presets being rebuilt will correspond to a range of presets suggesting that at some point a number of presets from somewhere were imported together. Backup these presets for future reference and then delete them (i.e. copy New Preset into those locations). Restart Helix until all such presets are removed and no further rebuilding occurs. What remains in Helix are now known to be fully compatible presets. If you want to restore the offending presets you can import them individually to inspect the details and then manually recreate them by editing a New Preset - do not copy them. When finished, replace the offending preset again with a New Preset before restarting Helix.

You can connect your Variax to any audio interface using its 1/4 analog output. Of course you will be sending the raw signal of the selected Variax model. There will be no signal processing such as your POD provides; you will need to do that in some other fashion.