silverhead

I notice your other post also. You’re doing some thorough research before purchasing. Good! Yes, 2012. All JTV guitars of that vintage were manufactured in Korea, and still are I believe. I’m not aware of an update board, not to say there wasn’t one. Current firmware is v2.2 or v2.3 depending on Windows or Max OS. Yes it is compatible with Workbench HD. You determine the installed firmware version, and update the firmware, using Line 6 Monkey. Your information about neck profiles and weight is accurate.

Not that I’m aware of. But you could just make a point of remembering which one is active when the light is on. That shouldn’t change. You could even encode that in the scribble strip display.

No. The HX FX a is not an audio interface device.

Here’s a similar topic posted recently ….. I believe my response is relevant here also.

Seems your symptoms are different. For me on Helix it is very repeatable and consistent. If I change a preset name directly within HX Edit (e.g. using the Rename function) and then Export the preset both enter filename and the embedded preset name are changed. However, if I change the preset name as part of the Save As… dialogue only the filename is changed; the embedded preset name remains as it was and is displayed in the Presets list when imported back into HX Edit. It’s not a bug; it’s designed that way to allow users to keep variations of the same preset name and organize them into different computer folders. For instance, a preset named MyPreset can be saved under different filenames/folders and yet will always be named MyPreset when imported into HX Edit. One other note: a preset name change in the editor is not complete until you hit the ENTER key.

This may be the same ‘feature’ I encountered recently in the Helix world. The preset (patch) name is a separate entity from the filename. When you change the preset name during the Save As… procedure it only ch ages the filename. The actual Preset name remains encoded as it was in the preset metadata. To actually change the Preset name you need to do so using the Rename feature In the editor, or during the Save As… procedure.

Not 100% sure but I believe this will require Line 6 to be involved. Open a support ticket.

Yes. The reset sequence depends on your specific Helix device. Read the Release Notes on the Downloads page. Could also be you need to Restore your Global Settings from the backup file.

Welcome to the Line 6 User Community forum! You’ve put a lot of time, thought, and effort into your first post here and the insights from your experience are valuable. As a new user it’s understandable that you are not yet aware of the way that Line 6 officially accepts and reviews feature requests and product update requests. It’s not done by posting in this user forum. Line 6 developers and product managers do not regularly visit this space so, unfortunately, in its current presentation your ideas will not reach the appropriate Lone 6 personnel. Line 6 uses a different web space called Ideascale where users can post their requests. Go to https://ideascale.com and sign up. Once you have access search for the Line 6 sub space. Once in there you should post each of your suggestions separately so that each can be considered and voted on individually by other users. Line 6 reviews this space regularly and takes some of the best ideas for future implementation.

You can install them on both.

I haven’t had an HD500 for some time but as I recall you are able to pan the output signal. Make sure your preset isn’t panning full L or full R.

No, there is no way to do that.

I must be misunderstanding something. You should be able to hear your guitar in the mix while recording. Assuming your Helix is used as the audio interface, the DAW playback will be heard through the Helix outputs (e.g. headphones). The playback audio is routed from your DAW to the Helix using USB 1/2, and you adjust this incoming audio level to balance with the audio level you hear from your guitar. The only time you don’t adjust the guitar volume in the same place as everywhere else is during recording. After that the recorded guitar track is adjusted just like everything else. Perhaps I’m just not sure what guitar audio you are recording. I typically record both a dry unprocessed track and a wet track simultaneously. I select different Helix USB channels as the Record Input source in the DAW. Helix sends the dry signal directly to the DAW, and also sends the processed signal both to the DAW and to the Helix audio outputs. With DAW monitoring turned off you hear only the processed guitar sound, not the dry sound. I use the Helix preset to generate a tone that sounds reasonable in the mix while recording. Later I use plugins (e.g. Helix Native) applied to the dry track to change how the guitar sounds in the mix if desired.

Your versions of HX Edit and Helix Native are incompatible. You need to upgrade your HX Edit and Helix LT firmware to v3.52 in order to export the LT preset in a formate compatible with Helix Native v3.52. Or you could downgrade your Helix Native to v3.51 where, as you note, the presets are compatible.

That’s a protective cover for the Variax VDI input on the back panel.

Thanks for clarifying. Makes sense to me. Have you opened an Ideascale item for this?

Yes, that’s the idea of Favorites. It’s also the idea behind the User Default feature, which allows you to overwrite the factory default settings of the amp as it appears in the Amp model (not Favorites) list.

I know you get the '.... favorites...' argument. Personally I've always wondered what the difference is, to the user, between User Default and Favorite. What's the actual difference from the user perspective other than, I suppose, being able to define two 'favorites' (which you can already do by using different model names)? In other words, is there any actual value in being able to do what you want?

The proper setup is to turn OFF the Ablelton monitoring. In the POD Go use the Global Settings -> Ins/Outs -> USB 1/2 Trim setting to adjust the level of your PC’s incoming audio until it balances with your guitar level.

Line 6 does not announce feature updates in advance so the answer to your question is: nobody knows. Of course, you can simply place your Voicelive2 device in the Helix FX Loop, but you would still be using two rigs. Use Ideascale to make an official feature request.

... moved to the Catalyst forum ...

Are you sure both tuners are using the same reference (e.g. A 440)? Try using a 3rd tuner to identify the culprit?

Make sure you are also using HX Edit v3.5.

Simply connect your external pedal to the EXP2 jack on the rear panel of the LT. Use the Controller Assign feature to assign EXP1 (the onboard pedal) and EXP2 (external pedal) to your preferred parameters (Vol level and Wah level). See manual for further details re: Controller Assign feature if desired.

I can’t seem to get this off my mind this morning. It’s like a song that gets into your head and just keeps repeating…. If I were to go ahead with development on this I would, like most software development, do it in stages. Phase 1: Compatibility Tester. This first piece of development would take a Helix preset as Input. Output is a Yes/No answer to the question “Is this Helix preset fully compatible with a POD Go preset in all respects: structure and routing, amp/FX block selection, number of snapshots, controller assignments, and any other considerations?” Without this basic capability I don’t think you can do anything meaningful. Phase 2: Compatible Converter. This would follow quickly after Phase 1 and would convert fully compatible Helix presets (inputs) into POD Go presets (outputs). Phase 3: Compatibility Analyzer: This would produce a report that identifies all incompatible elements of a Helix preset that is not fully compatible with a POD Go preset, and provides options and/or recommendations for manual conversion. It provides users with an itemized list of all items in a Helix preset and the manual additions and changes they would need to make using POD Go Edit to get as close as possible to the Helix preset, starting with a POD Go New Preset. Phase 4 and ongoing: General Converter. A series of iterations and product updates that gradually address the automation of the items in the Phase 3 reports, from relatively simple to more difficult. The first iteration would invoke the Phase 2 Compatibility Converter applied to the Phase 3 Compatibility Analyzer, make some clearly identified ’best guess’ decisions, and produce a POD Go preset that could be used as a starting point for further manual edits. EDIT: An afterthought (as it usually is). Don’t forget to factor in ongoing maintenance to this utility. If people are going to pay for it, and for it to remain relevant, it will need to be at least reviewed and usually updated as both Helix and POD Go receive firmware updates.