SaschaFranck

Unfortunately, unless you *know by yourself* which IR is needed for any patch (in that case you just drag it into your unit and reload the patch), there's absolutely no way to restore the patch properly, simply because HX Edit won't even tell you the name of the missing IR so you could possibly search for it, let alone provide a search option on its own. That's something really winding me up since years by now (and it's been even worse before some update - the missing IR even had to be in the correct slot, which made any IR management completely impossible). HX Edit isn't any more complexed than, say, a software sampler. And in case these are missing an audiofile, you get the name of the missing file a search dialog. Software file organisation 101, really.

Huh? Where did you read that? The vanilla Stadium has 2 external control inputs. No idea whether and how you can utilize them as amp controls. The XL has 4. For the dedicated amp controls however (2 on the vanilla, 4 on the XL) you might need that extension box.

As said, it's got nothing to do with that. It's about the used interface chipset, the firmware and the drivers.

Fwiw, there's one way to reduce latency under macOS already, which would be to deinstall the Line 6 drivers and run the unit(s) via macOS' "native" Core Audio. This does in fact bring the latency down quite a bit (from around 16ms at 44.1, 32 samples to a mere 9.5ms at 48kHz, IIRC), but that would limit you otherwise. Anything not using 48kHz might be impacted and you might as well run into trouble opening multiple apps using the unit as their output device, especially in case different apps are mixing different sample rates (which is absolutely no problem with the drivers installed). Maybe something similar is possible under Windows running the unit as a class compliant USB device and then using ASIO4All to achieve lower latencies in your DAW. JFTR: HX Edit will work without the drivers nonetheless, so it might be worth a testrun. For me personally (on a Mac), that method had more disadvantages, so I went back to the L6 driver. And if at all, ASIO4All might be an even worse "solution". And I also knew I just had to use a dedicated interface for low DAW latencies straight from the start. Anyway, it'd be great if they adressed that issue with the Stadium series. And I'd almost bet they will. After all, the big Stadium boys elevate them among the top 3 (or so) pricewise, so it'd possibly not be the best idea if the audio interface driver delivered the worst latency figures in its class (which unfortunately is the case with the current lineup, even my cheesy Zoom G3 does better).

For me, latency is absolutely crucial in my little home studio as I exclusively monitor through software unless I'm using guitar related hardware. Even more important when I'm on the road, because that's where I can't take any hardware monitoring devices with me (apart from my big floorboard which will not make it to hotel rooms and such - let alone to vacations). And yes, the last generation of HX devices come with unbearable high latency numbers. Playing an amp sim plugin through them is not possible for me at all (while not being "Mr. In The Pocket" I still seem to be pretty sensitive to latency). Which is why I also own the Motu (ok, I also got it because of the mic ins and the form factor). So, if that was improved, I'd greatly appreciate it - but in case they manage to keep device latency low, I'd possibly not get too mad about interface latency. If I was to build a small studio setup around it, that'd however become much more of a concern.

And fwiw, you're even mentioning Motu. I have an M2. Lowest latencies in its class. Still over USV 2. And you even say it yourself that drivers are the most important thing - which they kinda are, in combination with the used chipset and firmware. So why are you even mentioning USB 2 vs. 2.1 vs. 3 and what not as being important? They're not.

Oh, I see, it's your video. Then you have no clue about latency and the underlying reasons for it to be small or huge. Sorry to say so.

And fwiw, the guy in the video has zero clue about latencies and the reasons for that. He's making a great deal about what USB standard is supported. But that's *completely* irrelevant! RME managed to get the lowest latencies by far out of USB 2 10+ years ago already. So there.

How would anyone round these parts know?

The correct answer is: Tomorrow.

Best place these days seems to be Reddit. Unfortunately I hate that place due to it's structure.

Ok. But this is not the place where any of them ever answers.

What makes you think anyone round these parts could answer this question?

Oh that's cool!

Nah. Seriously, there's just some places (such as my old music refuge) with pretty much no internet access and no "fixing" options, either. That's interesting - where did he say that?

Quoting myeelf, but it seems I was wrong. Apparently capture creation seems to be an exclusive online process (same goes for stem splitting). We can only hope they manage to somehow store the capture data on the unit, though, until you're ready to upload - I mean, at least over here there's quite some places (basement rehearsal rooms or studios) with no sufficient internet connection you could connect the Stadium to.

I understand it in a way that the source capture will be generated straight on the unit, but you could as well send it to the cloud (given the unit is connected) and use their servers for optimization (which is pretty much what ToneX does, just that it doesn't generate captures on it's own, it's all cloud based).

Raw DSP juice seems to be 2-2.5 as much according to some L6 representative in some YT comment. Anything else can not be answered but I'd guess that some of that power overhead will also be used to improve quite some FX.

So far 16 genuine new ones and ALL old modules minus the very old hybrid cabs. So your presets should load 1:1 unless you've used the latter. Given the success of HXN, I'd bet they will do that.

That's not exactly true. The levels on USB 7/8 are exactly the same levels used by the Helix internally. And when you use a Helix send at instrument level, they're perfectly fine to feed an analogue amp.

You don't need the Radial in this setup. Just use a send of the Helix to feed your amp. You can set them to instrument level and they're pretty much as if they were made for this purpose.

Ah, good to hear/read!

Defenitely looking like pet hair - but that'd possibly only explain some smell, not the power supply heating up so quickly (IMO it'd take much more hair to cause that), let alone some serious glitchy malfunction. I say taking it to a decent tech is the best bet here.

Maybe, maybe not. There might be obvious hints. But as said, I'd rather take it to someone qualified.

In case there's smell, it's time to take it to a tech and have it inspected (unless you can do it on your own). You risk frying it completely otherwise.