Line 6 Helix Stadium Talk

Well it doesn’t seem like Helix Stadium is for you at the moment. You have made your feature request so maybe it’s time to talk about your dream solution elsewhere. Unless you are just looking to argue with people…

I'll let you in on something (you could possibly still look it up at TOP): When L6 introduced snapshots, I was one of the first to request switchable snapshot bypass - without owning a Floor. They introduced it a while later and a little while after that I bought a unit.

Just press the save button. It’s fine.

I just want to adjust global parameters as I would on an analog amp. No analog amp requires me to save anything just because I've touched the treble pot. This is one of the ideas behind global blocks anyway.
Besides, for the big GT-1000 setup, I have quite some global block parameters mapped to MIDI so I can control them via Touch OSC from a tablet. No way to save that way. I actually plan on purchasing a small MIDI knob box. Would be just the same issue. Being forced to save would render these approaches void as I'd still have to bow down.

I don’t get it, but Sascha’s ideal workflow sounds like way too many variables.

How so?
 
I don't want my hardware nor software making arbitrary save decisions for me, where I overwrite stuff without meaning to.

There's no "arbitrary" save decisions. It's just an autosave feature, which can as well be found in units from Zoom or the Tonex One. No idea what would be "arbitrary".
It could possibly be an option to have autosave on or off. Just as on the Zoom units.
 
Howdy!

The past 18-24 months have been, let's say... arduous... and when my ever-patient wife repeatedly asked when we'd finally go on vacation, I responded with "we just gotta get through NAMM, babe." Our friends in Spotlights are finishing up their European tour with Helix Stadium and Showcase running guitar amps (through quilter power amp and Marshall 4x12) and effects, vocal effects, tracks/intros/seques, automation, and a click for the drummer. (Sarah's using an LT for bass duties too.) We flew out to see their London, Paris, and Barcelona shows. They kicked ass.

Got back a week ago and all the post-NAMM emails, meetings, and Proxy madness made me avoid social media for a bit longer. So I'm not back back just yet, but at least I got through page 214 of this thread.

No, and this is something that plagues every UI with a list and increment/decrement engagements—If a list isn't visible, up means next. If a list is visible, down means next. Left/right, up/down, there's no free lunch here. If if bugs someone, Global Settings > Switches/Pedals > Swap Up/Down lets you change it.

No free lunch here either, as by definition, "active" snapshots autopopulate the state of the block when it's added. Still, you can do one of three things:
  • Bypass the block, copy it, and then paste it in place
  • Save the block as a favorite while bypassed
  • From a new preset, before selecting any other snapshots, bypass the block

There was indeed an elusive (now fixed, will be in 1.3) speaker impedance curve bug that affects approximately 13% of amp and cab combinations (but no default amp+cab combinations). From what I've been told, it shouldn't bias the high end more than 1 (maybe 1.5?) dB or so up or down. Is this what people are experiencing? Not sure, but the team sure isn't sitting on their hands, shrugging.

And as others have mentioned, amp models currently load the SIC of their default cab if an unlinked cab or IR is used.

I have songs with POD Farm that I cannot replace with any other plugin because of how accustomed I am to that particular sound. Totally get it.

Interestingly enough, one company purposely restricts the range of tonestack knobs to avoid "wrong" settings that might hurt a newbie's sensibilities. Line 6 certainly doesn't, at least on purpose. Maybe it's the SIC thing? I kindly request you check beta in a week or so.

A/D/A, oversampling, clocking, power supply, overall headroom, circuit layout... You'd think they should be minuscule differences, but collectively, it all adds up.

Wait, didn't I address this very thing with you in the past? Again, all the new effects developed for Helix Stadium have already been released for Helix/HX. Anyone insisting Stadium gets effects that Helix/HX doesn't is gatekeeping.
Glad to see that you are sort of back
Hope you got some rest and relaxation
So it looks like 1.3 is just around the corner at least for beta

I think you had mentioned 3 new Agoura amps will be in this one ?
Are you allowed to comment will these be new models or some existing amps “Agorafied”

Ps please tell Timbuck stadium is not a stop gap to the next flagship
 
Hi @Digital Igloo . I've experienced a small problem that could probably be fixed easily enough. I often have my drive pedals and boosts on path 1, and my amp(s) on path 2. Sometimes when using high output pickups like a HFS or Invader, path 1's output starts to clip. There is a level control on the output, but it seems to be after the threshold, not before. This means that I need to put a -6dB at the end of path 1, and a +6dB at the start of path 2 to avoid the clipping.

Could there be a better way? If output's level was before the threshold and input 2 had a level control, that would simplify things, but an invisible or automatic correction would be better. Is there anything that could be done about this? Thanks.
 
Hi @Digital Igloo . I've experienced a small problem that could probably be fixed easily enough. I often have my drive pedals and boosts on path 1, and my amp(s) on path 2. Sometimes when using high output pickups like a HFS or Invader, path 1's output starts to clip. There is a level control on the output, but it seems to be after the threshold, not before. This means that I need to put a -6dB at the end of path 1, and a +6dB at the start of path 2 to avoid the clipping.

Could there be a better way? If output's level was before the threshold and input 2 had a level control, that would simplify things, but an invisible or automatic correction would be better. Is there anything that could be done about this? Thanks.
Stadium is floating point between paths so there's never any saturation between them. If you're not actually hearing clipping, it's likely safe to omit those two Gain blocks.

I've requested that we completely remove clipping indication from Output > Path 2A, Path 2B and Path 2A+2B blocks.
 
Back
Top