With a few months between Stadium XL and non-XL Stadium releases, will some of these features perhaps land in a fw update right around non-XL model's release?There's a bunch of other stuff that won't be ready on day one either, like Expand D10, user-customizable Focus zones, user-recordable preset clips, Pedal Edit Mode, preset spillover, etc.
I wondered about this, but it makes sense from a priority perspective when you’ve got the touch screen and ease of editing on unit.The first Stadium editor might be more of a preset/IR/Showcase track librarian to start
Looks like the Stadium is intended to control the entire stadium.
These are like that misc port on the Nintendo 64 where we dreamed it was a docking station for some yet-to-be-released super gaming system or something.Why are we controlling drum trigger inputs again?
Now the drummer can control your presents and the entire stage light show with a brutal blast beat solo, all going through the control center.Why are we controlling drum trigger inputs again?
There’s stuff in the Stomp that I haven’t even thought to look at. I say let them cook.Why are we controlling drum trigger inputs again?
God I can't wait.Maybe one day in 2035 when we're all too old (or dead)
If that is true then guitarist could essentially do the the same step up for a solo have the lights change Colors and activate the fog machines triggersNow the drummer can control your presents and the entire stage light show with a brutal blast beat solo, all going through the control center.
@JiveTurkey Line6 didn't say anything about guitar synth noises, the processing power is there though.
Maybe one day in 2035 when we're all too old (or dead) to play.![]()
This is pretty much where I'll be in 10 years
Hi Karl!I wondered about this, but it makes sense from a priority perspective when you’ve got the touch screen and ease of editing on unit.
Why are we controlling drum trigger inputs again?
It’s actually so we can control everyone else’s levels to turn them down when the solo comes.Why are we controlling drum trigger inputs again?
Nearly every feature we discussed during the keynote (and many dozens—or hundreds?—more we didn't mention) were defined back in September 2017. So the architecture and infrastructure (hardware, firmware, software, web services) have been built with 2035 (or whenever) in mind. But each feature is actually made up of many smaller efforts, and most of those efforts have dependencies on tangential features and processes. "Oh man, this feature is so close, but we need this other thing finished first to complete it so I guess it can't be 100% at launch" is a common sentiment here, even if no customer notices what's missing. In other words, if a user says "Oh man, I wish [new feature] also did this!" it could be we already have "this" waiting in the wings.With a few months between Stadium XL and non-XL Stadium releases, will some of these features perhaps land in a fw update right around non-XL model's release?
Are we talking about "these are on our roadmap but nobody is working on them yet" vs "these features are well underway but won't be 100% complete/tested by the time the XL releases"?
Out of these, the one I'm most interested in would be the user customizable Focus zones. That seems like such a powerful feature, basically "presets within a block".
Why not? There's a tiny bit of (affordable for a flagship) circuitry to accommodate it, but it's not like they eat up precious I/O real estate—you simply choose whether Control A, B, C, and/or D is an EXP Pedal In, FS In, Trigger/Contact Mic In, or Amp Control out.Why are we controlling drum trigger inputs again?
and many dozens—or hundreds?—more we didn't mention
I guess I didn't realize triggers use 1/4" inputs like the rest? Interested to see what happens then!Nearly every feature we discussed during the keynote (and many dozens—or hundreds?—more we didn't mention) were defined back in September 2017. So the architecture and infrastructure (hardware, firmware, software, web services) have been built with 2035 (or whenever) in mind. But each feature is actually made up of many smaller efforts, and most of those efforts have dependencies on tangential features and processes. "Oh man, this feature is so close, but we need this other thing finished first to complete it so I guess it can't be 100% at launch" is a common sentiment here, even if no customer notices what's missing. In other words, if a user says "Oh man, I wish [new feature] also did this!" it could be we already have "this" waiting in the wings.
So thankfully, nothing anyone's seen so far is a massive lift (except for maybe Proxy, because of where we want to take it); it's just brute-force engineer hours to lock things in, tighten it all up, and test the crap out of it. At no point did we show anything where we don't have a solid map on how to get there in a timely fashion, although "timely fashion" means different things to different people; for example, how many people are pissed we didn't also announce stomp, rack/remote, and plugin SKUs at the same time, despite the fact that almost no one EVER does this? (Floor and Rack in 2015 notwithstanding.)
Yes, I suspect we'll see quite a bit of additional stuff by, I dunno, NAMM? And certainly updates before then. Now I just gotta convince Simon and Nick to budget for a NAMM booth party again.
Why not? There's a tiny bit of (affordable for a flagship) circuitry to accommodate it, but it's not like they eat up precious I/O real estate—you simply choose whether Control A, B, C, and/or D is an EXP Pedal In, FS In, Trigger/Contact Mic In, or Amp Control out.
![]()
This is like waiting for your girlfriend to come back after spending a semester abroad.