# How to prevent silencing of instruments on double-trigger with ADSR volume envelope **URL:** https://qa.fmod.com/t/how-to-prevent-silencing-of-instruments-on-double-trigger-with-adsr-volume-envelope/18694 **Category:** FMOD Studio **Created:** [April 22, 2022, 10:54pm UTC](https://qa.fmod.com/t/how-to-prevent-silencing-of-instruments-on-double-trigger-with-adsr-volume-envelope/18694 "2022-04-22T22:54:43Z") **Posts on this page:** 1 **Showing post:** 18
### Author: ![Alcibiade](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/alcibiade/32/4284_2.png) [@Alcibiade](https://qa.fmod.com/u/Alcibiade) #### Post date: [April 28, 2022, 8:49am UTC](https://qa.fmod.com/t/how-to-prevent-silencing-of-instruments-on-double-trigger-with-adsr-volume-envelope/18694/18 "2022-04-28T08:49:36Z")
> [@KurtHarlandLarson](#): > > I was in the middle of typing up a complete description for you of how I have these test events set up, when I think I discovered the crucial thing: I didn’t have ‘Cut’ on for some of my event instruments. When I turned that on, the behavior changed to be what one would expect and want. On a nested event which contains a loop, a transition, is persistent, or whatsoever (in short: isn’t “oneshot”), the cut button shouldn’t do anything. Which is easy to understand: the event has to cut anyway, otherwise it would loop indefinitely (the stuck loop that you fear!). If it does something different with the cut button checked or unchecked, it’s probably a bug, which could be similar to [the one I found](https://qa.fmod.com/t/bug-transition-timeline-makes-nested-event-play-forever-while-untriggered/17774) (and was fixed) some time ago. By the way, I would advocate hiding this button in the case the nested event isn’t oneshot, in a future fmod update, it will make things clearer. --- _[View the full topic](https://qa.fmod.com/t/how-to-prevent-silencing-of-instruments-on-double-trigger-with-adsr-volume-envelope/18694)._