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


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by HonestOpinion

  1. On 4/3/2022 at 1:19 PM, Kellan707 said:


    Resurrecting this one. 

    I just got a helix LT and 5150 iconic stack. I contacted evh to try and figure out if their switching schematic is short-to-sleeve or not but the guy I talked to had to dig into it and said he’d get back to me. Haven’t heard anything yet. 

    being that the iconic has no midi on board, how screwed am I for switching channels on the amp using the helix? Can something like a disaster area midi/trs box fix this for me or am I totally SOL for switching channels with my helix with this head?


    Have no idea what the tip/sleeve combinations are for the 5150 Iconic, but I wouldn't go purchasing any additional hardware for switching until I had tried the 'Ext Amp' options for switching available from the LT's Command Center. The switching capability is already built into the LT if the amp has a compatible footswitching design. Probably best to wait for some info from Peavey support on the foot pedal's operation/schematic but if that is not forthcoming you could always try getting it working, proceed at your own risk(and under warranty :-).

  2. On 4/4/2022 at 10:29 PM, Webethumpin said:

    What is the fix for this issue? I just had this to happen to me (8212) like 3-4 times. I was able to shut down ,wait. about 30 sec and reboot and it was fine. It appears that if you switch between options too fast this is when it happened to me. I don't know. I have only had my un nit for 3 days now. I have not done any updates it already has 3:15 version. any help would be great.



    Although redundant the best advice has often proven to be - get a backup of as much as you can, export setlist by setlist, preset by preset if necessary, do a factory reset, restore backup. Best case scenario of course is if you have a successful previous backup.


    If that doesn't work, uninstall Line6 software, reinstall HX Edit 3.15(or latest version) and use it or the Updater to upgrade the firmware. Then rinse and repeat - get a backup, do a factory reset, restore backup.

    • Upvote 1
  3. On 4/5/2022 at 7:34 AM, coachz said:

    Thanks for the reply.  There seem to be a few issues. 


    1.  ToggleEXP isn't working on my stomp xl.  I can toggle footswitch 7 and getthe display to show Exp 1 Active and Exp 2 active.  But control of my volume pedal on Ring of my insert cable [exp2, fs8)  Never passes from the volume block to controlling the wah block.  All globals are set correctly.


    2.  Cc59 isn't supported in Stomp xl but only in helix.  This is really crappy.


    Having this tiny stomp xl and being forced to use 2 expression pedals is silly when a bit of code can fix it.


    It appears that the CC is working to toggle from EXP 1 to EXP 2. Our overall strategy is to use a footswitch to activate/bypass the wah, leaving the volume block active, and simultaneously send a MIDI message via loopback to switch between EXP 2 and EXP 1. However, switching the EXP is only part of the equation. You must also get the expression pedal to control the desired block(Vol or Wah). This requires the correct 'Position' assignments for the EXPs (at least on the Helix/LT).


    Little confused here by your mention of both "footswitch 7" in the beginning of your post and then you mention FS8 later, from this quote - "Ring of my insert cable [exp2, fs8)  Never passes from the volume block to controlling the wah block."  That sounds like an assignment issue right off the bat. The loopback method I detailed only uses one footswtich assignment for 'Bypass' to the Wah as the volume block is never bypassed.


    As I don't own the Stomp XL, unfortunately I can't test this. As I mentioned earlier this loopback trick was intended for the Helix/LT. However, if you are getting the EXPs to change properly that is half the battle. It may be just that the expression pedal 'Position' assignments are not assigned in such a way as to change along with the 'Bypass' state to the corresponding block - volume or wah. If you have not already, take a look at  the assignments list under the 'Bypass / Controller Assign' tab in HX Edit and recheck the assignments. If the behavior of the Stomp XL mimics the Helix or LT (maybe it doesn't?) they should look like the following:


    There should be three assignment entries only for both the volume and wah blocks - Wah Position = EXP1, WAH Bypass = FS7 (footswitch used in your example) and Volume Position = EXP2. Delete any other assignments for volume or wah blocks.


    Without having a Stomp XL to test on this is probably as much guidance a I can provide. The Helix and LT switch internally for the built-in expression pedal. There is no guarantee that the switching for the external pedal required for the Stomp XL will behave identically.


    Note: For any Stomp users that want to attempt this and don't want to track back through my old "MIDI Loopback Tricks..." post you will need to execute these two steps before trying this method:

    1. Set 'Global Settings' --> 'MIDI/Tempo' --> 'MIDI Thru' = "Off"          (This prevents runaway infinite loop MIDI funkiness when you are looping MIDI back into the Helix)
    2. Connect a MIDI cable from your Stomp's MIDI output and loop it back to your Stomp's MIDI input



  4. On 4/4/2022 at 12:35 PM, cfields69 said:

    Hi all,


    Does anyone have any help on this? I have just updated my Helix and HX Edit and everytime I try to import a new Preset or Past an existing one it crashes with this error message.


    Any one come across this before/know how to solve it?

    Screen Shot 2022-04-04 at 17.31.26.png


    Have you taken a backup, and then done the factory reset and restore, per the update notes? If not, this is likely causing the issue. If that doesn't solve the problem I would Uninstall the Line6 software and download and reinstall HX Edit 3.15. Also, did you update your firmware to 3.15? 

    • Upvote 1
  5. On 4/2/2022 at 8:46 PM, coachz said:

    It looks like midi loopback will solve my problem and then I can simply send the midi commands with each snapshot.  When I want wah or reverb mix or any param to adjust I'll just dedicate a snapshot to  it.



    On 4/3/2022 at 8:52 AM, coachz said:

    I have midi loopback and it works for PC from instant commands in command center but when I send Command = "MIDI CC",  MIDI Ch = "Base",  CC# = 59,  Value = 0 I get no change from my pedal controlling exp2 to exp1
    exp2 is volume and it just stays there even after sending the instant command.  Any ideas please how to get it to work ?

    I am not using a footswitch, just a snapshot that sends the instant command when chosen.

    Is this function supported in the Stomp XL ?


    Turning on the tuner works if I add 50ms delay oddly.....

    A CC68{value} command, sent with any value between 0 – 127, will toggle the Helix
    tuner on/off


    The joy of the Stomps are that they are so small.  Having to get a 2nd expression pedal is not desired here if at all possible.





    Not sure if the expression pedal switching method provided in the "loopback tricks" post works with a Stomp XL. It was intended for use with a Helix or LT. Maybe our resident MIDI expert @rd2rkcan weigh in on this.

  6. On 4/2/2022 at 8:46 PM, coachz said:

    It looks like midi loopback will solve my problem and then I can simply send the midi commands with each snapshot.  When I want wah or reverb mix or any param to adjust I'll just dedicate a snapshot to  it.



    Cool, haven't seen that post in a while. Wonder if there is a more elegant way to do it in the most recent firmware version?

  7. On 4/2/2022 at 3:11 AM, craiganderton said:

    Re hex pickups, being able to process individual strings is really theory. At one point Brian Hardgroove from Public Enemy and I had a band (EV2) that was just him on drums and me on the Gibson HD.6X Pro hex guitar. I had octave dividers on the lower strings so I could get bass along with chords, and standard magnetic pickups for doing leads. So it sounded like a lot more than two people. (Eddie Kramer called us "The Black and White Stripes," which I thought was kind of funny - there's a one-minute EV2 clip on YouTube, although it was from a fan's camcorder so you can't really hear the guitar's bass.)


    The guitar didn't sell well, although some subsequent Gibson high-tech guitars that sold reasonably well, like the Dark Fire, had hex pickups. However, there are several problems inherent in hex pickups:


    Crosstalk. It's very difficult to get decent isolation between strings and maintain audio fidelity. So if you're distorting a string, you're still getting intermodulation distortion from adjacent strings. The high and low E have less crosstalk, so they sound "different" than the four middle strings.

    Dealing with all those outputs. You can't run six audio lines out of a guitar without going insane. Gibson used a modified Ethernet-type connection (similar to the Variax), so the cable itself was svelte. The strings were multiplexed digitally. But this brings us to the next problem...

    Where do the outputs go. The HD.6X Pro cable terminated in a breakout box with 6 audio outputs. With EV2, these went into an audio interface with 6 audio inputs. All the processing had to be done in the computer, and I used six instances of AmpliTube. But changing presets and such for six channels was a real hassle, and with the laptops of those days, six amp sims just about brought the computer to its knees. I depended on running the magnetic pickups through a multieffects to create different sounds.


    Gibson's later polyphonic guitars multiplexed the audio down a standard stereo 1/4" cable that terminated in a Firewire interface. That eliminated the breakout box and all the audio connections, but...the interface was Firewire (which is pretty much dead at this point), and had a fixed sample rate of 48 kHz. So if you were into using 44.1 kHz, you had to do a sample rate conversion. Then there was the issue of not being able to aggregate it with other interfaces on Windows, and the last driver IIRC was for Vista.


    The hassles involved in poly guitar are what led me to using multiband processing, which avoided a lot of the problems and still sounds pretty cool. I would assume someone with schematics and a sense of adventure could create a box that would create six separate outputs from a Variax, but again, now that you have the six outputs, you have to process you'd need a Helix with six independent parallel paths, or a way to get those outputs into a computer. 


    My experience with guitar synthesis has been with the Roland GK pickups and a Godin guitar with a built in hex pickup. Both types of systems used the same cable for connection - the Roland GK cable (13 pin DIN MIDI).


    I started with guitar synthesis way back when Roland's first GK pickup became available. It was an aftermarket affair that had to be mounted either with screws(horrors) or adhesive to your guitar. You also mounted a clip to plug in the cable. Rather kludgy on the install, tracking was not great, and the cable while within the bounds of usability was still clunkier than a standard guitar cable. Tracking and mounting on later versions of the GK pickups got better but it still felt like blasphemy to mount those things on a quality guitar so they always ended up on one of my cheaper bangaround axes. My favorite implementation was the Godin which tracked well and had the advantage of being built from the ground up with the pickup properly and integrally mounted with an eye towards synthesis. That is the model I hope more guitars move towards in the future with a standardized and sleeker cable and jack.


    I was unaware of the crosstalk issues and I suppose that is something that would have to be resolved to improve the technology.


    I never attempted your more sophisticated use of multiple Amplitube instances and always used a Roland GR guitar synth, upgrading as new models appeared. That made for a fairly simple single cable connection from guitar to guitar synth, no breakout required.


    I can see where some of the potential processor overhead savings from not having to translate from a mono to poly signal when using a polyphonic pickup are simply moved over to, or even exceeded, by the demands that six separate streams place on the modeler/synth, but hopefully the hardware is moving in a direction where those demands can be handled.


    I understand that this is a pie in the sky hope to some extent, as @DunedinDragonpointed out, in that there may well not be enough market demand for guitar synthesis and polyphony to justify the extra cost to market them widely in the offerings from major guitar manufacturers. Add to that the fact that many instruments have remained pretty much unchanged for centuries and it is not a surefire recipe for seeing things leap forward any time soon. Still, it seems like it would be a natural progression as the modeling and synthesis worlds seem to be merging to some extent with the addition of polyphony to modelers. I hope that trend continues to the point where separate offerings of guitar modelers and guitar synths are no longer necessary. Polyphonic modeling and synthesis will be collapsed into a single device. Ideally this will be accompanied by a much broader choice of quality guitars fundamentally designed to be used with polyphonic processing and synthesis.

  8. On 3/28/2022 at 8:02 PM, JWinstrand said:

    firmware 3.15

    helix floor 


    when i add a wah to my preset the toe switch will only work while the usb cable is plugged into the unit. grrrrrrrr!


    any help would be appreciated


    Another user had a similar problem recently with the toe switch not working after upgrade to 3.15. He got it to work again by doing a backup, factory reset (press FS9 & FS10 on the Helix while restarting), and then restore your backup. Also make sure no cable is plugged into your EXP 2 input.

    • Upvote 1
  9. Enhancements to MIDI may be able to more faithfully and efficiently capture the nuances of how a guitar is played in the 2.0 standard. Hopefully this will include improvements that simplify or even automate MIDI setups. @craiganderton's posts have been particularly informative regarding the new standard. 


    Wanted to take advantage of the OP's topic title though to evangelize the piece of guitar innovation that IMHO has been lagging the most even if it has nothing to do with the subject of MIDI - pickup technology, or at least its implementation. We are seeing polyphonic processing finding its way into guitar processors. However, guitar pickups remain monophonic. That means that current polyphonic processing still requires algorithms that process the monophonic signal, make a best guess as to the fundamental frequency for each string, and then process it accordingly. This introduces processor overhead, latency, and tracking glitches; despite the fact that the current products on offer for doing polyphonic processing from a monophonic source do an impressive job given what they are working with.


    If guitar makers started offering more guitars with hex, polyphonic, pickups we might see a more rapid adoption of polyphonic processing in the guitar world with lower latency, better tracking, and lower demands being placed on the processor. For guitar players not using polyphonic processing those hex pickups could be summed. Polyphonic opens up a world of possibilities with its ability to process each string separately, and differently. It would seem that the guitar world should start moving towards making polyphonic pickups (and processing) the new standard.


    In addition to the obvious feature of being able to do advanced processing of chords properly, polyphonic pickups as a standard would enable every guitar to instantly dial up alternate tunings or apply different effects or parameters to individual strings. You could even do subtle and picky things such as micro-corrections on specific strings for tunings, allowing the player to correct for the inherent tuning and intonation issues caused by guitar physics or flaws or problems with neck and fret construction. The possibilities are endless.


    The closest analogy I can think of for the current state of affairs, is if the Hi-Fi manufacturers and record companies had persisted in producing monophonic equipment and recordings long after stereo had proved to offer a superior listening experience. It seems it is time to start moving towards more sophisticated pickup technology as a standard rather than an exception.

    • Upvote 1
  10. On 3/31/2022 at 8:07 AM, silverhead said:

    I believe the intent of the discount program is for Helix Native and a Helix device to be used in tandem. Understandably, Line 6 wants to discourage the practice of anyone buying a Helix device, claiming the Helix Native discount, and then immediately returning their device to the retailer for full refund. 

    So the status of the Helix Native license depends on the timing of its purchase and the subsequent sale of the associated device. I think you need to retain ownership of your Helix device for some time (180 days I believe) after purchasing Helix Native at the discounted price before your Helix Native license becomes permanently vested with your Line 6 account. Meanwhile the Helix Native license remains associated with the device.


    After that period you can sell your Helix device and you have the option to transfer your Helix Native license to the new owner, which of course means you can command a higher selling price. Or you can keep your Helix Native license and the new owner of the Helix device is unable to claim the discount. If you return or sell your Helix device during that period your Helix Native license is revoked (I.e. removed from your Line 6 account and  ‘given away’ in the language of Line 6 Support since the license remains with the device) and the new owner may claim the discount. Of course in practical terms Line 6 doesn’t know that you returned or sold your device; they will only revoke your license when the new owner registers the device with what used to be your serial number.


    It sounds like you may be wanting to sell your Helix device within the specified time period. Is that the case? If so your Helix Native license is not yet permanently vested with you; it remains associated with your Helix device. Accordingly you can sell your device at a higher price and use that to purchase a new discounted Helix Native license associated with your new HX Stomp.


    Alternatively you could keep your current Helix device until your Helix Native license is permanently vested with you, sell it later at a lower price, and not have to purchase a new Helix Native license when you get your HX Stomp. In that scenario a discounted and unused Helix Native license remains associated with your HX Stomp which increases its resale value.


    At least, that’s the way I understand it. Could be wrong.


    On 3/31/2022 at 5:43 PM, phil_m said:

    As mentioned above, you need to keep the hardware for at least 180 days in order to keep your discounted Native license. I believe if you sell or return the hardware before that, you have two options - pay the full price for the Native license or give it up.


    The 180 days is dictated by the fact that some retailers have return periods that long.



    Doesn't a 180 "vesting" period introduce a rather subtle risk to original owners when reselling their device? Let's say you resell your device within the 180 day vesting period, making it clear to the buyer that you are selling it without the Native discount - you intend to keep Native. The seller then transfers ownership of the resold device to the new buyer with Line6, and accidentally, knocks out the seller's Native license in the process. 


    So, let's say Line6 blindly applies the 180 day vesting period policy for Native, regardless of the deal struck between buyer and seller. Caution to anyone reselling their HX device within 180 days. Caveat Venditor if you own a discounted version of Native. Even after informing the new owner that you are selling your device for less because you are keeping your Native license, you could still theoretically have that license yanked out from under you according to the vesting policy. I would hope Line6 would have some sort of method to remedy or prevent this scenario but perhaps not. Maybe it is as simple as the original owner of the device not transferring the serial number for 180 days to the new buyer. Seems like that could get messy if the new owner requires a warrantied repair within the 180 days, or if the new buyer was unaware they needed to wait out the vesting period before fully transferring ownership.


    If the post by @silverheadand @phil_m accurately describe how the policy works, it means there is a risk of losing your Native license, whether you return your device to the store, or resell it within 180 days to a third party. It just would appear to make more sense for the vesting period to apply only to device returns, not reselling. So tricky to enforce for reselling. Btw, does the 180 day vesting period clock restart if the second owner buys Native with an unused discount? I would assume not, since the new owner can't return it having bought it on the resale market rather than from a store, or can they? They are still within 180 days. Anyway, happy to have been able to add to the confusion :-)

  11. You may want to uninstall your old Line 6 software first. Once you have HX Edit 3.15 downloaded and installed and have successfully connected to your Helix you will also want to get a backup and update the firmware to 3.15.  After the firmware is updated be sure to do a factory reset and backup restore. Follow the update instructions carefully.

  12. On 3/23/2022 at 11:14 PM, Thatguy7070 said:

    Just got my Helix and I’m trying to toggle between wah and volume using the built in expression pedal. Currently the wah is set to exp1, the volume exp2, and I can’t figure out how to switch between the two.




    Assuming that you have tried restarting the device and don't have any external expression pedals connected. As you just received your Helix you may want to double check your rear panel and make sure you don't have anything plugged into the 'EXP 2' jack just to be thorough. As @kduck advised, you'll want to test by pushing toe-down, quite firmly, on a hard surface to activate the expression toe-switch. No stomping required but stand up and put some weight on it.


    Just to be clear, couldn't tell for sure from the pictures, is the issue that it is not switching from volume to wah, or is it that it is not switching from 'EXP 1' to 'EXP 2' in the scribble strip? When functioning properly the scribble strip will highlight the selected EXP and dim the deselected EXP.



    Does this happen on all/any preset(s)? If the scribble strip is changing properly, you may just have an issue with your preset's assignments. If the scribble strip above the expression pedal never changes then you might have a hardware problem. However, before I opened a ticket with Line6, since you just got your Helix, I would probably try a backup, factory reset (hold down FS9 & FS10 upon restart for the Helix), and then restore backup.




    What version of the firmware are you on?

  13. On 3/15/2022 at 10:29 PM, adam79 said:

    Anyone having this issue? I'm using the latest version of Helix Native, 3.15, that supports Silicon.


    I'm trying it from an empty Project...I create one new track, select Helix Native (VST3) from the Plugin Browser and CRASH!


    However, I also have a template that loads an instance of Helix to one of the tracks, and this works as expected.

    From here I can copy the instance to other tracks as well.


    It's only when I try loading Helix from scratch that it crashes Reaper.


    I have the latest ARM version of Reaper, 6.41, and I'm opening it natively.


    Any suggestions?




    Have you rescanned for plugins after installing Native 3.15? After looking for attached peripherals that might be causing an issue, at some point I would probably try reinstalling Native and then Reaper if required. Blunt force approach I realize but without more insight into specifically what is causing the problem this is probably how I would initially try to resolve this. 

    • Upvote 1
  14. On 3/24/2022 at 11:49 AM, cfhmonkey said:

    If you have an iPad, check out the "OnSong" app:



    I never have to rearrange the setlists on my Helix. Can just do it all on the iPad once the songs are configured in the app, and can make new setlists for different shows by simply dragging and rearranging on my iPad screen. Huge time saver and I don't even need to be by my Helix or HX Edit to set up new shows.


    I'm also a big fan of this functionality!


    It works well and I have played around with this at home but not used it during performance for one reason.  It can be a little tricky to use if you are also a singer and are navigating a multi-page song. I have a tendency on occasion to accidentally stomp on my Pageflip MIDI Bluetooth pedal or double-tap it, and inadvertently switch to the next/previous song. Happens infrequently and usually no big deal if you are not switching presets via MIDI. You just tap back to the song and have the lyrics back in front of you. However, you have to be really careful not to do this when using Onsong to switch Helix presets as it can switch you quite audibly to another preset - right in the middle of a tune. Could be quite a bit more disruptive to your performance than just having a moment without the lyrics. 


    Still, MIDI via Onsong is a far superior way to manage setlists on the Helix and I may eventually overcome my reservations about the above scenario and start using it for performances. If you are rock solid on your Onsong song switches or don't have to worry about paging thru lyrics, it is a great way to leverage Onsong's MIDI and setlist capabilities. 

  15. On 3/23/2022 at 1:23 PM, cruisinon2 said:


    Oh that's never going away. Thank a lawyer...;)


    Yep, my guess would be their lawyer told them to retain login stats so when/if some litigious user decides to sue Line 6 for their house burning down, L6 can pull up the database and say, "nope", that user pulled up that warning 68 times since last January and decided to ignore it.

    • Upvote 1
  16. On 3/9/2022 at 4:46 PM, coachz said:

    That seems to be the "normal" way but I only want 1 pedal so if Helix can't accommodate a single pedal scenario I'll have to just dial in the max volume to the patch so I play with volume all the way up on that patch so WAH won't jump.   I was surprised the wah bypass Position, wait, behavior parameters didnt' allow me to turn the wah on and off with a single pedal.  It seems clear to me know that it is coded for 2 pedals.   I'll stick with one pedal and just adapt if no one else finds a trick.   Thanks !


    Something like an alternate toggle option to Active/Bypass on a Volume block would be helpful in accomplishing what you are trying to do. For example, , Active/"Bypass At Current Level"Either that or allowing the expression pedal assignment to change per snapshot.

    • Like 1
  17. On 3/9/2022 at 4:12 PM, coachz said:

    Thanks for the reply but if I leave the Volume block active then when I operate the WAH, the volume will be going up and down which is no bueno.  I only have one Dunlop DVP5 on EXP1


    I see your dilemma. Have to ruminate on this one. My best suggestion currently would be to add a second expression pedal. Which HX device do you have?

    • Like 1
  18. On 3/9/2022 at 4:00 PM, coachz said:

    I called Line 6 to ask for help on this but no one is available today (4pm EST).  I then tried to text and get an agent and got the same message that no one is available.  Can anyone here help please ?


    If you want the volume block to always reflect the position of the  expression pedal when you switch snapshots, set global settings --> 'EXP Pedals' --> 'EXP * Pedal Position' = "Global" for whichever EXP you are using the Volume block on.


    When you change snapshots make sure you leave the Volume block active. This combined with the "Global" setting above will allow the Volume block to follow your current setting on the expression pedal. Conversely, the second you bypass the volume block, the snapshot will revert to the equivalent level of the Volume block at 100%.

  19. On 3/9/2022 at 6:35 AM, datacommando said:

    I did say this place could use a “spring clean”, but this is frankly appalling.

    At first it would not allow me to login on my iPad, then when I eventually managed to get in, the interface is totally screwy. It almost unusable on an iPad in landscape mode, only slightly better in portrait mode. Surely, someone must have checked how this runs in responsive mode on mobile devices.


    From bad to worse, but at least there are no more “guru” tags, which seemed to upset some users. I guess we’re all equal now.


    Jeez, what a shambles!



    After eventually being able to make this post, I went back into the main forum, only to discover that I’m logged out there, but I can still return here and edit this post - absolute mayhem! Oh, yeah, anyone seen any emoji’s in here - though not!



    The redundant double icon with the vertical member's handle has got to go!


    Not only are the "Guru" tags gone but so are the easily visible reputation "Likes" count. Granted members shouldn't be posting just to gather up "Likes" but it seemed like they helped when it came to incentivizing forum members to spend time and effort responding to inquiries as well as testing and resolving issues. These new changes appear to show a less than an astute command of forum psychology. I wonder what their intention was here? They removed the slot machine from the lobby.


    Seems like a lot of changes that no one wanted. Hopefully this is a transitional phase while they "improve" the forum's configuration. Bring back emojis, add some upload space, have Line6 staff respond to technical issues here as they used to, and extend connectivity without requiring additional logins as much as possible! Now those are changes most everyone could appreciate.

    • Like 1
    • Upvote 1
  20. Just wanted to point out the 'Edit' hyperlink is gone but you can still edit a post using the three dots to the right of your profile name. I get consolidating several functions beneath one link, but personally I vastly preferred the old one-click 'Edit' link to this new two-click method. It also will probably make the 'Edit' function more difficult to find for newcomers to the forum.

    • Upvote 2
  21. As @silverheadindicated following the instructions will walk you through the update process. Just wanted to mention that after updating to HX Edit 3.15 you will need to update the firmware to 3.15 as well. Don't forget the backup, factory reset, and restore. There is also a 3.15 version of Native available.


    Btw, how are you restoring backups? I own a Helix and not a Stomp, but I believe the process is the same. You may want to try the 'Restore From Backup' command under the file menu in HX Edit rather than trying to import your setlist, as you indicated above. You may be able to recover your presets. The Restore.. command is what you use after an upgrade as it restores presets, defaults, favorites, and global settings. Good luck!

    • Upvote 1
  22. On 3/7/2022 at 3:23 PM, Kaintuck said:

    I'm lost.....I've used my helix floor as an interface for ProTools 12 for a year or so.  i updated the firmware to 3.15  2 days ago, restored my backup, and now if I try to open up an old ProTools session, it tells me that ProTools cannot initialize the ASIO helix and that it's not configured properly, then it crashes.  I can create a new session in ProTools and the helix works just fine, so this makes no sense to me.  I downloaded the latest driver to no avail, I went back to 3.11, which was my firmware before, and that also didn't help.  Has anyone else run into this issue?


    You say you restored your backup. Did you also do the factory preset before that by holding down footswitches 9&10 upon startup?  

  23. 19 hours ago, theElevators said:

    OK. I got a confirmation from Line 6 support that this is a bug.  Well, we knew it was, but just to know we're not crazy.  The new "behavior" behavior is buggy.  I dowgraded to 3.11 and will upgrade when this bug is sorted out.  To me, the new legacy synth sounds + a new amp are not needed. 


    The downgrade process was very simple.  I just ran the line 6 installer and selected 3.11. 




    "Behavior" behavior, lol. Yes, that choice of parameter naming led to a bit of redundancy in my posts detailing my test results. Were you able to submit a repeatable test case to Line 6? So far, I have not found one after admittedly limited testing in comparison to what I think is required to thoroughly QA this feature. From my limited testing I was able to get predictable results. Clearly others are not having the same experience. Would still like to have a better understanding of exactly what the issue is. As I mentioned in an earlier post, perhaps the bug is showing up under certain combinations of settings and presets. Testing this is beyond my scope and probably any single user's. Hopefully it will be resolved for everyone in the next update. Until then I am staying with 3.15, I can live with it.

  • Create New...