Helix Bug Reports

[Egery4]

 Similar problem.

[datacommando]

On 4/4/2022 at 10:02 AM, Egery4 said:

Help me please.  There was a problem. Version 3.11 was installed. After that, the settings were reset and version 3.15 was installed. The problem has not been resolved. Did a reset again and installed version 2.82. did not help. Now it costs 3.10.

143 B · 2 downloads

 

On 4/4/2022 at 10:05 AM, Egery4 said:

 Similar problem.

Hi,

 

You say that you installed the v3.15 firmware update, but you did not say if you followed the installation notes that state you should make a backup of your Helix prior to the update, then after it completes, you should perform a factory reset, and then restore from the backup.

 

In any situation where things do not work as expected, or you experience any other weird things happening with your hardware - perform a factory reset. If you still experience abnormal behaviour with the unit, re-flash the firmware and follow the instructions precisely.

 

Essentially you are dealing with a computer and software- it’s very rare that a software update will brick your hardware. It all lights up - quite possibly a it’s just a glitch!

 

Hope this helps/makes sense.

 

EDIT:

I have just seen your post in the thread where that video was originally posted. If you have tried all the usual methods to fix this issue, without success, then you need to raise a ticket with Support, as suggested in the other thread.

Edited April 4, 2022 by datacommando
Added comment

[Egery4]

I have reinstalled various firmware versions and reset several times. Line 6 support responded that they couldn't help me at the moment. What other options might there be?

[datacommando]

On 4/5/2022 at 4:28 AM, Egery4 said:

What other options might there be?

Hi,

 

Other options? Well, none here, this is a user group that deals with general minor issues.

In the other thread where you got the video, there is a response from “psarkissian”, who is a Line 6 service engineer, and he stated:- “Log a Support ticket in your account. That will have to be serviced.”

 

I cannot understand why Customer Support said they couldn’t help you at the moment. Their job is to support the customer. There must be more to it than that. That answer makes absolutely no sense at all.
 

Hope this helps/makes sense.

[Egery4]

Thanks! I hope they help me.

[Pinkmania]

also my Helix Rack (3.15 and on previous firm) sounds different random, though no level was changed. For 1 - 2 or three days is good, day after is bad. All comments previous are usefull! but i can't understand why that happens.

Anyone knows how to run an auto-test for its harware?
Thank you very much indeed.

[datacommando]

On 4/6/2022 at 2:03 PM, Pinkmania said:

also my Helix Rack (3.15 and on previous firm) sounds different random, though no level was changed. For 1 - 2 or three days is good, day after is bad. All comments previous are usefull! but i can't understand why that happens.

Anyone knows how to run an auto-test for its harware?
Thank you very much indeed.

Hi,

 

In any situation where things do not work as expected, or you experience any other weird things happening with your hardware - perform a factory reset. If you still experience abnormal behaviour with the unit, re-flash the firmware and follow the instructions precisely.

 

All reset options for your Helix Rack can be found here:

 

https://helixhelp.com/tips-and-guides/universal/reset-options

 

Hope this helps/makes sense.

 

[SaschaFranck]

Still getting these constantly. And once it happens, not only HX Edit craps out but the Helix itself is freezing in, requiring a reboot.

Never had this happen with any earlier FW version. I'm seriously considering going back to 3.1.

Fwiw, I'm on macOS Mojave.

[Pinkmania]

Thank you very much datacommando,

 

in the past I had already made factory reset also with previous firmware, but not reflash.
Today I have reflash and perform a factory reset before and after reflashing. Now It seems all good, I hope next days still remains stable.
Unfortunately for Helix Rack, see page you linked, doesn't show "test mode" for Helix Rack, Floor only. Even if is not explain what test perform.
Several keys if pressend before booting, show some misterious menu. I can't remember which ones, but I think avoid that can be dangerous.

I'll post a feedback if Helix remain stable.
Have a good day. Thanks a lot.

On 4/7/2022 at 12:13 AM, datacommando said:

Hi,

 

In any situation where things do not work as expected, or you experience any other weird things happening with your hardware - perform a factory reset. If you still experience abnormal behaviour with the unit, re-flash the firmware and follow the instructions precisely.

 

All reset options for your Helix Rack can be found here:

 

https://helixhelp.com/tips-and-guides/universal/reset-options

 

Hope this helps/makes sense.

 

 

[datacommando]

On 4/8/2022 at 3:12 PM, Pinkmania said:

Unfortunately for Helix Rack, see page you linked, doesn't show "test mode" for Helix Rack, Floor only. Even if is not explain what test perform.

Oops! I forgot that the Helix Rack doesn’t have the “test” feature- only the Floor an LT models. Even if the Rack had the test, I’m not sure if it would have helped your random audio changes.

 

Here is a link to a video which shows what tests can be done on the Helix Floor.
 

 

Glad you managed to get your Rack unit working properly. Have fun.
 

[Pinkmania]

On 4/8/2022 at 8:07 PM, datacommando said:

Oops! I forgot that the Helix Rack doesn’t have the “test” feature- only the Floor an LT models. Even if the Rack had the test, I’m not sure if it would have helped your random audio changes.

 

Here is a link to a video which shows what tests can be done on the Helix Floor.
 

 

Glad you managed to get your Rack unit working properly. Have fun.
 

Wow! You're very kindly.
I had forgot, but looking at that video, I remembered with previous Helix unit, who dealer changed me because encoder N° 5 didn't works just back at home, before coming back to shop I tried to push some keys at boot (not only encoder) . One of them, I can't remember which ones, sent LCD in the same screen shown in video, as You said It didn't help me. That feature is a test maybe for controls. No diagnostic!
So previous Helix was replaced at once by dealer. With new unit since last 3 year I avoid "dangerous experiments"! Multi reset and reflashing, for now, seems works ;)
Thank You.

[jaburke4]

FYI-Having same lock up issue with specific presets no matter which way I approach accessing them. I now have done all prescribed resets 'following directions' with the same fault. Though it seems that it might take a day or so before it occurs. Back graded to previous firmware 3.1 and have not had the issue occur on same preset. Going to support.  Note: When first occurred I had the issue with a preset I downloaded from the CustomeTone page. The last reset the issue has locked onto is a purchased preset from the MarketPlace which has never been a problem before.

[melodiusthunk]

On 3/11/2022 at 6:57 PM, canadianjamest said:

I have experienced this identical issue and am trying to work through it with a number of presets.  I have never experienced anything like this in any previous firmware versions. 

 

After doing some trouble shooting on my end, the only thing that worked for me was to open HX Edit to the problem patch, then also open the "Command Center".  I then would click on the button I was programing in Command Center, in my case it was button number 3, and I was programming it to select Snapshot #5 to that button in the "HX Snapshot" control menu of the command center.  

 

I would then select each snapshot using the dropdown menu/list at the top of HX Edit and I would see the snapshot assignment for that button change/revert back to "next snapshot" instead of Snapshot #5 that I initially programmed onto that button.  I would then manually change it from "next snapshot" back to "Snapshot 5" that I wanted on that button, then I would save the patch.  I would then select the next snapshot from the dropdown list at the top of HX Edit and continue to do that same process for each snapshot.  Once I did this the changes were saved on all the snapshots and the patch would work correctly.  

 

This is definitely a bug, or if not a bug, a severe unintended consequence to the new ability to stack snapshots on one button.

 

I have some work ahead of me to change a number of patches to get them to work correctly.  

I too have experienced this very same problem.  Thanks for posting a workaround, and I hope the Helix team sorts this problem in the next release.

 

Scott

[rd2rk]

On 5/21/2022 at 3:57 PM, melodiusthunk said:

I too have experienced this very same problem.  Thanks for posting a workaround, and I hope the Helix team sorts this problem in the next release.

 

Scott

 

It's not a bug, it's the way it works now. They might have done a better job of documenting it though.

[joanesinu]

With HX effects:

 

I think it is a bug within the 3.15.0 firmware. Firtst, I did a factory reset on the HX device. After that, the first thing I did was to change global settings for the "Exp Pedal 2" to Ext Amp. So that jack plug will go to the amp channel input jack. The problem is that whatever I choose in the settings for "Exp pedal 1" or "Exp pedal 2", only the "Exp pedal 1" works when changing amp channel. If I plug the cable on the "Exp pedal 2" plug in the HX nothing happens whatever the settings are. Can you confirm this? Thank you

[joanesinu]

On 6/13/2022 at 2:02 PM, joanesinu said:

With HX effects:

 

I think it is a bug within the 3.15.0 firmware. Firtst, I did a factory reset on the HX device. After that, the first thing I did was to change global settings for the "Exp Pedal 2" to Ext Amp. So that jack plug will go to the amp channel input jack. The problem is that whatever I choose in the settings for "Exp pedal 1" or "Exp pedal 2", only the "Exp pedal 1" works when changing amp channel. If I plug the cable on the "Exp pedal 2" plug in the HX nothing happens whatever the settings are. Can you confirm this? Thank you

I solved the problem.

 

I had a wrong configuration. To use the EXP pedal 2 output the Ext Amp has to be on the options of "2 None" "2 (Tip)" "2 (Ring)" or "2 (T+R)". I was using the "1 (Tip)". So, the number on the config screen indicates the output, the EXP pedal output number.

[GiancarloM74]

Floor: Nobody noticed if using the headphone output and setting the headphone knob to zero the signal is reproduced the same but only the left side?

 

[datacommando]

On 6/15/2022 at 8:34 AM, GiancarloM74 said:

Floor: Nobody noticed if using the headphone output and setting the headphone knob to zero the signal is reproduced the same but only the left side?

 

 

I just tested 2 pairs of headphones (Audio Technica ATH-M50x, and some cheapo Superlux HD668B) with my Helix floor. They work exactly as expected. Stereo all the way from loud down to zero. No change in balance between left and right.

 

Check your Helix with another set of good phones that you know work correctly. If it still happens clean the headphone socket with Electric Contact Cleaner. If you still have a problem with the left channel there may be an issue with the connection to the board and you may need a service engineer to check it out.

 

Hope this helps/makes sense

[natewan]

HX Stomp on v3.15
Snapshots are changing parameters that I have assigned to Midi CC commands and not as Snapshot parameters.

 

How I found the issue:
It happens with any parameter assigned to a midi CC# but I found it while trying to toggle a note sync on a delay between 1/4 and 1/8 Dotted. When I change to a different snapshot the note sync goes back to what that snapshot was saved as. This parameter was not assigned as a snapshot edit.

This happens with snapshot edit set to discard as well as recall. 

[rd2rk]

On 6/23/2022 at 3:04 PM, natewan said:

HX Stomp on v3.15
Snapshots are changing parameters that I have assigned to Midi CC commands and not as Snapshot parameters.

 

How I found the issue:
It happens with any parameter assigned to a midi CC# but I found it while trying to toggle a note sync on a delay between 1/4 and 1/8 Dotted. When I change to a different snapshot the note sync goes back to what that snapshot was saved as. This parameter was not assigned as a snapshot edit.

This happens with snapshot edit set to discard as well as recall. 

 

Very strange, and not necessarily MIDI related (I duplicated it with no MIDI involvement).

Have fun explaining this to support... :-)

[reetu]

On 4/1/2022 at 7:02 PM, ech0FX said:

Does anyone else has noises when using any Pitch changer preset? Doesnt matter if simple or poly-Pitch. If you down-Pitch even by 1 Semitone, i get a wobbly noise.

 

Use it for bass. You can hear it at lot in super low tunings but even from a simple D->C is noticable.

I was using the Simple-Pitch for Years now, but since 3.15 it makes those noises.

The lower the more noticable.

I logged here to see if anyone else is having the same issue and it seems that I am not the only one.

 

I have Pitch changer in the "first" block, actually noise gate is first but it is disabled/bypassed in both snapshots where wobbly noise happens. I use the pitch block for matching my guitar tuning to different songs and in the acoustic parts where reverb is enabled after pitch this wobbly noise is audible clearly, especially in open chords.

 

I have tested with different reverb blocks and they all produce the same wobbliness. It disappears when pitch block is disabled/bypassed. 

 

Settings for pitch block are: position=100%, Heel&Toe=-1, Mix=100%, Level=0.0dB

 

 

[phil_m]

On 6/30/2022 at 12:39 AM, reetu said:

I logged here to see if anyone else is having the same issue and it seems that I am not the only one.

 

I have Pitch changer in the "first" block, actually noise gate is first but it is disabled/bypassed in both snapshots where wobbly noise happens. I use the pitch block for matching my guitar tuning to different songs and in the acoustic parts where reverb is enabled after pitch this wobbly noise is audible clearly, especially in open chords.

 

I have tested with different reverb blocks and they all produce the same wobbliness. It disappears when pitch block is disabled/bypassed. 

 

Settings for pitch block are: position=100%, Heel&Toe=-1, Mix=100%, Level=0.0dB

 

 

I wouldn’t have very high expectations for using the pitch effects with an acoustic guitar…

[jliuuu]

Hardware: HX Stomp XL

Firmware: 3.15.0

Description: Global Settings -> Footswitches -> Snapshot Mode -> Toggle leads to glitched Stomp mode display when in Edit view

 

On my Stomp XL, the new Toggle option added to the Snapshot Mode global setting in 3.15 works great, unless I switch into Snapshot mode from within Edit view. If I do so, the display for Stomp mode gets messed up and seems to stay that way. The issue remains even if I toggle away from Snapshot mode and back to Preset mode; from there, switching into Stomp mode still gives the wrong display. The issue occurs regardless of if Stomp Mode is set to 6 Switch or 4 Switch in the global settings.

 

My best guess is that the issue is only visual, since the footswitches still seem to perform their functions correctly when in Stomp mode; it's just that the display is wrong. And as long as I never switch into Snapshot mode starting from within Edit view (i.e. just staying among the Preset/Stomp/Snapshot screens), the Snapshot Mode -> Toggle setting seems to work as intended.

 

So to recap how to replicate:

1. Enable Global Settings -> Footswitches -> Snapshot Mode -> Toggle.
2. Enter Edit view on any patch.
3. Switch into Snapshot mode (so that you see the four snapshots on screen).
4. Switch into Stomp mode (by pressing the Mode footswitch) and observe the glitched display.

Here is a video for clarity: https://streamable.com/7vtria.

 

Can anyone else replicate this? Thanks!

 

 

 

 

 

 

[VEVEF32]

Hardware: Helix  hx effects
Firmware/Editor: Firmware 3.15 HX
Global Settings: snapshots discard changes (recall)

Bugs related to midi :

1. No fw to midi out of midi in incoming sysex messages (yes there are otber pedals chained after the hx on my pedalboard which need configuration also)

 

2. When configuring each instant midi message (im) for each Snapshot, even when keeping the same type of command (eg. Prog change) for the same im number, but just changing the value for each Snapshot (cc value or prog change number), hx randomly applies/change this value to all the snapshots and not only to the current one. And yes, i'm saving the preset after each modification. Sometimes it works, most of the time not. I did everything : factory reset and just make 1 config, update to latest firmware... Always the same random behavior

 

3. How can I disable one im in a specific Snapshot ?  Of course no need if i only have 2 snapshots as hx des not resend the same im consecutively. Anyway if i have more snapshots, and navigating not always in the same order from one snapshot to another, it becomes necessary to disable some im for some snapshots.

eg :

im1 : pc midi 1 program 1

im2 : cc midi 1 cc 10 value x

Snap 1 : im1, no change in im2

Snap 2 : im1, im2 with value 1

Snap 3 : im1, im2 with value 2

how do i set im2 in Snap 1 to not change to any New value ? (When moving Snap 2 to Snap 1 or Snap 3 to Snap 1)

 

4. When updating the audio processing chain by eg. just adding a gain, most of the time all im of all snapshots are lost, which honestly have nothing to do with the audio processing itself.

 

Thanks

 

 

 

 

 

[rd2rk]

On 7/17/2022 at 8:37 AM, VEVEF32 said:

Hardware: Helix  hx effects
Firmware/Editor: Firmware 3.15 HX
Global Settings: snapshots discard changes (recall)

Bugs related to midi :

1. No fw to midi out of midi in incoming sysex messages (yes there are otber pedals chained after the hx on my pedalboard which need configuration also)

 

2. When configuring each instant midi message (im) for each Snapshot, even when keeping the same type of command (eg. Prog change) for the same im number, but just changing the value for each Snapshot (cc value or prog change number), hx randomly applies/change this value to all the snapshots and not only to the current one. And yes, i'm saving the preset after each modification. Sometimes it works, most of the time not. I did everything : factory reset and just make 1 config, update to latest firmware... Always the same random behavior

 

3. How can I disable one im in a specific Snapshot ?  Of course no need if i only have 2 snapshots as hx des not resend the same im consecutively. Anyway if i have more snapshots, and navigating not always in the same order from one snapshot to another, it becomes necessary to disable some im for some snapshots.

eg :

im1 : pc midi 1 program 1

im2 : cc midi 1 cc 10 value x

Snap 1 : im1, no change in im2

Snap 2 : im1, im2 with value 1

Snap 3 : im1, im2 with value 2

how do i set im2 in Snap 1 to not change to any New value ? (When moving Snap 2 to Snap 1 or Snap 3 to Snap 1)

 

4. When updating the audio processing chain by eg. just adding a gain, most of the time all im of all snapshots are lost, which honestly have nothing to do with the audio processing itself.

 

Thanks

 

 

 

 

 

 

1 - I'm pretty sure that sysex handling has never been a feature of any of the Helix/HX products. Since it has never been a feature it CAN'T be a BUG! If you would like to see this feature implemented in future FW versions, sign up on Ideascale and post your request there. SEARCH FIRST so as not to water down previous requests for the same feature.

 

Log in | Line 6 Ideas (ideascale.com)

 

2 - I have no such problems. While random inexplicable PARAMETER changes related to Snapshots have been reported and verified, the problems with Instant Commands (that's what they're called, not Instant Messages) that you describe are more likely user error. Sorry, I know you disagree, but if you start a thread in the Helix section asking for help with this specific problem I'll be happy to try and sort it out for you. The ins and outs of using ICs and Snapshots can be maddening.

 

3 - see 2.

 

4 - Again, I have no such problem, and this is the first time I've ever seen this reported. Start a thread in the Helix section and I'll try to help.

 

I've seen your post regarding the same issues with HXFX. I'll bet if we fix one, it will apply to both.

[datacommando]

On 7/17/2022 at 3:37 PM, VEVEF32 said:

sysex messages

Hi,

 

Got to agree with “rd2rk” in the post above.

 

Big clue - Helix family of products has never been able to respond to System Exclusive messages.
 

See the reply from Digital Igloo (Eric Klein, Chief Product Design Architect at Yamaha Guitar Group, Inc. / Line 6 / Ampeg) in this thread from 2017 - 

 

 

[natewan]

On 6/23/2022 at 10:46 PM, rd2rk said:

 

Very strange, and not necessarily MIDI related (I duplicated it with no MIDI involvement).

Have fun explaining this to support... :-)

Update on this:

 

I have been working with Line6 Support via email and the Support tech is very responsive. I gotta say I am very pleased with the prompt attention they are giving me.

 

The issue is still unresolved though. I just ended a Zoom meeting with somebody from Line6 so I could show them what I am experiencing. He told me he is still a little unsure as to what the problem is and will bring in some others at line6 for other opinions.

 

Hopefully we can work this bug out. 

[VEVEF32]

I would disagree with statement that "forwarding MIDI sys ex message from MIDI in to MIDI out has never been a feature claimed by Line 6". Go to user manual page 41 (Global settings > MIDI/Tempo) and you find the magic sentence : "MIDI thru : if you activate this parameter, MIDI out is acting as a MIDI thru and forwards ALL MIDI IN messages received on MIDI in" (translation from french version of user manual). It is exactly how the MIDI thru (from MIDI in to MIDI out) should behave: forwarding ALL messages from in to out. Fact is Hx effects filters some MIDI messages. Here it is sysex, but it could also be midi clock or whatever. When supporting this forward feature you have to forward everything, and not filter anything.

 

On other points I mentionned, I already opened a ticket for solving this, but unfortunately after making many tests requested by Line 6 support (firmware update, re-creating the issue on an empty device without reloading any backup...) and making image snapshots, line6 support was not able to help me... and ignored the issue closing the ticket.

 

Meatime I found a way to solve the issue, just in case some other people have the same problem :

1) in Hx editor, export just the preset (.hlx)

2) open it in a text editor, it's a JSON file

3) while all my Instant commands where really appearing in the Hx effects, it was not defined in the JSON file (how it was stored ?!? mystery...). So definitions generated by Hx Effects device were quite empty :

At file header, I had :

  "tone" : {

   "commandInst1" : {

    "@command" : 19

   },

   "commandInst2" : {

    "@command" : 18

   }, 

without any other definition, while there was some additionnal definition for the "working presets".

Then at snapshots definition section, I had (showing just one snapshot example) :

 "snapshot1" : {

    "@ledcolor" : 6,

    "@name" : "Lyrics",

    "@pedalstate" : 0,

    "@tempo" : 120.0,

    "@valid" : true,

    "blocks" : {

     "dsp0" : {

      "block0" : true,

      "block1" : true,

      "block2" : false,

      "block3" : false,

      "block4" : true,

      "block5" : false

     }

    },

    "commands" : {

     "commandInst2" : {

      "@fs_enabled" : false

     },

     "commandInst3" : {

      "@fs_enabled" : false

     }

    }

   },

As you can see, no parameters defined for each snapshot, rather an empty definition (and CommandInst1 was appearing in the Hx effects, while not defined at all in the JSON file).

 

It appears that most of the time preset export does not export the MIDI Instant commands parameters. So let's reconstruct it...

 

4) to update the file, add at the beginning of the file, just after the "tone" :

  "tone" : {
   "commandInst1" : {
    "@bank0" : 0,
    "@bank32" : 0,
    "@channel" : 0,
    "@command" : 4,
    "@current" : 0,
    "@program" : 0
   },  
   "commandInst2" : {
    "@cc" : 00,
    "@channel" : 0,
    "@command" : 1,
    "@value" : 0
   },

One section for each Command Instant you want.  Here you define the type of the command which will be used for each snapshot. Here is one example for a PC and another for a CC. The @command value defines the command type. It is PC=19 and CC=18 in some of my presets, and some other have saved PC=4 and CC=1. Seems that PC=4 and CC=1 works better in my case. Not sure why there is this difference, I suspect that there has been a firmware change and such values change... that would also explain the issue I face. In this section, I guess all values sets the default values for all snapshots if they are not re-defined in each snapshot.  If defined in one snapshot, each value overrides the default value (It's my guess, but I did not test it, so I prefer to make the default and each snapshot definition)

 

5) at the bottom of the file, in each snapshot section, modify the parameters you want to send for each command for this snapshot. eg :

   "snapshot0" : {
    "@ledcolor" : 8,
    "@name" : "Couplet",
    "@pedalstate" : 0,
    "@tempo" : 120.0,
    "@valid" : true,
    "blocks" : {
     "dsp0" : {
      "block0" : true,
      "block1" : true,
      "block2" : false,
      "block3" : false,
      "block4" : false,
      "block5" : false
     }
    },
    "commands" : {
     "commandInst1" : {
      "@bank0" : 0,
      "@bank32" : 0,
      "@channel" : 0,
      "@current" : 0,
      "@fs_enabled" : false,
      "@program" : 0
     },
     "commandInst2" : {
      "@cc" : 101,
      "@channel" : 3,
      "@fs_enabled" : false,
      "@value" : 0
     }
    }
   },

In this example, when selecting snapshot 0, Hx effects will send a fake PC command (not used)(in fact it will not sent the PC command when value is set to 0, see below) and a valid CC number 101 on midi channel  3 (0x02 sent). More generally when you want to disable an Instant command in a particular snapshot, set all values to 0 (or send it to a non-active midi channel...).

Note that while CC will send the right CC number indicated in JSON file (counting from 0 to 127), the PC will send a -1 value (counting from 1 to 128). So for example :

    "commands" : {
     "commandInst1" : {
      "@bank0" : 0,
      "@bank32" : 0,
      "@channel" : 3,
      "@current" : 0,
      "@fs_enabled" : false,
      "@program" : 14
     },

will send a MIDI message : 0xC2 (=PC on channel 2), 0x0D (PC=13).

For the PC, if you set the @program value to 0, the PC will be disabled for this snapshot and not sent to MIDI out.

 

5) save the file and reload it in Hx editor as a single preset, in the desired preset location.

 

Also note that when defining one Instant Command in a preset/snapshot, the IC type (CC=18 or PC=19) is mentionned in file header, but parameters are strangely not defined at all when exporting the JSON file. Anyway, adding it into the JSON file and re-importing it forces the Hx effects to take it into account... and store it correctly if there has been some saving corruption.

 

Again, I would have expected the Line6 support to ask me to send some hlx files to verify such preset saving bugs. They didn't... not very technical answer.

 

Anyway, hope this helps...

[rd2rk]

  

On 7/30/2022 at 8:54 AM, VEVEF32 said:

I would disagree with statement that "forwarding MIDI sys ex message from MIDI in to MIDI out has never been a feature claimed by Line 6". Go to user manual page 41 (Global settings > MIDI/Tempo) and you find the magic sentence : "MIDI thru : if you activate this parameter, MIDI out is acting as a MIDI thru and forwards ALL MIDI IN messages received on MIDI in" (translation from french version of user manual). It is exactly how the MIDI thru (from MIDI in to MIDI out) should behave: forwarding ALL messages from in to out. Fact is Hx effects filters some MIDI messages. Here it is sysex, but it could also be midi clock or whatever. 

 

Most guitarists don't even know what a SYSEX message is. Most MIDI users don't use them. Most who've used them have done so to transfer a configuration file from an editor to their FCB1010 (or the like) without any real idea of what exactly was going on behind the scenes and have learned the hard way that you need a proper dedicated MIDI Interface to do it as many of the cheap cable interfaces most commonly used to connect MIDI instruments don't pass the longer SYSEX messages. My iConnectivity MIO (more expensive) passes SYSEX no problem, I have two of the cheapies which, while appearing to be identical (treble clef branding), one passes SOME sysex and the other passes none. Go figure!

 

IOW - using SYSEX is a special case mostly used by SYNTH people who generally have a much better understanding of MIDI than most, ESPECIALLY guitarists. Helix is a GENERAL PURPOSE device specialized for use by GUITARISTS. Just as it is NOT the best Audio Interface, it is NOT the best MIDI Interface.

 

So, to be clear, Line6 really SHOULD change their manuals and marketing materials to state clearly that SYSEX (and "whatever") is NOT supported and that the Audio Interface has more latency than many dedicated Audio Interfaces would. There are FAR MORE Helix users concerned with the latency thing than will EVER care about SYSEX. But I agree, the documentation SHOULD be accurate.

 

Personally, I'd be interested in seeing you document the last part of the quoted statement:

"Fact is Hx effects filters some MIDI messages. Here it is sysex, but it could also be midi clock or whatever. "

I just tested MIDI Clock, and Helix (don't have HXFX) passes MIDI Clock from Reaper just fine. I don't have a touch sensitive KB to test that stuff with, so you MIGHT be right about that. Maybe you can test that? I've not encountered any filtering of the basic MIDI messages that most of us are concerned with - PC, CC and NOTE.

 

As for the rest of your post, it's great that there's someone out there interested enough in this stuff to take the time and make the effort to do the no doubt significant amount of work it took to come up with this stuff. There's probably someone out there who'll actually use it and be very appreciative. However, it will NOT be used by the average Helix user who bought the device to replace their tube amp and analog pedal board. To most of us that stuff is nerdy g0bb1edyg00k. :-)

 

EDIT: I just re-read your previous post. While I've not had the random value re-assignment issue you mentioned (I save each change) maybe I'm not really understanding how you're configuring things or what the actual problem is. Regarding disabling an IC message just assign the message to an unused MIDI Channel. This will of course reset the message so that it'll be re-sent in the other Snapshots. If that's a problem I don't know the solution. Maybe this is another request for Ideascale? I'll vote for it!

[VEVEF32]

Yes I agree sys ex messages are probably not the most used messages. But just take one exemple : all expensive strymon pedals, which are references among effects pedals, only use midi in and sys ex messages to configure the pedals (such as the Big Sky). No USB. So if you use a hx effects as a 'command center' to control downstream strymon pedals in midi Daisy chain, then you are not able to update the strymon presets with a pc connected to the hx midi in, unless you use an additional midi merger or play with cables (which is not very nice on a pedalboard).

[rd2rk]

On 7/30/2022 at 2:33 PM, VEVEF32 said:

Yes I agree sys ex messages are probably not the most used messages. But just take one exemple : all expensive strymon pedals, which are references among effects pedals, only use midi in and sys ex messages to configure the pedals (such as the Big Sky). No USB. So if you use a hx effects as a 'command center' to control downstream strymon pedals in midi Daisy chain, then you are not able to update the strymon presets with a pc connected to the hx midi in, unless you use an additional midi merger or play with cables (which is not very nice on a pedalboard).

 

I'm not sure what you're saying The HXFX has 5 pin MIDI connectors, USB is not required to CONTROL the Strymon pedals. However, CONFIGURATION and CONTROL are two different things. CONTROL, switching presets and whatnot, making simple parameter changes on-the-fly, the things that most users are concerned with doing using the HXFX does not require SYSEX, just simple MIDI messages. I don't use Strymon pedals, so I'm not sure what "CONFIGURATION" entails. I'm guessing that "CONFIGURATION" means making wholesale and/or permanent changes to the Strymon Presets which are then CONTROLLED using simple MIDI. I had a look at the MIDI Spec for the BIG SKY and it looks like you could do this with simple MIDI, routing something like a korg NanoKontrol to the HXFX and THRU to the Strymon, but I can see where this might be a PITA vs using SYSEX. I THINK that MIDIOX can send simple MIDI using a batch file, but that's not something I ever looked into.

[datacommando]

On 7/30/2022 at 9:33 PM, VEVEF32 said:

Yes I agree sys ex messages are probably not the most used messages. But just take one exemple : all expensive strymon pedals, which are references among effects pedals, only use midi in and sys ex messages to configure the pedals (such as the Big Sky). No USB. So if you use a hx effects as a 'command center' to control downstream strymon pedals in midi Daisy chain, then you are not able to update the strymon presets with a pc connected to the hx midi in, unless you use an additional midi merger or play with cables (which is not very nice on a pedalboard).

You may want to read this - it’s quite old, but useful.

 

https://www.dropbox.com/s/68uptvxviegpkgo/The Unofficial Helix MIDI Guide.pdf?dl=0

 

Hope this helps/makes sense.

[VEVEF32]

Thanks @datacommando. Inside there is a lot of information I also found in various forums, which is concatenated here and not being in the Hx user manual. Interesting info source :-)

 

@rd2rk, what I meant is that lot of MIDI devices are not connecting to PC with USB to configure device : presets content (audio algos chain), global settings, etc..., but rather use PC > MIDI in link to do this, like strymon pedals. For doing this, they use only MIDI sysex messages because those messages are the only one in MIDI standard which are proprietary and manufacturer dependent. So, if you want to configure a preset on a strymon pedal (not select but really define what is the preset), you can do it 1) directly on the machine or 2) do it on the PC using a dedicated software (like the Hx edit program). But in this case, preset configuration update don't go thru USB link but only thru MIDI link and using sys ex messages. That's why I said that every time you want to define a new preset on a strymon pedal using your PC you have to connect to the strymon pedal using a MIDI cable. And if your strymon pedal is after the HX effects in the MIDI serial daisy chain, then Hx effects filters all sysex messages and you cannot do it. You have to unplug the MIDI in of the first pedal after the Hx and connect your PC directly after the Hx effects. You can also use a midi merge to perform this. But really, sysex messages should not be filtered by the Hx effects because it can be used by many other downstream devices for their configuration.

[rd2rk]

I understand. When I want to send sysex to my FCB1010 I use one of the MIDI to USB cables I mentioned.

What I'm saying is that while It's inconvenient to have to mess with cables to send sysex to the device, it's not a regular day-to-day routine procedure (maybe for uber tweakers) and it's not something that L6 is likely going to be able to fix on the current generation of devices even if they wanted to. AFAIK it's a HW thing. It's not a bug though it may appear so due to the misleading documentation, and much as you believe that L6 should have designed it with this use in mind, it is what it is. The best you can do at this point is go to Ideascale and vote for the existing "feature improvement requests" (sysex has already been requested at least once) and maybe post a "future product feature" request.

[natewan]

On 6/23/2022 at 5:04 PM, natewan said:

HX Stomp on v3.15
Snapshots are changing parameters that I have assigned to Midi CC commands and not as Snapshot parameters.

 

How I found the issue:
It happens with any parameter assigned to a midi CC# but I found it while trying to toggle a note sync on a delay between 1/4 and 1/8 Dotted. When I change to a different snapshot the note sync goes back to what that snapshot was saved as. This parameter was not assigned as a snapshot edit.

This happens with snapshot edit set to discard as well as recall. 

This issue has been declared normal function.

 

It kind of makes sense but also does not make sense. When selecting how a parameter is to be controlled, a snapshot should not effect other types of controlled parameters (ie. a snapshot should not change a parameter set to be controlled by a Midi CC#). Other parameters that are not controlled do not change but then again they are not changed between snapshots. 

 

I added a request for Snapshot bypass for Parameters here:

https://line6.ideascale.com/c/idea/1049072

 

Kind of like Snapshot bypass on blocks but for individual parameters.

[LocoNerdGeek]

Possible bug in Vibe Rotary.

1. Speaker blend still bleeds the drum in even if horn is panned in 100%.

2. Speed is off. When I set the same parameters on Vibe Rotary, 122 and 145, the Vibe Rotary is significantly faster.

 

Edit: that is in Helix Effects, type chosen was Stereo. I did not tried mono

 

 

[ppoceiro]

Maybe a bug with the send and return blocks.

Or maybe it's already reported.

While building a preset to work with guitar, mic and IEM, I added send blocks for the gtr and mic outputs to connect to FOH.

And I also build a separate path for IEM using the input return 1/2.

As per viewing an excellent video by Richie Castellano where he goes over a similar preset, I also decided using the sends instead of the 1/4" or the XLR to go to FOH for a few reasons.

 

The bug itself happened when adding a Return 1/2 block after a Send 1 (or 2) block. Doing this I can spare the separate path for the IEM and get the same result.

All was good after adding the blocks. Everything worked and had sound from all inputs. After saving, changing presets and going back to the preset it was empty and sounded like just DI.

Turned off the Helix (Floor by the way, with the lastest firmware and no other bugs) and when I turned it on there it was. The preset was loaded like it was saved.

Changing again presets and going back, empty again.

 

I was able to change the preset and get the same result I wanted by adding the return 1/2 block in path 1 after another send block. All worked and cycling presets did not emptied the preset. More or less the same thing that I did in path 2 but no bug this way.

I wasn't able to reproduce consistently the bug. Happened in two existing presets consistently. Happened often when building a preset from scratch. And I was trying now with my other unit, a LT, and happened again.

 

Is this a known bug? Can any of the experts around take a look?

Should I open a ticket?

I'm attaching a couple of pics of the screen with a simple test I did yesterday on the Floor unit and the preset I was working now on my LT that exibit the same bug when adding the return and send blocks (in this case the mic input was replaced by Variax but the result is the same).

KIM@MIC_bug.hlx

[52dmk]

Bug in 3.5 FlexoVibe.

Rate parameter does not have option to change to note subdivision in HX edit, but can press knob on Helix floor to change Rate to note subdivision. This then breaks link between HX edit and Helix floor, with changes made to Rate on HX edit not affecting Rate on Helix floor, and changes made to Rate parameter not changing knob position in HX edit.

Pressing Rate knob on Helxi floor returns Rate to numbered speed and allows HX edit to control Rate parameter again.

Same behaviour occurs for mono and stereo versions.

[52dmk]

Also finding same behaviour with 4-Voice Chorus

[jdomine]

On 11/4/2022 at 5:34 AM, 52dmk said:

Bug in 3.5 FlexoVibe.

Rate parameter does not have option to change to note subdivision in HX edit, but can press knob on Helix floor to change Rate to note subdivision. This then breaks link between HX edit and Helix floor, with changes made to Rate on HX edit not affecting Rate on Helix floor, and changes made to Rate parameter not changing knob position in HX edit.

Pressing Rate knob on Helxi floor returns Rate to numbered speed and allows HX edit to control Rate parameter again.

Same behaviour occurs for mono and stereo versions.

 

Good find. I have logged a bug for this and the 4-Voice Chorus. Thanks for reporting it!