duncann

Yeah. Too bad Helix doesn't have an auto-volume yet. You can get some decent auto-volume swells with the auto panner block, but it's time based instead of envelope triggered. So depending on what you're playing the auto panner could work. Probably not.

The longevity for the mechanical stuff is certainly a long-term concern. Good reason for using the editor. It would be interesting to know some details/results about the endurance testing done on the switches and buttons. Done either by Line 6 or the component manufacturers. But it's highly unlikely to find anything out about that. And for all the screens, I would assume the backlighting is done by LEDs? Probably no need to worry. Long-term, if something were to cause a catastrophic kaput, one of the first things might be a component with the power supply. Or possibly some flash memory? But even a device like Helix could be considered disposable after a time.

Lol. Too much info!

I quickly tried the patch cable thing, and while you could control the influx of feedback via an expression pedal, the type of feedback this provides is mostly of the unwanted, unmusical kind. The annoying kind that comes from a microphone that someone is trying to talk from. I use the pitch block type of feedback, the kind that the patch mentioned in this thread has, on a couple of my songs. It works pretty well, and can be musical, but it's not really the same thing as true feedback. It can only get close, depending on what's being played. A personal preference of mine for this patch is to set the maximum mix to around 70%, otherwise the effect becomes too exaggerated. Adding a bit of phaser in the mix, controlled by the same expression controller as the pitch block, can help with the dryness, and take away some of the artificial/chipmunk quality. Another idea to improve the patch is to assign the interval parameter from the pitch block to snapshots. This way you could get different flavors of feedback.

When you touch the tap/tuner switch, it will briefly bring up the tempo settings (global settings) as a shortcut for setting the values. Perhaps something related to this function is happening. Inadvertent touches or possibly a short triggered by the pedal? Has it always done this, or has it just started doing it?

NO NO NO! If you're going to start replacing parts, you must get them from ACME!

No worries. It's also somewhat confusing because it's also either the SPDIF or (AES/EBU or L6 Link) output, as Phil pointed out above.

Doesn't sound good then. I have read of a couple of instances where some of the internal ribbon connections can be finicky, so opening the unit's housing and doing a visual inspection of things might be worth a shot. It's probably an unlikely cause though. Other than that, there's probably not much else you can do but resort to the repair center again.

I thought this output is an either or thing. Either L6 Link or AES/EBU?

If you have some way of checking the output from the power supply, that would be a good place to start. Even better would be to try a different power source (at least 9VDC 3A I believe) if you have access to one.

You mean a firmware reflash? I know you'll be fine if you reflash the same version, as I've tried that. I've never tried a different version, but there's really no need to do that as only three versions support the model packs: 2.60, 2.61 (both had bugs), and 2.62. If you flash to a version below 2.60, you will loose the model packs while on the lower firmware version for sure.

No need to worry. A global reset will not destroy access to the model packs.

What version of the firmware do you have? Any of the packs require at least version 2.60 I believe.

Here's a pretty good webpage about autowahs in general. Probably way more than you want to know, but it does explain the parameters about half-way down.

You're welcome. :)

Snapshots would solve that easily enough. But differences between guitars would likely be minimal anyway. However, having the same exact fingers from day to day could produce greatly varied quacks. Not so easy to fix that.

I take back what I said above about using the band pass mode. High pass seems to work better for this type of quack. For Q, the higher it is the more pronounced the effect, so a fairly high Q would be good, maybe even max. A fairly high sensitivity as well, around 8. Attack around 100ms, decay 350ms, frequency 225Hz, freq depth 2.0KHz, direction up, and mix 100%. It's close using a clean amp tone. But that's for my guitar and pickups. The settings for your guitar might be slightly different. Just post the link, but links using a specific start time (...youtu.be...) won't work. It has to be youtube.com for it to embed in the post.

Something like this? It seems to me that a lot of what you're hearing with this is his playing technique, so if you can get close the technique demonstrated it might be easier to get similar results with Helix by using either the autofilter or mutant filter. Just play around with the settings for either and eventually you'll stumble across something that might be acceptable. You'll probably want to keep the mode on band pass. Both autowahs in Helix produce similar results but the autofilter has more flexibility by exposing more settings, so give that one a try. Also, you'll probably want to have this block located somewhere before the amp.

I tried this and it doesn't really result in what I think you're thinking it might do. (The reverse delay gives me nightmares; attempting to use it for a small section in my next song. It's easily the most potentially bizarre effect Helix has and it's evil :ph34r: ) Like you, I also notice that the reverbs always have a slight 'dry sounding' attack despite the mix (really a wet/dry balance) being at 100%. If you've ever heard the HD500 reverbs when set at 100%, I think that's the sound you're probably looking for, but I've been unable to duplicate that on Helix. Wish I could be more help other than confirming what you're hearing.

Since the text on the taskbar in the picture looks fine, as well as the titlebar text and menu text for the Helix app itself, it's probably safe to assume it's just the Helix app. Still Cleartype is worth looking at because I see differences in different applications because of it. For example, Firefox seems to render its text differently than other browsers, such as IE and Chrome, just not so extreme as what's in the picture above.

Cleartype might be worth looking into, but since it's only the Helix app, it's probably unlikely.

I notice there is an ideascale entry for this one: http://line6.ideascale.com/a/dtd/Multiple-splitting-options-for-Path-A-and-B/833936-23508

Multiple splits and merges for each processor path.

The 'E' happens immediately upon switching to the preset, even when using the editor, so that would rule out any vibrations. Also, I just noticed that when powering on Helix to a preset that produces the 'E', the 'E' does not appear.

Sounds like that would be expected behavior, but there seems to be a case for the 'E' popping up where there's no explanation, and it's unexpected. I have all exp controllers set to per preset. And I also resaved the preset with the onboard pedal in the heel position, switched to another preset, and switched back to the 'E' preset, which still produces the 'E'.