SaschaFranck

Totally unrelated (well, at least pretty much unrelated), but I'm getting the best faux pedal steel sounds by using a mixture of double bends, whammy bar and volume swells. Takes some practice but for certain moments, it's sufficient. Fwiw, being able to do such things more realistically is one of the reasons why I'm still considering a Variax or SY-3000 (along with a GK pickup which I already own). Too bad I really don't like any of the Variaxes as guitars. Unfortunately, I don't think I'll get a real pedal steel ever in this life (for a variety of reasons...), but maybe I'll pull the trigger on a Duesenberg Pomona one day.

Not possible. You can't bend individual strings in any software, unless you're using a guitar equipped with a Hex pickup. For Helix users, the best bet quite obviously would very likely be a Variax.

Let us know if the problem persists. I'm sure we can find a solution (the Flash Memory files should be cross platform compatible).

Have you tried different USB cables and ports? Unfortunately, this can be an issue. And fwiw, in case you're on Windows, while the same steps above apply, you should make sure HX Edit isn't running as a service in background (check that with the task manager).

Some of the filters seem to introduce clipping on their own at some settings, I don't know why. And fwiw, I think the filters could be greatly improved, they're really nothing to write home about, even my MS-50G does better.

Where's the problem? Just turn down the amp's channel volume, done.

Fwiw, when using Jamkazam, the latency of your interface (whatever it might be) should be the last thing to worry about. Usually, any online based services introduce a way higher latency.

The amp is rather resource hungry, so are the dual cabs. Use patch 1 and 2 serially and you should be good to go.

People might come to the conclusion to purchase a different product in case they want a low latency audio interface along with their modeler. I bought my main interface mainly because of the latency figures. Hence I did some research on that beforehand. And I've been pretty happy to find proper reports. In addition, IMO it *does* make sense to keep bringing this to L6s attention.

Get other people informed.

The RTL utility can't exactly measure USB input latency. In fact, it's tough to measure that at all.

Typical results. Huge latency.

From all I know, the driver hasn't been updated with 3.x.

Well, that's pretty much what I was saying... Compared to using a WDM driver, it's much lower - but yes, the reported latencies are wrong indeed. I don't think it's a fault of ASIO4All, though. Whatever, I think we can perfectly agree that the latency figures of the Helix' driver are almost outstandingly bad in 2020. Even the cheapest interfaces do better.

Within Logic, I can't see an option to switch between the two. The only option to operate the Helix in class compliant mode seems to be to entirely uninstall the driver delivered by Line 6 - or would you happen to know about other options? On my system (still on High Sierra, in case it matters, but I'm pretty sure it's the same on Mojave, which I could perhaps install but don't feel like, would have to slap a new GPU in), once the driver is installed, it's the only Line 6 item I can select. As said before, for a while I used the Helix without the L6 driver, but it doesn't allow me to use other sample rates than 48kHz in Logic natively (so Logic - or rather Core Audio - has to do some realtime conversion, which only sort of works as it seems) and, even worse, I can't open files using different sample rates simultaneously in WaveLab (something I do rather often) while using the Helix as an audio device for it as well. Hence I decided to go with the Line 6 driver, even if it's really bad regarding latency. On Windows, you could try out Asio4All. http://www.asio4all.org/ It was originally meant to deliver low latency performance for interfaces not coming with their own ASIO drivers (especially such as onboard computer interfaces, quite handy in case you only want to play virtual instruments on a laptop) but turned out to occassionally deliver better performance than the drivers delivered with some interfaces, too. Apparently this isn't true for the Helix, though (see the link to the other thread zolko60 posted).