phil_m

It behaves like all the other commands in the Command Center. Values are only sent out if they are saved in a different state in the destination snapshot than they are saved in the current snapshot.

I understand if people don’t like the way something works, but you can’t call something a bug if it’s the designed, intended behavior.

This shouldn't be necessary. Actually, Updater needs to connect to the internet to complete the update, so if you're using wireless to connect to the internet, you have to leave it on.

Just download HX Edit 2.80. It's still worth creating a backup even if you don't care about your presets because the backup will save your Global Settings. After you update, you can restore from backup and choose only to restore the Global Settings then.

What are all the volume blocks on 2B doing? If I had to guess, I’d say there’s probably a good chance that the expression pedal bug is affecting one or some of those and muting that path.

This is the part of the manual (on pg 36) that I'm referring to: The "value changing" refers to the value saved with the snapshot. Now I'm not saying I think you can't make a case for it being the way you want, but just that I don't think they consider the current behavior a bug (apart from the new 2.80 bug mentioned above).

I just remembered I saw this exchange on Facebook regarding the EXT AMP functionality. It seems there is a known bug that they're fixing (Igor does a lot of the DSP coding for Line 6). So I think that's what you might be noticing there. As far the EXT AMP and snapshot thing, I don't know what else to say. Yes, the fact that the LED state is getting misaligned is a bug, but the fact the relay functionality is actually working the way Line 6 intended it to. When changing snapshot, the Helix compares the state of relay to the one saved in the snapshot, not the current state. I can see why having it work the way you're suggesting would be desirable. As far as the ES-8, it seems a bit like cutting off your nose to spite your face to me. The ES-8 has no comparable feature to snapshots. Programming it seems very painful to me, but if you think it will suit you better, than by all means, you should go that route.

HX Edit is backwards compatible with older firmware.

EXT AMP is treated almost exactly like the MIDI commands. Yes, I think the LED not matching the relay is a bug (not one I'd necessarily call serious, but that's another discussion I suppose). I don't know if it's been address in 2.80 or not. So just to be clear - If you have two snapshots - one where the EXT AMP is set for the clean channel and the other is set and saved for the dirty, does the channel change when you change snapshots? It seems to me the issue is that you're hitting the switch while in one snapshot and things get messed up when you go back to the other. If you only change snapshots does it work as you'd expect?

Should be fine using the current version of Updater to roll back. It should just list all the available firmware versions. Just click on the one you want.

Some of this is coming back to me now... One thing in your example is that have each snapshot saved with the EXT AMP Tip off. I believe that for these commands, the Helix is comparing the value that was saved in each snapshot to decide whether it shoots out the command when you go to the new snapshot (not the current state of the switch). So it's seeing that in Snapshot 2, the saved setting is Off and that's the same as in Snapshot 1, so it doesn't change the state of the relay. I believe that may be the logic. If you had Snapshot Edits set to Recall, I think it would maybe work because hitting the EXT AMP switch will actually change the value saved in the snapshot.

First of all 2.71 isn't the latest firmware - 2.80 is. In your example above, do you have the Snapshot Edits parameter set to Recall? The one thing is, IIRC, is that I think you may have to have the EXT AMP command assigned to both a footswitch and an Instant Command for it work. I'll have to try it again.

Are you on the latest firmware? I haven't messed with this in quite awhile, but the last time I checked, it was working properly.

I think it would have been weird to release a plug-in where the first release was 2.0... I mean, Native isn't really tied to the hardware in a way where you have to have the hardware to use it.

If you have the receipts, you'll be fine getting this covered under warranty. It doesn't matter if you registered the unit when you bought it. You'll have to register it to get it replaced/repaired, though.

As I understand, there’s a bug that’s affecting this in the Preset Mode views that show snapshot, but it should still work in actual Snapshot Mode. Line 6 is aware of it and is planning to fix it in 2.80.1.

The DT has MIDI in and MIDI out jacks... The cable on the Uno are labeled as to which one go to which jack. Just hook everything up and run Line 6 Monkey, and it will do everything for you.

The M-Audio MIDISport Uno is a good option. The problem with inexpensive USB to MIDI adapters is that they almost always depend on the built-in Windows MIDI drivers, and those drivers don't handle the type of Sysex streaming required for these sort of updates very well.

I don't see a DT update that was released in 2018... What model number are you looking at? What's the firmware version of that update?

The DT amps have to be running the 2.0 firmware in order for the L6 Link control functionality to work properly. It's not new, by any means. It was released in 2012. But that added a ton of MIDI functionality to the DT amps, and that's what enables the L6 Link connection to work for these new Helix control functions.

Yes, exactly.

Go straight to 2.8.

It does take a while the first time, especially if you have a lot of presets. It should only do it the first time you restart after the update.

The Helix works differently than the HD series with L6 Link. Again, you need to have the 2.0 update installed on the DT for it to work with the Helix. If audio is mint through, but control isn’t, I suspect your DT needs updated.

You have to have the delay time set to a note value for the tap tempo to affect it.