PierM

You need a Zoia... :P

..jokes aside, would be great if they would add basic LFO and ENVELOPE/RAMP modules as modifiers. You could link any parameter from any block, and add automation like the one you asked.

On 2/10/2025 at 8:49 PM, urlordfu said:

And this is what seems to be the 2025 version of what Roland/Boss think of as a Variax. The VG-800.

If it sounded even remotely close to what a Variax with Helix sounded like, I'd be thankful. But it sounds horrible (to my ears) and just does not scratch the surface of what the Variax already is. I think it's that maybe Roland did not get the proper licensing to build on the custom tones. With the proper IR tied to a piezo pickup it would seem that the cat is out of the bag and now it's just up to one of the big names to run with this in a way that won't break the bank.

 

 My gosh...so much talk from that guy, so much expectation...then sounds garbage, and back to talk. Yikes...

I use these, and they works all great. The 770 sounds a tad weak because I have the 250 Ohm version.

1. Shure SRH840A
2. Beyerdynamic DT 770 PRO

3. AIAIAI TMA-2 Studio Wireless+

It will never happen.

Hi,

Widi Master and Widi Jack are fully compatible with any HX device. Widi Master will take power directly from the Midi Out port.

UHost doesnt work due a code wall in the firmware. CME asked L6 to fix the issue, but it will never happen.

There is no (yet) BT headphone available in any similar device in the market as the latency would make the experience miserable. :) 

Isnt about signal loss...but about doubling the risk of signal drops and glitches due a busy wifi channel.

On 8/15/2024 at 10:15 AM, SaschaFranck said:

 

Why not? It's working absolutely fine for me.

Because the fx loop stacks another "layer" of noise as is, so any overdrive pedal it's pulling this noise up into the signal. Experience may vary, but I believe it's a well known issue with these loops.

This is the exact topic of this thread :D 

On 8/15/2024 at 2:25 AM, ech0FX said:

Yea running the Loop after OD/SD/AMP works great. no noise at all. Only putting the FXloop Block infront on an HX OD or SD without any pedals hooked up to it you get white noise like hell.

For me the FXloop is pretty much unusable if i want to hook up an OD as a boost pedal

Imho you should not put any Fuzz/OD in the FX Loop, nor any other pedal that is supposed to drive and boost a signal. That's a rule I personally follow since day one, and I do really believe it's related to I/O circuits at the ports, so nothing you can change software side. Even the most clean clone of Klone pedal I put the in the Loop sounds noisy, and also it does work differently then when it's running in front (as it should, imho).

Personally, the only real downside of the loops, is they do suck a bit of tone, which is most evident with clean sounds, but it's always a compromise I guess. :)

EDIT; added "IMHO" to prevent sensible people to feel offended.

Im running an entire pedalboard filled with pedals in the FX loop (of course no gain, those are either coming from HX or BEFORE the HX main input) and always worked great. Of course the more AD/DA you stack, the closer the noise floor....but nothing to call home about.

On 2/9/2024 at 6:55 PM, davepat76 said:

It was specifically the HX stomp I was looking at. I know it has something called "parallel routing", but not sure about dual processors.

 

If you need just few effects per channel you could try this

With the HX Stomp isnt possible because you can only have a single stereo path, as you only have a single DSP. As Silverhead said, you could with the big brothers, LT and Floor/Rack.

(you could split the input and re-merge at the output, but DSP isnt powerful enough, so all you can do is a bunch of FX)

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). 

The HD500X is a legacy product since 2021, which means no longer receives updates for modern OS.

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.

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.

On 1/23/2024 at 7:00 PM, poppa1 said:

Hello,

 

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.

 

Greetings

 

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.

Those pickups are VERY hot, so they need some good clearance under strings.

Not a Logic Pro user but I have Live and Gig Performer projects on my M1 Macbook Pro, running multiple Native instances, even with some hardcore FXs like poly pitch tracking, reverbs, lines of delays etc... No problems and plenty of CPU juice.

I know isnt helping much, but you can stay sure isnt a Native limitation.

It will never happen. :) 

Ps: the MacOs "lite" running on iPad seems not happening anytime soon, if ever, which means they should write code for iPadOS specifically.

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...:/ 

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.

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 :)

What is the pick of death? Error code?

Did you turn your Mac on?