phil_m

The Supersonic doesn’t use standard relay switching. It’s a TS cable that’s carrying multiple functions, so it looks like the footswitch it’s varying the voltage going back to amp, and the ampmis responding to that. That’s not the type of channel switching the HX provides. FWIW, this was an issue with the TC Electronic G-System and the Supersonic as well. http://forum.tcelectronic.com/topic/4209/channel-switching-with-fender-supersonic/

I think the cause is just general USB variability from system to system. It could be just about anything, really. From what I’ve seen the majority of the USB communication issues with the Helix seem to happen with Windows 7 and newer Macs. Why that is, I don’t know.

I'm talking about the 6-button looper... I couldn't replicate the supposed bug. But if it's something you're able to replicate, yes, you should open up a ticket.

Someone else mentioned this, and I tried to replicate it, and I couldn't. Meaning the looper was working the way I'd expect it to. I'm not sure what you mean by not getting your loops to sync.

The biggest advantage that the Helix and HX offer over the HD500X is the fact that you can load IRs onto them. To me, that's the most useful feature for using them with an acoustic. I wouldn't say the HD500X offers way more options even compared to the HX. Yes, it does have the mic input, so if that's important to you, that's something. You can actually load more blocks on the HX than you can the HD500X, and it has more overall processing power.

Hate to be the bearer of bad news, but that's most likely the problem. Historically, the less expensive USB-MIDI interfaces haven't worked for Line 6 updates (or for most hardware that uses MIDI Sysex for updates). It seems that most of them don't handle MIDI Sysex messages well, that's basically what the update is. I think part of it is that the inexpensive adapters are relying on the built-in, class compliant OS drivers, and those don't seem to account for Sysex. The adapters that Line 6 recommends are listed here: I have an M-Audio Uno, and it's always worked.

There are no DT50 drivers - it's just a MIDI connection. What kind of USB/MIDI interface are you using?

There is no Native discount associated with the HX, at least not currently.

It's not delayed, so, yeah, if you ran it in parallel with the signal being processed through the Helix, you would likely hear phasing/comb filtering.

There's a Mix parameter in the IR block that let's you control the dry/wet mix. It's default value is 100, but you can dial it back to whatever you want. As far as the Cab block, you could accomplish what you want by putting it in a parallel path. You can control the mix between the two paths with "Route to" parameter. in the A/B Split block.

Are you sure it's not the protective film that's applied to the scribble strips? Did you ever remove the film after getting the unit?

Are you talking about this post? I think it's been closed since Tony posted it... There are no replies on it.

Well, he replied twice to the issue and didn't reply the last time. He could have simply missed your question. I'm not sure. You seem pretty combative throughout the whole exchange, though. As far as the voltage on the tip, I'm not sure. I could check mine with a meter. It seems a moot point now, though, since you've decided to go another route.

No one is blaming the customer or calling anyone an idiot here. I just asked you a few questions. And no one is closing this post... The audio artifacts post isn't open for replies because it's there for information purposes. In order for problems to be solved, Line 6 needs to actually gather information on them. These boards aren't here as customer service boards. They are user discussion boards. The best way to contact Line 6 customer service is by opening up a support ticket or calling the CS phone number. I'm not a Line 6 customer service agent. I'm an expert user here, and there are a lot of other people willing to help here. But there are limits to what we can do, obviously.

From the later comment, it's clear he's talking about the USB audio coming from the laptop to the Helix. So it's the USB 1/2 out from the laptop's perspective, but the USB 1/2 input going into the Helix.

There's no way to do this with the USB 1/2 input. It's a dedicated. From page 21 of the manual, "Helix also receives input from USB 1/2, but it's dedicated for monitoring audio from your computer (or iPad) and bypasses all processing blocks. As such, it's not available as an input block source." The USB 1/2 Input Trim parameter is a Global Setting, and those parameters can't be assigned to controllers.

I think my HX has frozen up perhaps once since I've had it... Did you happen to restore the second unit from a backup you created from the first unit? Was the second unit running the latest firmware? Sorry things didn't work out for you, but I can pretty confidently say your experience isn't typical.

What problem exactly? Cubase can't find the plug-in?

Hmm... The Helix doesn’t add any gain to the signal coming from USB7. It’s just tapped directly off the input. The input pad will affect it, but if you’re still clipping, that would mean the signal from your guitar is very hot. It sounds to me like something it probably setup incorrectly. The signal I get from USB7 is very low (as expected).

You just need to move the Volume Pedal block so it's earlier in the signal chain. Right now you have it after the delay block, so that's why it's killing the echoes. I typically like mine first thing in the chain, but, really, you could try it anywhere before the delay in your chain.

IIRC, being able to disable the Looper block was one of the most requested, if not the most requested, Ideascale item for the HD line.

Not true... The faulty units have a defect that the non-faulty ones don’t have. There are tens of thousands of LTs out there now. The fact that some have been unlucky multiple doesn’t mean anything than just that. The laws of probability dictate that such things will happen. The issue is the way the defective housings were stamped. There’s a clear delineation between the faulty and non-faulty ones. The popping you’re talking about is the defective metal reaching the top of the stress yield curve and goes into plastic failure mode (the housing snaps). If this were truly something that affected every LT, there would be way more reports of it happening. As it stands now, the reports have become very sporadic.

The main symptom of the faulty units is high noise floor when used with certain amps. It’s like a white noise/hiss. I guess one way to test is to compare the signal with the unit in analog bypass and DSP bypass. There shouldn’t be additional noise in either setting, but with the defective units, DSP bypass will be noisier.

I believe that the input impedance for all the fuzzes is the lowest value, but really, just play around with it and see what sounds best. What's so bad about that? I just don't understand why it would prevent you from using it... I'm not necessarily disagreeing with people who say it should act differently. I just don't agree with the described severity of the issue. It's really not a big deal to change the input impedance in other ways. You can also change it per snapshot if you want by assigning to a snapshot controller. So if you had a snapshot with a fuzz on, you set to a low value, and then just set it to 1M-Ohm for every other one.

Are you on Facebook? If so, you should contact Frank Ritchotte... He has a knack for making these sorts of problems go away...