SaschaFranck

There's two more advances of using HX Native for re-amping, that haven't been mentioned yet: - You don't need to re-record your takes, something you'd have to when using the hardware. - You can re-amp multiple takes simultaneously.

But how does that even remotely solve the problem? You'd still have to switch it on/off per preset, you'd be losing a block and you'd be losing overall volume control via the volume knob. Again, this has zero to do with what has been asked for. There's plenty of people running their Helixes through traditional amplification.

So, are you saying that's something you'd like to do at soundcheck? For each patch? I'd rather program dedicated patches for each situation (real cab vs. FR amplification).

This will only work globally in case you assign them to an external footswitch.

No. One of the reasons why global blocks would be great.

USB hubs have been an endless source of problems ever since I'm using them. I can't even remember how much I already had and apart from some medium-expensive Belkin one (that I unfortunately forgot in a backstage area a while ago), pretty much all of them had some issues every now and then. Fwiw, this is my experience with standard USB hubs (there's newer ones such as what, say, many people are using with their M1 Macs, also allowing you to connect various other things, those seem to do a lot better). In addition there's USB cables and for whatever weird reasons, the differences between them are staggering - and once you're using a hub, you double those potential issues. In a nutshell: Don't use hubs for anything mission critical in case it's possible.

Fwiw, this is not the best way to see what an amp can do for you. Neither in the real nor in the virtual world. Yes, I'm pretty much aware of all those various tests, saying "I set everthing to 5 and this amp sounds killer already!". That's only true for some amps. "English" tone stack on a classic Marshall anyone? Yes, everything turned up all the way. Or take a Boogie Mk XYZ model. Those are known for their super effective tone stacks and also for the interaction between tone stack and gain controls. In real life, you'd never chose a "let's hang around as close to 5 as possible" approach. It's not what you can see being dialed in on most people's amps, either. In case of the Line 6 factory defaults, leaving the drive settings at what they come up with is an even bigger mistake, at least IMO. Some of the default settings do their best to demonstrate how to *not* dial in an amp. Just check, say, the first 13 guitar amps in the list. What in the world were they thinking? Not one clean default and some of them aren't even just "hairy" but horribly "over-dialed". The first exception is amp #14, namely the Princess. But right after that, the mess continues. Deluxes and Twins are mainly known for their clean-ish tones - but Line 6 tries to turn them into whatever else it might be. Usually the result is plain awful. And fwiw, the same goes for most master settings (on amps offering MV in real life), sag, hum and ripple. All turned up WAY too high to represent the real amps in a way comparable to how most people are using them. Seriously, Line 6 did a pretty bad job on almost all their factory default settings.

Are you using the Stomp as your audio interface already? That's *the* important regarding anything else in terms of re-amping, but your post doesn't say anything about it.

I'm absolutely familiar with latencies, their typical values and what not. Those 40ms was the number you came up with. And I'd never try to delay any harmonising part that much in case I was recording it manually.

Why would there be a "natural latency"? Choir voices or bigband sections aren't 40ms apart from each other. And once I manually harmonize a line (as in actually playing a hamonization), there's no 40ms of latency, either.

I even used them on acoustics sucessfully - and those pick up tons of environmental vibrations.

Fwiw, you could just get a clip tuner for such purposes. Inexpensive and not too obtrusive.

Gotta say I never understood the "Output" setting, either. Doesn't seem to be possible to have the tuner active with the full sound still coming through (fortunately I don't need that function).

While plenty of folks seem to disagree, I think that all pitch shifting effects in the Helix sound pretty bad, so IMO there's not much you can do about it.

Have you tried an offline update (you'd have to download the appropriate flash files and point the Line 6 Updater to them)? Are you connecting straight to the Macbook or through a USB hub? The latter isn't recommended. Did you check another USB cable?

No, it's not academic at all. It's easy to run out of IR slots in the Helix if you have a vast collection of IRs and want to check a whole bunch of them for example by switching through them via pedal edit mode (which is a most excellent thing to do). So, I might save a patch using one out of, say, 50 IRs. But I don't want to keep all slots clogged up so I might as well just remove the ones I tried all together. This will render the patch I created useless. With proper IR management the patch would simply come up with a message. "IR "kickass cab.wav" missing, search for it y/n?". That's all that'd be required and it's got nothing to do with any "core software design". I have been involved in quite some betatests for sample based software and more than just once a file locating algorithm had to be implemented later on. It was always possible. There's no reason it shouldn't be possible within HX Edit. Seriously, this is a glaring omission - and if you were in the software sampler business and came up with a sample organisation such as this, you'd be out of the game tomorrow, as easy as that.

Personally, I'd either go for the onboard cabs and check the mic options or download the free RedWirez teaser pack (all you need to do is to subscribe to their newsletter, which you can of course unsubscribe from), the supplied Marshall cab IRs are pretty good IMO.

The answer is: Without any further information from the patch creator, you don't. One of the biggest omissions in the Helix' IR management. And IMO almost inacceptable (just that there's no way around in case you want to use the Helix). Also, it could be solved quite easily. HX Edit should just tell you which IR is missing and should also offer a search function (on your computers storage devices). Just what each and every software sampler is doing since decades by now.

Strg. oder CMD + S ist ein absolutes MUSS, wenn man mit dem Helix arbeitet, egal ob am Editor oder am Gerät selber (bei letzterem muss man eben zweimal "save" drücken).

As has been said, forget about BT for anything regarding live playing through it. Even the latest aptX codecs come with 40ms of latency - way too much for realtime playing.

The global EQ works great for such purposes. I don't exactly need it much anymore (if at all), as by now I had enough time to bake my own IRs for rehearsal/gig volume, but it's still there, just in case (or whenever I want to check some new IRs). Just set up a broad midrange boost/cut. Personally, I usually went for a boost to take my homebrewn presets to gig compatibility rather than the other way around. Frequency is something around 700Hz, Q is around 0.4-0.5, plus I might also add some low cut on boomy stages. It's only applied to the XLR out feeding my personal monitor.

Fwiw, it's a pretty sad affair. My prediction would be that in, say, 5 years (at best) from now on you won't be able to sell any top modeler without a mobile editor anymore. For me, it wouldn't even have to be wireless, using an USB OTG cable is just fine with me. Alternatively, Line 6 could release their communication protocol so 3rd party folks could come up with an editor (just as in Fractal land).

Exactly zero. Quite unfortunately and one of the reasons I might quite likely switch to a GT-1000 at some post-pandemic timepoint.

Yeah, but the point is, when running a DI box, you're usually feeding an XLR in as well. Alternatively, you're feeding a stagebox - and on the console end the signal could be routed into whatever inputs. But then, the very same is true for the XLR outs. Sure. I'm all for it. I'd rather prefer some other synth-ish options to be added before that, though (already mentioned them, decent filters and all sorts of modulators being the most important things).

Fwiw, something I'd really like to see is a direct communication between the Hardware and the native version. Should obviously be bidirectional, so any changes made on either side would automatically be reflected on the other side. You could as well just save the always open HX Edit (at least I have it opened all the time). All hardware options could be hidden in the plugin until you actually engage such a "link" mode (should only be available for one plugin instance at a time to avoid confusion). That'd likely be the most comfortable recording and reamping setup ever.