Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by mritt

  1. "Not quite sure what to do besides give up hope for using 3.5 and reinstalling 3.1 until the driver problem is considered FIXED by Line6"



    I am sorry if I was unclear in my attempt to help you. You can still use version 3.5 with the drivers from 3.1. I've been using my Helix daily since the update without any problems. I think the driver is more of a hardware handshake/identifier than anything to do with using or creating presets.


     I hope I cleared up any confusion.


  2. On 12/18/2022 at 12:36 PM, Hey_Joe said:
    When I finally updated my HelixLT to 3.5 I had this same problem (Win7, 64 bit, SP1).
    The driver properties are shown as v.
    Cannot play audio from computer through Helix.
    Cannot connect to Workbench HD, or my DAW programs (Reaper, Audacity, RiffWorks).
    Also tried re-installing the full v3.5 update.
    I also had no issues at all prior to the update.
    I tried following the instructions offered by mritt  -
    control panel>device manager>sound, video and game controllers>right clicked, selected PROPERTIES >chose to ROLL BACK device drivers.
    Rollback button is grayed out, cannot select.
    IHHguitar and mritt...or any of the Helix gurus that hang out you have any ideas. 
    Have tried calling Line6 Support but haven't been able to get through yet.
    Any help will be much appreciated - thanks in advance (I hope).




    If I was having this problem, here is what I would do:

    -I would uninstall the helix software on your PC


    -install an older version of the HXEdit software 3.11 maybe

    -the new features of  3.5 on your Helix won't work, don't  worry we wont be using them.


    -it might be helpful to track down the helix drivers installed and copy and paste them into a backup folder

    -install the latest version of HXEdit manually or use the update thing in the right hand corner of the program


    -give it a test

    -if you have no desktop audio, do the rollback thing. Windows should have archived the previous driver. If it did not, then browse for the drivers I said to copy/paste into a backup folder.


    I hope this helps.






  3. I had a problem with win7 too. I could hear the sounds from the Helix but not my PC coming through the headphones.

    -I went to control panel

    -device manager

    -sound, video and game controllers

    -the line6 helix driver had a warning next to it, so I RIGHT Clicked on it and selected PROPERTIES

    -I then chose ROLL BACK device drivers

    -it reverted back to the 3.15 driver and everything works fine


    I hope this helps.



  4. On 11/5/2022 at 11:41 AM, ertromp said:

    Hi there,


    I just updated to 3.5. However, I still didn't do step 3 (factory reset) as I'm a bit confused.


    From the release notes I understand this (as of step 3-4-5):

    • At step 3: If I perform a factory reset, Helix will overwrite the current factory presets of factory 1 and 2 with the new factory presets that come with firmware 3.5? Is this correct?
      • For example, the "01A US Double Nrm" presets will be changed with some tweaks brought by the update 3.5?
    • At step 4: If I restore from back up, all the "new factory presets" will go back to the prior factory presets?
      • In other words, if I'm not someone that uses factory 1 and 2 presets (which I don't), this won't have an effect in my sound?
      • Also: why should I restore from backup? After I updated firmware 3.5 (i made a back up tough as required in the update), I can see all my user presets. So I'm not sure why I would need to restore from back up (If I don't intend to use factory 1 and 2 presets). Or also, after doing factory reset, I can instead just import my user presets right? No need to restore from back up, or am I wrong? Is this really required?

    If you can help me out with this confusion I have, I highly appreciate your help.







    The factory reset is just good standard practice to make sure their are no traces of the previous firmware still in your device that could lead to problems. It takes less than 5 minutes.


    When you restore from backup, you can choose to restore which banks of factory presets or user presets you want restored. It cam also restore your IR's, your favourites, global settings and preferences  etc...It takes about 30 seconds. Seems a lot easier than importing them all and fooling around with the hardware adjusting your preferences.


    Hope this helps.







    • Thanks 1
  5. 7 hours ago, codamedia said:


    This is not difficult to do yourself... providing you have a DAW. 

    • If you own Helix Native it is particularly easy... just insert it on a track and pump some pink noise through it. 
    • If you don't own native you need to route some pink noise through the Helix, then view the results in the DAW. 
    • Most DAWs can generate pink noise and will have an EQ or Spectrum monitor to view the results in. 

    I had to do this with the HD500 I owned prior to a Helix.... mostly because Line 6 got silly in the HD and most of the EQ's only had % values, you had no idea what frequencies you were adjusting let alone by how much. I'm into using my ears, but that was ridiculous :) 


    Thanks you for the excellent idea. I don't own Native but I will definitely try out the pink noise test today. That's a genius idea. I've been trying for months to figure out a way of generating a test tone for such an experiment. Thanks.





    Great advice, that's what I did to generate images of EQ responses in the book. The attached image is what I used to show how the Helix parametric EQ can affect the frequency response.


    However, if you want a really deep dive on EQ in general, check out the article Understanding EQ Curves – Why Identical EQ Settings Can Sound Different. I think you'll find the section that starts with "Enter the Noise" to be particularly useful. This is the kind of approach I would take in any update involving the Helix EQ.


    Thank you very much for the detailed info. That is exactly what I meant with my original EQ question.You have some fantastic bits of info in that article. I liked it so much, I just purchased the Helix book. Thank you very much!


    • Thanks 1
  6. Does the book do any deep diving on the EQ blocks? I'd like to see a graphical representation of what they do. For example, if I use the 10 band EQ block and boost 2khz by 8dB - is it a spike or a curve? I'd also like to see what the Q values of the parametric EQ look like. How wide is the range of frequencies affected by a Q=0.2 vs Q=0.9. This info would speed up my preset building and aid me in my crazy tone matching obsession :)


    Any info would be appreciated. Thanks.

  7. I'm hoping for:

    rev generator's fuzz channel

    a variac simulator or a plexi with a variac setting (l6 pod500)

    Schaffer Replica pedal

    better parametric EQ with visualization and without the limiting low mid and high settings


    A feedbacker would be nice. I currently simulate the effect using the pitch shifter at +19 maybe (I'm away from my helix ATM) and fade it into the mix with the pedal. When the pedal is up, its 100% dry guitar, and when fully depressed you get 100% of the +19 harmonic tone. I don't  get that long sustained feedback you would get with a cranked amp but I could also engage the sustainer effect if I needed it. I hope that helps someone.



  8. There are probably a couple dozen ways to do this without creating a pop sound during snapshot change. Rather than shutting off an amp and turning one on, think volume instead and you will have a smooth transition. Some examples:


    Use volume or gain blocks in front of the amps you wish to switch between.

    distortion snapshot

    input 1 =     pedal gain [0]  ---- brit plexi --- output

    input 2 =     pedal gain [-120]  ---- jazz rivet --- output


    clean snapshot

    input 1 =     pedal gain [-120]  ---- brit plexi --- output

    input 2 =     pedal gain [0]  ---- jazz rivet --- output


    or change the output levels

    distortion snapshot

    input 1 =    brit plexi --- output [0]

    input 2 =    jazz rivet --- output [-120]


    clean snapshot

    input 1 =    brit plexi --- output [-120]

    input 2 =    jazz rivet --- output [0]


    change a split

    from 100% A to the the distorted amp

    to 100& B to the clean amp



    Hope this helps.

    btw. I am away from my helix so the values may be wonky...







    • Thanks 1
  9. I'm away from my Helix at the moment but this is what I would do:

    Put a volume or gain block at the start your signal path. Set the level as low it will go.

    Assign the blocks bypass to a footswitch set to momentary so it only activates when you touch the switch. (silence when touching)


    I hope this helps.


    • Upvote 1
  10. Just to follow up with my EQ problem. Rather than being a corrupt preset I'm thinking it may actually be a bug. In my original first snapshot (top picture of my original post) I was able to set the 2kHz band to +2.3dB. Now, strangely I cannot use that value. I can slide it to +2.2dB or +2.4dB, but +2.3dB won't pop up as the value. If I try typing in +2.3 into that band it reads 2.2 after I hit enter.


    Perhaps in the new FW, the EQ doesn't accept certain values and when it encounters these values in a preset it pumps them to +15db. Hmmmm...




  • Create New...