silverhead

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

I doubt that there are plans to do this but I don’t really know. You can submit a feature request.

Open a support ticket to report the bug.

USB Input 1/2 is reserved to receive the output of your computer (e.g. your DAW). It comes into the Stadium device as an Input that is shown in the Matrix so that you can balance , pan, mute/solo it to mix with the other outputs from various sources. It does not appear as a selection in the Input block because it is reserved.

Submit a feature request.

@jemenake, @mattsteeves Perhaps if you also opened a support ticket Line 6 would take another look.

You need to open a support ticket to officially report a bug to Line 6.

The thing is, there’s a new ‘they’ in town, and ‘they’ already make their own guitars. At best you might find some Variax IP in a new Yamaha guitar.

The editor for Stadium device es is called Helix Stadium, or HX Edit. Try downloading and installing that.

I'll copy/paste my response in an earlier thread on this topic...... Firstly, the official way to make feature requests is to use the Product Feedback form. Look for the “LINE 6 PRODUCT FEEDBACK” link on the bottom left of the Line6.com home page. Secondly, the Variax product line now comes under the ownership of Yamaha as part of the takeover of Line 6 several years ago. Development of several previous Line 6 product lines that competed directly with Yamaha, including Variax and StageSource/Stagescape, were halted at that time. It is unlikely that Variax as a Line 6 brand will ever be seen again. But who knows?

Open a support ticket for this. It may be a bug. If so, the ticket system is the way to bring it to the attention of Line 6.

In Edit View on the device there are Undo and Redo arrows immediately to the left of the preset name. In the Stadium app/editor they appear in the top left corner of the window.

To make an official feature request to Line 6 developers follow the instructions you’ll find in the Ideascale Retirement banner near the top of this page.

I wonder if there’s some sort of licensing or authorization issue since they are purchased IRs. Make sure your Stadium device is registered in your Line 6; account, and try running the License Manager.

Yeah, sorry I missed that. Useful discussion anyway!

Line 6 has said that the Expand D10 will support L6 Link for PowerCab connectivity. I don’t know thwt they have made the same commitment for the DT amps.

Warning: This is a lengthy and future oriented post. Probably not for everyone. It’s aimed at users who use lots of presets, want to manage different band setups, want to share the Stadium device with other users, or… The handling of presets and setlists has fundamentally changed from Helix to Helix Stadium. You can no longer swap setlists in and out willy nilly because they contain only aliases to the actual presets that reside in the USER setlist, of which there is exactly one with a limit of 512 onboard presets at any time. Also, since setlists contain only aliases it is possible to accidentally end up with a setlist that is not synchronized with the onboard presets - e.g. importing a setlist containing an alias to a preset that has since been deleted from the USER setlist. Or (worse) exporting a preset from a custom setlist view, thereby exporting the alias and perhaps unintentionally overwriting the actual preset in your computer folder. Further, we know that the Showcase feature is coming and that it will support preset and snapshot changes at any point in a Song. When you put all this together it becomes clear that the USER setlist, custom setlists, and Songs (including audio stored on the microSD card) are an integrated dataset that must remain synchronized. How do you manage this from a workflow perspective? How do you keep your dataset synchronized and work around the 512 preset limitation? Easy to say ‘just remove the limit’ but there will always be a limit and no matter what it is it will eventually be reached because…. Well, because we can. Now, 512 presets seems like a lot to me but I am a studio player, not a multi-band gigging musician. If I find myself in a different situation someday and keeping things synchronized becomes complicated, the following is what I would do. There is a set of functions called Helix Stadium Maintenance that is accessible using a special startup sequence as described in the final section of the online manual. Hold down the Home and Song buttons when starting up. Among the maintenance functions is a Backup and Restore capability. The manual states that the Create Backup function saves the backup file to the inserted microSD card. That’s the key to maintaining different synchronized datasets, essentially different system images. You can use different microSD cards to store different system images, with each image being for a different purpose. For instance, you could have a different dedicated image/SD card for each band you belong to, or simply for overflow when you have exceed the 512 limit, or for different device users. Here’s a suggested workflow to utilize this strategy: At the end of each session you would need to: - power down the Helix Stadium device - restart it while holding down the Home and Song buttons. This will cause the device to start in the Helix Stadium Maintenance mode. - insert your desired microSD card and Create Backup - when complete, select the Shutdown option on the Maintenance screen At the beginning of each session you would need to: - restart the Helix Stadium device while holding down the Home and Song buttons. This will cause the device to start in the Helix Stadium Maintenance mode. - insert your desired microSD card and Restore Backup, selecting the desired backup file - select the Shutdown option on the Maintenance screen - restart the device normally This workflow would provide a means to work within the current limitation and ensure that you always have a system with a dataset that has synchronized onboard presets, custom setlists, IRs, Songs including audio files, and (bonus!) Global Settings.

Elaborating on the above….. The manual states that the Create Backup function saves the backup file to the inserted microSD card. That means each of you and your brothers could have your own dedicated SD card for personal use. At the end of each session you would need to: - power down the Helix Stadium device - restart it while holding down the Home and Song buttons. This will cause the device to start in the Helix Stadium Maintenance mode. - insert your personal microSD card and Create Backup - select the Shutdown option on the Maintenance screen At the beginning of each session you would need to: - restart the Helix Stadium device while holding down the Home and Song buttons. This will cause the device to start in the Helix Stadium Maintenance mode. - insert your personal microSD card and Restore Backup, selecting the backup file you created above - select the Shutdown option on the Maintenance screen - restart the device normally

Glad you got it working. I want to correct some inaccurate information I provided earlier. The Helix StadiumMaintenance screen is not available from the Menu icon. It is only available through a startup sequence. You can hold down either FS 6 and 12 (as I suggested) or the Home and Song buttons (as described in the manual) when powering up.

Try holding down footswitches 6 and 12 when powering up. Then select Restore Factory Defaults. When complete, choose the Shutdown option.

The only dry output I’m aware of is the assignable ReAmp Source Out that is available over the USB 7 and 8 channels. (See Global Settings) These are provided to allow you to record a dry output tapped directly from the assigned physical input (no processing applied other than the required A/D conversion) into your DAW for plugin or reamping purposes. The Direct Output in Global Settings for the USB 1/2 and S/PDIF allows you to select these outputs in the Output block of a preset, but they output the processed, not dry, signal. Otherwise you can get an almost dry signal from a physical output by creating an empty path in a preset and selecting the desired physical output in the Output block of that path. This involves both an initial A/D and a final D/A conversion.

There is a limit of 512 presets in the USER setlist, which is where all the actual presets live. Are you reaching that limit? If not there is no need to export and import setlists and presets. You and your brothers can live together on the device. Avoid Exporting a preset from a custom (not USER) setlist view. That exports the alias for the preset, and unless you’re careful it can overwrite the actual preset in the associated folder on your computer. If you are exceeding the limit then you will need to manage external files on your computer or SD card. I think the easiest and most reliable way to do that is to use the Backup and Restore options in the Helix Stadium Maintenance feature. I believe the backup filename is automatically assigned and time/date stamped so you will need to manually keep track of which backup belongs to whom among you and your brothers. That way you can avoid the multiple exports and imports of preset and setlists; each of you can Backup your own system image before shutting down and Restore it next time you use the device. That will also backup all your custom setlists, your IRs and your Global Settings. You can each manage your own system images.

Open the Ideascale Retirement banner at the top of this page. There you will find instructions for product feedback, such as feature requests.

Have you restarted the Helix Stadium? if it restarts correctly proceed to the following paragraph. If not, open a support ticket. Once you can see the main screen, In the top left corner you will see a menu button, an icon with several horizontal bars. One of the selections from the menu is Helix Stadium Maintenance. One of the maintenance options (top right area of the display) is Restore Factory Defaults.

To make an official feature request follow the instructions in the Ideascale Retirement banner at the top of this page.