duncann

Something must have happened from the time you transported it to your friends work up to the time it was used at your friends work. It sounds like something damaged the circuity associated with the sound output. Take it apart and do a visual inspection if you're comfortable doing that. Look for a capacitor that bulges. Do you smell anything burnt about it?

to make matters worse (jeez, I can hardly see what I'm typing), try reading this forum on a 1440p or, better yet a 4k, monitor on windows 7 with DPI scaling that sucks and the browser set at 100% zoom.

You can read about this stuff and try and understand the technical aspects of what it's supposed to do, but as a guitar player, probably what's more important is how you perceive what it changes. Understanding what it does can aid your hearing by making you expect what to hear, but actually feeling what it does while playing a guitar is different. I guess what I mean is mess around with it and whatever sounds good to you, go with it. I still have trouble with this control too, as well as bias excursion. Sometimes I prefer it one way, other times the opposite. But the effect is subtle in a lot of cases and just tinkers around the edges of a tone. One thing I've found it useful for is getting rid of a sizzling quality in some higher gain tones by turning the bias up from the default of 50%. Turning it up or down affects the volume though, slightly. It's loudest at 50%.

Thanks for the compliments. Hope you find some use for the patches DarrellM5. Thanks hurghanico. That's the part where I use the seeker, at least the very beginning and end of that small part. I though it gave an interesting effect so I threw it in there. One thing I noticed about that effect on the pod is there is another one called Obi Wah. I wonder why line 6 has both of these effects in there because they both sound very, very similar. The obi wah gives control over the number of steps and the seeker lets you choose the filter type; low, band, or high.

Finished a new song, "Null Vitiator", from my album Existence, Bandcamp or Soundcloud. It was produced using an HD500X. This one is about the force of gravity and its capability of seemingly endless cycles of creation and destruction of matter. Thanks for taking a listen. Null Vitiator.zip

This will probably give you the best representation of this eq at around 3:40: https://www.youtube.com/watch?v=wLkVhOp5FCY

Another thing to consider is that, alone, it may be bee-like, but when put against a background, a lot of it may suddenly disappear.

In addition to what everyone else said, doesn't that amp have a default on axis 57 mic? I haven't bought the model packs yet, but I remember seeing that, and that mic is particularly bad for fizz, or good if you like fizz. For a start you could experiment with changing the mics and cabs to get something closer to what you like, and then work from there with possibly EQs.

Of the three things you mentioned in your original post, I have an open ticket on the DEP control one. It took them a week to respond with the equivalent of huh? what's going on? So it seems they are not even aware of at least this one bug introduced in the latest updates to hd edit, 2.25 and 2.26. You could try opening a support ticket. It is really the only avenue open to us. The only other possibility is if Digital_Igloo randomly shows up here to read this and asks the appropriate people to look into it.

That tone sounds similar to Guthrie Govan. A suggestion might be a dual cab setup with two xxl v-30s, one with a 57 off-axis and the other an 87 condenser. For the amp maybe a soldano overdrive with a tube drive in front, and very little distortion. See attached file. https://www.youtube.com/watch?v=Id3DyawANmI hd500x.unamed.zip

It's up to you if you want to update. There's really nothing gained by updating, unless you plan on buying any of the model packs or you have use of a global EQ. There is at least one esoteric bug that was fixed. The F-ball amp, when turning the bass to zero, mid to 100, and then treble to 100 would produce dead silence. Maybe there's other bugs that were fixed. It sure would be nice for line 6 to let its users know exactly what was fixed. There is a new bug that was introduced. If you use hd edit a lot and work with the DEP controls, you'll find that the percentage values are no longer displayed. You'll have to look at the units screen to see them. As far as some people having problems and others not, my guess would be something related to the host computer's usb implementation.

All of the older ones remain intact.

I would check out the wiring in the guitar. I can't see how it could be anything else but the guitar.

Lo Cut: 20Hz Low: 150Hz Mid: 1.8KHz High: 8.0KHz High Cut: 20Khz All Qs are 0.7 All Gains are 0.0dB The EQ defaults to ON. To get the default values back you can also do a global reset, but that's kind of a pain.

There's also a website calculator that I use from time to time. I'm sure there's tons of others too. http://www.thewhippinpost.co.uk/tools/delay-time-calculator.htm

Having to wear glasses really really sucks. :(

I wouldn't be surprised if somethings shows up, at least as an announcement, this summer.

Whew! Sounds like I've unwittingly avoided what sounds like a doozy.

Hmmm. I've been using the the seeker on the song I've been working on now for a while, both before and after the update. I don't notice any difference. I also have a patch that I use a lot that uses the sweep echo. Haven't noticed any difference there either. In the case of the seeker, both inputs are the same and the seeker is before the amp. For the sweep echo, both inputs are the same, the sweep echo is before the amp, but everything is in path a, the other path is muted. It must have been a specific configuration for the bug to happen? (This is one of those things where you learn of something you've been doing for a while and realize it could have been fcked up the whole time!) :lol:

The unit will report that if it's not connected to usb. Nothing to worry about.

I thought version 2.62 fixed the global EQ not working after engaging the tuner?

What bug is that?

It is indeed fixed. Now if we could just see what we're doing with the DEP controls in HD Edit ...

Line 6 released version 2.25 of hd edit (first version to have the DEP controls with no values), which corresponded to version 2.60-261 of the new firmware, and then when they released version 2.62 firmware, they also released version 2.26 of hd edit. On the download page for this version they state that it fixes certain DEP from not displaying correctly (not exact wording). Unfortunately, the bug is still there in version 2.26. To see the values, I guess you'll have to look at the pod's screen while editing with hd edit.

If you changed the tap tempo led from the default of on to off, when you do a global reset, then turn the unit back on, the tap tempo led is flashing again.