Line 6 Helix Stadium Talk

Oh this seems like a great idea what could possibly go wrong ?
Only that you mess up some setting on your Stadium.

I'm all for making 3rd party solutions possible as they allow for things that the manufacturer won't make due to cost or user need. I wish companies provided MIDI Sysex mappings or even APIs people could use to work with the device the way they want.
 
I don't know that there's a way to control their order when importing, but in the song view, if you use the gear icon in the upper right corner, in that view, you should be able to drag them into the order you want them in.
Thanks for the reply - yes, I’d already found how to do it within stadium but was hoping for a simpler way when they imported. DI has said that at some point we’ll be able to rename the 8 stem mixer channels per song - when that happens, the order only really matters for a person’s ocd but, other than that, consistency of the order becomes less important.

I think a lot of the problem here is how I’m using it. If anyone more experience with Moises wants to chime in and say ‘why are you doing it that way? You’re over complicating it and here’s what you’re missing’

The basic version of Moises does drums, bass, vocals, other. If you’re doing that it’s pretty simple….name your mixer channels to those four things and you’re all good for the import.

I’ve got the pro version - as well as the above categories, you get guitar 1, guitar 2, piano, keys, several other things, ability to split drums, a smart metronome…… So you choose what’s appropriate for the song but that means, in some songs, mixer channel 5 will be piano and in some it will be lead guitar. If I import to a clean project in my DAW (studio one in my case) then tweak the metronome, it buggers up the track order when exporting simply because Windows loves the alphabet (bass is first then drums the guitar etc)

My current workaround is that I’ve made a template in studio one where I name the stems with a number up front.

1. Drums
2. Bass
Etc

I export from Moises - the stems are labelled in a sensible enough way to allow me to drag to the appropriate channels within Studio One.

If the song in question needs a count in, I make it in studio one using SD3. For sure I could just cut the smart metronome track down appropriately but its sound isn’t to my liking. Yes, I know I can do count ins etc within Showcase but I still like having that track there ‘if needed’. I can always kill it in the mixer and use the showcase metronome if there’s a reason to but this seems easier to me right now. Happy to be educated otherwise :)

When I then export the stems, they’re labelled with 1, 2, 3, etc. Windows keeps the order and so does Stadium XL when I import them.

There’s probably a more elegant solution but this is working for now :). On my ‘to do’ list later is to now learn how to use the events within showcase to change patches.
 
So the other day, in my frustration at the bugs I was experiencing around stereo balance and block bypass with snapshots, I wiped my unit and factory reset it. Rebuilt presets from scratch. Since then, I haven’t encountered either of those issues. In fact, I enjoyed a completely glitch free experience this weekend.

I believe that my issues were caused by some sort of preset corruption which became baked into the template that I’d created and used to create all of my presets. Support is still researching this, but wanted to share in case others had the same issue.
 
Edit:
Oh sorry, I should have said XL.
Last week, the XL has a ~4 weeks delivery estimate, so I ordered from a local shop that was supposed to deliver in the beginning of January, but managed to get it to me Thursday last week.
So seems like they’ve caught up with demand.

Btw, everyday I play with this thing, the more I love it. I’ve mostly messed with the lower to mid gain stuff except for the Jubilee and Revs.

It was a substantial chunk of change but has reinvigorated my excitement for playing. And that’s been the theme: I’m supposed to build presets for my band material but end up jamming after I drop in 2-3 blocks, so addictive 😍

@Digital Igloo if yall come across a Carol Ann OD2, I wouldn’t be mad about it. I positive you could capture the dynamic nature of that amp extremely well 😎
 
Bit of a left-field question - I need an airline-suitable carry-on bag for the Stadium XL (and ipad, books etc.) as I'm due to be travelling to Vegas from the UK in January for an event; I'd rather take the Stadium instead of the QC, but the QC might be easier to transport.

Does anyone have any suggestions? And no, not the official bag thanks.
 
So the other day, in my frustration at the bugs I was experiencing around stereo balance and block bypass with snapshots, I wiped my unit and factory reset it. Rebuilt presets from scratch. Since then, I haven’t encountered either of those issues. In fact, I enjoyed a completely glitch free experience this weekend.

I believe that my issues were caused by some sort of preset corruption which became baked into the template that I’d created and used to create all of my presets. Support is still researching this, but wanted to share in case others had the same issue.
I had some weirdness after I made a copy of a preset then edited it to swap one amp model for another (both the from and to models were Agoura). I simply deleted the preset and everything has behaved normally since. The original preset that I'd made a copy of, works just fine as far as I can tell. So even though it wasn't something I'd made into a template, there does seem to be something that can go sideways when preset data is copied around.
 
So the other day, in my frustration at the bugs I was experiencing around stereo balance and block bypass with snapshots, I wiped my unit and factory reset it. Rebuilt presets from scratch. Since then, I haven’t encountered either of those issues. In fact, I enjoyed a completely glitch free experience this weekend.

I believe that my issues were caused by some sort of preset corruption which became baked into the template that I’d created and used to create all of my presets. Support is still researching this, but wanted to share in case others had the same issue.

Just wondering - since you’ve started again, was this at 1.2? Maybe that has helped?
 
Just wondering - since you’ve started again, was this at 1.2? Maybe that has helped?
I know you weren't asking me, but in my situation it was a preset created in 1.1, then copied around/edited in 1.2. No idea if the firmware versions themselves contributed though.
 
So the other day, in my frustration at the bugs I was experiencing around stereo balance and block bypass with snapshots, I wiped my unit and factory reset it. Rebuilt presets from scratch. Since then, I haven’t encountered either of those issues. In fact, I enjoyed a completely glitch free experience this weekend.

I believe that my issues were caused by some sort of preset corruption which became baked into the template that I’d created and used to create all of my presets. Support is still researching this, but wanted to share in case others had the same issue.

This was a common problem for me with helix. Once or twice a year, something in my main template would get corrupted and I would need to nuke it and start over. I never said much about it, I’m a power user and push a preset really far with a ton of controllers and crap so I’m not terribly surprised when something goes sideways at some point.

D
 
Back
Top