duncann

What does an auto delay do?

You appear to be correct. I get the same behavior.

I've also noticed that when compared to the HD/M9 octoverb, Helix's octoverb definitely leaves room for improvement. It's still usable though. I haven't noticed any sort of cycling tuning problems. To open up some options for better a better sounding octoverb, use it on a parallel path. Set the mix at 100% and use the merge block's level controls to adjust the dry/wet mix. Using it this way allows you to put various EQs, modulation, fuzzes, or whatever, directly after the octoverb, only affecting the octoverb's output.

For the auto-engage-disengage function: 1. Select the wah 2. Menu 3. Bypass assign 4. For switch, select the expression controller you want to use 5. Position controls at what pedal position to engage/disengage the wah 6. Wait controls how long to wait before actually engaging/disengaging the wah I find it works fairly well. It does take some amount of getting used to because there might be a point where you can hear the wah engage/disengage, depending on the chosen wah and/or the value of FcLow relative to how the tone sounds with the wah turned off.

Even if it were possible for the HD to encompass Helix models, I doubt it would eat any sales of Helix because Helix is about more than just the models. However, If I remember correctly, there are some models in the pay-for expansion packs (at least the panama and bass amps come to mind) that were modeled using the HX modeling process and then ported to the HD. So in a sense, there does exist a form of Helix models in the HD.

Recently opened a support ticket because I found out I had the not gray parts for the expression pedal assembly. Just gave them my address and they sent them out (no charge), which I received today for an out of manufacturer warranty Helix. Truly great service for a case where they have absolutely no obligation.

Certainly almost all things in 2.21 are worthwhile. However, the swell dynamic at least is really not great at all. Or if it is great, it's great in a very limited way, which makes it not great. Hope they fix this effect. Take a look at the auto volume in the HD for a swell that's great.

The spdif audio dropouts will supposedly be fixed, or so I've read from an unofficial source on these forums. If you use one of those outputs, that fix alone would make the next update a necessity.

I think Mission Engineering makes some sort of spring loaded pedal.

He probably wants the pedal to automatically return to the heel position at the moment when he decides not to use it.

Unlabeled knobs wouldn't be confusing enough, although it would be a good addition, or would it be subtraction. I always liked Line 6's idea of percentages for the EQs on the HD. For Helix, they should follow this and have every unlabeled parameter knob as a unitless percentage, no exceptions. :D And sometimes have the percentage go from 100 to 0, or even a random order of 100 numbers. Seriously though, visual indicators for the compressors would be extremely helpful, for bass guitar in particular.

Here's a setlist: http://line6.com/support/topic/27401-looking-for-hd500x-rockmetal-patches-made-using-headphones/?p=212677

I don't see why this wouldn't work. It would be a matter of having the HD send midi info, programmed into a preset, to your DAW and have stuff in the DAW happen based on the midi info. But you will need some sort of midi-to-usb device for the connection.

I always thought the cabs in the HD were fine, especially given the hardware Line 6 was working with at the time, and also that the HD is not a dedicated IR loader, which likely would have taken away a considerable amount of DSP the user would have to work with. Line 6 did a good job on balancing the cabs for whatever sound you might be after. There's a really good variety in there. Sure IRs could considerably improve what you get with the HD, since IRs are so much of the final tone, but I never really saw it as much of a problem.

Ok. I see what you're idea does now. Way over-thinking it on my part, lol. Sometimes a simple notion escapes me entirely. Voted.

But where is the momentary snapshot coming from? Where is it configured? The terms previous and current are being used, but how exactly would this work? Just some examples (assuming all snapshots are set to momentary): Say you're on ss1, or any ss, and there is no previous ss since turning Helix on. I guess it just won't do anything. Say you're on ss2, and the previously selected ss was 8. It would go from 2 to 8 back to 2. Now say you select ss4. Then ss2. Now the momentary ss for ss 2's switch is 4. It just used to be 8. It could get difficult to track this by memory... There would have to be some sort of indicator as to the previous ss. It seems like it would be easier to have a clearly defined momentary snapshot for each snapshot. Or two snapshots per switch that could be either momentary or latching.

I think I'm a little confused because the user still has to define a snapshot other than the active one, to be placed on the same switch as the active one. So, for example, with eight snapshots, for switch 1, you want to be able to define the pair as snapshot 1 (active), and the momentary snapshot as any snapshot from 2-8? Likewise on switch 2, the momentary snapshot would be either 1 or 3-8. Switch 3, 1-2 or 4-8. And so on. Or am I over-thinking this whole thing?

I don't think I've seen it mentioned, but did you try replacing the battery? On my Ibanez 1205E I can recall a weak battery at one point causing unwanted distortion/clipping. Not sure how this explanation might jive with it sounding OK through your Sans Amp though.

I guess I saying if they were to implement a momentary function for snapshots, which implies a 'pair' of snapshots per switch, there may be an opportunity to expand the number of snapshots at the same time, or a 'pair' of snapshots per switch, that can be momentary or latching. As far as pairs go, maybe it would be something like 1/9, 2/10, 3/11, 4/12, ... So switching between pair 1 and 9 could be either momentary or latching.

How about a variation of your idea. Instead of the current eight snapshot limit, increase it to sixteen, or two snapshots per switch (unless your intention is to have sixteen snapshots but just didn't mention it?). Then each snapshot switch could be either latching or momentary.

Impossible! Things have devolved into an inescapable recursive loop.

Please don't do that. It will start and end bad-league. :lol:

I think I recall DI saying a while back that it would be only limited by computer processing power, or whatever would be actually practical to use.

Here's all my HD500X presets for the album I've been working on: existence.hd500x.zip About half the album is done with the HD500X. The rest is done with Helix. They are all done through a Sony MDR-7506 or MDR-V6. Also, I did not use the headphone output from the HD500X. I used the spdif output, converted that to an optical signal, then to an internal pci-e soundcard, and finally a headphone output from that. I should also note that I didn't necessarily make any of these tones as standalone or isolated. They are meant to work in context, or by song. I also listened to this context on as many different sound systems as I could get access to. Maybe it'll help you, or not. But here it is if you want to take a look.