silverhead

That's why it's good practice to copy/edit presets only in the main USER preset area - not in a Setlist. A custom setlist that you have created, like your Set List 1, is used to select and order presets from the main USER preset area - not for editing/copying them. Remember - presets in a custom setlist contain aliases to presets in the USER area. They are not themselves different presets, hence editing them and expecting them to behave like different presets is bound to be problematic. Here's a quote from the manual: As a general guide, use the USER PRESETS folder to create your presets, and reserve setlists for placing those presets in a specific order for your performances, rehearsals, and recording sessions.

See the Downloads link at the top of this page. In the Choose Software field select Helix Stadium.

I’m not sure exactly what ‘this ticket’ refers to but this post itself is not a support ticket. To submit an official support ticket to Line 6 you need to follow the Support link at the top of this page.

I see, and the Stadium implementation is different in that it maintains only a single copy of a named preset; no duplicates and enforced change propagation in Setlists. Many people like this. Of course you can get different ‘versions’ using Snapshots but not in the way you mean. But the OG Helix didn’t offer ‘versioning’ of presets either. It just allowed you to have different copies of presets with the same name in different Setlists. Did you not have to maintain your private versioning system anyway? I notice that Stadium will append a number to the name of a New/Copied preset when it recognizes a duplicate name. For example, you can have different ‘versions’ of the same preset with “<preset name>” and “<preset name>(1)” in the User preset area. Stadium essentially gives it a different name with what could be considered an embedded version number. You could then include different versions in different Setlists while maintaining all versions in the User area. You can also include version information in the Info field of each preset. Can that help you with managing versions?

Yes, there is: https://line6.com/company/contact/productfeedback/ It’s not a topic/thread here that’s visible to everyone but it is the official way to get feature requests to the Line 6 development team.

You can open a support ticket to see if Line 6 tech support can help.

Unless I misunderstand you here… I guess the thinking is that if you have made ‘other changes’ to a preset then it’s a different preset and should have a different name. Having two different presets with the same name is just confusing. And it’s always been the case that if you switch presets without saving changes you lose the changes whether or not you consider them incomplete. Setlist organization has nothing to do with that.

The OP is asking about controlling two amp parameters with the switches: channel and hi/lo. I may be over complicating things or maybe I just don’t understand but I think that requires 2 TRS cables and switch assignments in the XL: one for Control A/B to control channel selection, and one for Control C/D for hi/lo selection. I’m not sure how you get both of those cables/signals into the single TRS jack on the amp while maintaining differentiation. EDIT: I think I misunderstood how the Control jacks work, and dandesy and maxxlines are correct. I now think you only need one TRS cable in a single Control A/B jack and assign two switches in Command Center for Control A (channel) and Control B (hi/lo). Sorry for any confusion I may have caused.

I realize this is your first post here and you haven’t had any response. I think that’s because nobody reading this (and there are many) has any good suggestions to offer. I expect the answer is “No, that won’t work.” but I’m not certain. I just wanted you to know that the forum is active despite the silence on your question.

This is a very detailed and well explained feature request. It would be a shame for it to go unnoticed by Line 6. Unfortunately, that's what may happen with this post. This is not the official way to submit feature requests. I strongly suggest that both @rikkimadan and @maxxlines submit an official feature request here: https://line6.com/company/contact/productfeedback/

You could also try using Customtone (see link at top of this page) and filter for the Stadium device and Collective Soul.

You need the Stadium app (editor) to install downloaded presets to the Stadium device. If your work computer restricts you from installing the Stadium app then you need to use another computer..

You might want to browse through the Factory presets and perhaps find a good starting point. If anything sounds close to what you want, check out the Info button for the preset for tips on its intentions and details.

Are you also appealing to Apple to not drop support for Intel architectures like Rosetta? That would also be helpful.

Open a support ticket. Line 6 will need to be involved.

It could be a settings issue. You're probably already aware of the Matrix mixer in Stadium, and that the 1/4", XLR, and headphones output levels can be controlled individually or all together. There's also a Global Setting that controls 1/4" and XLR output levels. This is just a guess but the latter may interact with the former. In other words, if you have the XLR outputs set to Mic rather than Line, and you have the mixer controls such that all outputs are controlled together, your headphones output might be lower than expected. Make sure the headphones output is controlled independently in the Matrix.

How are you monitoring? Guitar amp? Headphones? Speakers? What kind?

Another patch culprit mentioned above is KB5101650.

Don’t know. And Line 6 does not make their product development plans and activities public knowledge. If it happens you’ll hear about it when it happens.

Yes, there probably will be another update at some point because Line 6 has said so. But the timing is not, and likely will not be, known in advance. And OG Helix units have already been left behind in terms of features, capability, DSP capacity, touch screen, etc. …. and that will continue.

Not ideal but you could pick up an old laptop that runs an old OS that is compatible with the original Workbench program that is compatible with your Variax 700. That will allow you to create alternate tunings and store them with the model in your V700. The Helix LT will never be fully compatible with your V700 but in some cases it will successfully store and recall V700 models in LT presets. However this is not supported and may not work for you.

The official method for bringing feature requests like this directly to the attention of Line 6 is here: https://line6.com/company/contact/productfeedback/

…. and also make sure your firmware is up to date. I recall there were some Flag issues in previous releases.

I would open a support ticket for two reasons: 1) if it is a bug that’s the official way to report it to Line 6, and 2) if there is some possible recovery they are the ones most likely to know about it. Meantime maybe someone here has other information.

While there are only 5 icons that say "FX" the bypass state of the other icons can also be assigned to a footswitch. For instance, you can change the Wah FX to be turned on/off using a footswitch rather than the Exp Toe switch. You can even assign block parameter values to a footswitch. For instance, you can assign the amp's Gain parameter to toggle between two values. See the Pod Go Edit manual for details.