Stadium Set Lists

[bbehrens]

When I use a set list for a gig, but I tweak something in preparation for the gig in the Stadium Editor, it causes the Stadium to always use the USER Set List (or Master Set List or ALL Presets setlist - whatever it is supposed to be called). I then have to go into the Stadium itself and select the Set List that I was using because the Stadium editor changed the preset that I tweaked and therefore switched to the USER Set list. This is a very annoying behavior since the USER Set List is the Master Set List which can get very big over time (unless you employ a separate maintenance strategy requiring you to keep the USEER Set List (Master Set List or whatever) organized (which is quite the chore in itself).

 

I think that Line 6's approach of using pointers for every Preset was a pretty BAD IDEA. It is something that I have used in Windows (various versions over the decades) very sparingly and for specific purposes. I think that it causes more headaches than it solves and this may just be another example of that.

 

Am I misunderstanding how presets work on the Stadium and perhaps there is a better way. Let me know what works best for you or if you find it just as frustrating.

[PaulTBaker]

I like the way that when you update a preset, it updates that preset in all set lists (since it is a pointer)... Would like to see that as an option for the blocks as well.  

 

If you are making edits through the HxEdit Stadium software, after you hit save, reselect the preset in the setlist (which is still on the left) and it pulls in the setlist on the device.  So I hit save, then double click the preset on the left (in the setlist) and the floor device has the current set list available.

[bbehrens]

Thanks Paul. I will be sure to do that as it was driving me crazy (not the first thing on this unit that has driven me crazy either). But I, personally, do not feel like updating all presets with the same name at the same time saves me from anything except managing the history of that particular preset. But then I lose other changes that I may have made. ANOTHER thing is that I can make changes to a Preset and then click on another Preset, for reference, and if I did not save those (incomplete) changes then I lose those most recent changes as well. It's like I am using Microsoft Word v2.0 on Windows 3.1 in 2026!

[silverhead]

On 7/23/2026 at 10:24 AM, bbehrens said:

…. But then I lose other changes that I may have made. ANOTHER thing is that I can make changes to a Preset and then click on another Preset, for reference, and if I did not save those (incomplete) changes then I lose those most recent changes as well.

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.

[MojoAxe]

I play in three different band and for each band I use a group of generic presets plus additional song-specific presets.  I have a setlist for each band that starts with the same group of generic presets, followed by any song-specific presets.  I like the idea of setlists being pointers back to the database of presets because I occasionally make adjustments to those generic presets to refine them, and its nice that the changes are carried over to each of the setlists.

 

What I would like to see added in a future update are folders within the user preset list.  I already have about 120 user presets and that list is growing, so it would be nice to be able to organize them into folders such that I don't need to scroll through such a long list to find the preset I want.

[bbehrens]

On 7/23/2026 at 9:48 AM, silverhead said:

Unless I misunderstand you here…

You did misunderstand me. Perhaps I was not clear. With Saving another version of a Preset then I can always save different states of that preset for reference. I can do that with the Stadium too. I just have to introduce the idea of version numbers. Versioning is a MUCH better way of developing a preset. It must come from my software background. But the way it was implemented in the Stadium - I have to be much more careful about it and preset management gets to be a real chore. It doesn't save me anything but causes more work for me. Well, that is my work flow. Maybe the Stadium was a bad purchase choice. I just never got that feeling with the Helix.

[silverhead]

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?  

[bbehrens]

Yes, it does work as you described by appending a number to the end of the name. So if I have "Song 1" and copy it then it appends "(1)" to the end of the name so that I now also have "Song 1 (1)". This is how this works on the Helix Stadium Device once you figure it out (That is ANOTHER topic on this forum). But, you do realize that this only applies to the "USER" Song Library in the Helix Stadium Editor. If you copy "Song 1" in user set list "Set List 1" then you get a SECOND "Song 1" that is ALSO named "Song 1" and is the same "Song 1" as "Song 1". I am on the latest version of the firmware 1.3.2 of the Helix Stadium XL Floor and the Stadium Editor. This is one of many various discrepancies between the Floor Unit and the Editor. But it is getting better. DSP is another issue and Presets can get corrupted between the two editors as well. These are known bugs. I could not tell you any issue numbers though.

[silverhead]

On 7/26/2026 at 4:02 PM, bbehrens said:

... If you copy "Song 1" in user set list "Set List 1" then you get a SECOND "Song 1" that is ALSO named "Song 1" and is the same "Song 1" as "Song 1". ...

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.

[silverhead]

I’ve been thinking about this some more because I was very confused in the beginning about the behaviour when editing presets in the USER preset area vs, a custom Setlist. I think that what you describe about getting a second preset also named Song 1 is actually a bug, especially if it exists in the USER preset area.  I think there should never be two presets with the exact same name in the User presets area. You might want to consider reporting it via a support ticket. 
 

I think the quote from the manual I provided above that begins with ‘as a general guide’ is actually more than that: right now it seems to me that it’s the way to avoid confusion, apparent bugs, and inconsistencies in the implementation of the new approach to presets and setlists that was introduced with Stadium.

 

When you select a preset in a custom Setlist (an alias meaning not an actual preset) you are actually viewing/seeing the underlying preset in the USER presets area. When you then edit and Save the preset, the change is applied in the USER presets area. All aliases to that preset in other custom Setlists now point to the changed preset. I found it confusing until getting used to it. I know it’s different and you prefer the previous duplication of actual presets in custom Setlists but it is what it is.