silverhead

Yes. You use the Stadium app running on your computer to export Setlists and USER presets to a folder on your computer. Then you swap devices and use the app again to import them to the other Stadium device.

Stadium can import individual IR wav files, but not the set of IRs contained in a Helix Bundle or Backup file. Here’s a potential workaround for IRs: 1) In Helix Edit go to the IR area. Select all IRs and export them all in a single operation to a specific folder on your computer. 2) In the Stadium app go to the empty IR library window. 3) In the IR computer folder Select All wav files. 4) Drag/Drop the set of all selected individual wav files into the Stadium IR library in a single operation.

I can’t recommend either one over the other because both are excellent choices. In terms of “good amp simulation, realistic tone generation, ease of editing, and consistent performance.” they are very similar. Both are based on the same amp/FX modeling technology; both can be edited using the device itself or similar computer programs; both can be used as an audio interface for recording purposes. The POD Go has a wireless option. In those areas I suggest you explore each in further detail by reading their manuals to get a feel for whether you might prefer one or the other based on any operational details like available amps/FX and routing (e.g. parallel path processing). There is one design difference that I think you should explore. They differ in their approach to DSP management. The Stomp uses dynamic DSP while the POD Go uses a blend of fixed and dynamic DSP allocation. In practical terms the Stomp offers more flexibility in FX selection, routing, and placement in the signal chain, while the POD Go is arguably easier to use at the cost of having fewer FX options and no parallel path processing. DSP management may be the deciding factor for you; make sure you understand this difference in practical terms before purchasing. Again, the manuals will help especially the ‘Flex blocks’ aspect of the POD Go.

There is no visible difference between the trial version and the full version.

Startup the Stadium in maintenance mode by holding down the Home and Song buttons while turning it on. With a properly formatted MicroSD card inserted select Create Backup. Eject the SD card, insert it in the other Stadium device. Again, start that one in Maintenance mode. Select Restore Backup. The backup includes everything the user can create or import: USER presets, Setlists, IRs, Favorites, Templates, Songs, and Clones. Currently there is no granularity to the Restore process. You can’t select portions/segments to reinstall (e.g. only IRs); it’s all or nothing. Here’s a snippet from the Stadium manual: Helix Stadium can load individual presets, entire setlists, favorites, and IR (.wav) files from Helix/HX. It cannot load an entire Helix/HX backup file.

Maybe, and especially if lots of users request it. You can submit your request here: https://line6.com/company/contact/productfeedback/

No, Capacitive Touch is not designed as an alternative to pressing the switch down. It is intended to do something different. For further info there’s a section in the manual explaining Capacitive Touch.

Describe what you mean by ‘work’? What would you like/expect to have happen when you touch, for instance, the Play footswitch in Transport mode?

It’s not typical but not unheard of either. It usually indicates a local (household) power issue. Try using different household circuits or at least outlets for your POD and computer. No, the POD HD is not a Bluetooth device.

It might be worth (re)reading the manual section on the matrix mixer. Perhaps a mixer reset and making sure the channels aren’t linked unexpectedly?

Check your Output block setting. Matrix is its own output, different from 1/4" outputs, but includes 1/4", XLR, and Phones. Your symptoms in your second post suggest the Output block setting is 1/4", not Matrix, meaning that only the 1/4" jacks are receiving the output signal. Is that what you mean by 'bypass matrix'? If you have it set to Matrix you should also be getting the output signal at the XLR and Headphones outputs. Check those. If only the 1/4" outputs are missing when Matrix is selected I think that's a strong indication of a hardware fault in the circuitry from Matrix to 1/4" jacks.

This is a known bug that should be fixed soon.

You can submit this idea as a feature request here: https://line6.com/company/contact/productfeedback/ It has been suggested before but the more people request it the more likely it will eventually be implemented. The idea is partly addressed in Helix Stadium. This is how presets now behave in Stadium - a change to one preset is propagated to all. It has not yet been implemented on a per-block basis but the request has been made there too.

An IR is effectively a Cab. It is not an amp replacement. It is based on a capture of an ‘Impulse Response’ generated by a specific cab and microphone combination including a specific mic placement.

You can submit a feature request here: https://line6.com/company/contact/productfeedback/

Even though it’s no longer for sale it remains under license. Owners are not suddenly permitted to give it to others for free.

…. and not Jeremy …

But doesn’t this ‘trick’ also require you to visit every Snapshot to set the active/bypass state for the additional gain/vol block? I thought that’s what you are trying to avoid. If you’re going to visit every block then go with your initial desire to use the amp Drive parameter. Also, a gain/vol block at the end of the chain will not affect the tone as the Drive parameter will. I guess now I’m just confused about your intentions.

You could assign the Drive parameter to an expression pedal rather than the Snapshot controller but it would be difficult to repeatedly achieve the exact same specific value, e.g. 5 rather than 4.8, on each sweep.

I did not notice any difference using my Beyer Dynamic DT990 phones so I don’t think it’s a bug. Mine are 250 ohm impedance. Not sure that would be the difference, though, since your phones were satisfactory with the LT. Might be a hardware issue with the phones jack/circuitry in your device. You could open a support ticket.

You need to do that manually in each Snapshot. There’s no automation for that. You could submit a feature request here: https://line6.com/company/contact/productfeedback/

Line 6 Monkey was retired a couple of days ago. See the banner at the top of this page for how to proceed - use Line 6 Central.

Yes, that’s my understanding. There are 2 DSP processors which provide the independent processing for Path 1 and Path 2. Each path can also handle parallel processing within the same processor; the parallel paths in each are called path A and B. The parallel path can split, join, and split again but it’s all called A and B. Within each processor (Path 1 and Path 2) path B can be split at the very beginning providing Input 1B (or 2B). And/or path B may not rejoin path A at all after a split, providing Output 1B (or 2B). When both Input B and Output B exist on a Path the ‘parallel’ path is processed as a separate linear path, but still uses the DSP capacity of the Path’s processor.

The manual says you can control the path inputs 1A through 2B. The implication is that you need to use a Return block as a path input. Yes, a split block on path 1A is essentially the input to path 1B; 1B no longer has a separate Input block.

I haven’t done this myself but the manual says you can. See Global Settings -> Switches/Pedals, particularly the Control A/B settings. You will need a TRS cable with a Y-splitter to control up to two external pedals/footswitches. Also, probably good to read the manual section on Configuring External Controllers.