SaschaFranck

Well, the procedure as intended by Line 6 would be: No need to update HX Edit manually in case you're using a version newer than 3.00 already. So, when starting HX Edit and logging in, you should be told there's an update. In case you follow the instructions, the first thing to happen before your hardware unit gets updated would be that HX Edit would update itself. Only then will the actual firmware process start (and before anything starts at all, even before HXEs self-update, you'll be asked to do a backup). Now, at which point in time and why there might be glitches happening - only Line 6 will know for sure, but they seem to happen. Sometimes it's users not following the instructions carefully, using a weak USB connection and what not. But it also seems to happen out of the blue (I had that with the 3.15 update, and I've been absolutely aware of what to and what not to do). Whatever, manually updating HX Edit as a first step might not harm, but I'm sure it's not usually responsible for some updates to fail, my bet would be something happening while downloading, checksumchecking or transfering the actual firmware. In case it was just a failure caused by HX Edit, the hardware would still run as usual.

Yeah, there might be room for improvements in Line 6's update methods, but then, at least there's the Updater to get you back up and running.

No. It's describing a method to get you back up and running in case of a bricked update. A method working in 95% of all cases. And well, perhaps you should just click on the link before coming up with assumptions about what it might be.

Maybe next time I should offer a personal visit. With me obviously paying the travel expenses, no less.

Did you go for an offline update of the firmware?

Fwiw, the Top Secret OD has always been one of my favourites for that kinda sound. Great mixture between overdrive and some more fuzzy, wooly goodness.

My guess would be that you simply can't have everything. For "true delay trails no matter what" to work, the source delay would have to remain active in the background. But in case it's parameters are altered, it only could do so in case a "hidden" instance would be loaded simultaneously. Which would result in quite some CPU cycles to get lost. So, to me this behaviour is just normal - and I don't think anything changed from previous versions. Btw, from all I know, the Boss GT-1000 does it the same. There's spillovers when changing patches but the delay/verb nature will be changed according to the settings in the target patch.

Check the description I've posted 2 posts above. Very likely it will help.

Quite obviously, editing with HX Edit is incredibly more comfortable, but as I'm mainly a live player, I often need to do some corrections on the unit itself, because I can't be bothered to bring a laptop with me all the time. And I just wish that those corrections could be done quicker. With the Floor it was more or less fine because I had all relevant things mapped to switches and there's been 6 parameters permanently exposed, the most relevant usually being among those first 6, but as I scaled down to a Stomp, things are now quite different, it simply isn't as easy to edit on itself as it could be.

There's never been any factory IRs on any products of the HX family. What you get instead is the cab block - but that doesn't exist on the HX FX. So you still need 3rd party IRs.

Whoops - I should possibly add that to my other post...

I'd be all for that. But Line 6 very likely isn't (it's just not the way things work in their view of the HX-verse). So I thought it'd be a better idea to ask for some smaller progress. Kinda like the idealized parameter view on Fractal products.

Fortunately, I never need those massive drive amounts, so I'd likely never had noticed. Still an interesting find.

Yeah, that's why I was wondering in the first place.

Interesting find. And while it's not exactly behaving like a switch, there's defenitely something very noticeable happening around the 7 mark for the Pre Gain parameter.

For me, one of THE shortcomings of on-unit editing with the HX stomp would be that the parameters aren't listed in a manner making much sense, given there's only ever 3 parameters visible (and editable) at once. Examples: In case I want to tweak an amp model quickly, the two single most relevant parameters would be Drive and Channel Volume. These two are very strongly connected to each other (raising Drive often requires lowering Channel Volume and vice versa), but they're on two pages. Same goes for overdrive/distortion blocks. As soon as the unit offers more than 3 parameters, Level is found on the second page. And it also goes for all reverbs and delays. The two single most relevant (and again related) parameters for a delay would be feedback and mix, for a reverb it'd be decay and mix. And they're always on two different pages. All this is resulting in an almost endless clickfest - when it could be so easy in case those parameters would be on the same page. Look at how Zoom is doing things on, say, their MS-50G units. There's also 3 knobs only, but the most important parameters are always on page 1. Excellent. ----- If you think this could be a great improvement (IMO it'd be tremendous), vote it up on Ideascale. https://line6.ideascale.com/c/idea/1053987

https://line6.com/support/topic/65019-helixhx-update-doesnt-work-look-here/

Well, but all too apparently, whatever baseline models (used embedded in whatever algorithms) still seem to be based on IRs - at least that's what Digital Igloo said somewhere. If possible, it obviously makes all the sense in the world to rather have whatever IR-based baseline models represented by whatever algorithms, as that allows for seamless transitions between mic positions, so in case L6 did just that, more power to them (and the new cab blocks are really great, even if I couldn't find a replacement for the handful of IRs I shot, mixed and manipulated myself over the years). After all, the CPU efficiency of the new cab blocks is quite astounding.

Yeah, I have been reading that already. But where does it say that the old cabs were IRs and the different mics were done using an EQ under the hood? It's not that I couldn't understand how this could be done (you could for instance measure the sonic differences from one mic to the next and create Match EQ setting to represent the differences), but I never heard/read it was done that way with the old cabs.

Are you sure about that? And if so, how do you know?

All I know is that the front USB ports on many computers are no dedicated ports but in fact slapped onto a sort of internal HUB. You could possibly find that out by counting the numbers of physical USB ports on your machine and comparing that number to whatever system information available.

Not sure how many they are in reality. I mean, you only hear of those with issues. And as said, it happened to me as well with the 3.15 update - and I consider myself as being quite computer savy. I really think there's some options for something "fishy" to happen within the actual update process, be it server problems or any kind of data transmission issues (see what PierM wrote). I mean, the update process in itself by now is pretty much as foolproof as it gets. Open HX Edit "Hello, there's an update available, want to install?" - and when you confirm, you're guided all the way through. But then, as said, it was almost exactly like that for 3.15 already, and yet my Floor got stuck in the middle of the process. That was the very moment when I knew it wasn't always user error, it just happened out of the blue.

Exactly. People might still do whatever weird things (such as using the Updater instead before updating HX Edit), you never know - but all too apparently, these things just happen.

Yeah, same here - but with this update, it should be sooo obvious because as soon s you do it via HX Edit, you'll instantly be guided through the entire process, which is clearly stating at some point in time that both firmware and HX Edit have to be updated. And in case you do it via the flash file, you surely didn't went to the download section "just in case" but stumbled over the release notes on your way, those also clearly stating what to do.