Digital Igloo (Eric Klein, YGG)

My understanding is that features/models/effects in Stadium that can be handled by the older devices will be offered in updates.

It’s like how the PodGo updates have included a lot of Helix models and effects, but the device itself doesn’t have the processing power to handle certain things like polyphonic pitch shifting or cosmos echo.
Correct. Now what's left to see is how many features/HX models/HX compatible effects are released from now. I'm guessing some, but not many.

And understandably, most development resources will go to Stadium at least until the desktop and mobile apps are finished, and then for a few Stadium models/pending features firmware updates.
 
Hi Digital Igloo and forumers, maybe it was already answered :
Are updates for "old" Helix are planned or it's all over ?
Will there be marked something like "final update" ?
And will updates still be free ?
Thank you.
More updates for Helix/HX are definitely coming, but obviously, our current top priority is delivering on Stadium and Stadium XL promises. We don't know when the last Helix/HX update will be, because conceivably, any cabs or effects made for Stadium could very well still work in the previous platform. We'll need to snap the line eventually but I have no idea when—likely tied to OG Helix/HX sales dropping way off, which probably won't happen for a long while, given that many stores upped their POs last month.

There are currently zero plans to charge for updates. 3rd-party Marketplace content, however, will cost whatever the vendor wants to charge.
 
More updates for Helix/HX are definitely coming, but obviously, our current top priority is delivering on Stadium and Stadium XL promises. We don't know when the last Helix/HX update will be, because conceivably, any cabs or effects made for Stadium could very well still work in the previous platform. We'll need to snap the line eventually but I have no idea when—likely tied to OG Helix/HX sales dropping way off, which probably won't happen for a long while, given that many stores upped their POs last month.

There are currently zero plans to charge for updates. 3rd-party Marketplace content, however, will cost whatever the vendor wants to charge.
Awesome.
Maybe you can’t talk about this, but are you open to 3rd party collaboration on devices that utilize the Nexus port?
 
Last edited:
Hi Digital Igloo,
I'm surprised a geek (like me) didn't ask what are Stadium chipsets/DSPs yet.
We know Helix classic has dual sharc DSP.
Fractal makes no secret about hardware specs :
My question : will Line 6 tell consumers what is inside ?
Like there : https://line6.com/comparison/processors/
Found this old sources :

Thank you

Yes, but one or two competitors likely care more about it than our customers do, so for now we're not divulging anything. No reason to give 'em a few months head start.
 
Don't know if you answered this conclusively elsewhere, but after the Ampeg acquistion, do you guys now have access to their underrated guitar amps like the VH140C and VL1002 (ESPECIALLY the latter)?
 
Maybe loosely with the mid-boost frequency selector. But the one on the VL1002 changed the voicing of the main circuit, not just slam the front end with mid-boost. It also has two "gain" parameters, so in that way it was more like the Cartographer.
 
Maybe loosely with the mid-boost frequency selector. But the one on the VL1002 changed the voicing of the main circuit, not just slam the front end with mid-boost. It also has two "gain" parameters, so in that way it was more like the Cartographer.
that's basically a Lee Jackson Marshall Mod / Metaltronix I think . It had 2 gains as you said that were cascading , and Mid boost / cut at 4 select freq I believe like 250 , 500 , 800 , 1200 and it had 4 6550s in the power amp w an attenuator
 
Don't know if you answered this conclusively elsewhere, but after the Ampeg acquistion, do you guys now have access to their underrated guitar amps like the VH140C and VL1002 (ESPECIALLY the latter)?
Access as in design docs? Or a bunch of old new stock lying around? We have a bunch of stuff in a warehouse somewhere, but the only Ampeg guitar amp that I've seen here in the building is right outside my office—a GVT52.
 
Access as in design docs? Or a bunch of old new stock lying around? We have a bunch of stuff in a warehouse somewhere, but the only Ampeg guitar amp that I've seen here in the building is right outside my office—a GVT52.

Darn. Hope that warehouse has a VL1002 or even a VL502.

Of course, if Sam or Ben have the design docs, he could make a "loosely inspired" Line 6 original based on your existing JCM800 model and simply apply Lee Jackson's abundant mods.
 
Hopefully, @Digital Igloo , this is a broad enough question where you can answer without divulging anything specific for the Stadium launch:

Did you guys have any major lessons learned from how people reacted to Helix presets? I know you have an Axe-FX III in-house....have you guys ever compared factory presets, being that theirs have a much more favorable general consensus?

I mean, obviously, you showed presets with notes and pre-recorded demo clips in the prezzie, so you're doing things differently on an individual basis. I mean more in a general philosophy/strategy sort of way? Like maybe the 256 factory presets weren't enough? Maybe the names were too in-jokey or didn't say enough about the band/artist they were meant to invoke. Maybe there weren't enough song/artist presets? Maybe too many?

Stuff like that.....
 
Also curious if you guys are eyeing functionality similar to Fractal's Channels?

Don't get me wrong: Having some amps with all of the channels switchable in a single model is fantastic and a block saver. The limitation there, however, is that...

  1. Line 6 doesn't always model the cleaner channels of multichannel amps (No Revv Green/Blue, No Diezel VH4 channel 1 or 2, No EVH Green, No Bogner Shiva clean, etc.), so I still need to add another amp block to make comprehensive presets.
  2. The "beefier" amps won't let you do that because they take up too much DSP.
I'm sure the Stadium DSP is plentiful, and I'm happy we can put 12 blocks on a lane as opposed to 8 on OG Helix. Just curious if you're looking to optimize our workflow even further with another way of us getting multiple channels from a single amp block.
 
This might be a little too inside baseball or beyond what you want to divulge publicly at this time, but.....

Given that Helix caught flack for aliasing artifacts and extraneous crackling noise before the 3.1 firmware update, are you taking a different approach to mitigate that beyond just oversampling for the Agoura engine?

Also, in terms of latency reduction, are you using the same minimum-phase kernels Helix uses or are you using the Fractal approach of linear-phase kernels with abundant stop-band rejection?
 
Hopefully, @Digital Igloo , this is a broad enough question where you can answer without divulging anything specific for the Stadium launch:

Did you guys have any major lessons learned from how people reacted to Helix presets? I know you have an Axe-FX III in-house....have you guys ever compared factory presets, being that theirs have a much more favorable general consensus?

I mean, obviously, you showed presets with notes and pre-recorded demo clips in the prezzie, so you're doing things differently on an individual basis. I mean more in a general philosophy/strategy sort of way? Like maybe the 256 factory presets weren't enough? Maybe the names were too in-jokey or didn't say enough about the band/artist they were meant to invoke. Maybe there weren't enough song/artist presets? Maybe too many?

Stuff like that.....
All. Presets. Suck.© Even those from competitors.

But at least now you'll have appropriate context on why they suck, and you'll have a host of new tools to make them suck less to your ears, even as your presets continue to suck to everyone else's ears.
Also curious if you guys are eyeing functionality similar to Fractal's Channels?

Don't get me wrong: Having some amps with all of the channels switchable in a single model is fantastic and a block saver. The limitation there, however, is that...
  1. Line 6 doesn't always model the cleaner channels of multichannel amps (No Revv Green/Blue, No Diezel VH4 channel 1 or 2, No EVH Green, No Bogner Shiva clean, etc.), so I still need to add another amp block to make comprehensive presets.
  2. The "beefier" amps won't let you do that because they take up too much DSP.
I'm sure the Stadium DSP is plentiful, and I'm happy we can put 12 blocks on a lane as opposed to 8 on OG Helix. Just curious if you're looking to optimize our workflow even further with another way of us getting multiple channels from a single amp block.
We can't talk about what we may or may not be working on. I will say, however, that "will you do something this other guy does?" requests don't interest us much. If conversations with users organically result in unique solutions to their problems (e.g. snapshots), that's much cooler, both for us and our customers.
This might be a little too inside baseball or beyond what you want to divulge publicly at this time, but.....

Given that Helix caught flack for aliasing artifacts and extraneous crackling noise before the 3.1 firmware update, are you taking a different approach to mitigate that beyond just oversampling for the Agoura engine?

Also, in terms of latency reduction, are you using the same minimum-phase kernels Helix uses or are you using the Fractal approach of linear-phase kernels with abundant stop-band rejection?
No idea on either of these; sorry. This is more of a question for Ben, Brandon, or Norm.
 
All. Presets. Suck.© Even those from competitors.

But at least now you'll have appropriate context on why they suck, and you'll have a host of new tools to make them suck less to your ears, even as your presets continue to suck to everyone else's ears.

We can't talk about what we may or may not be working on. I will say, however, that "will you do something this other guy does?" requests don't interest us much. If conversations with users organically result in unique solutions to their problems (e.g. snapshots), that's much cooler, both for us and our customers.

No idea on either of these; sorry. This is more of a question for Ben, Brandon, or Norm.

I shouldn't have even mentioned Fractal's channels. The question was really in the last sentence:

[Given that the multiple channels in one blocks applies to just a handful of Agoura amps] Just curious if you're looking to optimize our workflow even further with another way of us getting multiple channels from a single amp block? [on Stadium]

My "organic" and hopefully "unique" solution would be an amp A/B block. So basically, it would load two amps into memory in a single block (kind of like the current Dual Cab block, but with one always bypassed.
 
Does the Stadium have a way to save favorites? What an excellent tool that's given little importance. I miss it so much when I work with other pedalboards.
 
Looking at the 12-minute "Meet Helix Stadium" video again (for the 12,000th time, actually), and I wanted to get clarity on something you said when talking about the new file system:

You start off by taoking about Favorites, then mention existing HX users not having to recreate their presets from scratch.

After another sentence or so, you say "....because you can import them".

Are "Favorites" importable and exportable as well?
 
Back
Top