Line 6 Helix Stadium Talk

[wharf rat]

There are two new presets for the Orange and Matchless. Just scroll down the list.

Guess I should have taken a closer look.

I still think it would have been cool to have a few captures baked into a few presets to truly show off the Proxy capability. Maybe I’m wrong tho.

Did we get any factory presets for the amps added in 1.2? I gotta spend more time with this thing lol

 

[dws2384]

Ouch. That's quite a lot of CPU usage then. I've seen QC patches using plenty of captures - but in case Proxy captures need the same amount as Agoura amps, any such patches would be impossible to create on the Stadium. Quite a pity as I'd personally capture quite some dirt boxes.

Anyhow, another question: What controls do the capture blocks come up with? And what are the tweaking options?

QC V2 captures max out at about 2-3 per path as well. V1 you can do way more

 

[brianwahl]

Absolutely, while I only tried the A-30/6 last night, I'll definitely be purchasing the ’64 for comparison too. Also looking forward to the modded plexi and anything ÷13 in the future too!

Awesome - thank you! The Modded 1959 Super Lead is on my short list. That pack has 85 captures/clones in it, so it'll be a bear, ha. But I LOVE that amp, so I'll be doing it soon. I captured it through a bunch of different cabinets, including a 2x12 matchless. That one is surprisingly cool with the Marshall - gives it a bit more midrange chime. Works great for the lower gain settings. Probably not my pick for the more mid/higher gain settings, but it's a fun option to have.

 

[I S]

When there's a new update that also updates and improves some backend/amp stuff, is there a way to update my patches to the latest underpinnings without removing the block and adding it again? The way it worked on Helix and I assume also now on Stadium makes perfect sense, unless I prefer the latest and greatest, unfazed by possible sound changes.

 

[brianwahl]

There are two new presets for the Orange and Matchless. Just scroll down the list.

My buddy Bradford made the stock preset with the DC30. Bradford and I dialed in the focus zones and the linked cab settings for the C30 amp model, too. The top left "Ch2 EOB is sort of my go-to setting for a pedal platform type of preset.

We did a lot of A/B'ing the amp model with our actual amps (Bradford has a new-ish C30, and I have a mid-90's one). The Agoura model is pretty spot on - we love it.

 

[Digital Igloo]

@Digital Igloo of course I know there are still many things to add to Stadium with way more priority, but is there any hope for a insta-mute Tuner mode someday (like this one I suggested a few months ago: https://thegearforum.com/threads/helix-feature-request-alternate-tap-tuner-behavior.8959/ )?

A solution for what you're asking for was designed back in September of 2017, when Stadium's first TRD was published. A metric ton of features have been fully defined, and Stadium's architecture has been built to accommodate all of it, but certain things have dependencies where it makes the most sense to be a part of a certain effort tied to a bigger story or group of features.

Implementation isn't exactly how you asked for it, but it should accommodate it in a similar fashion.

The Orange and Matchless amps sound fantastic. The clones I have managed to find sound great, but I find it strange and frustrating that there are no captures to try with the firmware update.

Since Proxy is still in its infancy, we didn't want to lock ourselves into a bunch of Factory Clones before it was at a certain level. Unfortunately, getting to that level requires analyzing more data than we've been able to collect. Now that the masses are using Proxy, we'll be able to really dig in to the data and ensure we're improving things in the right direction.

If doing a Proxy capture of a fuzz pedal, is there a way of telling Stadium that you’d like a low input impedance for the capture you’ve made so it does the right thing with your guitar volume?

Couldn't you just set the Input block's In-Z parameter manually? Or is the ask that you set the impedance once, and the preset automatically adjusts the input circuit accordingly when adding that clone as the first enabled block?

Is this the one and only chance you have to add/edit the metadata for the proxy captures?
(yes I read the manual but I can't see any other point where you can edit it)

I'm trying my best not to have to write out a novel on the touch screen. You can't do captures via the app it has to be on the stadium unit direct. When you initiate the proxy process it locks out the Desktop software and this is where you edit things. But is there a way to edit these once they're completely done? I feel like you really need a keyboard/mouse to do this when you're dealing with more than a couple captures.

Fully editable metadata is part of the big thing we're working on.

 

[MirrorProfiles]

Since Proxy is still in its infancy, we didn't want to lock ourselves into a bunch of Factory Clones before it was at a certain level. Unfortunately, getting to that level requires analyzing more data than we've been able to collect. Now that the masses are using Proxy, we'll be able to really dig in to the data and ensure we're improving things in the right direction.

With this in mind, can we assume that Line 6 is hanging onto all of the training data when users make models? Or is it just information from the training that is for analysis? I actually think this is a smart thing to do, in order to keep refining the accuracy. I also think it would be awesome if it's possible for users to have access to their own files.

I'd love to see companies taking advantage of the information side of captures more too - say when users are adding information about their amp, it could save other users having to manually enter a whole raft of information (say like making an eBay listing where it tries to help you out as much as possible to get information in). If the boring bits are effortlessly easy, I think users are more likely to manually add the interesting quirks about their amps - maybe they changed the valves around, or had something tweaked in the preamp. If Line 6 has a big pool of captures with great metadata associated with it, I think it gives them a LOT more to work with as far as R&D goes.

 

[Sascha Franck]

QC V2 captures max out at about 2-3 per path as well. V1 you can do way more

Ah ok, didn't know they were using substantially more CPU juice. With Tonex V2, CPU usage has stayed as low as it was with V1.

 

[dean701]

With this in mind, can we assume that Line 6 is hanging onto all of the training data when users make models? Or is it just information from the training that is for analysis? I actually think this is a smart thing to do, in order to keep refining the accuracy. I also think it would be awesome if it's possible for users to have access to their own files.

I'd love to see companies taking advantage of the information side of captures more too - say when users are adding information about their amp, it could save other users having to manually enter a whole raft of information (say like making an eBay listing where it tries to help you out as much as possible to get information in). If the boring bits are effortlessly easy, I think users are more likely to manually add the interesting quirks about their amps - maybe they changed the valves around, or had something tweaked in the preamp. If Line 6 has a big pool of captures with great metadata associated with it, I think it gives them a LOT more to work with as far as R&D goes.

I think that is what DI implied here. They will have all of the original recorded files plus the resulting clones and they can endlessly tweak for future improvements.

Post in thread 'Line 6 Helix Stadium Talk'

Yesterday at 1:34 PM

1.3.1 hotfix coming soon that improves a couple sonic quibbles in Proxy. Additional improvements coming in 1.4. Honestly, we could've kept tweaking things forever, but at a certain point, we need the masses to start cloning stuff so we can collect sufficient data to make sure we improve things the right way.

• Digital Igloo

• 
• 
• 

 

[molul]

Implementation isn't exactly how you asked for it, but it should accommodate it in a similar fashion

Cool. Looking forward to seeing how it works :)