duncann

I didn't have any problems so far with 1.06.5. Nothing really to lose anymore by trying since there is a safe boot mode now. But I've always been of the mind wtf, just go for it, when it comes to stuff like this.

I find the editor for the HD disappointing in a lot of ways. But it's way better than none at all. For me, using the mouse/keyboard - with pick in hand (sometimes dropping it) - has become an unconscious action. That's from all the time of using the HD's editor. So putting the unit on my desk will not be easier, especially since I have not the space for the that. The bending over is the biggest issue for me. Every time I've done this for extended periods, my shoulder becomes a mess for days afterwards.

Not quite the same as gain block, but this could be achieved right now with some of the blocks that have separate level, and/or panning/width controls such as the multtap 4 and 6 delays or the dual pitch.

Maybe it's just like clearing all the snot out of your nose. It makes you feel better. After listening to that video, that's actually similar to what I heard. Not exactly, but close. In the video it sounds like there is a mid-boost at one point, where on Helix it was more of a slight volume decrease around the same point, at least that's how I perceived it. But it didn't go far enough to see the rest of it.

I've gotta assume it's soon. I'll make a guess and say February 29. Several times in the past several weeks I've read the editor is their top priority right now...

Guess it's not fixed then. :( Is this a confirmed bug? Or is it supposed behave like this?

Not sure what the treadplate but is supposed to be, but adjusting the master volume on this amp has the volume peak at around 3.5. At around 5.0, there may be a slight decrease in volume. After that, there is an increasing power-amp distortion and no increase or decrease in volume.

Here's a list of those I've gathered, pretty sure they are all correct: 2: LED light Fun 5 & 6: global reset 7 & 8: reset setlists to factory, keep IRs 8 & 9: reset setlists to factory, clear IRs 9 & 10: reset setlists to factory, global reset, clear IRs 10 & 11: upgrades existing presets to latest format 11 & 12: clear current preset 5 & 12: clear setlists, clear IRs, return system settings to default 6 & 12: safe boot mode

No such luck, if luck is real. Ideally, something like this could be a solution for what you want: http://line6.ideascale.com/a/dtd/Auto-wah-or-auto-EVERYTHING-for-Helix/727014-23508

What I do until an auto-engage might be put in is to have the wah engaged all the time. The pedal that's controlling the wah can be used for both the mix and position. Depending on the wah, a mix starting around 35-40% gives a mostly transparent sound, so the wah is essentially off. But because the mix isn't 100% through the wah's entire range, the character is changed slightly. This can be compensated for slightly by adjusting Fc Low and Fc High, which some of the wah's have, some don't. Or you could just the expression pedal switch if you're using the onboard expression pedal. Not sure I get why you'd switch to a different patch to engage a wah though. Maybe I'm missing something?

I used to have one these also. Geekpimp is correct.

To also be aware, they still have not fixed the bug in version 1.04 of the Helix app where dragging and dropping multiple IRs from your file manager to the app will result in an unpredictable order in Helix. Selecting multiple IRs from the import dialog works fine through. So avoid the drag and drop method.

These days, a lot of the music out there is basically a ten second melody or phrase, over and over and over. Yuck! I don't consider that music. But to be fair, I'm sure a lot of older music, including classic rock (which I don't like at all), and 80s and 90s metal, is that way as well. There's a lot of technically gifted guitar players out there nowadays for sure, but a lot of them that I listen to, mostly from youtube videos, don't push themselves enough to capture the feeling that should be there. In other words, a lot of the stuff I hear isn't really about anything in particular. It's clinical, empty, and quickly bore inducing. But it's a hard thing to do. It could also be me in not listening to it correctly. Lol. Some advice since you find you've lost interest at one point or another, which I can relate to, is to write your own stuff. Write what you think won't lose your interest. There's gotta be something floating around in your head you can visualize - and duplicate in the real world as best as you can - that's your idea of the perfect music. Just do it! I guarantee it won't bore you.

The second item there is what doesn't seem to work correctly, then. Because a CC is transmitted in the condition that the switch being used is the one for selecting the preset and the one the message is assigned to. If works as stated when the preset you're loading is on a switch that happens to have no single-command message assigned to it, from the preset you're loading. If the preset you're loading is on a switch with a single-command message on it, from the preset you're loading, that is sent automatically. When I say single-command message, I've only tested with CC, nothing else.

Positive. I have that turned off. I was using ReaControlMIDI to view the messages being sent. It must load the preset first, and it also sees the switch you're pressing somewhere in this process, and then it decides to send the midi command associated with that switch in the just loaded preset. Could this be a bug?

Yes, correct. The commands being sent originate from the preset you're switching to. But this will only happen when the preset you're switching to contains a command on the same switch you're hitting to get to the preset that you're switching to. That's how appeared to work when I tried it. I've also noticed that if your intention is to have automatic commands sent from the preset you're switching to, there are the lightning bolt icons, or instant commands in the command center. That appears to be what these are for. You can have six of them. These are sent upon the preset's recall.

Don't know what the mobilepod app is. I'm guessing the auto swell effect is an auto-volume? If so, use the Auto-Volume, listed under the delays.

I just tested and can confirm what you're saying is what actually happens. So if you have a midi command assigned to the same switch being used to switch to a preset, Helix will automatically send the midi command of the preset you are switching to. This sounds like it would be expected behavior. Don't know for sure. But there is no way shut this off without removing the midi command, or reorganizing the order of the presets, so that when switching presets, the two functions to coincide to the same switch.

I really like the style of this. There's a lot of really creative stuff going on here. Little bit rough around the edges, but other than that, really nice.

There is a global option to shut this behavior off, which is MIDI PC Send/Receive.

Ok. I think I see now where there could be limited use for something like this. So, for example, you want a dual amp setup using path A (1 and 2), but you also want a second, simpler, less dsp intensive setup using path B but still have all the routing options available on path B (1 and 2), which is not possible now because the path A setup would encroach into path B.

Ah ha. So it's the convenience of it. I've quickly learned with Helix to split things up among the paths. And the more you use it, the easier it becomes to almost instantly recognize where or how much of something you can put on one path. I honestly have yet to worry about any dsp usage issues.

I don't see how routing flexibility would be changed at all by this. Essentially what's there now is what there would be if you were able to put 100% of the dsp (both processors) on one path. Nothing really changes. There would still be only one long path from start to end with the ability to add two splits and merges. Of course there's still the other options of multiple inputs and outputs for routing possibilities I'm more curious why they allow for only one split and merge per processor. More of those would be extremely useful. But there's probably technical reasons none of us know about for why they did it the way they did, both processor allocation and limited splits. No clue about any of the reduced latency stuff. Would it be enough to make any sort of perceivable difference? One thing that's very likely is DSP processors are not at all similar to mass market computer processors in the way they are designed and programmed.

Beyond the programming challenges this might present (maybe it's not even possible without a complete reworking of Helix's firmware from the ground up), what would be the advantage?

One thing is for sure. The editor, whenever it's released, will have bugs. I just wish they'd release something, now, and call it a beta. I #@##@! up my shoulder again attempting to tweak things.