Line 6 Helix Stadium

What part of Proxy would you need to remove in order to have more space? I mean, just don't download profiles and you should have all space available.
I admit I'm being unrealistic. I just don't want to see it at all, and I was using storage as an excuse to argue for it being removable. I understand the irrationality contained in my statement.
 
I think now that they've put in the plumbing for blocks to interact with each other (i.e., impedance characteristics/curves between amps and speakers) it seems plausible to mix preamps and power amps, though I imagine it might be a little tricky to find pairs that match well out of the box. Maybe it's more straightforward than I think though. It's been a consistent thing on wish lists and I'm sure they'll eventually implement it if possible assuming demand remains.
I think one of the Line 6 originals is a mix with an Orange power amp. Maybe the Ventoux?
 
I would like to see more consistency in the folder structure for models. Currently, as I understood, some newer HX models would be in the legacy folder, while others older ones would be in the main folder. It would be better to have a dedicated folder, such as an "Agoura Module" folder or a general "HX Models" folder to not mix apples with oranges. :sneaky:

Or am I seeing to much through the eyes of an IT guy? :unsure::geek::p
Each model category is one big list with subcategory skip buttons in the sidebar. Tap an empty block location, tap the Amp shortcut button at the bottom of the screen, tap LEGACY GUITAR in the sidebar, and the Amp list quickly scrolls down to the Legacy guitar amps. Just timed it—1.5 seconds.

Or like in Helix, you can turn the Lower Knob to scroll through all items (or press-turn to skip subcategories) without opening the model list at all.
I don't think storage space will be an issue in the foreseeable future for the HXS 😄 The thing even has a microSD slot for cards up to 32GB.
Stadium and Stadium XL include a 32GB card behind a security panel. Can't remember what sizes we've tested, but it wouldn't surprise me if 1TB or larger microSD cards worked just fine. But as of 1.0, the only data the card stores are Showcase tracks and full state backups; it'll definitely do more in the future.
 
Each model category is one big list with subcategory skip buttons in the sidebar. Tap an empty block location, tap the Amp shortcut button at the bottom of the screen, tap LEGACY GUITAR in the sidebar, and the Amp list quickly scrolls down to the Legacy guitar amps. Just timed it—1.5 seconds.

Or like in Helix, you can turn the Lower Knob to scroll through all items (or press-turn to skip subcategories) without opening the model list at all.

Stadium and Stadium XL include a 32GB card behind a security panel. Can't remember what sizes we've tested, but it wouldn't surprise me if 1TB or larger microSD cards worked just fine. But as of 1.0, the only data the card stores are Showcase tracks and full state backups; it'll definitely do more in the future.

Are y'all eyeing a specific limit for Proxy captures yet? Like 128 slots or 512 or whatever have you? Or is it too early for that decision to have been made yet.
 
Why would you see it if you didn't use it? Genuine question.
I might not. But depending on how the UX is designed, it could be seen.

And I would always think "those are resources that could be going toward modeling," and it would annoy me. I understand my viewpoint is a bit extreme (on the "I don't even want to see it" thing), but not completely baseless (on the resource thing).
 
I might not. But depending on how the UX is designed, it could be seen.

And I would always think "those are resources that could be going toward modeling," and it would annoy me. I understand my viewpoint is a bit extreme (on the "I don't even want to see it" thing), but not completely baseless (on the resource thing).

Using that line of reasoning, pretty much any capacity of the device that you don't use would fall under the same disqualifier. There is no one who uses 100% of the outputs, 100% of the inputs, 100% of the models, and 100% of the knobs and switches throughout the life of the device.
 
Using that line of reasoning, pretty much any capacity of the device that you don't use would fall under the same disqualifier. There is no one who uses 100% of the outputs, 100% of the inputs, 100% of the models, and 100% of the knobs and switches throughout the life of the device.
I have repeatedly asserted my awareness of the overboard nature of the opinion, though I will say that maintaining a fully parallel core amp sound functionality is more significant than your examples. And I know that nobody at Line6 is ever going to listen to me. I'm just a minority opinion shouting into the void. I like modeling, and I like it being the full resource focus of the devices that I use. If my device has less effect or amp models than it could have had because capture was added, maintained, and enhanced, that's a net loss for me. I completely understand why many people think that's overboard. But it's my preference.

Maybe at some point, I'll end up with a future Axe IV and nothing else.
 
I might not. But depending on how the UX is designed, it could be seen.

And I would always think "those are resources that could be going toward modeling," and it would annoy me. I understand my viewpoint is a bit extreme (on the "I don't even want to see it" thing), but not completely baseless (on the resource thing).

I think it is baseless, in terms of resources.
Why you ask?

1) In terms of dsp/cpu resources: don't use and I guess you don't need to think about it wasting any resources.
2) In terms of Line 6 dev team's resources: I'm sure they are capable of balancing two different modelling options just fine. Let them handle that one and then (see first point).

And

3) You've repeatedly said this since the product launch, and I think at this point we've heard you.
We know you don't like captures. Other people do, so let them have their cake and eat it and stop being a party pooper.
 
I have repeatedly asserted my awareness of the overboard nature of the opinion, though I will say that maintaining a fully parallel core amp sound functionality is more significant than your examples. And I know that nobody at Line6 is ever going to listen to me. I'm just a minority opinion shouting into the void. I like modeling, and I like it being the full resource focus of the devices that I use. If my device has less effect or amp models than it could have had because capture was added, maintained, and enhanced, that's a net loss for me. I completely understand why many people think that's overboard. But it's my preference.

Maybe at some point, I'll end up with a future Axe IV and nothing else.

I think you are only hurting yourself by being so religiously dismissive of a technology that is still evolving. I also think you may be setting yourself up for disappointment. If Cliff gives in, there may not be any no-capture modeling devices left in a few years.
 
I might not. But depending on how the UX is designed, it could be seen.

And I would always think "those are resources that could be going toward modeling," and it would annoy me. I understand my viewpoint is a bit extreme (on the "I don't even want to see it" thing), but not completely baseless (on the resource thing).

No I feel the same. I have no desire for Proxy. However - some of the current OD models aren't to the same standard as the amp models I feel - eg TS. That's where Proxy may come in handy.
 
I am not a fan of profiling/capturing for many reasons, but if we get it on the Helix platform I might warm up to it simply because it provides a quick way of getting sounds from other platforms into the Helix. I can imagine liking an amp and/or cab sound on one unit, capturing it, and now having use of it in the Helix without a lot of tweaking. Even so, my use for it would probably be limited. But I won't begrudge others wanting it.
 
See, here is just a differing opinion. I care greatly about the capture capability. So it makes a huge difference to me. That would give a make or break for me on the stadium.
 
I think it is baseless, in terms of resources.
Why you ask?

1) In terms of dsp/cpu resources: don't use and I guess you don't need to think about it wasting any resources.
2) In terms of Line 6 dev team's resources: I'm sure they are capable of balancing two different modelling options just fine. Let them handle that one and then (see first point).
They will handle it however they like. My saying something will have no bearing on that. But those resources are finite.

And

3) You've repeatedly said this since the product launch, and I think at this point we've heard you.
We know you don't like captures. Other people do, so let them have their cake and eat it and stop being a party pooper.
No, I'll just keep saying what I think, just like you do.
 
I think you are only hurting yourself by being so religiously dismissive of a technology that is still evolving. I also think you may be setting yourself up for disappointment. If Cliff gives in, there may not be any no-capture modeling devices left in a few years.
That's ok. I'm old enough that I can find another solution for as long as I'm playing, or just stick with what I have, which already sounds great.
 
No I feel the same. I have no desire for Proxy. However - some of the current OD models aren't to the same standard as the amp models I feel - eg TS. That's where Proxy may come in handy.
That's certainly a legitimate preference to have. I'd just put a pedal in front of the unit, but that's my choice.
 
Back
Top