zooey

Sort of. You wouldn't have the other modes a click or two away though, and fully free-form switch assignments might be harder to keep in your head. It's an idea that comes up periodically, and gets​ some up votes, including mine as I recall.

Ouch, that lollipops. Some things you've probably thought of... Was it registered with Line 6? You could get it from them if so, online I think. How about the place you bought it, if it was new?

I've been living in a 4 presets/4 snapshots world pretty much since snapshots happened. Lately I've been wishing you could set up some patches that way, some all stomps, and some all snaps. Each patch could just remember which switch layout was selected at the time you saved it. If you always live in one layout and never change it, you don't have to do anything, every patch will remember that one same mode. Ideally though, just to prevent unintentional inconsistencies, there should be a global setting to turn per-preset such layouts on or off. Does that seem useful? Any downsides? Worth putting on IdeaScale?

I like some of their not-free stuff much more than more than the freebie. Just my opinion, but it is that.

1024 or 2048 samples, with 2048 using more DSP, so it's likely you can only use one per path. And yes it converts most formats outside its spec.

Yeah, all well and good, but when I came back to this later, everything I did seemed way too bright. Back to high cuts again. Still think it sounds good, and the different IRs give you a bunch of variations you can't really get with standard EQs. But solve the world? For me, no.

Spent some time today with the Celestion IRs I picked up during a couple of their sales. First time I've had a chance to do that, and I have to say, it was fun, even though the initial audition process was a pain. I can't even conceive of trying to do that with the, what is it, 8000+ files in some of the​ larger packs from other companies. I started by picking a semi-random cab from the semi-random collection I have, and listening to all the mix files at the top​ level, ignoring all the other options. That wasn't because I knew they were clearly the best sounding ones, I have no idea without listening too them all, but I really didn't want to get paralyzed any more then necessary by too many choices. Of those, I thought liked the 'all mics + room' variant best, so I loaded that version of all the cabs I had into my Helix, and tried them with some of the patches I've been working with lately. Those patches either have snapshots from pretty clean to pretty driven, or they're built to just turn the guitar down for that same range. Net was that I tried a bunch of different kinds of sounds through that set of cabs. Mostly I liked​ ones with more fullness and body to them, and some seemed really quite good. It seemed easier to get a natural amp sound with them then with the built in cabs. I ended up with no hi cuts, and low cut fairly low, like 70 Hz, just to conserve amp power. That's never been possible for me with the factory​ cabs. So, after I take break to reset my ears and thinking, I'll see what I think of the few patches I saved. Hopefully I wasn't completely out to lunch first time through. It's super easy to lose perspective after a while, at least for me, so who knows.

Just to be clear, Line 6 specifically says that the factory presets change from release to release. Any new models typically get showcased, and there's every reason to think existing presets may get tweaked too. Personally, that's not very important to me. If I use a factory preset as anything other then a demo, which is rare, I copy it into a user bank anyway, which has the side effect of isolating it from changes to the shipped version. What I think people really want to know is is if there have been changes to the underlying modeling engine. Given that the truth of that is proprietary math details, these kind of re-amping tests are the best we can do, and are IMO very valuable as exactly that.

Apologies Will, glad you did the thing and posted it, sorry to have misconstrued. So it's settled then, no change to the basic sound in 2.20, at least to the blocks Will tested. Good to know.

HO, I thought you were proposing that the whole operating mode would switch between Recall and Discard. That's what I thought might be too hard to keep track of. Just switching the current snapshot between its modified and saved states sounds great.

You're of course right about not needing discard for the whole patch, that's covered. I like the idea of toggling the current snapshot between its saved and modified states. Simple and effective.

So you didn't actually do the test, you just attached an empty file? If that's true, I'm glad you outed yourself, because that really WAS misinformation. I know you THINK nothing changed and the result would be dead silence, but that's pretty different from actually having proved it. The interwebs have enough wrongness in them without intentionally adding more because it's supposed to be funny. And please excuse if I'm completely misunderstanding you and being a jerk, I can be thick sometimes...

Or if they don't charge you until it ships, you could just order it now, it'll be a while... Hope you like your JEM :)

My initial reaction is that while this proposal makes sense logically, it's a bit fiddly. Simpler might be better. A variation I've thought of before is just that if you're in Recall mode, a second press of the current snapshot recalls the saved version of it. Just that, no other state management. Alternatively, that second press recalls the saved state of the entire patch, all snapshots. Most flexible version would be a global setting saying whether a second press does nothing, reverts the current snapshot, or reverts the whole patch. Plusses of those are that they're easy to understand, no double- or long-click delay, and there's less state you have you remember but can't see. Biggest downside I can see is unintentionally invoking it if you aren't thinking about it and press the current snap just because it's where you want to be. If you find that happening to you a lot, the feature might not be for you, just turn off that global setting. What do folks think about that?

I have an old pair of original 240s. I'm quite used to listening to music on them, and they sound good for that. I spent my first months of modeling using them with Amplitube and Scuffham, then Helix. Took a while to get dialed in, but all those were very cool in that environment. When I finally got an FRFR setup, 2 Alesis 112s, all the patchesi built in the 240s sounded like complete dung through them. I've since spent lots of Helix time through those, and I'm happy again, but they're not at all the same as the 240s. Moral of the story I think is that nothing is the same as anything else. Build patches using the playback setup you're going to use in real life, at realistic volumes​. Make sure you're not too close to the speakers, especially if they have a separate tweeter/horn.

Of anyone has the time to do a null test before and after, that'd be great. Done similar questions were out soundly to bed that way a while ago.

Yeah. That's that "chewy" thing when he digs in. Just wonderful.

Can a snapshot footswitch be momentary? I know stomp switches can be, so if snaps can't work the same way, building your solo setup as a stomp instead of a snapshot might be your best answer.

No cunning trick there I think. Computer apps behave the same way. You either get both single and double click events when you double click, or there's a delay to figure out whether it's double or not. That's pretty much inherent in the concept. And I agree that that's not great, and that the ability to turn it off would be important. But really, I doubt anyone would want to live w that delay, even if they'd like the functionality, so maybe it's back to the drawing board. This is why conversations are good, and product/app design is trickier than you might think. Maybe Line 6's clearly awesome UI design team has some better ideas.

How about double-tap to restore saved settings​? I'd vote that up.

Wise stuff here...

And you're not the first to do that :)

Quite cool, like it! Can you say some more about the recording tech? Are you saying three people improvised this live from different cities? How did you set that up with reasonable latency?

Great work Jason, and much appreciated!

Other blocks are ok, but the amp itself doesn't think any of its settings are controlled by snapshots; most were, so it's trashed. Backup is that way too. Ironic and annoying. It was a patch I've been working on for a while now, and hate to lose. I have some earlier revs of it, but that was the current and most evolved one. This is a first for me. Firmware 2.0.11. EDIT: Actually firmware 2.11.0, I think (not at my Helix).