Stupid user error- beware of yourself

[jbuhajla]

Just thought I would share a quick silly mistake I was making. I was adjusting on my "favorite" preset in 1A. A short time into it I thought "I had better save this to another slot so I don't screw up this one in 1A". We'll about 20 minutes later, made my complete weekly backups, then powered down until later that day. I powered back on later, and noticed that none of my changes I made to my preset were saved. After about 30 minutes of wasting time troubleshooting non-existent issues, I remembered I saved the preset in another slot before making all the changes. The preset had exactly the same name, just in a different slot. 

 

So, it is really easy to do something silly, but think that the Helix malfunctioned. Just something to keep in mind kids....

[cruisinon2]

"ID10T error"...always a favorite. ;)

[duncann]

I can remember numerous times in the past where I'd edit a preset, save it to a different location - sometimes with the same name sometimes not, and continue on. Session done, power off Helix. Next session, turn Helix on and forgetting what I did with the preset in the previous session, I subtly notice something doesn't sound right. It turned out that Helix didn't remember that last preset I was on when Helix was powered off, but instead recalled the non-edited version of the preset. This doesn't happen if you engage the edited preset twice before powering off. I'm not sure, but this might have been fixed recently, that is if this whole thing wasn't an hallucination.

[zooey]

If I'm not mistaken, on power-up, it goes to the last RECALLED preset, and Save As isn't a recall action. After a Save As, make sure you switch to another preset and back to the newly saved copy if that's where you want to be next time.

[duncann]

If I'm not mistaken, on power-up, it goes to the last RECALLED preset, and Save As isn't a recall action. After a Save As, make sure you switch to another preset and back to the newly saved copy if that's where you want to be next time.

 

Here's what I see happening, and maybe it's correct behavior or not. It doesn't seem correct.

 

Edit a preset and then save it to a new location. When you do this, the preset you just saved is automatically active, so I would assume this is the preset that's recalled upon a power cycle. It is not. The preset that was active immediately before the save procedure is the one that's recalled upon a power cycle. To get it to recall the newly saved/edited preset, you must engage this preset before powering off, even though it's already active. It seems to me that whatever preset I see on Helix's screen should be the one recalled upon power on. I guess this could be considered a bug or a minor oversight.

[jbuhajla]

Here's what I see happening, and maybe it's correct behavior or not. It doesn't seem correct.

 

Edit a preset and then save it to a new location. When you do this, the preset you just saved is automatically active, so I would assume this is the preset that's recalled upon a power cycle. It is not. The preset that was active immediately before the save procedure is the one that's recalled upon a power cycle. To get it to recall the newly saved/edited preset, you must engage this preset before powering off, even though it's already active. It seems to me that whatever preset I see on Helix's screen should be the one recalled upon power on. I guess this could be considered a bug or a minor oversight.

Ah HA, that is exactly what is happening. It is not a hallucination. Not a bug, but just a good FYI on how it works, and I'll definitely be aware of this in the future. 

 

Keep this in mind when someone posts about "preset not saving correctly". This may be what is happening. 

[MusicLaw]

Good points! Just because that is the way it is operating now, does not mean that it might not be able to be changed in a future firmware release. This should not be more involved than changing/adding/ammending a few lines of code.

 

Submit the suggestion via an IdeaScale post! If enough people make Line 6 aware of their desire that the behavior be changed, it just might be.

[zooey]

Here's what I see happening, and maybe it's correct behavior or not. It doesn't seem correct.

 

Edit a preset and then save it to a new location. When you do this, the preset you just saved is automatically active, so I would assume this is the preset that's recalled upon a power cycle. It is not. The preset that was active immediately before the save procedure is the one that's recalled upon a power cycle. To get it to recall the newly saved/edited preset, you must engage this preset before powering off, even though it's already active. It seems to me that whatever preset I see on Helix's screen should be the one recalled upon power on. I guess this could be considered a bug or a minor oversight.

I think we're saying the same thing. You have to RECALL a preset to get it entered into Helix's "last preset" storage slot. Saving a preset doesn't do that.

 

And I agree, that's not intuitive, and should be fixed. I've just learned to live with it, let Line 6 concentrate on stuff that's harder to work around.

[duncann]

I think we're saying the same thing. You have to RECALL a preset to get it entered into Helix's "last preset" storage slot. Saving a preset doesn't do that.

 

And I agree, that's not intuitive, and should be fixed. I've just learned to live with it, let Line 6 concentrate on stuff that's harder to work around.

 

Yes. Exactly.

 

At the least, when saving a preset to a different slot, it shouldn't then make the saved preset active without also placing it in the last preset storage slot. Or, continue to make it active, but also put it in the last preset storage slot.

 

Pretty minor thing, and probably easy to fix, and there's indeed better things to focus on. I've kind of it ignored also. It has caught me off guard more than once though.

[jbuhajla]

See, I put out information thinking that I was just being dumb, but it was actually booting up with the previous preset. I am glad I decided to post this. I thought maybe my middle agedness was playing tricks on me. 

[zooey]

I'm sure it is (;-)