PierM

Good question. Never tried with the old 3.15. I could check this with Native (that I didnt updated yet) in hardware compatibility mode.

I did some test with my Stomp, and couldn't benefit in any way of that optimization, so I guess it's a DSP headroom not yet available to us (if will ever be).

Set your blocks on the HX Stomp to match the Live Logic leds. Once you did that, just use the Live Logic. (then, I'd just ignore the leds all togheter, as they are pretty much useless since they are all white, other than weak and small...) OR, just save the assigned blocks to start in bypass within the presets, so you are forced to activate them all with the Live Logic, when you enter a preset. It can be annoying for busy presets, but if it's just couple of blocks it should be fine. Since the Live Logic has only one single memory slot, I personally find that programming the Live Logic FS to mirror the HX Stomp FS CCs, is the best way to go, without going nuts normalizing all your presets to a single command scheme, which btw won't always work bidirectional due the nature of the hardware toggle.

That guy would make a brick sounding great lol! Whatever he tests, doesnt matter guitar or pedals being used, just sounds beautiful.

Basically they said everything and its opposite. Marketing as its best.

Even the Ampero Stomp II does it, and to me it makes A LOT of sense.

Again, we'd really benefit of a "performance mode", which does put the block select rotary encoder in sleeping, and making the 3 encoders under the screen, assignable for 3 params adjustment on the fly. This means you'd have 3 FS, and 3 Knobs, assigned to what you want for live performance. In your scenario, you could assign R1 to Amp Drive, R2 to Channel Volume, and R3 to Distortion Level. Of course this page would need a dedicated GUI.

Double tap to stop. Double tap + hold to clear. If you want more control, read the manual in the command section; there are all looper commands available, and you can assign them to the FS you want, doing what you want (rec, play, overdub, stop, reverse, double speed, half speed etc..). You also have access to double actions assigned to FS press, and FS release.

They are not an iR, that is not a correct way to describe them. An iR is a finite sample that will linearly convolute the input to a range of specific freqs, each one with its unique level and at a specific octave (and much more). The helix cab does emulate an iR, using dedicated algorithms to simulate the elements that are needed to do an impulse response. (simulation). Mic placement, Mic model, pre-delay, cab model....each one of these is an algo, then we dont know what's the reference model for each one of those. Could be a lookup table, (less memory than an audio file, more DSP efficient), who knows. But a Cab cannot be an iR as a photo isnt a CGI render. Not better, not worse, just different ways to achieve similar results. :)

Helix Cab is an algo, not an iR. Official description; "We call the speaker emulations in Helix “hybrid cabs”, because they use a number of proprietary algorithms to reproduce the same frequency and dynamic accuracy typically seen in a 2048-point impulse response, but at far lower DSP usage. Not only that, a hybrid cab allows you to move the microphone from directly on the grill to up to 12 inches away (in .5 inch increments), and accurately captures the proximity effect/bass boost of the microphone in all positions while doing so. All of this detail means that the speaker cabinet reacts just like the real thing, not just sounding better but feeling better under your fingers. Due to the efficiency improvements hybrid cabs offer, it’s actually possible to run up to four speaker cabinets at once in Helix (depending on DSP load), all with different microphones and microphone positions! The main thing to get out of all of this is that while Helix offers the ability to load third-party impulse responses, you shouldn’t feel that it’s necessary to do so to get fantastic tones. HX cabs offer authentic speaker and microphone behavior with more flexibility and lower DSP usage, leaving you more processing headroom for effects."

That's the Tap Tempo. Is the default setting for that FS.

Front ports have limited available power, which is also shared (so current draw isnt stable). Also, they use crappy cables that arent shielded for EMIs. Front ports are fine for composite devices, low current stuff, low level driver devices (so mouse, keyboards, wireless dongles etc etc).

You must have missed the fact this is a porting from Line6 Metallurgy plugin (as well as the other amps added), which is a collection of metal/doom amps, also sporting the new cab technology.

... Jimi Hendrix, Adam Jones, Kurt Cobain, Pete Townsend, Melvins, Pelican, ISIS, etc etc etc...

This was exactly my suggestion back in the days, when they started changing the firmware update process. Would probably reduce the problem a bit... But honestly not sure we would solve all these problems once for all, because as I said earlier, I did get similar problems in the past, even following each step correctly. I still believe the bigger offender here is a glitch during data transmission from local storage to device, which happens while updating. Not even sure this would be a viable solution, but best system would be 1) Download package 2) Upload package to device to reserved memory (NO INSTALL YET) 3) Local MD5 Checksum 4) If valid then INSTALL 5) Validation and reboot I've the fear memory is so tight that there is no room to do a seamless upgrade, which means at least 1 level of redundancy with the previous firmware.

For what I have seen yesterday, the HX firmware button was grayed out, forcing me to update HX Edit first. Was impossible to do otherwise.

True, but let's also say the sloppy L6 forum support doesn't help. They didn't even start and pinned a proper official 3.5 thread, where you could post feedback and search for help.

Install should start after package has been downloaded. If you look at the messages while it's updating, it does download the package, install (send data), and validate.

In my experience, the moving variable here is the USB connection. For some reason the HX driver is very sensible to the USB port being used, and also the USB cable for the connection. Means at setup parity (same PC, same HX, same OS, same everything), you can go from success to fail, just because a "wrong" USB port and/or cable. I've been one of those guys, doing everything right, and still getting random crashes. Now I know that I have to use THAT specific USB port on my laptop, and the shortest USB cable I do have in house. Never had the issue again, since years. These updates aren't being transported to device, and then auto installed locally. They works with PC/Laptop sending data, so even a small glitch during that process, will fail the update.

It's pretty much a useless effort to chase Microsoft with Memory Integrity policies. They keeps changing things from time to time, and drivers that were perfectly compliant within a version, they are flagged as unsafe the next OS update. I wouldn't be surprised to know that L6 has no idea what's the problem is exactly. Just turn it off, as it's basically impossible to have all drivers compatible with that Core Isolation. As soon as you don't browse porn 24/7, and download warez, you are gonna be fine.

Same here. 10 minutes, smooth as ice.

Contact support. I do have the same transmitter, and does last at least 5 hours with a full charge.

Firehawk is a dead project, so nobody is listening your complain. Said that, even if you had a smartphone or an iPad, I can tell you the editor works s**t as it's also an abandoned app.

It's weird, as I'm also in Italy, and used to have a Sweetwater account for years, but now it says has been deactivated. :(

I do sincerely appreciate that, but my variax was grabbing dust since pandemic started...as I sold my Helix Rack which I was using with its VDI interface. I also have a FH 1500 but for some reason variax isn't working with it, and I can't even think to ship that 30Kg amp overseas for a check'n'repair. Also, despite I do have something like 30 guitars, most of them expensive custom shop s++t, that variax has one of the best neck ever and I want to play it as much as I can. I've been probably lucky, but seriously that JTV 59 neck/fretboard is just bananas. :)