duncann

It looks like per block snapsnot omission is coming, among other cool things:

There is no global option for what you want to do and there will be a pause when switching presets. Any particular reason why you're not using snapshots? Using them would remove the pause and effectively provide the global option you're looking for.

Ha! Are you kidding? I could never duplicate that. To make matters worse, the entire thing was run through a reverse delay, with 100% mix and a 2 second time. So that means I had no idea what was going to come out of the speakers, regardless of what I was actually playing on the guitar.

Depends on what you mean by improvisation. Everything starts off as improvisation, but all of it eventually goes through a heavy refining process (note by note), some deviating heavily from the first musical thought and some staying very close to the original with perhaps only some style or specific phrasing added. So I suppose that's not really true improvisation, which I frankly suck terribly at. The only thing I ever improvised on the spot and never changed is Entropy (made with the HD).

There are some things I still like better about the HD. For example, seeing as how the clarity of HD isn't as great as HX, it's more forgiving as far as lack of technical playing ability and can even go so far as to assist in obstructing minor musical deficiencies ... or is that an excuse for poor writing and tone making and blaming it on the pitiable HD :) In any event, thanks to the HD, it's one component in the evolution of striving to become a better guitarist. You're on to something with the last part of your post. In making revisions to the original, the first point of unquantifiable emotional content, or in the pathos, which can be hard to remember the more time passes (probably doesn't help that less is available these days - time, not memory), and adding new layers of emotion, something is bound to be lost. The goal is to always try and improve the original though. Perhaps that's easier said than done and it's actually easier, unfortunately, to realize a degree of failure. Hope not. Something to think about...

Thanks for making me aware of a more recent version, not that I use it anymore though. I wonder what it is they fixed?

The Kinky Boost seems magical for getting that extra gain, smoothness, sustain, and warmth all in exactly the right proportions.

Not against having more amps or choices, if a particular amp actually adds something unique. If it's an amp that's more or less just a variation of something already there, it wastes development resources that could be spent more effectively on something else. There's already too much repetition for amps in Helix. A choice in name only isn't really a choice, just noise.

Wandering outside the scope of Helix's amp measure, and staying there at the same time, I'm curious to know why many people find it difficult to be satisfied with what's currently right in front of them, to a rational degree?

This video might help a bit. And below the video are some measurements of the mid-focus eq taken from this link: https://line6.com/support/topic/335-frequency-response-graphs-for-hd500-eqs/ Unfortunately, the links in the link are broken, thus the images for the mid-focus eq. So with all this information, you should be able to construct an equivalent using what's available in Helix.

A setlist can still be renamed with HD Edit by changing to the 'set lists' tab and then on the setlist name you want to change, one long-left-click (~ 0.5 - 1 second) followed by a short left click. Very odd, but it seems to work.

I'm with Kilrahi. Nothing wrong with getting hyped up about something. Just don't let the inevitable disappointment wreck you. Usually, when you want something bad enough...

Could the pet feature be a global (or two) envelope filters? I can recall DI getting excited about stuff like that: first comment from: https://line6.ideascale.com/a/dtd/Modulation-Sources-LFO-s-Envelopes-Envelope-Followers-ect/774179-23508#idea-tab-comments

I don't want to jinx things, but they may have finally fixed this problem...

So it would in effect expand - to a switch by switch basis, instead of an entire preset only - the snapshot edit global for recall/discard. Keep the current global as it is, but if one wants to override that global for each switch, perhaps a couple of settings could be added to the command center for each assignable switch. There does seem to be room there for more. One encoder could determine where each switch gets its snapshot edit value from: Global/Recall/Discard. Another encoder could determine what to override: Entire Block/Parameters/Both. Could be useful. I say add the flexibility, as more or less an option (just like so much in Helix already), and don't worry about catering to a concern that wouldn't be the fault of Helix...

Lol. Chilled monkey brains anyone?

Just as a note for people, I noticed that even with the restore of a backup where the firmware versions match (between backup and device), it still does the rebuilding process. So the programmers must really be playing it safe.

Is it possible the backup is from an earlier firmware version that what you presently have on Helix?

Actually, from what I see, besides the slight drifting as phil_m mentioned, the light is working pretty much in sync with the sound, the settings of the tremolo block, and when an LFO reset signal is sent. If you're getting sound on the first beat, that means the tremolo's LFO is half way through its speed setting; the tremolo's LFO will always start with no sound. It doesn't care about external timings, where you are in a measure, or beats, it just happily obeys its own settings, unless you have its speed set to note division, which relies on the snapshot, preset, or global setting for BPM. Which might be a component of why you're seeing strange things. A reset still occurs but since the BPM may have been unintentionally changed it will be completely different than what was before. That's why I previously mentioned to set the speed setting to a specific Hz value. To make matters worse, the behavior of this scenario might be variable depending on where the BPM value is coming from: global, preset, snapshot, or an external midi clock. I've already seen that when Helix is receiving an external midi clock an LFO reset doesn't work, so either don't send a clock to Helix or turn Helix's global setting for this off. I don't have enough time to see if the other cases are different. Not sure, but I might have noticed that when the BPM source was set to snapshot and the tremolo's speed was set to note division and LFO resets were sent close together, the BPM changed but the tremolo's LFO acted as if it hadn't, so... If you want to send LFO resets, and change BPM within a track, I might suggest trying to use snapshots. So take the external midi clock out of the picture, set Helix's tempo select global to per snapshot, then create different snapshots with different BPMs, and make sure the tremolo's speed setting for each snapshot is an appropriate hertz value. If I remember correctly, in the past when I used snapshots to reset LFOs, I noticed I had to first switch to a snapshot I didn't want then switch to the one I did want. If I didn't do that, the LFOs wouldn't reset. Maybe that behavior has changed since, but in any event you could switch to the snapshot and then immediately send CC64. How this whole thing might work with your other devices, you got me there. It might not work, I just don't know. Hope this post makes sense, and it's entirely possible I'm completely overthinking this whole thing. To sum up, with Helix by itself or in conjunction with a computer, I still don't see any odd behavior with resetting LFOs.

I've been waiting for this feature, but Line 6 keeps disappointing:

What the light is doing (I normally have the tap tempo led turned off) in relation to the sound can vary depending on when the LFO reset is sent. So it could be that the light is bright on an upbeat or downbeat, or even anywhere between. For equipment I use, it's just Helix and a computer with Reaper. That's it. I've never used midi sync because I don't have a reason to. The LFO reset alone achieves what I want. So perhaps some the problems you're having might be because of external equipment and how everything is interacting. Upon reloading the preset (I used to use this method to reset the LFOs, but with snapshots. Since they added CC64 I don't do it this way anymore): Reloading the preset when the light turns on results in sound when the light turns off. Reloading the preset when the light turns off results in sound when the light turns on.

Tried again with your preset. One thing I've never used before is having Reaper send the midi clock to Helix, which appears to work fine. But when used in conjunction with sending an LFO reset midi (via midi or physical tap), the LFO reset seems to be ignored completely. Turn the midi clock sent to Helix off (or turn Helix's global setting to receive midi clock off) and LFO reset works fine. A couple of other things that might be creating a hitch. Keep in mind that with the tremolo at 50% duty cycle and square wave, the sound won't start until half way into its full duty cycle. Also, if there are two LFO resets too close together it will change the BPM, and if the speed is set to note division it will have an unwanted effect. Set an explicit Hz value for the speed instead. By no means am I an expert on this stuff, so I could easily be missing something, but I'm glad to try and help.

If you click on the array of small squares you'll get to see some bigger pictures.

So I tried replicating what you're seeing with the tremolo block. I could not get it to do what the images in your post above show. When sending an LFO reset via midi or physically tapping the tempo switch once, the result was always the same, which was the LFO resetting as expected. Firmware version is 2.7.

For delays, I should have mentioned a delay with built in modulation. When I get some more time, I'll have to see if I can reproduce what you're seeing with the tremolo.