schweizt

All I can say is Helix Native is worth every dime. The recent updates (3.01, 3.10) are extremely useful if you have a studio. Yes, I was fortunate to buy it for $99 back when I got my Helix floor unit. I had no idea how useful it would be. Glad I spent the extra $99.

SOLVED. I did a fresh install (again) of Helix Native 3.10 on PC DAW #1 and it miraculously worked. Since I tried the same thing more than once the previous night, I can only guess something was stuck in memory (although I'm sure I rebooted - I don't think I was that dumb). The previous night, I did the firmware update for the Helix floor unit. Maybe something related to updating Helix Edit, the Firmware, etc., before installing Helix Native caused a problem. The problem is SOLVED. I don't have good advice for others, though, regarding how it got solved. I did start with a completely cold start of the PC tonight before attempting to install Native 3.10 over Native 3.01. Native 3.10 checked out fine in new projects and existing projects, so it looks stable. On a separate note, I do want to add I was very pleased that Line 6 finally changed the firmware update process, so all the backup, etc., work is done automatically with Helix Edit as part of the firmware update. It is now one pretty seamless process.

I still need to check. I decided to try my other PC DAW - PC DAW #2 (I have two PC DAWs), and Helix Native 3.10 runs fine with the DAW software on PC DAW #2. That is good news. So there must be an issue with how Helix Native 3.10 is getting installed on PC DAW #1. Again, the "old" Helix Native 3.01 installs (and even reinstalls) fine on PC DAW #1 and runs fine on PC DAW #1.

I can take a look. However, I tried Native 3.10 in 1) completely new projects, 2) existing projects that did not use Helix Native, 3) existing projects that did not have Native but then I applied it to an existing guitar track that was I knew was fine, 4) etc. I did not want to risk corrupting any existing projects that already had the older Native 3.01 being used. After installation, Helix Native 3.10 shows up fine as a VST3 plugin option, it just crashes the DAW when the plugin is "opened" and the screen returns to the Windows 10 desktop.

Thanks for the suggestion. I'm pretty sure it's something else. I am not using an SD card. The updated Helix Edit runs fine. The Helix floor unit runs fine using 3.1 firmware. The Helix Native 3.01 runs fine (after I uninstalled Native 3.1 and reinstalled Native 3.01). The "crash" is not a blue screen, etc. The "crash" is that the DAW closes and returns to the Windows desktop. I'm on a PC running W10.

My only solution so far is to UNINSTALL Helix Native 3.1 and reinstall the older Helix Native 3.01. It is critical that Helix Native works correctly, since I have a lot of songs with trax that use Helix Native. Other songs use trax with both Helix Native and trax recorded directly from my Helix floor unit. Please let me know the solution. It appears to be a cross platform (more than one DAW) issue.

Installed Helix Native 3.10 tonight. Helix Native 3.1 is crashing in Sonar Platinum and Cakewalk by Bandlab. Helix Native 3.01 ran just fine for months in both DAW programs. I have tried to load it different ways. If I drag Native onto a track, it shows up as an Effect. Once I click on the Helix Native Effect to "open" it, the DAW program closes. If, instead, I add Helix Native as an Effect in the track FX bin, the DAW crashes without even letting Native appear as loaded. In both cases, the DAW completely closes.

I solved the problem by uninstalling HX Edit. Then I reinstalled it. First, though, I think you need to restart your computer. HX Edit is probably running, so you can't uninstall. So, reboot your computer. Uninstall HX Edit using the HX Edit Uninstaller. You could reboot again. Reinstall the new HX Edit 3.0. **I would also suggest plugging the Helix into the PC before you start the install. Also have the Helix turned on. So you want a live connection before you run the install.

Having the same problem: I’m stuck on “firmware downloaded successfully”. Same problem on two different PCs. Any ideas?

No problem doing it directly on the unit, right?

Which reset is recommended after a firmware update? Reset Options #Helix Floor/LT Button Combination Description 2 LED light Fun 3 & 4 Test Mode 5 & 6 Global reset 7 & 8 Reset setlists to factory, Keep IRs 8 & 9 Reset setlists to factory, Clear IRs 9 & 10 Reset setlists to factory, Global reset, Clear IRs 10 & 11 Upgrades existing presets to latest format 11 & 12 Clear current preset 5 & 12 Clear setlists, clear IRs, Return system settings to default 6 & 12 Safe boot mode To use Reset Options: Power off the Helix Hold the desired button combination Power on the Helix Release the button combination Please note: Buttons are numbered from top left to bottom right.

I think your hunch about "HX Edit and USB/Computer/Helix memory communication" could be correct. I don't believe I had a "corrupt" preset. I was able to load all of the presets later successfully. They all work fine. The method I used initially, when I had the problem, was to drag the preset (actually a group of presets) from the Windows File Explorer window directly to the Helix. When I was dragging multiple presets, which worked fine for 95% of the files, a few of the presets did not copy correctly to the Helix, so the Setlist became corrupt. (I was copying a lot of presets, say 10 at a time, all to the same Setlist, with the intent of filling up all the slots.) So, one suggestion is to use the "Import" feature in HX Edit when importing presets. Avoid the drag and drop from File Explorer to be safe, especially with multiple files. Most of the time, drag and drop works, but the one time it does not work correctly will result in a catastrophe. It would make sense that there could be some type of buffer that has filled up that interferes with the drag and drop working correctly. Another suggestion, which I believe may be even safer, is to use "File->Import Preset" command in HX Edit. There is some chance that is cleaner than the Import button. Finally, I agree the safest option appears to be working directly on the Helix. I did use that approach at first to make some progress. That did become tedious, so I finally resorted back to using the laptop. I owned a couple POD 2.0s, an HD500, still own an HD500x, still own a Spider V, etc., so I am very proficient at "deep editing" using a computer. However, I am definitely proceeding with caution as I continue using HX Edit, especially to copy presets.

By the way, I could not load a backup. I thought that might overwrite the corrupt setlists. The fix? I ended up resetting the Helix (holding down switches 7 and 8 on startup). I then loaded various setlists to test them out. I was glad all the IRs were still there. I will eventually roll my own patches, but I've been using the downloaded patches to get a better understanding of the functionality of the Helix. I gained a quick understanding of the benefit of snapshots only because some of the downloads used them. There are also a few sounds I would not know how to create (e.g., I discovered one required 4 stacked effects). Hope my situation will benefit someone else in the future.

It will allow me to export the corrupt setlist now, with the error in the screenshot following the save process.

This is the error message if I attempt to copy and paste a preset into one of the corrupt preset areas in the setlist.