Digital_Igloo

Sorry, guys. It's like herding cats around here today, for obvious reasons. POD HD 2.6 Global EQ—Three fully parametric bands plus low and high cut filters, available from an additional Setup menu page; we had to do quite a bit of clever optimization to fit Global EQ, and you might see a tiny bit of extra DSP for other blocks (a few percent perhaps) Metal Pack ($49)—Peavey 5150 (block logo), Bogner Shiva, Remastered JCM800 (model 2204), plus favorite POD Farm models Insane, Big Bottom, Varaic'ed Plexi, Purge, Aggro, Smash, and Octone Vintage Pack ($49)—Orange OR-80, Roland JC-120, Fender Champ (Tweed), VOX AC30 Fawn Normal, VOX AC30 Fawn Bright, JC-120 cab, Fender Champ cab, plus POD Farm Acoustic Bass Pack ($29)—Ampeg SVT Normal, Ampeg SVT Bright, Gallien-Kruger 800RB, SVT 8x10 cab, SVT 410 HLF cab Fully Loaded ($99)—All three packs We're hoping to have 2.6 available by the end of March for HD500X and HD Pro X, with support for HD500, HD Pro, and HD (Bean) shortly thereafter.

Yes, they're the same. Firehawk will land at US MAP $449. It's decidedly not a direct replacement for HD500X, although we expect many who don't require MIDI, L6 LINK, and dual signal chains (sorry!) may prefer it. POD HD will continue to be our ~$500 flagship modeler for the foreseeable future.

Hai guyz! What's going on in this thread? :D

I honestly have no idea what that's all about. :huh: Anything out in March would definitely show at NAMM.

How would Variax connect to AMPLIFi? There's no VDI. :huh:

Dynamic DSP is here to stay, at least in Line 6 flagships. There will always be a point where you can select certain models and run out of DSP. Conversely, there will always be a point where you can select certain models and run out of block locations. This is just what happens when one block can take up 30-40x the DSP of another; we trust the user to be smart about allocation. Obviously, we want you to get a "more than acceptable" number of blocks before running into the wall. Adding more block locations is tricky, as it'd feel like you're running out of DSP sooner. The GUI doesn't really support it anyway, unless we had a scrolling pedalboard view, which would make everything really clunky and make me a sad panda. Moving the blocks closer together doesn't work either, but I'd have to show you the GUI mockup graphs to prove it. Eight effects blocks is kinda the magic number for POD HD. But for future products? We hear you loud and clear. :)

As a bonus, AMPLIFi will automatically download the right tone when your own backing track starts. :)

If you're only ever recording mono, sure you could use only the left output. There's no problem recording POD HD into a Focusrite interface. I record my POD HD Pro into an Apogee Symphony I/O. If you wanted to use POD's USB audio interface, there shouldn't be any interference with POD HD Edit. It's designed to work that way.

I put a Z.Vex Fuzz Factory, Wooly Mammoth, and/or Klon Centaur in front of my HD Pro all the time. Because we haven't modeled them (yet). Also like to put a DL4 before the HD Pro, only because it's really easy to grab and tweak, especially for weird warbly feedback nonsense.

So if you're talking about a tethered mobile solution (tablet or phone via physical USB cable), then yeah, that's doable... except with iPhone. :( We did some research a while back and asked "If you had to choose one, would you prefer a phone/tablet or Mac/PC editor for the next flagship POD?" Every single person said "Oh, man, I'd really love both, but if I HAD to choose, Mac/PC hands down." Ideally, the user wouldn't have to choose. Of course the ultimate goal is to create a UI that's so fast and easy to use, there'd be no point in dragging out a laptop, phone, or tablet at the venue.

Obviously, the biggest hurdle is POD HD's lack of Bluetooth hardware. Collectively, the size of a POD HD preset is many times larger than an AMPLIFi preset (deep amp/cab/Variax/L6 LINK parameters, up to 52 controller assignments, MIDI mapping), not to mention there are 512 of 'em. Waiting 10-20 minutes just to sync preset data is a non-starter. This is a limitation of current Bluetooth technology. That, and since POD HD is considered our flagship performance and studio solution, it makes sense to pursue Mac/PC integration over mobile. POD and AMPLIFi are designed for two very different environments, but it's nice to know that people are intrigued by the AMPLIFi experience.

Man, it's sure doing a lousy job of that, then! :D I kid, I kid

Yes, there are new devices coming at NAMM, and then more later throughout 2015.

Whoa, be careful. I'd like to stick around here. Not what I said; we were talking about realizing IdeaScale submissions, which could imply new products or an update to any existing product. Still, you're right—POD HD is not EOLed.

Have you tried it with a StageSource L2t or L2m? Is it important that the FRFR's form factor be more guitar amp-esque?

What's a 5150?

I'm on it... :D

Who's sensitive? I'm not the guy who doesn't understand dynamic DSP allocation. I'm the guy who understands actual AMPLIFi sales reports.

AMPLIFi's been really successful for us. The SKU with the smallest potential user base—AMPLIFi TT—sold out in less than a week. Lots of people understand what it's meant to accomplish. A few don't. No biggie.

Sigh... For the umpteenth time, HD500X was released specifically because certain parts were EOLed and we couldn't continue to make (the incredibly successful) HD500 as is. It actually had more DSP horsepower than other products in its class, but because we give you the ability to add whatever you want wherever you want until you run out of DSP (instead of fixing the signal path with one amp, one delay, one reverb, etc.), some people misconstrue this as underpowered. And our strategy regarding that isn't going to change. We're not going to cripple flexibility in our flagships just because some people can't seem to understand the advantages (and gotchas) of dynamic DSP allocation.

Fair enough. I assume TheRealZap's post was a tongue-in-cheek reaction to another member who also used "FACT!", when indeed, the real facts are unknown to all but a handful of people on this forum. We're all adults; if ten years trolling Harmony Central's taught me anything, it's to never be offended by what others say on teh interwebz. :) One could make the argument that Line 6ers should steer clear of these parts until [XXX] number of IdeaScale-culled features have been implemented to everyone's satisfaction, but it's a pretty nebulous metric. Line 6 works from a veeerrry long product roadmap that's constantly evolving. Some IdeaScale submissions may not make it into products for several years. A bunch of big ones may, uh, show up later next year. Several may show up at, oh I don't know, let's say... Winter NAMM 2015 on January 22. Dozens have already found their way into products, but one may not care, because it either wasn't their particular submission, or it wasn't for their particular product. To be honest, there aren't an overwhelming number of new IdeaScale submissions that hadn't already been discussed within our own ranks. Most of the time, IdeaScale is a tool for validation and prioritization for what we've already considered (or started developing), but it really shines with bugnuts ideas from left field, which may spawn other ideas that might actually fly. That's what I'd personally like to see more of. Except for the cupholder-in-the-amp idea. Yeah, we're not going to do that.

Releasing information to appease forum members—at the cost of forum banishment, losing one's job, or breaking trade law—is ludicrous.

Yep—the firmware has this functionality, but unfortunately, one can't access that parameter until the app is updated, which shouldn't be too much longer...

Thanks, fflbrgst. Bump—anyone else?

First time I've seen this—honestly have no idea what's going on. :huh: I'm fairly sure it's not a NAMM thing, as there are zero plans to EOL POD HD500X or HD Pro X anytime soon.