Minor Bug: Saving a Preset while in one of my Setlists sends me back to the USER PRESETS setlist.

[Gillespie1983]

Example:

Preset 04 in Setlist MY_GIG is an alias of Preset 70 in USER PRESETS 

 

When playing through MY_GIG's presets, I stopped and edited Preset 04 and dbl-pressed Save.  Changes were saved, then the STADIUM automatically repositioned to USER SETLIST(70). 

Pressing "Next Preset" sent me to USER PRESETS(71),  not MY_GIG(05).  I had to manually re-navigate back to MY_GIG and scroll to Preset 05.

 

[silverhead]

You need to open a support ticket to officially report a bug. That way it will definitely be seen by Line 6 developers. This is a user support forum and Line 6 staff don’t generally hang out here.

[Nos402]

On 11/23/2025 at 11:04 AM, Gillespie1983 said:

Example:

Preset 04 in Setlist MY_GIG is an alias of Preset 70 in USER PRESETS 

 

When playing through MY_GIG's presets, I stopped and edited Preset 04 and dbl-pressed Save.  Changes were saved, then the STADIUM automatically repositioned to USER SETLIST(70). 

Pressing "Next Preset" sent me to USER PRESETS(71),  not MY_GIG(05).  I had to manually re-navigate back to MY_GIG and scroll to Preset 05.

 

 

YES. I've opened a bunch of tickets about various issues. They are probably starting to hate me. This could definitely be a problem at a gig if you don't notice.

[silverhead]

It’s possible that this is a design decision rather than a bug. Remember that the only version of the actual preset is the one that exists in the USER setlist.  A custom setlist contains only an alias to the actual preset. Hence when you edit and Save a preset, even if it’s done from a custom setlist context, you are actually working in the USER setlist. Perhaps leaving you there after the Save operation is intended to be an explicit indication of what you’re doing.

 

But the response to a support ticket will clarify.

[Nos402]

On 11/23/2025 at 3:52 PM, silverhead said:

It’s possible that this is a design decision rather than a bug. Remember that the only version of the actual preset is the one that exists in the USER setlist.  A custom setlist contains only an alias to the actual preset. Hence when you edit and Save a preset, even if it’s done from a custom setlist context, you are actually working in the USER setlist. Perhaps leaving you there after the Save operation is intended to be an explicit indication of what you’re doing.

 

But the response to a support ticket will clarify.

 

True but at the very least it should be an option. If I'm in a set list at a gig, and make a quick tweak, I want to stay WHERE I AM in the set list so I can hit "next preset" and go to the next song. I don't want to have to do a tweak, then tap the set list, then tap whatever song I was on to resume my gig.

[Gillespie1983]

On 11/23/2025 at 4:52 PM, silverhead said:

It’s possible that this is a design decision rather than a bug. Remember that the only version of the actual preset is the one that exists in the USER setlist.  A custom setlist contains only an alias to the actual preset. Hence when you edit and Save a preset, even if it’s done from a custom setlist context, you are actually working in the USER setlist. Perhaps leaving you there after the Save operation is intended to be an explicit indication of what you’re doing.

 

But the response to a support ticket will clarify.

You could be right about the design decision, but the Desktop App remains in the custom setlist.  Two different design teams?

[silverhead]

On 11/24/2025 at 11:16 AM, Gillespie1983 said:

You could be right about the design decision, but the Desktop App remains in the custom setlist.  Two different design teams?

Interesting. Be careful about using the Export preset function while viewing the list of aliases in the custom (not USER) setlist view. Exporting from there will export the alias as a file, potentially overwriting the actual preset in the USER space if you’re not careful. That’s why I’m inclined to think that returning to the custom setlist may actually be a bug.