# Envelope 1 Attack/Decay Bug?

**URL:** <https://forum.udo-audio.com/t/envelope-1-attack-decay-bug/1171>\
**Category:** Super 6\
**Tags:** issue\
**Created:** [25 April 2022 00:26 UTC](https://forum.udo-audio.com/t/envelope-1-attack-decay-bug/1171 "2022-04-25T00:26:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![brain\_tan](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@brain\_tan](https://forum.udo-audio.com/u/brain_tan)\
**Post date:** [25 April 2022 00:26 UTC](https://forum.udo-audio.com/t/envelope-1-attack-decay-bug/1171/1 "2022-04-25T00:26:47Z")

</div>

Adjusting attack in a saved patch causes decay to jump to its manual position, and vice versa. (Desktop running the latest firmware, manual mode is off)

To reproduce this behavior:

1. Set attack and decay on envelope 1 to something slow, near maximum

2. Load any patch saved with a quick attack and decay.

3. Adjust the attack.

On all patches, including init, this causes the decay value to jump to the slider’s manual position, even though I didn’t move it. The same thing happens if I move decay: attack will revert to its manual setting. I haven’t noticed other interactions between envelope sliders but maybe there are others. Anyone else experiencing this?

---

<div class="post-metadata">

**Author:** ![Mauro](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mauro](https://forum.udo-audio.com/u/Mauro)\
**Post date:** [25 April 2022 09:22 UTC](https://forum.udo-audio.com/t/envelope-1-attack-decay-bug/1171/2 "2022-04-25T09:22:34Z")

</div>

The same on my keyboard version running FW 0.30.

---

<div class="post-metadata">

**Author:** ![udo-audio](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.udo-audio.com/udo-audio/32/8_2.png) [@udo-audio](https://forum.udo-audio.com/u/udo-audio)\
**Post date:** [26 April 2022 06:43 UTC](https://forum.udo-audio.com/t/envelope-1-attack-decay-bug/1171/3 "2022-04-26T06:43:44Z")

</div>

@brain_tan yes this happens. Thanks for detailed feedback. Is an easy fix. Expect this addressed in next release which is work in progress at the moment
