silverhead

Just checking ... are you using Workbench HD? That's the version compatible with the JTV series. Also, make sure you have a fully charged battery and a 1/4" cable plugged into the Variax. That's the 'On' switch.

Are you familiar with the Discard Edits parameter? That may be what you’re missing. In OG Helix it was called the Snapshot Edits parameter. https://manuals.line6.com/en/helix-stadium/live/snapshots#The-Snapshot-Panel

Correct. You can’t change the specific IR selection within a generic IR block using Snapshots for exactly the reason you state: audio dropout associated with loading new IR (DSP). It’s the same as wanting to swap, for example, specific delay models within the same generic Delay block using Snapshots, say from Simple Delay to Bucket Brigade. The required DSP swap defeats the entire purpose of Snapshots. Nor can you change Cab or Mic model selections using Snapshots. Or Reverb models, or ….

Open a support ticket.

You need to do this in the User preset area, not in a setlist. When done within a setlist it simply creates a copy of the original, with the same name, on the assumption that you plan to use the same preset at different points during the set. If you want to use a new preset in that particular Setlist slot you need to create the new preset in the User preset area, use the Save As operation to rename it, and then assign it to the Setlist slot.

Open a support ticket.

That sounds more than annoying. It sounds like a flawed implementation. Surely the purpose of using Setlists is that you can navigate to the next preset quickly and easily. I think that when you are viewing a Setlist and hit the Up/Down switches the system should select the previous/next preset in the Setlist, not in the User presets area. I would report this behaviour as a bug.

Just want to check the basics….. You don’t mention your Variax model. Is it JTV or later? If not you need to be using the original Workbench program, not Workbench HD.

Are you sure the Stadium Native plugin is in a folder that is scanned by FL Studio?

Please submit an official feature request here: https://line6.com/company/contact/productfeedback/ Otherwise this post won't likely reach Line 6 developers/management and so won't be considered.

I notice that you are using the Line 6 UX1 as the audio interface. That product included a license for the original POD Farm plugin, not POD Farm 2. Is it possible that you are using different versions of POD Farm for comparison?

Try transferring both Helix Native presets to your Helix. Then manually copy the blocks in the vocal preset into Path 2 of the guitar preset. That should leave you with the desired dual path guitar+vocal preset.

I’ve moved this to the proper forum.

The Line 6 Central app allows you to install older firmware versions.

Stadium operates differently re: firmware downloads. You need to use the Line 6 Central app to view and install older Stadium firmware versions.

I’m not aware of any such thing as Helix Native Studio. I presume you mean Helix Stadium Native. The procedure is a bit different than Helix Native due to the different way presets are handled in Stadium. It is well described in the Stadium Native manual and I suggest you start with that (see Support link at top of this page. Select Manuals). If you are having difficulty come back here with specific details on where the documented procedure is not working for you. Currently Helix Marketplace assets (your paid-for presets?) are not supported in Stadium Native.

Theoretically possible? Maybe. At all likely? No. But never say never. Submit this as a feature request. https://line6.com/company/contact/productfeedback/

Nobody is able to answer this yet. Neither the Helix Stadium app nor Helix Stadium Native are able to load Helix Marketplace assets yet. That will come in time but no date has been announced. Here’s the relevant statement in the current Helix Stadium manual: As of this writing, Helix Marketplace premium presets and IRs are not supported. They will be, but unfortunately, we have no timeline to share. And in the current Helix Stadium Native manual: Original Helix presets purchased from the Line 6 Marketplace are not supported in Helix Stadium Native at this time.

Yes Helix Stadium Native runs on both platforms and you can use both under a single license.

I have approved your post and it should now be visible publicly. Yours was one of several awaiting approval in that thread and I approved them all. By way of explanation…. Moderators are alerted to a first-time post by a new user when the post initiates a new thread. We are not alerted when a fist-time poster responds within an existing thread, which is what occurred with you and the others. That’s a gap that I will bring to the attention of the Line 6 forum developers.

I don’t see any post from you in the moderation queue. Can you point me to the thread in which you posted?

Nothing to lose, and you will get an answer on that point.

Yes. See the MIDI section of the manual describing Transport Control using Global CCs.

Yes you can do this but I don’t recommend it unless you’re very careful to manually maintain a method to track compatibility. You need to understand that individual backups of these items can’t just be reloaded independently at a later date and expect things to work together properly. By ‘things’ I mean the tightly integrated set of data that exists on the Stadium device. Among other things it contains User Presets, Setlists (aliases of Presets), and Showcase Songs (containing Flags that can reference Presets). If you simply load a backed up copy of your User Presets you can easily break any references to existing Presets contained in your Setlists or Songs. With OG Helix you only had to keep Presets and IRs compatible manually. With Stadium there are more individual items that you can export/import individually yet are interdependent: User Presets, Setlists, Songs, IRs, and Clones. These (at least) compromise a tightly integrated dataset.