cruzfolmli

Ok so update. I left the base's usb unplugged all night (left transmitter in the device) - plugged the base back in this morning and now its a steady/pulse white on the base and it is all working. So recommend you try that.

I've opened up a line 6 support ticket so will update here for others with what they say.

I'm having the exact same issue (solid green transmitter pulsing red base). Followed the instructional video. Have updated the base twice.

Please vote on the ideascale if you would like to see it implemented :)

I think it would be pretty cool if the HX Stomp had the ability to bind Snap/Stomp, Stomp/Snap, Preset/Stomp or Stomp/Preset to FS4 or FS5 so instead of scrolling through the pages you can jump straight between modes. I've started an ideascale here - https://line6.ideascale.com/a/dtd/HX-Stomp-bind-modes-eg-Stomp-Snap-to-FS4-or-FS5/975080-23508?submitted=1

For those wondering - I received a response from Digital Igloo on thegearpage - They're all set up from the Command Center, so they won't apply to HX Stomp, at least not right away.

So getting back on topic - will the above apply to the HX Stomp or will it only be accessible from the Command Center (which the HX Stomp doesn't have)?

I often just leave my g10 plugged into my guitar, is this safe? Could it damage the guitar or the unit to leave it plugged in all the time (except when it needs charging)? Thanks,

Make sure you're using the latest version of helix.

Yes I use it. You need to Midi learn the snapshot index to a CC #. For example midi learn or set the snapshot index to CC #24 Send a CC #24 with a value of 127 it will change the snapshot index to 8. Once you confirm that is working set up another button with the same CC number as above (CC#24) but with a value of 20, it will change the snapshot index to 2 etc... So it will look like this: Button A = CC #24 Value: 127 Button B = CC #24 Value: 20 (you will need to make sure your foot controller lets you send a custom CC value and that the CC number is the same for both buttons) If you can't send a custom value the best you will be able to do at the moment is send a 0 (setting it to snapshot 1) and a 127 (setting it to snapshot 8).

I'm running through a focusrite scarlett 2i4 no issues at all.

I think you could even do a bit more in dimming especially of the text of the off blocks, but like massive improvement. Wouldn't think it would be too hard - I guess they will bundle a bunch of fixes together.

Yep I've voted for it, and it seems it's under review according to the site - should be a simple fix but something that is much needed.

If you're interested please upvote the idea: https://line6.ideascale.com/a/dtd/Helix-Native-Performance-Live-View/926104-23508#idea-tab-comments

Hi everyone, So there is a known bug with the new Helix 2.5 (Helix Native 1.5) mono reverbs. This has since been patched in the Helix 2.54 update (but not yet in Helix Native). So for those of you that didn't know - the bug makes the new mono reverbs (glitz, ganymede etc...) appear to have a really low mix/depth/wetness to them - making them almost hard to hear. So to fix this for now, make sure that you use your new reverbs in stereo mode (even if you run a mono set up). You'll instantly hear a much wetter sound. I've reported this bug for now.

You can do this now if you use Ableton (maybe other daw's too) and are able to customise the CC number and value being sent from your midi controller. There is a Snapshot Index control that you can map to midi. Sending a CC value of 0-15 is snapshot index value 1, 16-25 is snapshot index value 2 etc... or something similar you might need to play around to get the exact values 127 is snapshot index value 8. You can only bind 1 CC number to the snapshot index so you need to make sure that whatever you bind the Snapshot Index to, you need to set the CC Number to be the same across all buttons. Example: I have midi mapped CC 24 to the snapshot index. Button A (CC 24 Val: 1 = Snapshot 1) Button B (CC 24 Val: 24 = Snapshot 2) Button C (CC 24 Val: 127 = Snapsot 8)

Yep sure would hope so - I've emailed support with the bug also. What set up do you use?

I also sent through a bug request. Because the software isn't behaving how it should. I think the main difference is actually in the text of the block. Have a look here: In the first picture the on and off blocks have the same brightness to the text compared to the second picture (the helix editor) which has a much more dimmed text. I mean you can also clearly see how much more dim the blocks are (look at the Verb)

You map it to a midi channel not a switch. So say you map it to channel 24. Have switch 1 send CC #24 value: 1 then have switch 2 send CC #24 value:127 etc...

Is there going to be the fix for the new reverbs when on mono? This was fixed on one of the newer releases for helix. What happens is the volume of the reverb when it is set to mono is so small. When you set the block to stereo (still outputting as mono) the reverb is much bigger.

Any chance we could get a performance view that would make the window similar to that of a Helix Interface? Instead of 3/4 of the screen being for the editor? Would be good to full screen this part:

Yeah it's a massive issue. Take a look at this super blurry low res pic - I can easily see what pedals are off in it.

To midi map a volume pedal you need to: 1. Map the volume expression to a knob (example map it to knob 1) 2. Open Helix Native and choose the volume pedal - automation (choose position - and set it to knob 1)

I use Ableton and you can control the snapshot index with a Control Change (CC). The CC values are split up for the different snapshots. Example: 0-15 will set it to snapshot 1, and then so on so on (I think 16-29 is snapshot 2)...127 is snapshot 8