LarryPeter514

Like other have said, this is totally dependent on what you and your band want to hear on stage. For me, I send Helix XLRs to FOH, and my wedge. 1/4" output (with no cab IR) goes to the power amp input of a Vetta 2x12 combo and to the effects return of a Peavey Delta Blues. This is a perfect, responsive stage sound for me and my band.

I've been much happier using a wah pedal before the Helix input. The wahs are the only components of the Helix I just can't bring myself to use. The response curve of the expression pedal is so far from any wah that I would have to relearn technique that I used for 50 years. I'm too old for that. Also, it feels like the wahs aren't "modeled" in the way other components are. The rolloff of the frequency sweep sounds like it was lifted from their "filter" section, and it's pretty easy to setup a filter that works as well as some of the wahs do. Decreasing the mix does sound better, but A/B that with a good wah and you'll see that's not what wahs do. I suspect the rolloffs of the filters in a real wah pedal are frequency dependent - like many simple analog filters are - meaning that more neighboring frequencies pass through at different positions of the pedal. Some, like Morleys, used a compression scheme that keeps the perceived volume consistent through all pedal positions. I'd much rather Line 6 keeps momentum going with new models and refinement of older models than fix the wahs, but, still... maybe someday?

Thanks for the helpful info. I've decided to move to one of our Windows 10 computers and copy the My Documents/Line6 folder over. I need the Firewire stuff still running on the 7 system.

Thanks, silverhead. My logical brain was saying those words to me, while my emotional brain was shouting, "FINALLY AN UPDATE! MUST INSTALL AND ENJOY NOW!!" I just needed another vote on the logical side.

I see that the new 3.8 Helix update is not being recognized by HX Edit on Windows 7, and yes, it no longer lists Windows 7 as a supported OS. So before making any potentially brick-makng decisions I wanted to see if the forum members could provide some guidance. 1. Will HX Edit 3.8 run on Windows 7 if downloaded manually? I've seen other developers drop OS's from "supported" status even though the software would perform fine on older OS's. 2. If I need to move everything to a Windows 10 station, will the preset backups I've made on 7 be recognized on HX Edit 3.8 running on Windows 10? 3. What's the most efficient starting point if I move to Windows 10? Manually install HX Edit 3.71 (the firmware my devices are on now) and my backup files, or do I need to start with Line 6 Central? Please, no lectures about keeping a workstation on Windows 7 for so long. This computer has been the one used to install and test most of my gear updates for years, and it's the last Windows OS that reliably supports the many Firewire devices I still need from time to time. Thanks in advance.

Thank you all. I will submit a ticket for this.

This has been happening consistently since updating my Helix LT to 3.71: If one preset is left on for a prolonged period, block 4 in path B will become inactive - doesn't work if bypassed or "on", and toggling between bypass and "on" makes no difference. Sound still passes through, and all blocks after it still work as expected. Changing to another preset and then back, or turning Helix off and back on eliminate the problem. First noticed this when my Helix was left on in the studio overnight and the preset had no delay when I began recording the next day. I have accidentally done this many times in the past, but the issue only began after updating to 3.71. This is obviously not an unworkable situation, but it recently happened during a rehearsal when I had been using the same preset for around an hour, then we took a break to eat. Came back and the delay wouldn't work. I use a template for all my presets where before-amp pedals and amp blocks are on path A, time-based effects and cab are on path B. The fourth block on path B is where I will always have a delay (this issue happens no matter which delay it is). Not knowing how individual "blocks" relate to individual DSP processors, I'd just like to know if this is a sign of an impending DSP failure. It seems a lot like a memory leak in desktop world. Has anyone else experienced this?