zooey

No. Just no. Please don't take a risk like that, just to save a few minutes during a firmware upgrade.

Which is evidence that you know what you're doing with IT stuff. It's not evidence that the virus reportedly found on two USB sticks not in your possession is a false positive.

Not trying to be difficult, and as I said myself, I think you're probably right, but how do you KNOW that?

Yes, but typically master volume isn't really a drive control, it's output volume. Yes it's drive if the output stage is maxed out, but that's not typically the case in master volume amps. In Helix, it's channel volume that fills that role, master means power amp drive.

Just to clarify, IMO the various gain/volume controls in Helix are named pretty counter-intuitively. Gain is preamp drive Current name isn't too bad, but Preamp Drive would be clearer. Master should be called Power Amp Drive Current name is very misleading, since all other gear I'm aware of uses the term Master to mean overall output volume, independent of the drive and volume of each channel. It doesn't affect the drive of any stage. Channel Volume should be called Output Volume This is just the output volume of the patch, doesn't affect drive at all. You know, like Master usually means :) Not sure that's a direct answer to this question, but hopefully it helps make the overall architecture clearer.

Given those two different sources, chances seem good that it's a false positive. Those do happen, with all antivirus software. Was it the same antivirus software in both cases?

If it's new I think the USB drive just has the quick start on it, maybe a little more manual-ish info, but it's almost certainly quite out of date.

Compressed as all getout too, it's not just youtube doing that.

If you're trying to pinpoint a problem frequency, try setting Q as HIGH as possible, which makes the affected bend very narrow, set gain to a big boost, and sweep frequency around until you find the nasty one. Then you can switch to cut, and maybe widen the Q if that sounds right, and try to find settings that remove as little as possible but fix the problem.

Voted

Will is right about channel volume only controlling how loud the final output is, it doesn't affect drive. Turning up master hits the (virtual) power amp harder. Turning up Drive hits the preamp harder. Channel volume is just volume, no change of tone.

Not a high gain guy myself, but happened to run into this guy you might want to check out. You can download his patches too.

No. If you're in edit mode, everything is editable.

The Windows alert sound etc always blow my head off​ before remember to chill them. I play guitar significantly louder then I run my computer :)

Thank you @MojoAxe for that clear explanation. I haven't done 2.21 yet, and can't until later, but it sounds like you've identified a very unintuitive aspect of this process, and helped guide people through it. Line 6, you know I love you, but sheesh, this is user-centered software design 101. The instructions​ have to be clear, and have to work on a basic human level, before the techier bits even matter.

Far as losing snapshots, that's not great. Hope it doesn't happen to me when I upgrade. You're the only one I've seen reporting that with 2.21. Doesn't mean it's not happening, or not happening to others too.

You have to export your IRs before upgrading, then import them again after. That's how it's always been, and is covered in the release notes. The easiest way to put your IRs back in their original locations is to rename them with a 3-digit prefix before you export them. Makes it easier to drag them back into the editor in order, and easy to see when something's in the wrong place. And yes this is a pain. We hope that Helix Native will include some form of IR management that removes the need to do this by hand, and ideally makes it easier to reorganize your IRs without your presets losing their pointers to them.

Two people are reporting this behavior, and support said to send your Helix back for repair? That seems odd to me. Has anyone tried to repro this and NOT seen it? (Not at my Helix or I'd try myself.) When you come back to the patch, do you see the settings you saved, but it sounds different? Or are the settings getting messed up? FYI, other users can't see that issue link, only the person whose ticket it is.

Not at my Helix, but I'll try this when I can, maybe tonight or tomorrow. If anyone can get to it sooner, great, sounds like a bug or a mystery, another set of ears on it would be good.

Helix is usually able to convert .wav IRs to the format it uses internally, but maybe that one's just too big. I haven't run into that with cab IRs; reverb IRs may be much longer so they can have really long tails, but cabs usually don't. In any case, you could try manually truncating it to 2,048 or 1,024 samples. Those are the lengths supported for Helix.

Apparently my guitar is missing at least one string. No wonder I'm not a metal guy. ;)

Side note: IMO the easiest way to audition a bunch of IRs is in pedal edit mode. Once you've the IR block and that parameter "selected", you can use the + and - footswitches to step through them. Use the expression pedal to move long distances.

Hit More Reply Options. You get the full editor, which can attach files. If I remember right, you have to change the extension to .txt to upload presets, forum software rules. Try it without doing that first though.

HO, we might be saying the same thing. Here's the Helix Help on this: When you initially recall a snapshot, it'll have the blocks enabled that it was saved with. That can't be prevented, it's how snapshots work. The global Snapshot Edits setting controls what happens when you enable or disable some blocks, switch to a different snapshot, then switch back to the first one. If it's set to Recall, your changes to the first snapshot will still be in place. If it's set to Discard, they'll be thrown away, and the snapshot will be recalled as it was saved. I personally use Recall. You can set up one or more snapshots the way you want them for a song before it starts, kind of an on-the-fly custom variation of the preset. If instead you want each snapshot to always be recalled as it was saved, you'd use Discard. Make sense?

Thank you, glad to help. Tell my boss and my wife please ;)