silverhead

I don’t know what the issue is but here are a few troubleshooting ideas to isolate the problem. - test the cable (sorry to be so basic but that’s where to start!) - make sure the levels are compatible; i.e. 1/4” Output level matches amp’s FX Return level expectation. - connect the output to a different device’s input; not your amp. - use an XL Send output, not the 1/4” output Those steps should give you an indication of how far the signal reaches, and whether the problem lies somewhere in the XL or in your amp.

The built in pedal has a toe switch allowing it be used as two separate controllers, EXP-1 and EXP-2. By default, the Wah block is assigned to EXP-1 and the Vol block to EXP-2. So if you have depressed the toe switch (unknowingly ) after assigning the Vol block the pedal moves to the EXP-1 assignment and is no longer controlling the Vol block. Press the toe switch and see if that rectifies your issue.

I’m a bit confused. You’ve posted this in the Helix Stadium sub-forum but you are talking about the DL4 MkII product. I have moved this topic to the proper sub-forum.

Yes, that’s true and there’s currently no way to get the first beat emphasized outside the context of a Song. I presume that’s because there are no bars/beats unless there’s a Song structure including time signature supporting them. A sequence of unstructured clicks has no ‘first beat of a bar’. Without a time signature (3/4, 4/4, …?) there’s no ‘first beat’. The Start flag in a Song provides this structure. I expect this could be changed in a future firmware update if enough people want it. Submit your feature request here: https://line6.com/company/contact/productfeedback/

Are you naming the new preset when you save it?

Are you using the built-in pedal on the Stadium XL or an external pedal? In either case make sure the pedal assigned to the Vol block is active (EXP-1 or EXP-2) when moving the pedal.

Yes, this is a known bug that will be fixed in an upcoming firmware release.

Looking at the product description for PF 2.5 (see Products tab at the top of this page) I see two things thwt may be relevant: - yes, there is a free trial version - it is restricted to 32 bit machines. I don’t know if Win11 bas a 32-bit compatibility mode.

I think we’re going to see improvements in how setlists are implemented in a future firmware update (but I have no basis for that expectation; purely speculation). The idea of using aliases with a single copy of a USER preset is a good one, imho, but the current implementation is a bit confusing to me. Like you, I also see no point in having a setlist file on my computer that has nothing but aliases. I also don’t understand the frequent appearance of a numbered suffix. e.g. (1) behind a USER preset’s name when importing setlists.

One option is to maintain separate microSD cards for different purposes (e.g. bands). Swapping presets in and out of the USER area can become problematic with setlists and Showcase. It’s possible to end up with incompatible versions of USER presets, Setlists, and Song data in the device. For instance, suppose you swap out USER presets named, for convenience here, A and B. If a setlist contains an alias to preset A and/or B it seems that setlist is now incompatible with the USER preset area. Also, if a Song contains flags that refer to preset A and/orB the Song data is also incompatible. Stadium system data including USER presets, setlists, and Songs form a tightly integrated dataset. Creating and restoring backups using different microSD cards maintains data integrity. Another thought that I haven’t experimented with so I’m speaking theoretically here…. What about using Songs and Playlists instead of setlists? I know you can create an Empty Song in Stadium using the app. Presumably you could add a flag at the Start of each Song that loads the desired USER preset. That way you could use different Song names in a Playlist without being forced into USER preset redundancy as you described above using setlists. The Songs would have no audio; they would just be used for preset management. Again, purely theoretical. I like your idea of renaming setlist elements while retaining the alias to the underlying USER preset’s name. Have you submitted this as a feature request?

I suggest you open a support ticket to report these issues directly to Line 6. Similar issues have been discussed here and reported already but the more reports Line 6 receives the more likely it is they will be fixed reasonably soon. Line 6 generally releases firmware updates for new products in a timely manner to fix critical bugs.

Open a support ticket to report these issues. There are some known bugs regarding Snapshot behaviours that will be addressed in a future firmware release.

This was discussed in another topic here but I can't find it at the moment. Short story is that this is not (yet?) possible and others want to see this too. The feeling is that a solution could be to use MIDI commands for Song operations. In other words, preset selection could trigger operations for a specific Song (e.g.playback) via the Command Center. If you want to add your voice to this suggestion submit a feature request here: https://line6.com/company/contact/productfeedback/

You get feature requests to Line 6 developers by providing product feedback here: https://line6.com/company/contact/productfeedback/ No need or mechanism for moderators to forward it.

Try reinstalling the firmware. Backup anything you want to keep first.

A stem file is typically a pre-mixed audio file containing multiple tracks (eg. drums, keyboards, etc.) that can be further processed as a unit. If you mean “Can Stadium extract the original tracks from a stem file and treat them as individual drum, keyboard, etc. tracks” the answer is no. But you can transfer a stem track along with other individual tracks into Stadium to create a Song. However, the stem file remains a single track/unit in Stadium.

There are known bugs in the way Snapshots are behaving, especially regarding block on/off states. They will be fixed in a future firmware update.

First, format the new, bigger card using the Stadium Maintenance utility. Then you can do one of two things depending on what files are already on the old smaller card: - if the files on the old card are just backups, including Song audio files, there’s really no need for them to be transferred to the new card. Just create a new backup on the new card and proceed as usual. If you want to restore an older backup just use the older card. - if you really need the older files on the new card you can transfer the files using your Mac. But what’s on there other than backups that remain available on the old card?

and…to all others who have posted here about this issue, you should open a support ticket if you haven’t done so already.

Have you updated your ticket with this information?

I have found that the first beat is emphasized only during Song playback. It is not emphasized if the setting is 'Always On'.

Open a support ticket to provide this information to the Line 6 developers. This is a user support forum and the people who need to receive this information don’t hang out here.

I’m wondering if this is related just to the editor/app. Are Snapshot changes consistently working properly if you just use the device, not the editor, to create and modify the Snapshots? Seems to be the case for @bverfon. Is it true for others? I expect this won’t help with importing presets from OG Helix but it may give the developers more insight to identify and fix any related bugs.

I don't think it's a firmware issue because no one else is reporting this. Open a support ticket.