MonkeyXT

... tasty morsel to nibble on. Thanks for the clarification, and the pointer toward possible new expansion for the future.

Recreated 100% exactly as you described by following above exactly. Going to that amp another method (joystick, NOT starting from input block) gives expected result of scrolling to next back/forward amp model. Starting from input block as 'parking' spot for the 'cursor,' and jumping to the amp block via the AMP button, results in the above improper behaviour. My preset was made at position one of my otherwise empty Setlist 7 (the only technical 'deviation' from the above). I'm using Helix Rack/Control, with current firmware 2.10.

Thanks for the additional clarification. Makes sense to me..

I'd be curious as well; Makes me wonder - how much data is involved in a complex amp model of HX quality? And how does that expand into active memory in order to 'report for work' in the realm of the DSP. Fascinating stuff really - it's the man behind the curtain. But I imagine it's as simple as the good folks at Line 6 working from a reasonable assumption; that Helix has to be prepared to have ALL blocks in a given preset active at once (sort of like 'worst case scenario' thinking). I can understand that - it would be hard to anticipate what someone would want on stand-by for swap-out only. In order to ground myself in my expectations, I need only picture creating a PODhd preset with some complexity, including working in a second amp; I ran up against the DSP wall time and again, as it was made with capabilities which the DSP couldn't support - the PODhd500X addressed that, but without Line 6 being able to pack that into the bean format, I waited patiently for the next step in their evolution (and I'd developed a bunch of HD presets which covered my needs handily, even if I was pushing the envelope for more =]). I've been able to pull a LOT out of Helix presets, especially by comparison as above =]

Just a thought - if the Helix had allowed for calculation of active blocks only, I would expect a lag to be introduced as Helix 'dumped' the one model in favour of the other into active handling... I don't for a moment actually know how this would work, but that's my instinct talking.

I actually recently set up a preamp to be an 'overdrive' into a full amp model - somewhat similar approach, except that I was allowing all the colours to come through. Your take on this is certainly intriguing.

Prior to Helix, I was using PODhd - bean POD, my preferred style. As a result, in my own mind I have my own 'comparison' so I have my own personal take. I'm not bothering to watch the above video, mainly because the comments here tell me that the method is either flawed or doesn't come across after the YouTube compression etc. I won't go on and on, but I will say that I'm a huge fan of the PODhd, and have gotten a LOT out of it. It remains my backup. Helix... quantum step up in all respects, and challenged me to embrace everything including some of the 'warts' of dealing with 'real amps' ... it's changed my paradigm of sound crafting. And comparing it to sitting down with an amp, it's come into line with that in every respect. A willingness to dig in and more than anything, the thing I tell everyone who'll listen to me that uses modelling tech like this, is dialing in using ears moreso than getting hung up on what the screen label says.

I've seen it on my rack unit - I happened to 'think' I'd seen it in a previous firmware, but wasn't sure. I use EXP1 for Wah functions mainly, though occasionally I have it repurposed to a different effect. When the ability to set up auto-engage by position came along with v2.10, I set up an 'auto-wah' ... and soon after was greeted with a wah coming on by itself, at what it had mistakenly read as position 1%. It had not left the parked position I'd set, which was toe-down.

I witnessed this very thing on Fulcrum's floor Helix - he had gone through all of them and applied the workaround fix, and all had been working fine. Then all of a sudden he was telling me that they had reverted. I think at the time he said he was changing the bank switch mode (holding both down for a moment) when he noted it right after.

I'd noted this quite some time back; because the file names of the individual preset files are derived directly from the preset names as shown on the device itself. For instance, the more recent factory presets have a couple groups of presets which feature the colon ":" character - a nono for any file system. Exporting those individually errors out and it's not exported whatsoever - the ONLY way to save presets with 'illegal' file system characters is a setlist at a time. As limiting as some might think it is, I believe the preset names might have been better to be restricted to legal file system characters - or at least have a toggle to allow or deny them. Just a thought...

Just a quick thought; did something auto-engage on EXP1 that you missed?

This is akin to the awesomeness that would be the Miku pedal (if in doubt, see Chappers and the Captain doing their demo of this - Fulcrum pointed me to this a good while back...) Got a good laugh out of this. (I have a partially British background... perhaps that helped =])

... Yes, strangely enough, I may have gotten myself turned around on this point - not sure how. I just sat down and took a copy of a non-SS preset framework, and just started working on creating some SS variations; seems like my habits were just off-kilter that evening. (In my defense, I'd been up FAR too many hours straight by the time I posted that.) I think I've got my head screwed back on here - now if I could just start using the auto-engage features and such without the EXP1 jumping down to 1%, I think I'd be back on track.

Yes, as above; it's really squirrely and hard to pin down - there are many times when the Snapshot-controlled parameters actually stop changing, and it all seems to tie to making non-Snapshot edits along with anything else. ... again; regardless of how the Global Snapshot setting is toggled. The bypass state inconsistency is new data on this, also. I was looking at this all again, and having the same continued issues. And I realized why I hadn't seen it for several days; for the most part, I was either working with my existing presets / Snapshot settings, or I was making single-purpose stripped down patches just to absorb the new amp models. As a result, I hadn't begun expanding into a new built Snapshot (or edited a previous one) in a while. Now I'm hoping I didn't accidentally alter any of my others and save the result without noticing this inconsistent behaviour first. Not knowing how long a 'hot-fix' release might take, I'm right on the verge of sitting down with pad and pen, making notes on some of my recent tests/edits/etc, and then rolling back to 2.01 for the moment. ... I hesitate because I strongly suspect that Line 6 will soon drop the fix, and also, I'm enjoying the new amps a lot. Thanks Fulcrum, fido083 and HonestOpinion for the additional input. I definitely have spent a lot of time second-guessing myself on this... but in all, I know that the process of working with a preset enhanced with the use of Snapshots was different and predictable prior to fw 2.10.

As things stand now, you could put the looper in front of the audition candidates, play into it, and just let it run while you dial in the different models/parameters. Not as immediate, but you could land on something, pause the looper, play live to flesh out, then get the looper going again and continue navigating.

Hard to believe I'm just noticing this now; Helix Rack/Control, firmware 2.10 (As an aside; I'm experiencing the EXP1 jump to 1% issue - even after removing the troublesome block and re-adding it fresh.) Now this; regardless of how I have the global Snapshot setting (recall/discard - I'm normally on discard so that I can go directly back to the saved state of the Snapshot in one footswitch step) my non-Snapshot controlled parameter edits won't revert to their saved state unless I go off of, and back onto that preset. Saving this out as a copy in that condition seems to leave it in that condition - parameters aren't changing on Snapshot selection. I made changes which would be obvious audibly as well, in case it was the display that was failing to update - but, nothing changes audibly either. Correction; if I clear the assignments, and re-apply, it appears to work once, then fails - I'm having some troubling pin-pointing the exact patterns here, so I'll update as I go along. I'm hoping someone can take a test patch and mess around with it and the Global setting for Snapshots and see what you find. This is a new preset I created, an extremely simple path, and it was 'born' to fw 2.10 - so I've seen this oddness on both re-imported patches 'born' in previous firmware versions, and newly created onesl. I'm half-asleep as I type this, so I'll add any further details I find. Any further observations by others welcomed and encouraged.

This past weekend I watched Fulcrum's floor Helix w/FW 2.10 go from his having 'fixed' every Snapshot effectively/correctly, to suddenly having it all revert to the erroneous behaviour. I forget what he was doing at the time; nothing more than selecting a preset I believe. He power-cycled the unit, and afterward it seemed to all be 'fixed' again - however, it's officially rendered itself unreliable. Meantime with my Helix Rack/Control rig, now that I started changing wah blocks over to EXP movement engage, I've started to have the wahs randomly coming on - navigating to the parameter shows that it's reading 1%, where it should have been reading 100%. I have it 'parked' at toe-down since I'm used to engaging the Toe Switch. My expression pedals are the Mission Helix toe-switch one (EXP1) and Mission regular Line 6 model. They're not loose in movement; even if so, the way I'm configured, it would read just under 100% as it was still visibly at toe-down. Another time, I came out of the tuner and the wah came on as I resumed my signal. I'd been thinking that I was side-stepping much of the trouble with the expression pedals by way of the physical presence of a second pedal plugged in: not so. This has taught me that my habitual use of EXP2 for volume functions, while EXP1 w/Toe-switch engage has been tasked with wahs and such, kept the issue from affecting my audio path it seems. Hopefully this will be 'hot-patched' soon.

Have other Helix Rack & Control users chimed in on this? I might have missed that. I'm on current FW 2.10. I've thought all this time the rack unit with physical EXP 1 and 2 plugged in wasn't being affected by the volume block drop to 1% issue, but I guess that's because I always shunt volume type duties to EXP2 (even with previous L6 units, I'd always add a second EXP to the shortboard for instance). Now, having done a bit of testing with EXP 1 - previously set to use the toe-switch (Mission Helix EXP w/toe-switch) for on-off, generally for wah in my case - now set to auto engage by position, I have now found a couple of times being hit with the wah coming on by itself with zero physical movement of the pedal itself. Checking the parameter, I saw it was at 1% while still at 'parked' toe-down position (I set the auto-engage to come off of parked there, as opposed to heel-down). I'll have to skip using this feature until it's sorted.

Ditto on the above; having the Rack / Control version, and physical EXP 1 and 2, seems to bypass some of this. And on another note, I've found the lit-status of combination stomp switches issue repeatedly on previous firmware updates as well. And needless to say, especially prior to Snapshots' introduction, I had a fair bit of that going on. Re-bumping the switch status light's state at least seems to be far simpler to correct for me this time around, for some reason (either I didn't arrive at the simple method I use now, or something was fighting me in the firmware; not sure which). I just go to/highlight a block within the group stacked onto the switch which has the status (lit/dim) that matches what I want the default state of that stomp's led ring to be in, go into bypass assign, and simply roll the encoder away from and then back to the stomp switch number. Press home button, then position the 'cursor' to the spot I want it parked on as a default (the amp/one of the amps) and resave. Done. EDIT - amsdenj on here and/or TGP mentioned about just touching the switch and then re-saving... and I wish I'd simply followed that first =] Absolutely correct; touching the switch to cycle through the involved blocks/processes affects the LED ring when doing this; stopping when on one which puts the LED into the desired state is MUCH simpler than what I outlined above - and of course, navigating back to a desired block (particularly one involved in the switch's function) using the joystick control leaves the LED assignment alone. Perfect - thanks for posting that.

That's good science; experiment plus control.

Excellent - thanks for posting. Really liking these new additions... I wasn't even aware of that amp until all this =]

IRs - yes, prefix with; 001 002 003 ... ... since it's a 3 digit maximum result, this pads the prefixes correctly for that numbering range. (So sayeth I, another bedroom wannabe =])

Similar to above; I dialed it up, tweaked a bit, tried a couple of different drive pedals for a bit of push in front, and turned that on and off here and there... not one other thing in the patches... next thing I know, an hour has gone by, and my ears have grown accustomed to that super-present 'in-the-room' dry sound because of the lovely characteristics of this sound chain - super articulate and super responsive to picking dynamics; I'd class it among the top in that quality, and it's one that I consider vital (as do many others without a doubt).

Excellent! Sounded outstanding.

Ok, at least it's not just me - first thing I did was go to the previous sound I was tinkering with, and thought it was floating my boat even more than before the update. But I was assuming it was a matter of 'placebo' effect - shiny new firmware making me happy and thereby, listening with 'happy' ears... Now I see these other few comments; duly noted. Next session I'll go through the factory presets to give a fresh listen. But, one of my big happy moments was, with the simplest process, setting up a wah to simply engage when coming off of 'parked' position, and reversing that. Just awesome. The new amps - really nice; I'm really taken with the new L6 original one - I'm another who's all for that approach to creating 'fictional' amps that simply work great.