SaschaFranck

Done.

I've got a Zoom UAC-2, very nice latency numbers, but I still wouldn't really recommend it due to their driver support being quite slow. These days, for lower end-ish interfaces, as said above already, I'd likely recommend Motu. If money was no issue, supply chains sorted and latency the main thing you're interested in, RME all the way. IMO there's no better driver support anywhere.

Being a good person sometimes is quite challenging (usually too much of a challenge for me...).

I thought UAD was releasing native versions of their plugins...

Do you have any plans to actually play through HX Native (or maybe some other plugins in addition)? In that case, the Helix hardware isn't the best choice due to rather high latency figures and you'd be served better with your FR interface. You'll be running into the same issue when using both as an aggregate device, fwiw.

Look here, says January 2022: https://gearspace.com/board/showpost.php?p=15796206&postcount=5092 There might be further additions later on in the thread.

There's some units with double purpose outputs, though (not the Helix however), such as my Zoom G3. Its left/mono out doubles as a headphone output (which is then stereo). No idea whether there's some clever switching happening inside once you plug the phones in, though.

As said, part of what might be the reason that quite some people prefer Fractal's modeling, might be that out of the box the Fractal units are sounding quite glorious. And I can still remember it myself... when I got my Helix, first thing I did was updating and restoring the factory presets. Then I decided to go through some of them. Wow, what an underwhelming experience, regardless of the guitar I plugged in. Was pretty similar when I loaded pretty much any A+C block into an empty preset. A while later I had an Axe FX III borrowed from a friend for some days, apparently with pretty much all factory content (presets and defaults) intact. What an incredible difference, really. And while that - very obviously - is quite a subjective thing, it's still what you read in all sorts of related discussions. Having said that, even after tweaking the Helix for quite a bit, I still think that some models in the Fractal offerings are better, perhaps even a lot. But in the end, the handful of models I ended up using within the Helix were pretty much as good and it certainly didn't justify the extra money and/or hassle to even think about switching. If I would ever get an Axe FX, it'd be for other reasons but sound quality. But I'm further away from even thinking about it than ever before.

I'm on Mojave myself as well and I can backup my HX Stomp just fine - did you check different cables and USB ports (and make sure you're not using a hub)? Can you export your presets and favourites? Because if you could, you could do just that and restore the global settings manually after the update. You could then perform the update itself as described here:

I think a newer list can be found in the GS thread (thread starter is the owner of the dawbench site as well).

I do the same with one switch. Freeing up snapshots for other tasks. All throughout 3-4 years of using the Floor exclusively as my live rig, I used 3-4 presets.

I never did that, so stomp switches have been paramount for me.

Oh right, sleep mode still isn't something Windows is doing properly, forgot about that (not an issue under macOS almost since decades).

Doesn't matter. But it might be a good idea to not start your DAW before the Helix is switched on. Some DAWs still don't seem to like "hot swapping" interfaces under Windows.

- Stomp mode allows me to do some things snapshots don't. For instance, split modules can't be excluded from snapshot bypass, but I may want just that (in fact, I do want just that). - Along similar lines, stomp mode allows me to control block(s) patchwide. I can for example add a global boost with a stomp set to snapshot bypass. - Stomp mode allows me to use the capacitive switches to quickly navigate to the controlled block(s). - Stomp mode allows Floor users to have 10 of them, whereas there's just 8 snaphots (which IMO is a really stupid limitation, why aren't there 10 snapshots as well?). When I had the Floor, I usually used the 4 stomp, 4 snapshots mode (and always wished it was 5/5, which would as well be possible).

Babyfaces are a great choice. You might not be able to get them at this point in time, though (massive supply shortage). Heck, Thomann has even taken them out of their shop since a while already. I have as well heard pretty good things about the latest Motu offerings. In case you're prepared for some reading (but for the most complete information on that very subject as well), I highly recommend this thread on Gearspace: https://gearspace.com/board/music-computers/618474-audio-interface-low-latency-performance-data-base.html Unfortunately, that won't work. Latency is always as high (sometimes even a bit higher) as what the slowest part of the aggregate device is able to deliver.

Don't thank me, you'll become a pastafari soon enough!

Fortunately just "most", not "all". https://www.spaghettimonster.org/

All this is incredibly buggy. I can select an empty patch (the default "factory" one), insert, say, an EQ and control the bypass status via EXP 1 (which is my latched footwitch). Then I can select an exact copy of the same empty patch, do exactly the same and it doesn't work. I can then copy the block from the working patch into one that doesn't work (controller assignments will be kept intact) and it doesn't work. If I copy the block from a patch where it didn't work into a patch where it did, the assignment all of a sudden is working. Bottomline: This isn't anything I would ever rely on. Thanks for nothing, Line 6. And fwiw: Yes, my footswitch is working perfectly fine. As soon as I set it to normal footswitch operation, it's working each and every time.

If you plan to use constant detunings a lot, don't do it inside the Helix. The algorithms aren't good enough for that and are introducing plenty of latency. If you only use it very ocassionally, you might be fine.

It is more or less dead simple but there seem to be quite some bugs - otherwise the two identical patches wouldn't show any differences.

Yet some more observations: When you control "route to" via EXP 1, the "Wait" parameter is missing. Why would that be? You can even see there's a little delay. Also, even if you set "Max Route To" for B to 100%, the switch will only go to 99%. All this is seriously bug-ridden, as it seems.

WTF is going on with all this? I've got two absolutely identical patches, with one the switching is working, with the other it isn't. Stripped them down. "Blah" is the one where it's working, in "Jaja" it's not. Simple EQ bypass is controlled by EXP 1, nothing else happening. Blah.hlx Jaja.hlx

And fwiw, why doesn't that "active sensing" work with a plain latching footswitch as well? Sure, the EXP workaround is in fact working, but it's not just as easy to set up. And, possibly even more important, I do now need to remember to always switch the EXP/FS tip setting when I pull the Stomp off the pedalboard, because in standalone mode I'm using 2 momentary switches.

H Hrrhrr...