Jump to content

Helix Bug Reports


HonestOpinion
 Share

Recommended Posts

Instant commands are not saved :

- in .hlx preset export file (so are lost when reimporting)

- when making a preset copy/paste from one preset slot to another.

 

Configuration : Hx effects, firmware 3.50, from boot (without reloading previous backup).

Creation of a new preset, with 2 snapshots

Declaration of 2 instant commands :

- IC#1 : Program change midi chanel = 1, prog = 2

- IC#2 : Control change midi chanel = 3, CC = 4, value = 5

Then IC#1 modified for snapshot 2 :

- IC#1 : Program change midi chanel = 1, prog = 7

 

In exported .hlx file (see below the whole file), only type of IC command is exported (19 = PC, 18=CC) :

   "commandInst1" : {
    "@command" : 19
   },
   "commandInst2" : {
    "@command" : 18
   },

Midi chanel, CC number and values are not exported

 

In addition, differences (here in IC#1) between snapshots are not exported in "snapshots" section of .hlx file :

   "snapshot1" : {

[...]

     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }

[...]

   "snapshot2" : {

[...]

     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }

 

 

-----------------------------

Here is the complete .hlx file :

{
 "data" : {
  "device" : 2162693,
  "device_version" : 55574528,
  "meta" : {
   "application" : "HX Edit",
   "appversion" : 50331648,
   "build_sha" : "3d6176f",
   "modifieddate" : 1668163552,
   "name" : "MyPreset"
  },
  "tone" : {
   "commandFS1" : {
    "@command" : 7,
    "@fs_customlabel" : "Switch Tip-GND",
    "@fs_enabled" : true,
    "@fs_label" : "Ext Amp",
    "@fs_ledcolor" : 7077838,
    "@fs_momentary" : false,
    "@fs_primary" : true,
    "@select" : 2
   },
   "commandFS2" : {
    "@command" : 7,
    "@fs_customlabel" : "Switch Ring-GND ",
    "@fs_enabled" : false,
    "@fs_label" : "Ext Amp",
    "@fs_ledcolor" : 462860,
    "@fs_momentary" : false,
    "@fs_primary" : true,
    "@select" : 3
   },
   "commandInst1" : {
    "@command" : 19
   },
   "commandInst2" : {
    "@command" : 18
   },
   "dsp0" : {
    "block0" : {
     "@enabled" : true,
     "@model" : "HD2_VolPanGain",
     "@no_snapshot_bypass" : false,
     "@path" : 0,
     "@position" : 0,
     "@stereo" : false,
     "@type" : 0,
     "Gain" : 8.99779
    },
    "inputA" : {
     "@input" : 1,
     "@model" : "HelixFx_AppDSPFlowInput"
    },
    "inputB" : {
     "@input" : 0,
     "@model" : "HelixFx_AppDSPFlowInput"
    },
    "join" : {
     "@enabled" : true,
     "@model" : "HD2_AppDSPFlowJoin",
     "@no_snapshot_bypass" : false,
     "@position" : 9,
     "A Level" : 0.0,
     "A Pan" : 0.50,
     "B Level" : 0.0,
     "B Pan" : 0.50,
     "B Polarity" : false,
     "Level" : 0.0
    },
    "outputA" : {
     "@model" : "HelixFx_AppDSPFlowOutput",
     "@output" : 1,
     "gain" : 0.0,
     "pan" : 0.50
    },
    "outputB" : {
     "@model" : "HelixFx_AppDSPFlowOutput",
     "@output" : 0,
     "gain" : 0.0,
     "pan" : 0.50
    },
    "split" : {
     "@enabled" : true,
     "@model" : "HD2_AppDSPFlowSplitY",
     "@no_snapshot_bypass" : false,
     "@position" : 0,
     "BalanceA" : 0.50,
     "BalanceB" : 0.50,
     "bypass" : false
    }
   },
   "dsp1" : {},
   "footswitch" : {
    "dsp0" : {
     "block0" : {
      "@fs_enabled" : true,
      "@fs_index" : 3,
      "@fs_label" : "Gain",
      "@fs_ledcolor" : 65408,
      "@fs_momentary" : false,
      "@fs_primary" : true
     }
    }
   },
   "global" : {
    "@DtSelect" : 2,
    "@PowercabMode" : 0,
    "@PowercabSelect" : 2,
    "@PowercabVoicing" : 0,
    "@current_snapshot" : 1,
    "@cursor_dsp" : 0,
    "@cursor_group" : "block0",
    "@cursor_path" : 0,
    "@cursor_position" : 0,
    "@guitarinputZ" : 0,
    "@model" : "@global_params",
    "@pedalstate" : 0,
    "@tempo" : 120.0,
    "@topology0" : "A",
    "@topology1" : 0
   },
   "snapshot0" : {
    "@ledcolor" : 0,
    "@name" : "Tune 1",
    "@pedalstate" : 0,
    "@tempo" : 120.0,
    "@valid" : true,
    "blocks" : {
     "dsp0" : {
      "block0" : true
     }
    },
    "commands" : {
     "commandFS1" : {
      "@fs_enabled" : true,
      "@fs_momentary" : 0,
      "@select" : 2
     },
     "commandFS2" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 3
     },
     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }
    }
   },
   "snapshot1" : {
    "@ledcolor" : 0,
    "@name" : "Tune 2",
    "@pedalstate" : 0,
    "@tempo" : 120.0,
    "@valid" : true,
    "blocks" : {
     "dsp0" : {
      "block0" : true
     }
    },
    "commands" : {
     "commandFS1" : {
      "@fs_enabled" : true,
      "@fs_momentary" : 0,
      "@select" : 2
     },
     "commandFS2" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 3
     },
     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }
    }
   },
   "snapshot2" : {
    "@ledcolor" : 0,
    "@name" : "",
    "@pedalstate" : 0,
    "@tempo" : 0.0,
    "@valid" : false,
    "blocks" : {
     "dsp0" : {
      "block0" : true
     }
    },
    "commands" : {
     "commandFS1" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 0
     },
     "commandFS2" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 0
     },
     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }
    }
   },
   "snapshot3" : {
    "@ledcolor" : 0,
    "@name" : "",
    "@pedalstate" : 0,
    "@tempo" : 0.0,
    "@valid" : false,
    "blocks" : {
     "dsp0" : {
      "block0" : true
     }
    },
    "commands" : {
     "commandFS1" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 0
     },
     "commandFS2" : {
      "@fs_enabled" : false,
      "@fs_momentary" : 0,
      "@select" : 0
     },
     "commandInst1" : {
      "@fs_enabled" : false
     },
     "commandInst2" : {
      "@fs_enabled" : false
     }
    }
   },
   "variax" : {
    "@variax_customtuning" : true,
    "@variax_lockctrls" : 0,
    "@variax_magmode" : true,
    "@variax_model" : 0,
    "@variax_str1tuning" : 0,
    "@variax_str2tuning" : 0,
    "@variax_str3tuning" : 0,
    "@variax_str4tuning" : 0,
    "@variax_str5tuning" : 0,
    "@variax_str6tuning" : 0,
    "@variax_toneknob" : -0.10,
    "@variax_volumeknob" : -0.10
   }
  }
 },
 "meta" : {
  "original" : 0,
  "pbn" : 0,
  "premium" : 0
 },
 "schema" : "L6Preset",
 "version" : 6
}

 

 

Link to comment
Share on other sites

On 11/11/2022 at 5:54 AM, VEVEF32 said:

Instant commands are not saved :

- in .hlx preset export file (so are lost when reimporting)

- when making a preset copy/paste from one preset slot to another.

 

Configuration : Hx effects, firmware 3.50, from boot (without reloading previous backup).

Creation of a new preset, with 2 snapshots

Declaration of 2 instant commands :

- IC#1 : Program change midi chanel = 1, prog = 2

- IC#2 : Control change midi chanel = 3, CC = 4, value = 5

Then IC#1 modified for snapshot 2 :

- IC#1 : Program change midi chanel = 1, prog = 7

 

In exported .hlx file (see below the whole file), only type of IC command is exported (19 = PC, 18=CC) : ...

 

You can use the 'File' --> 'Extract Files From Backup' command in HX Edit on an older backup, prior to the 3.50 update to compare and contrast export files from different points of time in your update process. I imagine you will want to ensure the MIDI information is available in these prior backups before doing a factory reset.

 

Another piece of troubleshooting I would probably do would be, restoring one of my pre 3.50 exported presets with MIDI commands, and seeing if the MIDI info comes with it. Also, goes without saying that I would confirm that the current preset that you showed in your .json sample actually saved on the device with the MIDI commands.

 

Did you do the recommended factory reset? You indicated you have not reloaded the previous backup. If you have not done either of these steps (make a backup first), that would be my first order of business once I established that my MIDI settings would also be restored.

 

Additionally, check in HX Edit under 'Help' --> 'About HX Edit' and make sure you have the 3.50 version of the editor. Not just the 3.50 firmware.

Link to comment
Share on other sites

It looks like the 3.5 factory setlist TEMPLATES is broken - the actual presets are shifted one preset back with relation to their titles in the preset list, as illustrated below: the first preset called "Quick Start" is not the actual "Quick Start" preset as it was in 3.15, but in fact it is the "Parallel Spans" preset. The actual "Quick Start" preset is missing. Next preset called "Parallel Spans" is in turn the actual "SNP:4-Amp Spill" preset, an so on. Not a terribly huge deal since you can always just restore 3.15 TEMPLATES from backup, but still looks like a bug. 

 

Capture.PNG.0a83041aaf392d1187d81c5f8003ea37.PNG1642784273_Capture1.PNG.dc188bba48a0cea29ff3b4714b82e35b.PNG

  • Upvote 2
Link to comment
Share on other sites

On 11/12/2022 at 12:47 PM, Txepa said:

0? Hola, por qué se me han bloqueado algunos efectos al actualizar 3'50?

jjjjjjjj.jpg

 

Hola,


Parece como si estuviera editando el Preset 01A y estuviera tratando de agregar un bloque de efecto Poly Shift. El efecto Poly Shift utiliza grandes cantidades de DSP, de hecho, podría ser casi la mitad de una ruta completa. Si desea albergar un efecto Poly, mueva los otros bloques hacia abajo en la ruta 2 dejando la ruta superior vacía; esto le permitirá obtener el efecto deseado. Si algo parece no estar disponible es porque ha agotado el DSP disponible. Nota: los efectos mono usan menos DSP.
Consulte la página 31 del manual del propietario de Helix para obtener más información.
https://line6.com/data/6/0a020a3f041b611d61cac763b/application/pdf/Helix 3.0 Owner's Manual - Rev F - English .pdf

 

Espero que esto ayude/tenga sentido

  • Upvote 1
Link to comment
Share on other sites

This is a new issue I started having after updating to 3.5

 

At home, I create my tones listening via the headphone out using the same IEMs I use live and everything sounds great and stereo works as expected.

 

When I play live, I use the stereo XLR outs. I played 2 shows this week and both times it sounded incredibly thin, almost out of phase, and there were problems with the stereo spread.
 

I’m running through an x32 mixer and everything is panned correctly, I’ve checked everything on the x32 and it’s definitely the Helix producing the issue. 
 

I tried panning the main output block on Helix hard left, and then hard right, which produced very interesting results. When I pan hard left, I get nothing on either channel. When I pan hard right, I get signal through both.


From that, I’ve concluded that the right channel is coming out of both xlr outs instead of left coming out of left, and right coming out of right. This doesn’t happen via headphone out.

Link to comment
Share on other sites

  • 2 weeks later...
On 11/26/2022 at 1:48 PM, tagmusenmagnus1 said:

Just updated to 3.50. 

The Line 6 Litigator can not change cabs in the new Amp/cab-block. When using legacy it is working fine.

 

Not seeing that on HXS or Helix Floor, using HX Edit or on the device.

Try a Factory Reset.

  • Upvote 1
Link to comment
Share on other sites

Hi there.

I upgraded to 3.5 and it seems I can no longer control the model of my Variax from the bypass control. As you can see in the screenshot below, I split my path A/B for electric or acoustic, assigned to footswitch 1. I also have a variax (preset) model assigned to footswitch 1.

 

The expected behavior is when footswitch one is disabled, the variax is set to spank-1 and the top route is selected (wah, dist, amp, cab). When it is enabled, it switches to the lower path (comp, gain, eq) and sets the variax model to acoustic-5. The model knob on the variax can override the set models, but they will always reset when pressing footswitch 1.

 

This was all functional before 3.5. Now the path switches, but the model never changes from what is set on the guitar knob. 

 

PpUdaRZ.png

 

Is there a new setting or something I am missing that is preventing the helix from setting the model?

 

Thanks

Link to comment
Share on other sites

On 11/28/2022 at 12:47 AM, dickmannma said:

Hi there.

I upgraded to 3.5 and it seems I can no longer control the model of my Variax from the bypass control. As you can see in the screenshot below, I split my path A/B for electric or acoustic, assigned to footswitch 1. I also have a variax (preset) model assigned to footswitch 1.

 

The expected behavior is when footswitch one is disabled, the variax is set to spank-1 and the top route is selected (wah, dist, amp, cab). When it is enabled, it switches to the lower path (comp, gain, eq) and sets the variax model to acoustic-5. The model knob on the variax can override the set models, but they will always reset when pressing footswitch 1.

 

This was all functional before 3.5. Now the path switches, but the model never changes from what is set on the guitar knob. 

 

PpUdaRZ.png

 

Is there a new setting or something I am missing that is preventing the helix from setting the model?

 

Thanks

 

Did you take a backup and do the factory reset and restore after your upgrade? If not, execute those steps.

 

In the Input block do you have 'Variax Settings' = "Per Preset" on the second parameter page?

Note: Once set in one preset it is set in all.

 

Btw, the following is a known bug in the 3.50 release notes

  • In some cases, the Input block's Variax Tone Knob setting is not recalled across preset changes

 

 

Link to comment
Share on other sites

Good morning all! I started having the following issue with my Helix ever since the v3.5 update:

I've been using my Helix (Rack) in 4CM with a Line 6 DT25 amp for about a year, also connected via MIDI to send messages changing preamp models, Drive level, and Channel Volume. It works great, sounds killer - love it all around. On Saturday Nov 19 toward the end of rehearsal I had a problem where the amp suddenly started emitting a loud "OOOOOOO", low-frequency feedback-type noise. I immediately shut it off and we ended rehearsal early. I dropped the amp off at my tech later that week but he has not yet tested it. Saturday Nov 26 we had a gig, and I played using the same setup with a different amp (I have three DT25s - one head and two 1x12 combos), and in the middle of our first set the same thing happened again. I shut off the amp and finished the set using just the Helix. At the end of the set I turned the amp back on and did a quick test, and everything was working fine. I went back to using the DT for the second set and had no issues. Last night I was playing (with the same DT25 head), and it happened a third time. Because this happened three times with two different amps in a span of 20 days, and the Helix was the common denominator in all three instances, we're starting to think that it is the culprit (if the DT25 combo passes bench test it will be an even more compelling indictment of the Helix). Only two things in my setup have changed prior to the onset of this behavior:

 

- I updated to v3.5 on Saturday Nov 5.
- I used to use separate Send and Return blocks to go through the amp (for no reason other than ignorance). I changed all my patches to utilize a single FX Loop block just to clean up the path, free up space, etc. That said, last night I changed all my patches back to separate Send/Return blocks, and the problem occurred again AFTER I had done this.
 
Per my amp tech: "The firmware upgrade may have loaded an error that's producing a random command to link an input and output which would cause an electronic feedback loop which would produce the howl. Imagine sticking a PA microphone directly in front of the cone of a PA speaker." What's weird is that this happens in the middle of playing - not immediately after making a patch/snapshot change, or something like that. That said, after a year of great, worry-free operation in this setup, followed by three instances of this issue in 20 days following the firmware update, I'm naturally suspicious that something in there is to blame. For now I've downgraded back to v3.15.
 
Any thoughts, similar experience, etc?
Link to comment
Share on other sites

On 11/30/2022 at 12:41 PM, Maksim19691990 said:

Hi everyone. Sometimes after turning on helix lt, the volume drops greatly. But everything is decided if you stick and pull out the cord of the guitar in.

Check Globals:EXP Pedals and see if your position might be set to snapshot or preset. That could easily cause what you are experiencing.

 

Link to comment
Share on other sites

Most-recent HX Edit and Rack firmware as of today.


Was building new presets in Set List 3 from scratch using HX Edit on a Windows 10 PC.  Set Lists 1 and 2 had existing presets that were brought in from a previous firmware version.  I did not copy and paste anything to Set List 3.  Set List 3 was all new.


Periodically, HX Edit would disconnect.  Clicking the reconnect button would not work.  I had to unplug the USB cable and then HX Edit would connect again.


The most-recent time this happened, HX Edit gave an error dialog box.


"Failed to get preset names."
"Operation failed due to DSP overload. [code -8611]"
"OK"


From that point, I could not access the presets in Set List 3.


I restarted the computer and got the same error dialog in HX Edit.


I restarted the Helix Rack and got the same error dialog in HX Edit.


However, now when I try to open Set List 3 on the Helix Rack hardware, Set List 3 now appears to be a copy of Set List 1.


No matter what, I'm unable to access Set List 3 from HX Edit.


It appears I will have to reset the presets on the Rack and reload my presets. (Fortunately, I had exported the majority of them and only have to recreate two simple presets.)


Before I do any type of reset, is there anything Line6 would like me to do?  I can wait a day or two before I have to get back to building the presets again.

 

I can easily be reached at the email address attached to this account.


Thanks!

Screenshot 2022-12-03 161129.png

Link to comment
Share on other sites

On 12/3/2022 at 11:19 PM, thedoctormo said:

Most-recent HX Edit and Rack firmware as of today.


Hi,

 

As of today the most recent HX Edit is v3.51, and the firmware still remains at v3.50. 
 

When you installed the latest firmware v3.50 firmware did you follow the release notes instructions to make a back up and reload your presets and global, settings? 
 

If you neglected to do this, then you may have issues because your presets may not have been updated to the latest Core system format, and/or your Global settings have not been installed, and gone back to the default settings.

 

Looking at the error code, my best guess would be a corrupted preset.

 

Hope this helps/makes sense.

 

Link to comment
Share on other sites

On 12/3/2022 at 5:55 PM, datacommando said:


Hi,

 

As of today the most recent HX Edit is v3.51, and the firmware still remains at v3.50. 
 

When you installed the latest firmware v3.50 firmware did you follow the release notes instructions to make a back up and reload your presets and global, settings? 
 

If you neglected to do this, then you may have issues because your presets may not have been updated to the latest Core system format, and/or your Global settings have not been installed, and gone back tonthe default settings.

 

Looking at the error code, my best guess would be a corrupted preset.

 

Yes, 3.51 and 3.50.

 

Usually after a firmware update, I do not restore a backup.  I make note of my global settings, export all presets to individual files, and update the firmware.  Then, I review and reset the global settings (and review any new settings) and import the presets.

 

However, in this instance, Set List 3 contained presets that were created from scratch in 3.50.  They were not imported from a previous version.

 

Set Lists 1/2 contain presets that were created with earlier firmware versions.  They imported without any issues.

 

Just one set list of about 15 presets is corrupt.  However, I can't even get to any of the presets in that set list to remove a corrupt preset.

Link to comment
Share on other sites

On 12/4/2022 at 6:08 PM, thedoctormo said:

Yes, 3.51 and 3.50.

 

Usually after a firmware update, I do not restore a backup.  I make note of my global settings, export all presets to individual files, and update the firmware.  Then, I review and reset the global settings (and review any new settings) and import the presets.

 

However, in this instance, Set List 3 contained presets that were created from scratch in 3.50.  They were not imported from a previous version.

 

Set Lists 1/2 contain presets that were created with earlier firmware versions.  They imported without any issues.

 

Just one set list of about 15 presets is corrupt.  However, I can't even get to any of the presets in that set list to remove a corrupt preset.

 

When you say "reset the global settings", do you mean you manually set them from "global setting notes", or you do you execute a factory reset? If you are not doing a factory reset after firmware upgrades - bad plan and it could easily be the cause of your issue. The factory reset needs to be part of your upgrade process.

  • Upvote 1
Link to comment
Share on other sites

Hello,

I have the following malfunction on HX-Stomp on "specific" presets (snapshot mode).

HX-Stomp: 3.5

HX-Edit: 3.51

But this occured since we were given command center.

 

"Specific" means having a preset change on fs2:

fs1: snapshot 1

fs2: preset xxx (switches to whichever preset)

fs3: snapshot 3

In command-center I set up snapshot changes to happen at press:

press: snapshot n

release: none

Despite those settings snapshot changes happen at release (not on press as intended).

 

When using presets with just snaphot changes (no preset change on fs2) then switching works fine (on press).

Something strange (with snaphot and preset-change presets): Sometimes it works as intended right after setting it up, but after a short while it is malfunctioning again).

 

I tried as well:

press/release (press: snapshot/ release: none)

press/release (press: snapshot/ release: snapshot)

press/hold (press: snapshot/ hold: none)

press/hold (press: snapshot/ hold: snapshot)

All with no succes, or just for a short time (same strange sporadic success).

But all in all no success.

 

Attached files:

R-FUZZ-S (snaphot changes on press doesn´t work, just on release)

R-s-S (snapshot changes on press work fine)

 

Could anyone check my attached presets and check if this can be reproduced?

Or better, fixed? 

If you need more information, please ask.

 

Thanks a lot!

 

 

 

R - FUZZ - S.hlx R - s - S.hlx

Link to comment
Share on other sites

On 12/4/2022 at 11:08 PM, thedoctormo said:

Usually after a firmware update, I do not restore a backup. 


Hi,

 

This is the probable cause of your issue. 
 

The Release Notes for the Firmware Update specifically states the factory reset, and restore from backup, are a required part of the update process.

 

The reset/restore are essential to ensure your presets are fully compatible with the new firmware. This is even more important with the v.3.50 firmware as there were significant changes to the Helix Core.

 

Hope this helps/makes sense.

  • Upvote 1
Link to comment
Share on other sites

On 12/5/2022 at 5:16 AM, datacommando said:


Hi,

 

This is the probable cause of your issue. 
 

The Release Notes for the Firmware Update specifically states the factory reset, and restore from backup, are a required part of the update process.

 

The reset/restore are essential to ensure your presets are fully compatible with the new firmware. This is even more important with the v.3.50 firmware as there were significant changes to the Helix Core.

 

Hope this helps/makes sense.

 

Good point regarding the restore. The setlist that is currently failing to load when attempting to import, may well succeed upon a restore. @thedoctormoshould have a backup, particularly if the upgrade was done from within HX Edit, as it is part of the editor's upgrade process. Another possibility per the recommendation to do the factory reset, is that it may allow the import of the setlist, unless it is corrupt.

 

@thedoctormoFollowing the release notes and just doing the backup, factory reset, and restore is the most trouble-free way to execute a firmware update. Winging it without a compelling reason has the potential to introduce complications. The factory/template setlists can always be unchecked during the restore to enable retention of the firmware version's new setlists/presets. Saving any presets in the current factory/template setlists the user wants to retain should be done before executing the factory preset. 

  • Upvote 2
Link to comment
Share on other sites

On 12/5/2022 at 10:42 AM, HonestOpinion said:

Winging it without a compelling reason has the potential to introduce complications.

 

Hi,

 

I'm not entirely sure that there could be a compelling reason not to follow the instructions. The process of updating will reset the Globals to default and the reboot/rebuilding presets is there to ensure that the presets are brought into line with the current firmware. This must be more relevant when there has been serious changes to the Helix Core. 

 

I have always been a rebellious type of person, but anyone who decides to ignore large sections of the "How to Update" instructions and then has issues that they describe as "bugs"... well, there is no help for them. As you have pointed out, after the update is complete and everything seems to function as expected, then you can be selective about when gets reloaded to the hardware. It's not complex and for most users it is a relatively pain free process. Ignore the rules and it becomes yet another "update bricked my Helix" post.

  • Upvote 2
Link to comment
Share on other sites

Привет!

У меня сборка ВИндоус 10 Хоум, поставил разные версии HX Edit, она не запускается ни при каких условиях. Пробовал ставить совместимость с 7 и 8 Виндоус, не помогает. Антивируса и защитника на компьютере нет, подскажите как заставить запускаться HX Edit, пожалуйста

Link to comment
Share on other sites

On 12/5/2022 at 2:50 AM, Elephantstomp said:

Hello,

I have the following malfunction on HX-Stomp on "specific" presets (snapshot mode).

HX-Stomp: 3.5

HX-Edit: 3.51

But this occured since we were given command center.

 

"Specific" means having a preset change on fs2:

fs1: snapshot 1

fs2: preset xxx (switches to whichever preset)

fs3: snapshot 3

In command-center I set up snapshot changes to happen at press:

press: snapshot n

release: none

Despite those settings snapshot changes happen at release (not on press as intended).

 

When using presets with just snaphot changes (no preset change on fs2) then switching works fine (on press).

Something strange (with snaphot and preset-change presets): Sometimes it works as intended right after setting it up, but after a short while it is malfunctioning again).

 

I tried as well:

press/release (press: snapshot/ release: none)

press/release (press: snapshot/ release: snapshot)

press/hold (press: snapshot/ hold: none)

press/hold (press: snapshot/ hold: snapshot)

All with no succes, or just for a short time (same strange sporadic success).

But all in all no success.

 

Attached files:

R-FUZZ-S (snaphot changes on press doesn´t work, just on release)

R-s-S (snapshot changes on press work fine)

 

Could anyone check my attached presets and check if this can be reproduced?

Or better, fixed? 

If you need more information, please ask.

 

Thanks a lot!

 

 

 

R - FUZZ - S.hlx 18.02 kB · 4 downloads R - s - S.hlx 18.43 kB · 0 downloads

 

I tested R-FUZZ. Fails as described. I'm going for corrupted preset on this one.

Load the attached preset Test SS Chng. This is a partial re-creation of the basic functions of R-FUZZ.

Note that the snapshots change on PRESS, as they also do on your R-s-S, so that can't be the problem.

I suggest that you try to re-create the preset from scratch. PITA, I know, but without spending my whole day troubleshooting every aspect of your somewhat complicated configuration, which works fine on your nearly identical R-s-S preset, I don't know what else to suggest.

 

 

Test SS Chng.hlx

  • Like 1
Link to comment
Share on other sites

rd2rk, thanks for joining the challenge!

 

I already re-created those presets with same results.

When using your Test SS Chng.hlx "linked in one direction" switching works fine.

BUT when you go back and forth between dedicated presets this malfunction comes up on your preset as well (at least on my system).

Could you please try the following:

In Test SS Chng.hlx: command-center, FS2: HX-Preset: 121 (or whatever you like)

Then create a new preset with just: command-center, FS1: HX-Preset: 120 (or wherer Test SS Chng.hlx is)

Now go back and forth between those presets and try if switching happens on press.

On my Stomp when I switch (within Test SS Chng.hlx) between snapshot 1 and 3, the switching happens on release when going from snapshot 3 to 1.

I got the feeling this malfunction just occures when presets are linked in both directions with command-centers HX-preset command.

You could as well try my attached files:

Test SS Chng on 120

Destination on 121

 

Thanks a lot!

 

Destination.hlx Test SS Chng.hlx

Link to comment
Share on other sites

On 12/7/2022 at 2:48 AM, Elephantstomp said:

rd2rk, thanks for joining the challenge!

 

I already re-created those presets with same results.

When using your Test SS Chng.hlx "linked in one direction" switching works fine.

BUT when you go back and forth between dedicated presets this malfunction comes up on your preset as well (at least on my system).

Could you please try the following:

In Test SS Chng.hlx: command-center, FS2: HX-Preset: 121 (or whatever you like)

Then create a new preset with just: command-center, FS1: HX-Preset: 120 (or wherer Test SS Chng.hlx is)

Now go back and forth between those presets and try if switching happens on press.

On my Stomp when I switch (within Test SS Chng.hlx) between snapshot 1 and 3, the switching happens on release when going from snapshot 3 to 1.

I got the feeling this malfunction just occures when presets are linked in both directions with command-centers HX-preset command.

You could as well try my attached files:

Test SS Chng on 120

Destination on 121

 

Thanks a lot!

 

Destination.hlx 3.21 kB · 1 download Test SS Chng.hlx 6.14 kB · 1 download

 

When I tried your presets I noticed that after testing the SS switches in TEST SS the "modified" status indicator worked as expected. After switching to DESTINATION and back, TEST SS loaded as "modified". The changes should have been discarded between preset loads.

 

I deleted your presets from my HXS and created a new one, then copied it, changing only the Preset switch so they'd toggle back and forth. The problem went away and the behavior was consistent as in my original test.

 

IDK what's happening, but it seems like something in your HXS modified my original Preset.

Try the attached presets and if the bad behavior recurs check your Global Settings>Preferences - mine are set to SNAPSHOT EDITS = DISCARD and SNAPSHOT RESELECT = RELOAD. These settings should NOT have anything to do with the problem, but MAYBE that's where the "bug" is coming from?

 

The presets are using103 and 104, change as necessary.

EStomp1.hlx EStomp2.hlx

  • Thanks 1
Link to comment
Share on other sites

Hello rd2rk,

(wrote r2d2 first...)

 

Your presets worked without a flaw.

(You´re suggested global setting changes made no difference).

I used them as a base to recreate my presets.

But after recreating the switching was buggy again.

But this time I found out what it caused and guess this is definetely a bug.

So...

In my old buggy "main preset" there were those commands:

 

PRESET A

FS1: Snaphot 1

FS2: Preset 101 (fancy sound)

FS3: Snaphot 3

 

PRESET B (Used for fancy sound due to limited blocks in HX-Stomp)

FS1: Preset 100 (for easy return to PRESET A)

FS2: Preset 100 (for easy return to PRESET A)

FS3: Preset 100 (for easy return to PRESET A)

 

I used all three switches here to just step somewhere to go back.

But exactly this brought up the bug.

More precise:
In PRESET B should be just one "Preset 100 (for easy return to PRESET A)" and it has to be on the same FS in both presets (like it was in yours).

Or at least it must not be on a position where a Snaphot is in PRESET A.

Otherwise it is buggy. 

 

Puh, can you follow? A bit tricky to explain.

More strange:

It only worked with your presets.

When I reduced my PRESET B to one return button, it could´t be fixed.

On the other hand, when I put three return buttons in your PRESET B the bug came up as well.

An stays, even though you correct it later.

Strange things...

 

Anyways, I used your presets as a foundation and fixed returnall my buggy presets (one return!).

Now I can switch everything on press (not release).

That´s so satisfying and on point changes happen in all my presets finally.

 

Thank you so much for your support!!!

 

 

 

Link to comment
Share on other sites

Hi

 

 

Hardware: Helix  stomp
Firmware/Editor: Firmware latest 3.50.0; HX Edit 3.51
OS: iOS 12.6.1 Mac mini
Global Settings: factory reset

Bug: after updating there is no processing of the signal. tuner works but no processing if you do not tune. Update was pretty fast not the mentioned 30 min. did a factory reset(press 2&3 and switch on stomp)
 

  1. switch 3 is flashing red
  2. if you hold for tuner, fine tuner comes up, signal is there, red light is on
  3. deactivate via switch tuner no processing, red light flashing
Link to comment
Share on other sites

Following 3.5 update on HX Stomp, the top encoder became very sensitive, for example when scrolling between blocks on a patch it would jump multiple blocks sometime move a block my just touching it. I did the full process including factory reset and restore. I did a subsequent reboot and seems OK, but based on a stomp FB group I am on, a few others have had this issue. 

Link to comment
Share on other sites

 

 

Glitch Delay seems to have changed its behaviour in 3.5

 

Hardware: Helix Floor, Helix Native
Firmware: Firmware latest 3.50.0

Bug: Glitch Delay 100% pitch setting does not function correctly when interval is set to +12

 

In previous firmwares when glitch was set at 100% pitch and intervals set at +12 (and+12) 100% of effected slices would be repitched to +12, even as the sequence reordered itself. Now the sequence introduces unpitched (+0) slices .

 

This only seems to happen at +12 settings, as any other interval (e.g +11) and expected behaviour happens (100% of effected slices are at +11)

 

I've tried this on both Floor and Native. 

Link to comment
Share on other sites

  • 4 weeks later...
On 12/5/2022 at 9:41 AM, danilkanice said:

Привет!

У меня сборка ВИндоус 10 Хоум, поставил разные версии HX Edit, она не запускается ни при каких условиях. Пробовал ставить совместимость с 7 и 8 Виндоус, не помогает. Антивируса и защитника на компьютере нет, подскажите как заставить запускаться HX Edit, пожалуйста


Check this out:

https://line6.com/support/topic/49342-hx-edit-281-and-helix-native-starting-with-with-a-blank-screen-and-crash/page/3/

Link to comment
Share on other sites

With Helix 3.50:

 

Quote
  • Encoder ballistics have been drastically improved. For example, tonestack values can go from 0.0 to 10.0 with one turn

 

This has also unfortunately changed the way scrolling works in general. When scrolling with the Magic Mouse on macOS, scrolling is unnatural and too fast. Can this please be fixed?

 

Edit: scrolling is NOT fixed in 3.51 — it is still too fast. There didn't need to be any update to the scrolling in Native as it has no hardware. Please, can you revert to how it was pre-3.50.

 

Another bug:

 

Every time I insert a new instance of Helix Native (within Logic Pro), the "Current Hardware Compatibility Mode" is not set to my default that I have set. As I am using a computer, I have set the Default to "Off", yet when opening up Native on a new track, it keeps going back to "Helix Floor/LT/Rack" instead of "Off [Default]"

 

My setup:

  • macOS 13.1 (22C65)
  • Helix Native 3.51

 

Edit as I was looking for the Helix Native build-number: I just clicked "Check for Updates" within Helix Native and there was an update (3.51)... is there no way of being notified of updates? This bug was fixed within 20 days of 3.50 being released, and I've been using an outdated version since. And, why is there still the 3.15 Update pinned on the main board? Why not have the current update pinned at the top?

 

Thanks for your time.

 

Link to comment
Share on other sites

On 1/5/2023 at 3:49 AM, noah2453980 said:

Edit as I was looking for the Helix Native build-number: I just clicked "Check for Updates" within Helix Native and there was an update (3.51)... is there no way of being notified of updates? This bug was fixed within 20 days of 3.50 being released, and I've been using an outdated version since. And, why is there still the 3.15 Update pinned on the main board? Why not have the current update pinned at the top?

 

Thanks for your time.


Hi,

 

First up, in here, you are preaching to the converted - There are no Line staff here and only very occasionally do they visit these forums - See the “sticky comment” in the black banner stripe at the top of this page entitled “Welcome to the Line 6 forums”

 

If you think that having the 3.15 Update pinned is bad, then go across to the Helix Native forum where the top pinned post is for the Helix Native 1.50 Release Notes last updated by Digital Igloo in January 2018.

 

The place where Line 6 staff hang out and sometimes respond to posts is over on The Gear Page (Digital & Modeling Gear) or the Facebook Helix Family group.

 

As for notification of the v3.51 update to HX Edit and Helix Native, regular forum contributor @HonestOpinion posted this on December 2nd 2022.

 


I realise that it seems like Line 6 just don’t care about these forums, but they have been rather busy providing some pretty slick updates to the HX range of products.

 

Hope this helps/makes sense.

  • Like 1
  • Upvote 1
Link to comment
Share on other sites

  • 2 weeks later...

Hi
I updated my Line 6 Helix to firmware 3.51. No problems during the update process.
But now when I look at the presets, for example the 01B Essecx A30, it doesn't look like it should. There is no amp and dual caps pre-installed. There is only one Amp&Cab combination.
Does anyone else have this problem?

thanks for your help

this is how it currently looks.jpg

how it should look like.JPG

Link to comment
Share on other sites

On 1/16/2023 at 2:41 AM, serge83 said:

Hi
I updated my Line 6 Helix to firmware 3.51. No problems during the update process.
But now when I look at the presets, for example the 01B Essecx A30, it doesn't look like it should. There is no amp and dual caps pre-installed. There is only one Amp&Cab combination.
Does anyone else have this problem?

thanks for your help

this is how it currently looks.jpg

how it should look like.JPG

 

It looks like you have the old factory presets still. In order to get the new ones, you need to de-select the FACTORY1 setlist from the backup when doing the Restore from Backup part of the update process (this would be after you do the Factory Reset). That way the new presets in that setlist will remain while all the other presets in your other setlist will get overwritten with whatever was on your your unit prior to updating.

Link to comment
Share on other sites

On 1/16/2023 at 7:13 PM, phil_m said:

 

It looks like you have the old factory presets still. In order to get the new ones, you need to de-select the FACTORY1 setlist from the backup when doing the Restore from Backup part of the update process (this would be after you do the Factory Reset). That way the new presets in that setlist will remain while all the other presets in your other setlist will get overwritten with whatever was on your your unit prior to updating.

 

Many thanks for your help. It solves my "Problem". Now it sounds the way I wanted it to and is a lot more fun to play the Factory Presets :-)

 

 

Link to comment
Share on other sites

hi there..

recently i updated my LT to firmware 3.50

then i controlling my guitar input pad via snapshot,the problem is sometimes the parameter is switching back to Global when i change snapshot.

does anyone here have same problem?

original state.jpg

revert state.jpg

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...