Line 6 Helix Stadium Talk

[mbenigni]

Well, crap. I tried remapping CC 1 to CC 16 using the MIDI Events Processor. I'm still getting this bizarre behavior.

I also have the Global MIDI Channel set to 1 and the Bypass/Control MIDI Channel set to 2. Are those both incoming and outgoing?

@mbenigni, you do a lot of synth stuff. Do you have any idea what's happening and how I can fix it?

Yeah, I've thought about jumping in a couple of times, but I'm not sure I'm following the problem entirely. No help that I've been out of the Helix/ Stadium loop for so long. There are probably others (e.g. DI) better qualified to answer.

You're trying to use your mod wheel to target the Stadium's onboard synth engine's mod parameter, but that mod parameter is also responsive to the expression pedal - do I have that right? The general idea in situations like this (where devices have overlapping default CC#s) is to get each of your target devices on entirely different channels. But if both devices are subsystems in the Stadium, then it comes down to how configurable each of them are. (For instance, can you change the MIDI channel of the Stadium synth block, or is that a single global setting?)

Sorry, I have more questions than answers:

"I'm still getting this bizarre behavior." Which bizarre behavior? Remapping to CC16 should have - if nothing else - disabled your mod wheel, no?

"I also have the Global MIDI Channel set to 1 and the Bypass/Control MIDI Channel set to 2." I don't actually know what the Bypass/Control MIDI Channel is.

 

[DanRad]

Yeah, I've thought about jumping in a couple of times, but I'm not sure I'm following the problem entirely. No help that I've been out of the Helix/ Stadium loop for so long. There are probably others (e.g. DI) better qualified to answer.

You're trying to use your mod wheel to target the Stadium's onboard synth engine's mod parameter, but that mod parameter is also responsive to the expression pedal - do I have that right? The general idea in situations like this (where devices have overlapping default CC#s) is to get each of your target devices on entirely different channels. But if both devices are subsystems in the Stadium, then it comes down to how configurable each of them are. (For instance, can you change the MIDI channel of the Stadium synth block, or is that a single global setting?)

Sorry, I have more questions than answers:

"I'm still getting this bizarre behavior." Which bizarre behavior? Remapping to CC16 should have - if nothing else - disabled your mod wheel, no?

"I also have the Global MIDI Channel set to 1 and the Bypass/Control MIDI Channel set to 2." I don't actually know what the Bypass/Control MIDI Channel is.

I may just take this to a direct message with Michael — though @Digital Igloo, if you have any thoughts, please jump in!

 

[JiveTurkey]

I would change the midi settings on the GM and HX end vs the controller end.

 

[Digital Igloo]

I may just take this to a direct message with Michael — though @Digital Igloo, if you have any thoughts, please jump in!

Helix/HX responded on one MIDI channel (Ch1 by default) and any MIDI CCs not reserved for global functions could be mapped to control any parameter. But as we added more global MIDI CCs (for example, controlling the 6 knobs below the screen, <PAGE/PAGE>, and Save), we'd eat into available assignable CCs.

So with Stadium, we split them onto separate channels. Global CCs control a wide variety of functions (EXP Pedals, XY controller axes, tap tempo, knobs, Looper functions, etc.) and we plan on adding more in the future. Bypass/Control CCs are assignable by the user so you can quickly map, say, Fuzz on/off, Amp Gain, Reverb Mix, or Delay Feedback to switches or knobs on your controller. The Global CC channel and Bypass/Control channel should always be different.

Stadium also add the ability to control bypass and parameter min/max from notes on your MIDI keyboard/pad controller. Incoming CCs and notes can now be assigned via MIDI learn in two seconds.

 

[DanRad]

I would change the midi settings on the GM and HX end vs the controller end.

But which settings? I changed the Bypass/Control channel on the Helix. I can't find a similar setting to change on the GM-800.

 

[DanRad]

Helix/HX responded on one MIDI channel (Ch1 by default) and any MIDI CCs not reserved for global functions could be mapped to control any parameter. But as we added more global MIDI CCs (for example, controlling the 6 knobs below the screen, <PAGE/PAGE>, and Save), we'd eat into available assignable CCs.

So with Stadium, we split them onto separate channels. Global CCs control a wide variety of functions (EXP Pedals, XY controller axes, tap tempo, knobs, Looper functions, etc.) and we plan on adding more in the future. Bypass/Control CCs are assignable by the user so you can quickly map, say, Fuzz on/off, Amp Gain, Reverb Mix, or Delay Feedback to switches or knobs on your controller. These should always be on separate MIDI channels.

Stadium also add the ability to control bypass and parameter min/max from notes on your MIDI keyboard/pad controller. Incoming CCs and notes can now be assigned via MIDI learn in two seconds.

Any idea why Stadium's EXP 1 would still be responding to a modulation wheel transmitting on Channel 1 when Bypass/Control is set to Channel 2?

 

[DanRad]

Any idea why Stadium's EXP 1 would still be responding to a modulation wheel transmitting on Channel 1 when Bypass/Control is set to Channel 2?

Okay. I'll try not to take up much more time on this thread with this, but changing Global to 2 and Bypass/Control to 1 fixed it. That doesn't seem right, but there it is.

 

[JiveTurkey]

But which settings? I changed the Bypass/Control channel on the Helix. I can't find a similar setting to change on the GM-800.

So in just quickly looking at the app without my GM connected; I see this:

Thing is; this looks like I just assigned CC2 to trigger CTL1 switch which is assigned to the part modulation functionality. So it's still using up an onboard switch? I'd probably find a preset with the mod wheel programmed to one of the switches. I believe there is at least one preset with that mod switch configured? It's been a long time since I have dug into anything other than the 4 gigging presets I use.

 

[mbenigni]

I would change the midi settings on the GM and HX end vs the controller end.

Doh, I completely forgot the GM was part of this scenario.

Based on DanRad's issues, I'd be inclined to put the controller and the GM on a MIDI channel well removed from any/all Stadium channels.

 

[DanRad]

So in just quickly looking at the app without my GM connected; I see this:
View attachment 57791
Thing is; this looks like I just assigned CC2 to trigger CTL1 switch which is assigned to the part modulation functionality. So it's still using up an onboard switch? I'd probably find a preset with the mod wheel programmed to one of the switches. I believe there is at least one preset with that mod switch configured? It's been a long time since I have dug into anything other than the 4 gigging presets I use.

My brain is fried. I'm going to give this a rest for a bit and come back to it.

 

[Digital Igloo]

Any idea why Stadium's EXP 1 would still be responding to a modulation wheel transmitting on Channel 1 when Bypass/Control is set to Channel 2?

Because EXP 1 emulation is a Global CC, which defaults to MIDI Ch1. Set:

• Global Settings > MIDI > Global MIDI Channel to something other than 1, but different than the Bypass/Ctrl MIDI Channel
• Global Settings > MIDI > Bypass/Ctrl MIDI Channel to something other than 1, but different than the Global MIDI Channel

For example, your GM-800 could be Ch1, Stadium Global could be Ch2, and Stadium Bypass/Ctrl could be Ch3.

 

[DanRad]

Because EXP 1 emulation is a Global CC, which defaults to MIDI Ch1. Set:

• Global Settings > MIDI > Global MIDI Channel to something other than 1, but different than the Bypass/Ctrl MIDI Channel
• Global Settings > MIDI > Bypass/Ctrl MIDI Channel to something other than 1, but different than the Global MIDI Channel

For example, your GM-800 could be Ch1, Stadium Global could be Ch2, and Stadium Bypass/Ctrl could be Ch3.

Okay. I did that, and as of this moment, everything appears to be working properly. Thanks, everyone, for their assistance, and apologies for momentarily hijacking this thread.

 

[Mooselake]

I spent a couple hours with the Jujube preset I recently put together. I liked it more than I thought. and think that once I hone the preset a little more, it'll stick in my main rotation. I say that without any consideration of what a "real" Jubilee sounds like, it's simply based on my subjective reaction to playing through it.

 

[Melodioso]

Was it ever confirmed if the "original" Line 6 amps (such as the Badonk and company) will benefit from the Agoura modeling ?

 

[ejecta]

This thread delivers.

 

[molul]

Was it ever confirmed if the "original" Line 6 amps (such as the Badonk and company) will benefit from the Agoura modeling ?

If I understood correctly, they would benefit, but priority is porting the other amps and adding new ones.

 

[EOengineer]

I forgot to add this the other day. The Stadium XL hardware is working FANTASTICALLY as my new reamping chain. I used it for the comparison work sending out send 1 set to instrument level.

OG Helix was a mess of ground loops for me and I never could get what I wanted. This gives me added hope that Proxy may up the game in terms of capture consistency.

 

[banned]

Looks like L6 isn't answering any questions on modeling quality - just answering feature questions related to showcase, matrix etc.

I wonder what's happening over there at HQ.

 

[Mongillo19]

Looks like L6 isn't answering any questions on modeling quality - just answering feature questions related to showcase, matrix etc.

I wonder what's happening over there at HQ.

It's a lose lose for them.

I'm sure they are aware but also, I doubt a few grumblings from us at TGF is going to change their release schedule. I'm sure there are bigger things coming that they have to get to.

 

[Whizzinby]