# Stoping nested events when parent event stops **URL:** https://qa.fmod.com/t/stoping-nested-events-when-parent-event-stops/17760 **Category:** FMOD Studio **Created:** [October 7, 2021, 3:41pm UTC](https://qa.fmod.com/t/stoping-nested-events-when-parent-event-stops/17760 "2021-10-07T15:41:45Z") **Posts on this page:** 1 **Showing post:** 11
### 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: [October 11, 2021, 8:34am UTC](https://qa.fmod.com/t/stoping-nested-events-when-parent-event-stops/17760/11 "2021-10-11T08:34:04Z")
> [@g.hadji](#): > > Otherwise I would need to set the max instance of my nested event to 2 instead of 1, to avoid any brutal cut from the stealing feature. Yes, I already raised this point and made a suggestion for steal release time, here: > [@Suggestion: steal release time](https://qa.fmod.com/t/suggestion-steal-release-time/17144/4): > > In fact, after thinking twice, I don’t really get the argument. I’ll explain myself. If stealing is a tool for resource management but always makes a pop by abruptly cutting the sound, then sound designers will mostly avoid to use it, but rather use it as a safety net (ideally never triggering). Eventually, why not leave the trade off to the sound designer, between an instant and hard steal, or a delayed, smoothed steal (with a temporary stealing voice count overload)? It would greatly expand … However, in your case, I don’t think you should have set a max poly. You let the release cut the sound, even if it stacks with previous entries. > [@g.hadji](#): > > I guess that in the end, the volume automation method is corresponding more to what I had in mind in term of fast switching behaviour. That’s good, then! --- _[View the full topic](https://qa.fmod.com/t/stoping-nested-events-when-parent-event-stops/17760)._