SaschaFranck

Well, at least it'll happen with the next (Stadium) generation.

You could always ask in their FB group. I got macros for everything I needed there. And in this case it should even be possible without scripting, all you'd need is a big button displaying numbers and receiving MIDI CCs.

I'm quite sure that this would be somehow possible with TouchOSC.

Unfortunately, the answer is no.

The easiest solution: Don't use IRs unless you *really* have to. For me, following that guideline, meant ending up with exactly 2 cab IRs (which are my main live IRs) and 3 IRs to enhance both my nylon and steel string acoustics. For anything else I'm using the internal cabs, which actually are excellent since their last major revision. I could possibly even get away without my live IRs, but I have tweaked them in a way that, at least for me, they're working incredibly well regardless of the musical and/or technical environment.

Fortunately, that's irrelevant since some FW revisions back. The only thing a patch needs is the IR to be present on your device. And in case you're using more than 128 IRs, you better keep track of them manually.

Well, that's actually as true. For me it's usually that I split the signal in any such situations anyway, so I didn't think about it.

Where the instruments come out depends on the mixer at the end of the split path. You can run both signals into any output, blend them, pan them just left/right, whatever you feel like. The splitter at the beginning is only there to divide your left and right inputs.

No need to waste a precious block for that. Just create a split by dragging a block down to path B, then do the L/R panning on the splitter.

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.