# FMOD sound release and pcmreadcallback execution

**URL:** <https://qa.fmod.com/t/fmod-sound-release-and-pcmreadcallback-execution/14631>\
**Category:** FMOD Engine\
**Created:** [May 1, 2019, 4:12pm UTC](https://qa.fmod.com/t/fmod-sound-release-and-pcmreadcallback-execution/14631 "2019-05-01T16:12:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jossdisguise](https://avatars.discourse-cdn.com/v4/letter/j/b77776/32.png) [@jossdisguise](https://qa.fmod.com/u/jossdisguise)\
**Post date:** [May 1, 2019, 4:12pm UTC](https://qa.fmod.com/t/fmod-sound-release-and-pcmreadcallback-execution/14631/1 "2019-05-01T16:12:20Z")

</div>

Having a problem where the pcmreadcallback is still executed after FMOD:🔉:release has been called and FMOD::Channel::stop has been called on the channel playing the sound.

Is there anyway to;

- Synchronously release the sound and channel, waiting for any outstanding queued callbacks to be completed.
- Guarantee the ordering of release / stop and the callback?

We have a class which wraps a sound and channel and implements the callback (this ptr passed via user data). This behaviour is causing a rare case where the callback is executed after the class has been destroyed.

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [May 6, 2019, 4:50am UTC](https://qa.fmod.com/t/fmod-sound-release-and-pcmreadcallback-execution/14631/2 "2019-05-06T04:50:27Z")

</div>

Are you able to share a reproduction of the issue at all?  
I haven’t been able to get that behavior in any tests I have run.