silverhead

Here are the startup options: http://line6.com/support/page/kb/_/effects-controllers/helix/helix-reset-procedures-and-troubleshooting-tricks-r768 I don't see one for Test mode though.

In the Bluetooth settings of your mobile device, try forgetting the existing connection and re-pairing the devices.

I would open a support ticket, or call Line 6 directly.

You need to reinstall the firmware to restore factory presets. Before doing so you may want to backup any existing presets/setlists that you want to restore later. Use the HD500 Edit program to do this. Use Line 6 Monkey, with your HD500 connected via usb, to reinstall the firmware. If you want the detailed firmware installation instructions look in the Knowledge Base FAQs (under the Support tab above).

You don't actually 'delete' a patch. You can copy a different patch into the same location, replacing rather than deleting the patch. You can use, or create, what you consider to be an 'empty' patch for this purpose.

Helix can certainly send the required midi messages, and it certainly doesn't care what external midi device its connected to. I don't know whether the Kemper can receive and act on the messages but I presume so.

Engaging the tuner will do that I think. Make sure it is Bypass, not Mute, mode. The tuner would undoubtedly get confused if that were possible, and you won't get any sort of stable reading from it, but the signal should pass through totally unaffected.

You could bypass the Input block, or temporarily set it to an unused physical input, or engage the tuner.

Yes the 'check beta box' applies to both. Both links are identical, leading to the software downloads page where you specify the desired download.

I suggest you open a support ticket to work directly with Line 6 tech support on this.

Here's a preset that I think does what you want. It is structured as pfsmith0 describes. http://line6.com/customtone/tone/215659/

To create a 'compare' function: - copy the original preset to a new destination - add a looper in pre-postion to both presets - edit the new preset as desired - record a loop using either preset - start loop playback - switch back and forth between the two presets to compare them

Workbench Variax models will not control anything in the Helix device. It will simply get you around the barrier of only being able to select a single Variax model and tuning in any Helix preset. You simply transfer that part of your control to the Variax. You will still need to control the change from your Engl to your clean amp in the Helix preset by using a dual-path/amp setup with appropriate footswitch or pedal controllers. For instance, suppose you have preset 1A set up as above so that you can switch amp sounds within the same preset. You can use the Helix to select Variax model Custom-1 in the preset so that's your starting point. Set the Alternate Tuning in the preset to Don't Force (not Custom). Use Workbench to create a model that uses Lester-1 and applies alternate tuning if desired. Store this model in the Custom-1 slot in your Variax. Then use Workbench to create your desired Sitar model, again with optional alternate tuning. Store this model in Custom-2 on your Variax. Finally, make sure your Variax Tuning Selector knob is in the Model position. Now while playing when you select Helix Preset 1A your alternately tuned Lester-1 model in Custom-1 is also selected. While remaining in preset 1A, when you want to go clean/Sitar you use your Helix controller to get the clean amp sound and you set your Variax pickup selector to position 2. The Variax will remain in the Custom-1 bank while you select any of the 5 stored Variax models in that bank, each of which can have its own custom tuning as prescribed in Workbench.

I presume your Helix is on and connected to your computer when running Line 6 Updater? If so and you're getting the black screen, try putting Helix in update mode as described in the following (the last step in each list for Helix and Helix Rack respectively). Then launch Line 6 Updater. http://line6.com/support/page/kb/_/effects-controllers/helix/helix-reset-procedures-and-troubleshooting-tricks-r768

There is a simple 'undo' feature that will restore the preset to its last-saved state. Switch momentarily to a different preset and then return to the preset-being-edited. I know it's not what's requested, but it can be useful. You can enhance it by saving your desired changes along the way - much like you would do with any file after making changes or adding information that you don't want to lose. If you want to keep intermediate changes, save the preset. If you don't want to save the changes then presumably you're prepared to lose them. You can also copy the preset-being-edited at multiple points to create your own set of 'undo' points. Doing this in conjunction with using the Looper in pre-position will also let you conveniently audition the changes and different versions of the preset. Sure it's not ideal - but you can manage it until/unless the editor incorporates a better way, which certainly sounds like it's not imminent.

In the Footswitch Assign page there is a field called Custom Label. Assign the block to a footswitch and then type the label. Hit the ENTER key to complete the procedure.

I see you are on firmware 1.10 and editor 1.12. (I can tell from the word 'firmware' in the top left area of the snapshot - that wasn't added in the editor until v1.12) You need to update your firmware to 1.12. You are running incompatible versions of the firmware and the editor.

I think that any preset (except any empty or 'New Preset') that hasn't previously been saved with the current firmware is rebuilt on each startup. For instance, immediately after a firmware update the factory setlists are automatically rebuilt. I believe the next startup will rebuild any existing user setlists. After that, anytime you load a new user setlist all its presets that were not saved before powering off are candidates for rebuild on the next startup, and so on. Importing a Customtone download will cause it to be rebuilt next startup if not saved. Explicitly saving a preset removes it from the rebuild candidate list. But that's just my theory based on observation...... it could be wrong. I suppose that theory could be tested if anyone is so inclined. Rebuilding does no harm as far as I can tell.

You could try using Workbench to create the models and alternate tunings you need for a single song, and then store them in the same bank in your Variax. In other words, you stay in the same Helix preset for the song and use your Variax pickup selector switch rather than Helix to control the multiple model selections and tunings.

You're putting a lot of effort into this. It's a very useful resource and your efforts are appreciated!

Fair enough. I haven't been involved in as wide a range of beta testing as you. I was just speaking from my experience, both as a tester and a software developer. It's partly a matter of terminology. I call what you are referring to 'usability testing', and that generally happens earlier in the design stage. And I'm sure Line 6 is not losing track of all the suggestions that have been made using the resources form a larger user base. Those suggestions may appear in later version of the editor. EDIT: Also, I notice that you still have to tick the 'Beta' box to see this latest release. So unless Line 6 just forgot to change the status that suggests that this is an interim release during an ongoing beta period. So you may yet see some of what you'd like to see!

Bug finding/fixing, for sure. But new features? Not so much. Typically the feature set of any software release is pretty well fixed at the design close stage of development, and that happens long before beta testing.

I've moved it.

Is it just one cable? The complete Variax Workbench interface package includes two cables and a hardware interface device (a rectangular little boxy thing). One cable from Variax to interface device and another from device to computer.

Glad you're enjoying it!