stephane_dupont

Select Snapshot 1, assign #1 to the first instant command (via the command center), and then select snapshot 2 and assign #2 to the FIRST instant command (meaning you have to replace your #1 message in the FIRST instant command).

Nope, it works with instant commands too. I use it to automatically change the preset on a M5 per snapshot, it's working nicely.

Not sure if I understand your question, but if you mean having CC commands sent each time a snapshot is loaded, yes it's possible via the "Instant Commands" (go to the Command Center). If you have some instant commands shared across snapshots, they won't be send when you change snapshots. But on the contrary, if you have different CC or different values on the same CC depending on the snapshot, these "differences" will be sent.

+1

(and I think "MIDI PC Send" should be Off by default to prevent the things that are talked about in this post, but "MIDI PC Receive" should be On by default.)

I don't know about the default value it should have, but to me the problem is if you turn it off (if I'm not mistaken), Helix doesn't obey anymore to PC commands. So, shouldn't it be splitted in two options, "Midi PC Send (On/Off)" and "Midi PC Receive (On/Off)"?

Nope, already tried, that doesn't work. That being said, for MIDI only, MIDI cables are way more easier (and stable) to use anyway...

For my live setup (which is a Helix being used as a multi FX and sent into two amps, and also being used to send MIDI signals to a computer that handle various things), I had to remove the USB connection between the Helix and the computer and use a MIDI cable instead. If not, computer was making noise in the amps... (Using an outlet without ground helped a little, but just a little, was not enough.)

Two bug reports I made to the Line 6 support center, the second making the editor unusable for me. Be cautious if you don't want to lose some time parameters in your presets! Bug 1: When we send a Program Change MIDI message to the Helix, the following behavior occurs: - If we send a program change with value X and the preset X is not selected, preset X is selected (normal behavior) - If we send a program change with value X and the preset X is already selected, preset 0 is selected: this is not normal, was not the case before the last firmware and has no sense. It should do nothing (or reload the current preset, but I would prefer like before, that it does nothing), but certainly not selecting preset 0! Bug 2: There's a bug with the timings in Helix editor. I have a preset with a controller (EXP pedal 2) changing the Time parameter of a Simple Delay from 596ms to 964ms. It works well, but: - If Helix editor is open, it goes from 590ms to 960ms instead - If I save the preset while Helix editor is open, I lose my values, they became theses rounded 590ms and 960ms values forever. Hopefully we can get a fix soon?

Two bug reports I made to the Line 6 support center, the second making the editor unusable for me. Be cautious if you don't want to lose some time parameters in your presets! Bug 1: When we send a Program Change MIDI message to the Helix, the following behavior occurs: - If we send a program change with value X and the preset X is not selected, preset X is selected (normal behavior) - If we send a program change with value X and the preset X is already selected, preset 0 is selected: this is not normal, was not the case before the last firmware and has no sense. It should do nothing (or reload the current preset, but I would prefer like before, that it does nothing), but certainly not selecting preset 0! Bug 2: There's a bug with the timings in Helix editor. I have a preset with a controller (EXP pedal 2) changing the Time parameter of a Simple Delay from 596ms to 964ms. It works well, but: - If Helix editor is open, it goes from 590ms to 960ms instead - If I save the preset while Helix editor is open, I lose my values, they became theses rounded 590ms and 960ms values forever. Hopefully we can get a fix soon? UPDATE: added on this thread: http://line6.com/support/topic/16083-helix-bug-reports/

Same here.

Helix will work really fine with tube amps, but if you don't use amps and/or cabs on Helix! In other words, you can use your Helix as a pedal board for your AC30 (and that work great), but use only FXs, not amps. If you tried factory presets, they are all with amps so they won't play fine with your AC30.

As I'm programming the Helix for my next series of gig, I realize there's a lot of stuff we can't do for now with the Helix, one being as simple as the following: - 3 delays - 3 footswitch, each one activating one delay while bypassing the 2 others. To do that, we can still use MIDI, it's more annoying to program, but it should work... Except it doesn't because sending a CC value corresponding to a footswitch doesn't allow to specify it's state, just to toggle it. We could imagine another set of CC to do that, with 0..63 to putting it off (or doesn't do anything if it's already off) and 64..127 to do the opposite. Or keeping the same set of CC's and having 0: off, 127: on, any other value: toggle. http://line6.ideascale.com/a/dtd/Midi-CC-for-footswitches-allowing-to-specify-it-s-state-On-Off/819853-23508 Thank you for your vote!

Made a post and a support ticket for that. Made me lose an hour of testing to figure it out. At least it should be in the manual!

And Undo/Redo ? ^_^

So no one from Line 6 can confirm us the exact behavior? I thought here was the best place to ask, but shall I create a support ticket instead?

In any case, it would be great to see the behavior confirmed here by someone from Line 6, and maybe add a few words about it in the manual?

Also, it's really strange that an A/B split reduce levels by 3db, but a Y split doesn't... If someone from Line6 can give us more details that would be great. EDIT: my bad, Split also reduce level by 3db.

Hello, There's something that I don't understand with "A/B" and "Merge" block levels. Let me explain: Let's say I have a straight signal, from guitar to XLR outputs, no block on the signal, nothing. A blank preset. Now, I add a 0db gain block, just to be able to split path (If I'm right, we can't split path without a block?). Still the same, the sound has not changed. Now, if I click on the 0db gain block and move it below, a "Split" and a "Merge" blocks are created. If I configure the blocks like that: Split: Split A/B, Route To "A 100" Merge: 0db / Center / 0db / Center / Normal / 0db I should have the same sound than the blank preset from the start right? It should go from the input, to the split block, 100% of the signal is sent on the A path, there's no block on it, then the merge is with everything center and 0db, the output should be the same as a blank preset right? ... but it's not the case. It's less loud. I recorded both to test it thoroughly (first recorded dry guitar, then reamping with straight path and then with the split/merge): with the split/merge blocks, there's exactly 3db less. Bug or feature? If it's a feature, can you explain it? :) Thank you.

Thanks for the changelog, it's good to see new effects (and new amps, but I care less about these ^^)... ... BUT, I don't want to sound like an always complaining unsatisfied customer, but I'm really disappointed about the fact that for users that upgraded from M13 to Helix, there's still some extremely useful effects missing like LoRes delay, or the Growler. Wouldn't these effects should be top priority so that M series users can "really" switch to Helix? I mean, I'm currently in studio so I don't care, I can have the M13 in an FX loop of the Helix. But soon I'll be doing gigs again, this is not a viable option as you can guess :) I know you can't probably say anything, but is there a chance these two particular effects will be coming soon?

A little question for someone at Line 6 (Digital_Igloo?): to power off the Helix, is it better to hit the on/off switch, or can we just shut the power? (My Helix is on a pedalboard with some other stuff, and I've got a "general" power switch for all the stuff on it. Is it not recommended?) Thank you.

Same here with a Moog EP-3.

It's not a bug but something wanted. I much prefer it that way personally. I believe there's an IdeaScale somewhere to have this choice as a global setting.

If I read your post correctly (I'm tired, so maybe not...), there's almost a workaround for that. We just have to be able to send several MIDI messages per footswitch. Then, MIDI cable from your Helix MIDI OUT to MIDI IN, and voilà . For now, we can't, but here's a link to vote for it: http://line6.ideascale.com/a/dtd/Several-MIDI-messages-per-footswitch/787480-23508 Waiting this, if by any chance you've got a computer near your Helix when you're on stage, you can use a software to do that (for example MIDI Bome Translator) that will allow to receive one single message and send back several.

Didn't manage to do that. If someone got tips...