silverhead

Here’s the product description. I guess you can read some capabilities into it. The Expand D10 digital I/O expansion unit greatly increases the flexibility of Helix Stadium processors. Connect Variax® modeling guitars using VDI and Powercab® 112+/212+ active guitar speaker systems using L6 LINK™. It also expands the ways in which Helix Stadium processors may be used with audio interfaces, digital mixers, multi-connector breakout boxes, and other devices via 8-channel optical out. Features • Variax Digital Interface (VDI), L6 LINK, AES/EBU, and 8-channel optical connectivity • Connect Variax modeling guitars via VDI • Connect Powercab 112+/212+ active guitar speaker systems via L6 LINK • Send two channels of AES/EBU digital audio at 44.1kHz or 48kHz • Send up to 8 channels of digital audio over TOSLINK optical • Connects to Helix Stadium processors with a Cat6 cable via Nexus

I'm not aware of any reported overheating issue. Only you can tell how warm it is, but warmer than room temperature would not be abnormal. I wouldn't worry about it until and unless something fails or it becomes painful to the touch. In that case open a support ticket; it's under warranty.

I can’t see it either. I suspect it has to do with my aging eyes and perhaps glasses to correct some astigmatism.

There’s a picture of it in the online manual in the Presets, Setlists, and Templates section. Scroll down until your see a subsection called Selecting Presets from the Switches (or just search for that term from the outset). Like Helix you have a top row and a bottom row, assignable to presets or snapshots. The picture shows the 8 Presets view. You can have one row for Presets and one for Snapshots so use your imagination. It looks similar to the POD Go which also lacks scribble strips. The biggest adjustment you will need to make if you’re coming from the Helix scribble strip world is not the display. It’s the navigation. You need to press the Home button to toggle between Edit view and Play view. It’s a button, not a footswitch. You need to bend down and use your finger. It may be assignable to a footswitch in the Command Center - I haven’t investigated that.

My levels are about the same. I wouldn’t worry about it unless you hear something you think isn’t right. I pay more attention to the signal level indicator in the Output block; if that turns red it means there’s clipping. Also, you can test the output level meter (the one on the right thwt you refer to) in the Amp block. If it behaves like a normal level meter it might change colour to orange and then red as you raise the amp’s Drive/Gain, Master, and/or Channel levels. I don’t know if it actually does change, but if you can make it change colour then you can be confident everything’s OK as long as it stays green.

No.

You can click/drag presets (multiple at a time if you wish) in the USER setlist view using the Helix Stadium editor.

I’ve also noticed that block selection doesn’t track/sync. I suppose it’s a minor bug. Open a support ticket to report it. Correct. I expect it will be implemented in a future update.

Global EQ in Helix applies only to the analog outputs. It does not affect USB outputs which are used for DAW and computer audio. So yes, you will need an external EQ.

I presume you have the Stadium XL? Control C/D do not apply to the non-XL Stadium devices.

I have moved this topic to ‘the right place’. But more importantly,

I expect the problems will be short term.

I can’t answer your question directly, but since you just got your Stadium you may not have had a chance to look at the Command Center section of the online manual…. https://manuals.line6.com/en/helix-stadium/rev-a-v1.1.0/command-center

A reminder to all users that this forum is a peer-to-peer user forum. No one from Line 6, particularly not the developers, is required to hang out here. Some do occasionally out of personal interest but we as users shouldn’t count on it. Nobody here can fix a bug or implement a new feature. Accordingly, this is not the official place to make bug reports or feature requests. If you want your bug report or feature request to actually reach Line 6 you need to do something else. To report a bug, open a support ticket. https://line6.com/support/tickets/add.html To submit a feature request: https://line6.com/company/contact/productfeedback/

Yes, custom setlists is the way to go for live events. Be aware, though, that the implementation of setlists is completely different in Stadium vs. OG Helix. There is a big conceptual change, and I think some bugs that still need to be worked out. The following is aimed at all readers here, not you specifically….. Conceptually, the USER setlist is now the only place where the actual presets live. A custom setlist is a list of aliases (pointers) to the USER setlist presets. Read the associated section in the online manual for clarification. This is still early days for the new mindset and implementation. I have experienced and reported some behaviours that I think are bugs: - when you Export a preset from the USER preset view it creates the associated preset file on your computer, as expected. When you Export a preset from a custom setlist view it creates a copy of the alias on your computer. If you’re not careful you can overwrite the actual preset on your computer. I think Exporting presets from the setlist view should be disabled; I can’t see any use for saving a single alias in a file. I can see a use for exporting/saving a setlist of aliases. - I have also experienced duplicates. I think there should only be a single copy of any preset name. I think any bracketed duplicate preset name is the result of a bug. If it’s a different preset it should have a different name; if it’s actually a duplicate of the same preset it shouldn’t exist. That’s the whole idea of the new implementation. My suggestion at this point, until some bugs are resolved, is to edit and Save presets only from the USER setlist view. The interaction between the presets themselves in the USER setlist and their aliases in custom setlists is where I think the bugs live. This will require careful attention and some extra touches (on the device) or mouse clicks (in the app/Librarian) for a little while to make sure you are in the USER setlist view but it should reduce the unexpected behaviours. I may end up eating my words here. If there is a valid reason for duplicate presets to exist in the USER setlist I would like to hear it. Meantime I encourage everyone experiencing duplicate preset names to open a support ticket to report it. The more info and evidence Line 6 has of these bugs the more likely they will get fixed sooner than later.

https://line6.com/support/page/kb/general-faq/operating-system-information/ To talk to a live person, call the numbers you’ll find by following the Support link at the top of this page.

Bugs should be reported through support tickets. Feature requests should be made via product feedback.

The Big Book of Helix Tips and Tricks (available on Sweetwater, author Craig Anderton) does a fantastic job of this. There’s also a very good website: helixhelp.com

You’ve quoted the original post in this thread. Subsequent discussion has clarified things. Short story: the manual clearly identifies the Agoura models.

No and yes, respectively, although ‘stuck with’ may be a bit harsh. Many people never upgraded to Helix because they remain completely satisfied with their POD HD products.

The *.hir filetype is proprietary to Line 6 and requires authorization. Since you purchased them from the Line 6 store they should be on record in your Line 6 account. Make sure you are logged into your Line 6 account within Helix Native when you attempt to load the hir files, and any associated licensed presets.

This is the proper link. Is it not working for you? If not try the usual browser cleaning stuff like clearing cache. https://line6.com/company/contact/productfeedback/

You might consider preparing for a complete system recovery if things go wrong. Familiarize yourself with the recovery steps (both system and app/data files) you would need to take if editing the Registry as suggested goes awry. Use the available utilities to backup all files and create a Recovery drive. You would be able to restore the exact same system image that you have now. You could even rehearse the steps in advance, right up to the point where you would actually perform the final recovery step. I had a catastrophic hard drive failure on my boot drive earlier this year. It was a real pain in the a$$ because I was not properly prepared. I had to purchase a new boot drive, install Win11 from scratch, and manually reinstall all apps and files. Fortunately I had at least used File History to back up important data files on a separate drive, but I still lost some data. Now I have everything in place to recover fully and quickly if (no, when) that happens again.

Open a support ticket to report the bug.

Personally I’m not sure, but you can find out by looking at the MIDI and Command Centre sections of the online manual.