MonkeyXT

That would indeed be most helpful. ... I say this, but the fact is, I only use the editor for backup & restore functions; my Helix Housekeeping is done right on the hardware.

Yes, exactly right. When I was done, I'm left with just ... I believe just one Stomp controller (takes the delay time mix and sets them to instant 'Rockabilly' territory for me, so that's available in any of the 4 Snapshots I ended up with). Before that... it was pretty hairy; one Stomp was maxed (8 functions) to switch out an amp and pair of cabinets with another, plus turning on or off (I forget which right now) an EQ adjustment, plus something else I'm forgetting.. another changed the nature of the first amp in gain structure, adjusted the Channel volume to normalize that, input gate with unique parameters (Oh! I think that's the one more thing I forgot on the other Stomp I described...) etc...) It was absolutely worth the effort to make the notes and create the new version(s) - once I had it 'transformed' to a Snapshot version of same, I then began a series of edits, eventually including using a FRFR speaker to guide me through the tweaks I wanted in order for me to be very 'neutralized' going into the board direct in live situations... before this, my reference speaker setup was causing me to leave in too much high (and low for higher gain) end; the live board had a treble roll-off... After my experiments and tweaks, I gigged the results... excellent. Board was run completely neutral for me as intended.

I wish it had just been that; I had parameter adjustments peppered liberally all around the preset as well as block activate/deactivate instructions. And I wanted to allow Snapshots control almost all of it... so I needed to allow for all that without there being controller conflicts. PLUS I was making changes as I went; I'd maxed out the stomps, and had made compromises, which I was 'un-doing' as I went as well.

I have this theory, but I'd have to actually have some hands-on to actually test this, and I'm not all that motivated to do so =] But anyway; HeadRush is explained as having the first quad-core processing power - fair enough. Hands-on reports popped up a number of places where some interestingly complex patch creation has run into the wall seemingly quite 'early' in the game. I submit that a massive percentage of the processing - theoretically near enough to half (after allowing for the OS/housekeeping of the system itself) is actually dedicated to the job of 'redundancy' - so, rather than the DSP having to unload the current processes, then load up the new ones, I suspect the HR system loads in the 'empty' half (quicker as a result), gets that running, allows spillover because the previous patch is actually still there with all input cut-off the moment the preset button was engaged... then does the housekeeping of clearing/unloading the other 'half' of the DSP capacity in the background, readying it for the next swap. DSP pool A -> DSP pool B -> A -> B etc...

Where this became tricky for me personally was the point where I took my 'super-patch' and create a Snapshot version of it (it came from before Snapshots, so it relied on various Stomp controller assignments to get things happening as I required, giving me a whole raft of the sounds I needed at hand for my 'Tele-twins' sit-ins with my good friend. Noting it all so that I could re-build and allow Snapshots to do the adjustments where appropriate actually required a whole bunch of hand-written notes to keep track of it all. Parameters, stomp scenarios, on/off status... but I wanted to be able to look at it without jumping back and forth from the previous revision to the new 'SS' version. Worked out great... once in a while I stare at those notes; I was meaning to capture that data into a spreadsheet, and even began laying it out... then decided that, in this case, I could actually do the handwritten notes faster for this type of thing. ... so, an assignments display page would certainly be useful =]

If it's a Stomp, you can touch it and it'll jump about to the various areas it's assigned to... With an Expression pedal, that's not going to be as easy to follow around, come to think of it, as there's no way to interact with the expression pedals like that. I'll have to investigate this once I'm in front of my Helix.

Short answer is no to pretty much all of the above, unfortunately for your preferences. They're not compatible, and I suspect there are some common, but other not shared models to reference. You'd have to start from scratch (but armed with the knowledge of how you went about programming the previous devices). There's a computer editor, but no Bluetooth/app methodology. I'm sure many will tell you; working with Helix is quite intuitive - armed with the many threads of advice and helpful tips here on the forum areas, you'd likely be up and running in short order on a Helix LT.

This is a great new term, and one which I intend to help propagate. If I've missed its use previously somehow, I apologize - but for me, it begins here. =] Cheers

Yes. OOps, sorry... yes, you push in the Presets knob, and you're presented with the Reorder option. Plus rename setlist, Snapshot, select Snapshot, and the display of the preset's Midi references.

In this case, it's probably easier to do on Helix itself; a preset you create that's at the end of the setlist, for instance, you can press the save button once, and there you're presented with several options on the encoder knobs: one of those is 'reorder...' You can then dial that, and the preset gets moved to the new position - effectively inserting it in the spot you want (it's actually doing all that moving of the other presets for you as you go). Super-easy that way. No need to actually save at that point either (hope I'm remembering this menu properly right now; I'm not near my Helix at the moment).

One thing I can reiterate which I saw on The Gear Page; it was stated outright that the streamlined firmware update process won't happen until "later in the year" and specifically, "Helix Native first" - so it won't come at the same time as Native, but some time after that. I believe it was Frank R. who posted that in response to a question/comment about that aspect.

That was me =] In this case though, the OP would want to go to that block, and then push the menu button, and select bypass assign. Then it can be cleared from that screen. The hold bypass/push encoder works for a parameter controller, but not an enable/bypass block assignment. Edit: see also Ninja-style simultaneous post above =] Nicely done, PierM

You can drop volume control blocks into the various spots you require, and tie them all to EXP 3 to work simultaneously - up to a maximum of what I assume would be 8 assignments to the one EXP, though I'm basing that on the function cap on a stomp switch or similar to control blocks/parameters. You appear to require 3 discrete volume blocks - 2 mono ones dealing with the preamp sends, and a stereo one to handle the wet L/R feed. You could in fact set independent minimum and maximum values for each instance, and they'll 'scale' to the movement of the Expression 3 pedal controller. You would just need to set up the volume blocks, then for each one, go into the menu/controller assign panel and make certain they're assigned to EXP3 as their controller. At that time you can set your desired min/max etc. Hope I haven't missed something here; it's early still for me today...

I don't think you're missing anything - it's all relative to how we use the devices. For me, that momentary push for default is a handy 'gut-check' to see if I've gone too far off the rails at times =] Sometimes I use it as a shortcut to get to where I want it, if I've already gone well off of the default and I'm re-positioning that control. A global configuration option would likely be a nice option - like "push encoder for default value on/off"

You have the option to go into the menu button (directly to the right of 'SAVE') and then select Controller Assignment - from there you can dial to select which parameter, and then the controller (Snapshot in this case). That never requires the push-turn action. I've occasionally fumbled this as well, so I understand your comment, as do many others I'm sure. Fortunately there is another way, even though it's a bit more fiddly than the push-turn shortcut.

Sounds like you neglected the step of assigning the parameter changes to Snapshot control; you need to go to the Snapshot wherein you intend to change the parameter(s), and as you're about to begin turning the encoder knobs to change the values, push the knob IN first, and hold in momentarily as you begin to turn it. You'll know it's worked correctly immediately; the parameter value will now show in [brackets] like that, indicating that Snapshots (in this case) have control of those values. Do this for every value you intend to change within a set of Snapshots. SAVE results before exiting that Snapshot. From there, you can dial unique values for the bracketed parameters for any Snapshots in that preset.

Thanks for the info - this is definitely of interest.

Well, that's a whole bunch of useful data - I'm going to make note of all of this and do some more testing of my own (though I am not equipped to do measurements with anything more than my ears.... but at least those were good enough to tell me something was amiss in the first place...) In my super-patch, there are two split/merge points - one after each amp, as I use 2 cabs merged, plus on path 1 I have some parallel effects after the split (chorus and phaser) ... Though, for me, that was my base-line sound, and it was sounding as it should for me. My issues cropped up only after I changed the 2nd/downstream path 2 amp from ANGL to Litigator for my higher-gain sound option, and found that the result of the main clean sound with the 1st/upstream path 1 amp and cabs running past the downstream amp and cabs was hobbled in some fashion sound-wise. Much as you described above; dynamics and tone in general negatively affected... Thanks for digging into this. I'm hoping Line 6 is monitoring this thread; it adds data points to my support ticket, as I see it.

Did the OP see my post, and the suggestion to read my post about this subject? I'm glad this can of worms has been re-opened in some fashion..

I actually went into a support ticket over this subject (I believe we're talking about the same thing) - check the forum for my thread post which I believe was called 'Virtual True Bypass?' They scoped my submitted patches and declared them 'much the same' in the end. The statement was that it's impossible for a bypassed block to affect the sound downstream. My ears insist this isn't the case, and I'm pretty sure they didn't plug in a guitar to test with a plain old ear test. Please have a look at my thread to confirm that we're essentially talking about the same thing - though I didn't to the parallel routing because my patch is complex enough to not allow that - instead I had to keep them serial. HOWEVER - I did make a work-around, gig tested this past weekend; I used a stereo effects loop pair (1/2) into which I inserted my own custom made short jumper cables straight from in to out, and did a hardware bypass of the second downstream amp when I wanted it out of the signal path using the separate send and return blocks on either side of the 2nd/downstream amp. I'd meant to go back to that thread and update it with this 'workaround.' What I found was it changed massively when I went from one amp to a different one in the downstream position; I had been using an ANGL downstream, tamed down greatly, but the Litigator coming into the equation was a better fit for what I was looking for, so I swapped it in a copy of the patch. Then compared... and was shocked by the difference, especially when using IRs instead of cab/mic blocks. I can say this, too; for some reason, the audible difference to my ear is greatly reduced in this most recent firmware update (as it happens; couldn't be in response to my ticket, since there was too much overlap of time). I hadn't intended on revisiting this can of worms; I had determined to 'agree to disagree' with the findings I was presented with... but your posting shows that it's likely not just me and my good friend Fulcrum hearing the difference. He heard it instantly when I demonstrated it to him. Thanks for posting.

I believe it's based at least in part on the fact that there are apparently low cost / free loaders which can 'host' the plugin. I confess this subject isn't my wheelhouse - but my interest Is strong, since I do want to be able to use a 'virtual' Helix on my computer =]

Yes indeed; as above. Check the Headroom parameter, and turn that up up up =]

(The Mission pedal doesn't require a power source; it does what it needs in conjunction with the EXP jack of Helix; a passive device - just in case that was factoring into your thinking - cheers)

I'm looking through my backups - I see that I have a preset from the factory 1 setlist saved right after I installed firmware 2.00 - there are two similar factory preset names: Nighttime Drown Nighttime Swim I see that the Nighttime Swim one looks to be the correct one. ... I don't see an option to attach a file here - perhaps you can let me know how to get the preset to you.

Voted up as well; I fear the possibility of this hardware failure, especially since I only use the editor for backup/restore functions - all of my patch editing is done on the device itself (very much my preference). I go out of my way to use the joystick as minimally as possible.