duncann

When did you order yours? I ordered beginning of this month and when I last talked my rep he wasn't sure if I made it in the first shipment or not.

Can the Preset UP/DOWN be changed to Preset DOWN/UP?

Old thread, but certainly helpful. I just bought one of these for my HD500X and noticed it does indeed have a dead zone to it. Kind of sucks because the throw on this thing is already shorter than the onboard one. It does have a 10K pot. I tried adding 22K and it worked better, but still some dead zone. The closest I could get was 20K, which almost perfect.

When set to auto, input impedance is matched to whatever the input impedance of the first effect in the chain happens to be. Not sure if there is a list of what this value is for each effect. In probably doesn't matter in any case. Going from the highest setting, 3.5M, to the lowest, 22K, there will be an attenuation of the highs from the input signal. The input setup controls what is used for input source 1, input source 2, and in-z. When global, it gets these values from the POD's system menu. When preset, it gets these values from the currently selected preset.

I just picked one of these up from Sweetwater (last one they had). It's really well built and works with HD units, likely Helix as well. The only thing I wish companies who make pedals like this would do is state explicitly the amount of physical travel their pedals have (what's the correct term form this?). I'm used to the pedal on my HD500X which has quite a bit more travel than the EP1-L6. I was unprepared for this and it's going to take some getting used to because the value changed is quite large when used as a wah or volume for very small movements of the pedal.

Next up...

Yep! That's usually how it works for me as well, to this day. Part of it is ear fatigue, so make sure to think about that when creating tones. You can take short breaks in between tweaking to extend the time to tweak a little bit, but eventually, it becomes a useless, time-wasting endeavor. Here's an excellent guide to read during the short breaks: http://foobazaar.com/podhd/toneGuide/

There really is no such list. If someone made a list, I think it would be rather complicated. The parameters you mention can appear to act differently depending on the amp and cab/mic used. And there are just so many combinations. There is a lot of info about what these parameters are supposed to do, and maybe even some suggestions about what they should be set at, but the suggestions would be nothing more than someone's personal opinion. What matters most is how things sound to you. To get a better idea of what these do: once you've found your favorite amps, you're best bet would be to experiment with those and see how they react to changing DEP values. Same with cab/mic combos and the cab's DEP values. Res works with thump and decay, so basically the higher the res is the more effect thump and decay will have. With res at zero, this effectively (no totally) turns off thump and decay as well. So build yourself a mental image about these parameters by turning virtual knobs. I'm afraid there is no shortcut for adjusting these, which is, I think, one of the reasons why people generally have a hard time dialing in tones on HD devices, especially if one is not familiar with it. I've had an HD for several years and I still get frustrated when dialing in tones from time to time.

Either Soldano Crunch or Overdrive would be good. There's a lot of amps in there, though, that cover a middle ground. You could also use a clean amp and add some overdrive in front of it, which might provide a little more flexibility within a single patch. As another option for clean, there's also Soldano Clean.

Try downloading the flash file from here: http://line6.com/software/readeula.html?rid=6262 (this is version 2.62 for POD HD500) Run Line 6 Monkey and highlight the flash memory item, then use the update from file button and choose the file you just downloaded.

I used to experience something similar with my bass patches that were prior to the amp bass pack. Usually doing the preset change thing you describe cured the problem. But for me it was actually a boost in volume that should not have been there. I just always thought it might be my bass with a battery powered eq on it, but I wonder now, because ever since using the bass pack amps I haven't had this problem. In my case the two amps were the Flip-Top and Tweed B-Man Brt. If the cabs/mics have anything to do with it, those were 115 Flip Top/47 Cond and 4x12 Tread V-30 and 409 Dynamic.

Here is one of the compressors with parameters, go to about 1:40, then pause at 1:45: https://www.youtube.com/watch?v=T6w41qFLB88

If you plan on keeping your HD for an length of time and play bass through it, the bass pack at least is a must! Plus the new bass cabs, 4x10 Rhino and 8x10 Beast offer some great tones when used as cabs for guitar, not just bass.

We were talking about midi messages being automatically sent from the pod when the user changes patches. The video doesn't cover that. In fact, as far as I know the discovery by rd2rk of auto CC#s being sent upon a patch change is an undocumented feature. But the video you posted shows very well the documented midi features when used with a daw.

With Steve Vai at least, I never liked his sound when he uses a Sustainiac. It always sounds like a kazoo.

Ok, you cleared this up now. I had it backwards. The midi CCs you want sent does indeed need to be set in the patch you're switching TO. So none of tools were the problem, I was. So you can have 13 arbitrary auto CC#s sent upon a patch change, 11 toggle (0 or 127 value only), and 2 (exp1 and exp2) with a specific value, 0-127. The order of these events seem a little strange: 0: B0 1F 73 [CC31 MSB] chan 1 val 115 (exp2) 1: B0 1E 78 [CC30 MSB] chan 1 val 120 (exp1) 2: C0 3C 00 [Program Change] chan 1 val 60 3: B0 0F 7F [CC15 MSB] chan 1 val 127 (fs1) 4: B0 10 7F [CC16 GP Slider 1 MSB] chan 1 val 127 (fs2) 5: B0 11 7F [CC17 GP Slider 2 MSB] chan 1 val 127 (fs3) 6: B0 12 7F [CC18 GP Slider 3 MSB] chan 1 val 127 (fs4) 7: B0 17 7F [CC23 MSB] chan 1 val 127 (looper) 8: B0 19 7F [CC25 MSB] chan 1 val 127 (exp-toe) 9: B0 13 7F [CC19 GP Slider 4 MSB] chan 1 val 127 (fs5) 10: B0 14 7F [CC20 MSB] chan 1 val 127 (fs6) 11: B0 15 7F [CC21 MSB] chan 1 val 127 (fs7) 12: B0 16 7F [CC22 MSB] chan 1 val 127 (fs8) 13: B0 18 7F [CC24 MSB] chan 1 val 127 (tap)

Not sarcastic at all. Even knowing that there is objective data, your brain can still easily override that to convince yourself otherwise, turning an objective reality into a subjective one, at least for the observer. It's even likely. You eventually become an inseparable part of the system whether you like it or not. So does an objective reality exist at all? Does a tree...lol. Or maybe a person's hearing system is really fine tuned to hear the subtle differences.

Seeing as how the guitarist community is rather small as population percentage, I'm guessing, it's doesn't seem like it's too hard to get word out. I think it's more that Line 6 has created a product that's worth something and moves this type of product beyond what's already out there. Innovative. Helix (not the, that's gotta drive the people at Line 6 nuts) is something that more or less sells itself.

Keep at it. Keep telling yourself as you adjust thump and decay with res at zero that you can hear a difference. Your brain might start telling you something different than before.

Well, I guess I should have mentioned that I specifically set the midi info in the patch I was changing from to see if any CC messages were being sent at all. The only time any automatic CCs were sent was for 0 and 32, and that's to indicate the setlist, not because of any specific, manual CC setting within a preset. The preset locations I used were in setlist 7, blank, and not factory presets. I also tried both pedalboard modes, FS5-7 and ABCD. The tools I'm using for this don't show any automatic CC messages sent upon a preset change, so if you're seeing this, the only thing I can think of is the difference in the tools being used. Who's right? Don't know for sure. Maybe somebody more official can possibly chime in. No need to apologize for anything.

Wouldn't have to worry about fret wear (at least I don't think so with titanium?), plus you'd get the ultimate in scalloped frets; just be prepared to slice your fingertips to the bone. If you made it to the end of the video it also has a modular neck/fretboard.

After looking briefly, HD does not send any automatic CC#s if set in a patch, Using ReaControlMIDI here is what's logged when switching from patch 1(0) to 2(1) in setlist 7(6) on channel 1: 0: B0 00 00 [CC0 Bank Select MSB] chan 1 val 0 1: B0 20 06 [CC32 Bank Select LSB] chan 1 val 6 2: B0 00 00 [CC0 Bank Select MSB] chan 1 val 0 3: B0 20 06 [CC32 Bank Select LSB] chan 1 val 6 4: C0 01 00 [Program Change] chan 1 val 1 5: C0 01 00 [Program Change] chan 1 val 1 The same occurs regardless if any CC# midi assignments are present for a switch. edit: the above is what's logged when switching presets using HD Edit (not sure why it's doubled). The only thing that's logged when switching using the device is the last line of the above log (it's not doubled when using the device). The CC0 and CC32 entries indicate the setlist and is also sent when using the device to switch setlists.

Kind of defeats the purpose for hitting only one switch, but if your amp can receive CC messages, you could change the patch and then immediately hit another switch which would be assigned to send the right midi CC to change the amps channel.

Cool. You guys have really thought about everything for ease of use and flexibility.

Is it easy to zero in on a very specific value, or does it take a lot of concentration towards your muscle movements to move the expression pedal very delicately?