Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About sboggs71

  • Rank
    Just Startin'

Profile Information

  • Registered Products
  1. No solution, or workaround, yet. I have ruled out the possibility of this being caused by using Helix Floor/HX Edit at the same time as Helix Native, by using a different audio interface, opening the song, creating an empty dummy track, adding Helix Native to the new track, and trying to import a preset from "disk". Sometimes S1 will crash immediately at that point, but sometimes it will present the popup message telling you where the crash dump file is, which is what happened this time. Perhaps it is as simple as hitting a global memory limit for Helix Native (total guess, unsubstantiated). I have a plenty of memory, it would be nice to change this in settings, if this were the case. I am sure we are not the only ones this is happening to. Please let us know if you have any progress {:-). That would be fantastic.
  2. This didn't work for me, unfortunately. These are the steps I tried: I changed the setting (Studio One > Options > General > Enable High DPI Mode), which required a restart of Studio One to take effect, then immediately attempted to import a preset into Helix Native. Studio One closed immediately. The next thing I might try: use my Focusrite as an audio interface, instead my Helix Floor. Maybe using the Floor and Native at the same time causes some problem. I have a total of 9 tracks with an instance of Helix Native as an insert. CPU ranges from 67%-70%. Maybe importing a preset into Native causes a spike in the CPU to cause a crash? I am really not sure what the cause is.
  3. @SmackedActor Short answer: No. For some of my songs (the ones most "complete" aka "having more tracks"), Helix Native still causes an immediate crash when I attempt to import a preset. So far, the only "non-solution" that I have found: reduce the number of tracks with instances of Helix Native. But that doesn't help if you just want to transfer and use a preset from your file system (whether exported from Native, or your Helix Floor unit via HX Edit), so this is not a solution for the original issue: It (for me) is an easy problem to reproduce. Hopefully Line 6 will reproduce this, and address the problem. Please let us know if you find a more graceful way to handle this problem, or what works for you.
  4. Update: I have removed from one song many of the instances of Helix Native. This seems to have helped or eliminated the issue, though I have not fully tested this to have a sturdy confidence level. However, confidence is high. Will advise more, once I have had a change to really try to pressure test this a bit.
  5. More info, Presonus was kind enough to send me this from the .dmp file that Studio One created during a crash, followed by some advice: SYMBOL_NAME: Helix_Native__x64_+5d81eb MODULE_NAME: Helix_Native__x64_ IMAGE_NAME: Helix_Native_(x64).vst3 STACK_COMMAND: ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_Helix_Native_(x64).vst3!Unknown OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {dd8b278c-2608-b0e4-1a2a-4f6e89532dba} Followup: MachineOwner Looks like you are correct in that it is Helix Native. If this is an ongoing issue or is reproducible, you will want to contact Line 6. We have seen a few issues with Helix in recent days. See if they have an updated driver/software for the device. For general troubleshooting in S1, you can try re-installing the program as well as clearing your settings files. Go to Help>Open Settings folder. Copy the contents of the folder over to a folder on your desktop. Close S1 and delete the contents of the settings folder with the exception of the user.license file as well as the "Extensions" folder. Open S1 and go to Studio One>Options (Preferences on a Mac) to reconfigure your settings. Test to see if the problem is resolved. If it is not, please feel free to copy your settings files back over from the backup that you created in step 2. That was all from Presonus. This weekend, I will try exporting all my tracks, creating a new song, and dragging the tracks in (then re-organize them back into their folders/groups/VCO's/busses etc).
  6. Attempting to load presets works ok. Attempting to save presets to my Library results in a crash. I had been using using Helix Native with Studio One for a few months before this problem started (I think after I updated both Studio One and Helix Native around the same time, April 2020). Everything works fine, until I try to save a preset to my library. At first (like 5-8 times?) Studio One would crash instantly. Sometimes now, I get a Windows Alert message that says "An unexpected Error occurred in his Application or one of its Plugins! A crash dump has been created at ...". I have tried switching interfaces, from my Helix Floor, to my Focusrite interface. I get identical behavior from both. This does not happen in all projects. I have two projects (songs) with lots of tracks. One has about 45 tracks, another has around 100. On that one, only 7 tracks have an active instance of Helix Native. There are 7 tracks with the plugin disabled. I tried a couple of tiny 1 or 5 track projects, and was able to add presets to my Library. However, I had been able to save presets to my Library in the larger project previously, and I have reduced its size since then. I have a WIN10 i7-9750H 2.6GHz, 32GB 2019 Omen laptop. I am not using 50% of the RAM. Studio One 4.6 (latest), Helix Native 1.91. I don't think this is a hardware limitation. If this continues for a few more days, I am going to have to find another alternative. I need to be able to use the same presets between tracks and between songs. Any advice is welcome. Thanks in advance.
  7. The gateway to success is this tiny circle with the ellipsis (...). Click it. Search the manual for "Using the Preset File Menu" to understand these options. Manuals for different versions will have different page #'s for the same text. Import/Export is simpler, and separate, but I'm not covering that here.
  8. I finally got this to work. The solution was to reinstall the Helix driver. I did this even though I had the current version of the driver installed. Once I saw that it was the same version, I didn't even bother to uninstall the old one first - though Line 6 may have designed their installer to run an uninstaller first. "Line 6 Driver2 Helix v1.91 Installer.exe" was the file that I downloaded from Line 6. Cheers!
  9. Did you find a solution to this? I have just installed PreSonus Studio One, and am seeing the same message from the DAW, "The audio device Helix could not be initialized. Please check your hardware configuration and try again". I am able to connect to Audacity instantly, and send signal, so I have ruled out USB cable issues. Studio One sees and connects to my FocusRite Scarlett. On the Helix, I have the sample rate set to 44.1kHz, and preset output set to USB1/2. I am not sure what else to try, and I am pretty new to working with DAWs. Setup: Win10 i7-5500U @ 2.4GHz, 16GB RAM. Updated OS, updated StudioOne. I believe I have the latest driver for the "Line 6 Helix"
  10. I use a Spider Valve MK II 112 with an FBV Shortboard. I would like to add an FB1 expression pedal to control parameters other than volume/wah, such as delay mix, reverb volume, gain knob on overdrive, etc. I have the software for the Line 6 FBV Control. Is it possible to control parameters such as those I have listed? If so, is there a brief tutorial to get started available, or could someone post several steps to get started? I have searched, but am unsure whether this is even possible with the equipment I am using. Thanks!
  • Create New...