# Sound container behavior bug

**URL:** https://qa.fmod.com/t/sound-container-behavior-bug/11388
**Category:** FMOD Studio
**Created:** [April 8, 2014, 10:55am UTC](https://qa.fmod.com/t/sound-container-behavior-bug/11388 "2014-04-08T10:55:15Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ninomojo](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@ninomojo](https://qa.fmod.com/u/ninomojo)
#### Post date: [April 8, 2014, 10:55am UTC](https://qa.fmod.com/t/sound-container-behavior-bug/11388/1 "2014-04-08T10:55:15Z")

</div>

Hi there,

Each time an event is called, I want it to play one of 5 sounds, going to the next sound sequentially, always in the same order. So I drag’n drop my 5 sounds into a sound container, and I uncheck the random button. Like so:

![](https://dl.dropboxusercontent.com/u/5390428/Screen%20Shot%202014-04-08%20at%2012.36.38%20PM.png)

The problem is, the sequence that is played isn’t the one that is displayed in the UI (“1,2,3,4,5”), but something like “1,4,3,5,2”.

This is kind of an unexpected behavior. A workaround that produced the expected behavior (at least in Fmod Studio, haven’t tried in game yet) was adding sound 1 first, then drag’n dropping the next sounds one after another. It looks exactly the same in the interface, but now it plays in the expected order.

Cheers!

---

<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: [April 16, 2014, 7:11am UTC](https://qa.fmod.com/t/sound-container-behavior-bug/11388/2 "2014-04-16T07:11:13Z")

</div>

A fix has been created, and will be included in the next public release of Studio.

---

<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: [April 8, 2014, 11:49pm UTC](https://qa.fmod.com/t/sound-container-behavior-bug/11388/3 "2014-04-08T23:49:09Z")

</div>

Thanks for the bug report. We’re already aware of this issue, and are working on a fix.
