# Snapshot not releasing but ramping up again on stop when another snapshot is triggered

**URL:** <https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342>\
**Category:** Unity\
**Tags:** unity\
**Created:** [October 23, 2020, 1:19pm UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342 "2020-10-23T13:19:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wobblersound](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@wobblersound](https://qa.fmod.com/u/wobblersound)\
**Post date:** [October 23, 2020, 1:19pm UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342/1 "2020-10-23T13:19:34Z")

</div>

Hello,

it seems there’s an issue when stopping / starting snapshots.

version used: fmod 2.01.05 - unity 2020.1.2f1

scenario

- the snapshots are started / stopped by code
- the snapshots have an AHDSR modulator on their intensity (1 sec atk, 4 sec release)
- the two snapshots are set to override (but bug will also happen with blend mode), they just set 2 send volumes on a bus (they “enable” their send and mute the other one)

legend: for simplicity i call the screenshotnames  
SNP\_BiomeStartRVB -\> SNPStart  
SNP\_Biome1RVB -\> SNP1

- start snapshot SNPStart
- at some point, stop SNPStart and at the same time start another type of snapshot SNP1. see attached screenshot that as soon as SNP1 starts, the intensity of SNPStart is instantly cut off instead of fading out, and also ramping up again instantly

note that the snapshot SNPStart still exists for the remaining 4 seconds, but its intensity is set wrong due to the other snapshot being set.

notice that if i only stop the SNPStart the release ramp works just fine.

 ![fmod ramp snapshot](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/0/0c006d23cfddffe2fdce9e62fba1a59652add801.jpeg)

sidenote:  
(i think i could observe the same issue when triggering snapshots as instruments from within studio with the “not stopping condition” and stop one event from another event with command instrument…)

please elaborate 🙂

---

<div class="post-metadata">

**Author:** ![wobblersound](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@wobblersound](https://qa.fmod.com/u/wobblersound)\
**Post date:** [November 3, 2020, 8:25am UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342/2 "2020-11-03T08:25:46Z")

</div>

hello again, i really would appreciate an answer here. thanks for investigating.

---

<div class="post-metadata">

**Author:** ![wobblersound](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@wobblersound](https://qa.fmod.com/u/wobblersound)\
**Post date:** [November 10, 2020, 1:21pm UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342/3 "2020-11-10T13:21:00Z")

</div>

and again, after another week, i ping here to see if the ppl of fmod have anything to say to this?

---

<div class="post-metadata">

**Author:** ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)\
**Post date:** [November 11, 2020, 10:40pm UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342/4 "2020-11-11T22:40:01Z")

</div>

Thanks for reporting this issue. We’ve been able to reproduce it, but are still working on identifying the root cause.

In any case, this is definitely a bug, and will be fixed in an upcoming release of FMOD Studio.

---

<div class="post-metadata">

**Author:** ![wobblersound](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@wobblersound](https://qa.fmod.com/u/wobblersound)\
**Post date:** [November 12, 2020, 12:58pm UTC](https://qa.fmod.com/t/snapshot-not-releasing-but-ramping-up-again-on-stop-when-another-snapshot-is-triggered/16342/5 "2020-11-12T12:58:09Z")

</div>

ok, thx for letting us know. looking forward to the fix 🙂
