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


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by PierM

  1. On 1/28/2024 at 5:16 PM, ninecows said:

    To be fair for the OP. The USB 3 standard is more than 15 years old. To sell a product today that is (randomly or suddenly) incompatible with USB3 is not something that can be excused by writing USB2 in the manual. If it’s only guaranteed to work today with USB 2 it needs to explicitly say so in the manual and on the product page. Like: “USB2, but NOT USB3 compatible”. 

    I agree that using hubs and low quality cables etc is a different story. 

    Unless line6 specifically state that it will not work with USB3, people are not wrong in expecting it to work. Especially if it has been working for years. And they definitely don’t deserve to be flamed for assuming it would work. 



    The point here is that a USB audio interface is 99% using the USB 2.0 protocol (even if you'd set these consumer interfaces to their max rates, the final required bandwidth would be a fraction of a fraction of the 2.0 available speed) while USB 3.0 and 3.x are needed for high speed data transfer, like USB disks and anything else does benefit from an high speed bus.


    That said, a USB device that is only using the 2.0 protocol, should work with any "blue port" connected to a 3.x bus. It will end just using the bandwidth it does need, that's it. Isn't a different technology, just a faster bus.


    So, while it is true (and obvious, tech wise) that Helix (and any derivate) are USB 2.0, they shouldn't have any issue with a 3.x.


    As I said, I'm also using only 3.x ports, for both PC and Mac environment, and everything is fine.


    IME, these problems are random and hard do isolate/debug, and are more caused by what's being shared at USB Root level by the chipset, or cable lenght, or even power management. Could be the updater


    Im pretty sure that when you get that issue on a blue port, and then it works on a black port, isn't about 3.0 VS 2.0, but about what was being shared by that 3.0 port at Root level (single ports from the Root are pretty rare, especially in laptops, so they are often being shared with other ports, which means multiple calls at the same root level affecting polling, through an hub). 

    • Upvote 2
  2. On 1/25/2024 at 9:00 PM, silverhead said:

    I highly doubt it. It is not mentioned among the bug fixes in the release notes. I suppose I t’s possible that it is among the ‘Other minor fixes and improvements’ but you’d need someone who can test it to tell you. Looking at the description of the WIDI UHost I see it uses Bluetooth. The POD Go does not. So I expect there’s an approximately 0% chance that it’s ’fixed’ (which I think is a misnomer in the first place since I wouldn’t classify it as a bug). The POD Go uses MIDI over USB. It makes no claim to handle MIDI over Bluetooth.


    uHost is a BLE Midi Host that you can plug to any MIDI device or controller that has has a compliant USB port. This will give the device access to MIDI BLE. So isnt the uHost that has to talk with the Pod (which would be impossible since the Pod doesnt have BLE), but it's the uHost which gives BLE MIDI to it.


    I use it with my HX Stomp, awesome stuff.

  3. Just to remind you guys we are in 2024. Modern PCs and Macs, doesn't even use a USB 2 hardware root, so this isn't really the point. USB 3 ports they do auto run with 2.0 speeds when required by the device plugged.


    Point is these updaters are extremely sensible to many things, as basically everything coming from L6. :)


    Isn't always user error, sometimes it's just bad HAL from the companies.

    • Like 4
  4. On 1/23/2024 at 7:00 PM, poppa1 said:



    very very strange,


    The Line6 support wrote "At this point please test it with another computer".

    I have several removable SSDs, so I made a clean Win 11 SSD and installed Yamaha AG 06 with drivers, Helix Native and my DAW. Native worked properly. So the Computer or Hardware could not be the problem.


    I changed to my "normal" SSD, uninstalled Native and HX Edit 3.70, deleted all Line 6 folders and files, rebooted the PC, and then reinstalled first Native and then HX Edit 3.70.

    Native now works properly.





    There is nothing strange when it comes to Native licensing system, which is an utterly garbage by default... it's so unstable and sensible to any minimal system change that sometimes does throw that error from nowhere and you need to start doing random crap to your system until you get it working again. We are trying to find patterns and streamlining solutions over here, but every new version seems introducing more error variables and error randomness.

    • Upvote 2
  5. Hi,


    try uninstalling again, then go into the C:\ProgramData\Line 6 and look if you still have these folders;


    C:\ProgramData\Line 6\Helix Native and C:\ProgramData\Line 6\HelixCore


    If they are still there, delete them both with everything inside them.


    Now reinstall the 3.71 and see if it works...


    I got this same s**t on Mac, and solved deleting that HelixCore library, which seems a leftover from previous version.


    Seems they will never learn how to do it right...:/ 

    • Upvote 1
  6. On 12/8/2023 at 4:39 PM, fruijter7777 said:

    About Helix Edit and Helix Native:

    Why are there no (options to see) pictures of the amps and effects, like there are in Amplitube 5 and TONEX of IK- Multimedia.


    I own a Helix Floor and this would be more  joy and far more handy !!!


    Anybody knows a special reason for this flaw?


    Because the main UI is mirroring the LCD of the Helix, which doesnt have enough resolution or graphic power to render a patch with skeuomorphism sprites, as you can get with Amplitube or BiasFX and similars, which are meant to be rendered on a computer/tablet screen.



    • Upvote 1
  7. On 1/5/2024 at 3:16 PM, silverhead said:

    I believe he’s referring to the golden guitar pick that is displayed alongside a preset that was purchased in Helix Marketplace. It indicates that the preset is protected and needs authorization. Your Line 6 account knows that you own the asset (or not) so you need to login to your Line 6 account within Helix Native to gain authorization. If your Line 6 account does not reflect your ownership the preset cannot be accessed.


    Ah ok, make sense. Tnx for the explanation.


    Never bought a preset, never will, so didnt know that gold pick of death :)

  8. On 12/28/2023 at 9:10 PM, cruisinon2 said:


    It's anybody's guess of course... but in my experience, companies that wake up one day with a bug up their a$$ to "reinvent themselves", tend to regret it. Now where'd I put that bottle of New Coke? Lol...  They either go back to doing what they do best, or they end up in Chapter 11. Being one of the pioneers of amp modeling, I can't see them abandoning the market completely in pursuit of some untested gamble as their new "flagship" device. I doubt Yamaha would be on board with that sort of financial Russian roulette, either...


    Yeah, not saying I see them releasing a flying horse, but something more "multimodal" oriented, behyond the black box with a screen, buttons and a pedal archetype. 

  9. As a L6 product user/owner since their "day one", imho next flagship wont be a modeler at all, but something completely different and unexpected. I dont see them anytime soon scratching the barrel of the oversaturated modeling market.

    • Upvote 2
  10. Im also using the Capo and I cant get any of the problems above. Real time responses? Of course they are realtime, and latency is pretty good especially for small intervals. To me sounds like you are placing the pitch block in the wrong spot in the chain. 

  11. On 7/20/2022 at 9:07 PM, kmcnall said:



    I struggled mightily  with this problem, so I want to document it on a clean thread.   I'm grateful for those whio helped and tried to help with this issue.


    Problem:   After migration to a new Mac Studio using Migration Assistant, Helix Native crashed my DAW hard with any access of the Helix Native Plugin.   Attempting to load any project already using the plugin also crashed immediately.


    Ultimate Reason for Crash:   Helix Native's authorization process is not friendly to the Migration Assistant.   There does not seem to be a clean process for migrating to a new Mac.  I'm still unclear on exactly what happened and why.


    Ultimate Solution:     Completely uninstalling and reinstalling Helix Native.   There is not a clean way provided to do this.  The following information was provided by Line6 on what needs to be removed to completely uninstall Native and whatever data file was the actual culprit.  Please use due caution before using this procedure:


    Please look for and delete the following files:
    /Library/Application Support/Avid/Audio/Plug-Ins/Line 6/Helix Native.aaxplugin
    /Library/Audio/Plug-Ins/Components/Helix Native.component
    /Library/Audio/Plug-Ins/VST/Line 6/Helix Native.vst
    /Library/Audio/Plug-Ins/VST3/Line 6/Helix Native.vst3

    Delete the following folders:
    Folder 1:
    /Library/Application Support/Line 6/Helix Native/
    Folder 2:
    ~/Library/Application Support/Line 6/Helix Native/ - this folder is hidden by default. In Finder, from "Home" view, press Command/Shift/and Period to display the ~/Library folder. It will appear grayed out but able to navigate within it.

    Once completed, download and install the latest version of Helix Native.  When you relaunch your DAW and access the Helix Native plugin, you may ore may not be prompted to log in and authorize.




    Many tried to help me with this.  The tendency was to think my DAW (Digital Performer) was the culprit, so I installed Reaper and also tried to use Garage Band all with the same results.


    If Line6 was still providing telephone support, this would have been resolved much faster.   Ticket support with 3-day turnarounds is tough.


    I've made the following recommendations to Line56 to hopefully spare others this problem.


    1)  If Helix Native is not friendly to Migration Assistant, let users know this, and provide a working procedure.

    2)  Provide a complete uninstall program, with a means to save user data.

    3). Change the authorization process to avoid this problem.


    In the process of trying to resolve this, I did not run into a lot of people having this problem.   I don't know why they would NOT have the problem if migrating from one Mac to another, unless their strategy was to simply reinstall everything.    It may be that this occurrence was  an anomaly unrelated to the normal process.   


    I hope this might spare someone else the time and trouble.!


    Berst to all.





    Man, I have to thank you for this! Lost 3 hours of my day because of that lollipop L6 authorization issue. I didnt do absolutely anything, just started with the DSP error out of the blue after a reboot, and none of the various suggestions around here worked out. Was going to give up 'til I've found this guide which worked perfectly. The core point here, at least for me, was to delete the two Application Support folders and reinstall.


    Thanks again, and another big BOOOO for L6. Just hire better coders, jesus christ. I have a huge library of plugins from any kind of developer, and Native is the only one giving me these random problems (lost the count of how many DSP erros I've got since I use Native, and every time it's a different voodoo to solve it)

    • Upvote 1
  12. On 12/2/2023 at 10:30 PM, datacommando said:



    I had a confirmation of this being a “bug”, earlier in this thread, then later in an email from Support. Also, over on TGP, Digital_Igloo responded to another person asking about this issue. His reply was:- “Yes, there’s a bug. Will be fixed in 3.71. No time frame, but it should be soon.”


    The Glitch Delay is not something that I use everyday, but it is incredibly irritating to discover that it now malfunctions for no apparent reason. I will just avoid using it until the fix, as it is too much hassle for me to roll back for something I don’t rely on.


    Hope for a quick fix.


    I use it quite a lot, but in a very very subtle way, as it's less boring than a standard delay and if properly setup it can be a lovely sparkly ambient filler. I programmed sort of clone for the Zoia, but still rolled back my HX stomp for now. I did the mistake to jump into this firmware because I was interested in the new clean amp they added...

    • Upvote 1
  13. I confirm Glitch Delay is broken and that's fu**ing annoying. Seems like feedback is either 100% or 0%, so the block is pretty much unusable. When random stuff, unrelated to the firmware, get broken does lollipop me off as you never know if other blocks have been messed up as well, so it makes me nervous with all my own presets stability and consistency. Rolling back (AGAIN). 



    • Like 1

    On 11/30/2023 at 3:03 PM, datacommando said:



    I’m not sure where you got that idea, because they are available:- from the Downloads page for the 3.60 Firmware


    Compatible OS: Mac OS X, Windows 7, Windows 8, Mac OS Mavericks, Mac OS Yosemite, Windows 10, Mac OS El Capitan, macOS Sierra, macOS High Sierra, macOS Mojave, macOS Catalina, macOS Big Sur, macOS Monterey, Windows 11, macOS Ventura, macOS Sonoma


    Picked out in red to make them more obvious!

    Hope this helps/makes sense.



    Im pretty sure he's refereing to the OS tab in the main download section. That list of OS is indeed old as my a**.




    • Thanks 1
    • Upvote 1
  • Create New...