silverhead

Let's remember - the HD500X was not intended to lure Hd500 owners to upgrade. It's essentially the same product, manufactured with a new and better chip because the old one was no longer available. It also has improved footswitches, but is the same cost as the Hd500. A more expensive chip was not a profitable option.

Wow. Tempest in a tea pot. Glad I'm not a web designer. When did making a link mistake become a capital offence worthy of the death penalty? Yes - it's confusing and probably a mistake. In the time it took to write this post you could have done something constructive about it, like inform Line 6 of their link error. Why not do it now?

The HD500 (and HD Pro and HD Desktop) will all receive the v2.6 update soon. Line 6 released the X-models update first. In all cases the v2.6 firmware supports the new Model Packs, purchased separately.

... and here is the response: The HD FX that are in Firehawk are exactly the same as the POD HD series and the M Series. In both the case of amps and effects, we added "HD" to the names to distinguish them from the XT, but we didn't bother adding an "HD" if the name was already different. IE - "Heavy Distortion" and "Killer Z" are both Boss Metal Zone models, and we didn't add HD to the name of the HD version since the name was distinct from the classic model. Again, thanks to phil_m for noticing my earlier misinformation.

Those folks likely won't want to use the global EQ. It would undo their hours on end of tweaking to get the tone to sound the way it does with the heavily EQed speaker mode. Add the Global EQ to that and it's back to tweaking.

The thing about users posting videos or sound clips is that there are so many other variables involved that it's really not a good indication of how the whatever-it-is will sound when played by you in your environment. I think Customtone is a good illustration of that. I'm sure everybody who posts a tone that claims to sound like so-and-so really believes it does. And it probably does - with their guitar, their monitor/amp, their fingers, their room, their outboard equipment, .......etc. But when I download it and listen to it on my equipment, well... not so much. Of course, some tone-makers and videographers create some really good stuff. But unless you know the source I wouldn't rely on the demo. And that is especially true if you don't think the demo sounds good. I think you would be doing yourself a disservice to listen to a few poorly prepared videos or demos and conclude that the product isn't good.

I don't think the looper uses any noticeable DSP. It uses memory. It's just a recorder that taps into the DSP signal chain and writes the signal to memory, and then feeds it back into the DSP chain on playback. It's a signal routing feature, not a signal processing feature.

But would you want to? The speaker mode settings are essentially different EQs. So after having gone to the trouble of fine tuning your Pod HD global EQ do you want to have it further affected by speaker mode? I don't know - just asking.

The easiest way to avoid accidentally triggering the Looper is to wrap a rubber band around the base of the footswitch preventing it from engaging.

Funny - just the opposite is the case with the M20d mixer. The 31-band graphic equalizer (global) is only available using L6 LINK. It is not available on the XLR outputs. We can all have equal opportunity to complain about what's missing. M20d owners can complain about not having the global EQ when they are NOT using L6 LINK, and Pod HD owners can complain about not having it when they ARE. But global EQ on the Pod HDs is something that has been requested by many users for a long time, and now it's here. Credit where credit is due. And it's available for Stagesource speaker owners if you connect the Pod HD to the speaker via the analog outputs/inputs. All you lose is the ability to store the speaker mode in the HD preset - which is irrelevant if you want to use the Pod HD global EQ because in that case you don't want to change the speaker mode (and associated EQ) in any case.

Yes, and no.

I've asked Line 6 to clarify this for us and haven't heard back yet. However, after reviewing the information I have already been provided with I believe I may have misunderstood. I now think you are correct, phil_m. The HD FX in Firehawk are the same m-series FX in the Pod HD, just renamed to distinguish them from the Pod Farm FX. While this information is not yet conclusive I wanted to correct any misinformation I may have provided as quickly as possible. I will wait for the official response from Line 6 and update you here when it comes. Meantime I think everyone should assume that the Firehawk HD FX are the same ones in the Pod HD, not an improvement. Sorry for any misinformation, and thanks to phil_m for catching it.

You maybe correct. I'll have to double check that.......

I have the same issue with cell phones. Try to get one without an integrated camera or all the other bells & whistles. I just want to make phone calls.

That's correct. Global EQ and support for Model Packs. No new FX, but new amps in Model Packs available for purchase.

The Pod HD has an Input-Z parameter that applies only to the Guitar input, not the VDI input. I'm not sure it makes that much difference, but technically it is the only DSP difference between the two input signals other than the obvious D/A and A/D conversions. I expect the real difference is due to the length and quality of the guitar cable you are using. These factors are different for every user and I don't think they are modelled at all in the VDI DSP.

Yes, any HD FX in the Firehawk are improvements over the m-series FX in the Pod HD units.

Those who are not getting sound should check the Setup menus for the Inputs setting. it can be Global or Preset. I believe the default is Preset, but if you had previously changed it to Global you will need to change it back again.

No need for you to apologize. Your thread was hijacked by someone who suddenly wanted to argue about dual amps. If there's anyone who should apologize, well, ......

I don't think we need new terminology like Scenes within a Patch. I think all that's required is to implement delay trails during preset changes. Once that's done the current architecture and terminology is fine. You'll still have 8 setlists of 16 Banks (Patches) and 4 Presets (Scenes). In fact the current architecture and terminology will remain more flexible since you won't be constrained to the Patch's physical configuration among the Scenes. You'll still be able to change everything in a new Preset (Scene) within the Bank (Patch). So vote for the ideascale item that suggests delay trails carry-over during preset changes.

Was your recent personal history with fraud or data breach related to Line 6 transactions? Is there any specific reason why you think the error message brue58ski received would indicate fraud on this attempted transaction? I tend to agree with him - things are just not fully prepared for release yet.

Since there is still some signal getting through when you use the amp's volume control, I think the pedal assignment and the pedal itself are working properly. The modeling for that particular amp allows some signal to get through even at minimum volume. Either that's how the physical amp behaves, and the modeling correctly reflects it, or there is a problem with the modeling. In either case it's out of your control. Perhaps other regular users of the treadplate model can try to replicate your experience, and report back.

Oh - yes I misunderstood. Thanks for clarifying.

You're right. It can't be done- at least not in the software. But you can wrap an elastic band around the switch so that it won't activate when you mistakenly step on it.

Doesn't that defeat the whole purpose? As a player, if I'm going to be tethered I really don't care whether the tether carries just power or all the other information currently carried by the VDI cable. A tether is a tether. And the shorter it is, the less range I have to move around while playing.