# Track Mutes After Transition Timeline in Horizontal Music Event (Possible Bug?) **URL:** \ **Category:** FMOD Studio\ **Created:** [November 5, 2025, 10:56am UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589 "2025-11-05T10:56:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Fabulousk](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fabulousk](https://qa.fmod.com/u/Fabulousk)\ **Post date:** [November 5, 2025, 10:56am UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/1 "2025-11-05T10:56:13Z")
I recently showed my students how to create a horizontal music event in FMOD, where multiple level tracks are placed next to each other on the timeline and switched using a labeled parameter with magnet regions. Each magnet region uses a 2-bar transition timeline, where the source track fades out over 2 bars before the destination track starts. However, some students encountered an issue where, after the transition, the destination track is suddenly muted. The audio track itself remains at 0 dB, but no sound plays. I was able to fix it temporarily by extending the destination track one bar earlier into the transition timeline, but technically it should work without that adjustment. Is this a known bug, or does anyone know a proper fix for this behavior? Thanks in advance. ---
**Author:** ![humblebeegames](https://avatars.discourse-cdn.com/v4/letter/h/c5a1d2/32.png) [@humblebeegames](https://qa.fmod.com/u/humblebeegames)\ **Post date:** [November 7, 2025, 5:37am UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/2 "2025-11-07T05:37:17Z")
Bump ---
**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 12, 2025, 3:55am UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/3 "2025-11-12T03:55:01Z")
This is a known bug that was introduced in FMOD Studio version 2.03.09: If an instrument begins exactly when a transition timeline ends, and that transition timeline does not have a destination region, that instrument may not trigger correctly. This issue is already in our bug tracker, and will be fixed in an upcoming release of FMOD Studio. In the mean time, you could use a workaround (such as the one you already discovered) or use FMOD version 2.03.08 or earlier. ---
**Author:** ![miur-us](https://avatars.discourse-cdn.com/v4/letter/m/d2c977/32.png) [@miur-us](https://qa.fmod.com/u/miur-us)\ **Post date:** [December 21, 2025, 8:16am UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/4 "2025-12-21T08:16:58Z")
After updating from FMOD 2.03.08, I noticed this issue on Unity last night. I’m waiting bug fix. Thanks for FMOD team! ---
**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\ **Post date:** [December 21, 2025, 11:52pm UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/5 "2025-12-21T23:52:44Z")
Thanks, we’ve registered your interest. ---
**Author:** ![norbertweiher](https://avatars.discourse-cdn.com/v4/letter/n/b38774/32.png) [@norbertweiher](https://qa.fmod.com/u/norbertweiher)\ **Post date:** [June 24, 2026, 1:34pm UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/6 "2026-06-24T13:34:05Z")
Just encountered the same bug (Unity / FMOD 2.03.09 combo). Any news on the timeline for a fix? ---
**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\ **Post date:** [June 24, 2026, 10:44pm UTC](https://qa.fmod.com/t/track-mutes-after-transition-timeline-in-horizontal-music-event-possible-bug/23589/7 "2026-06-24T22:44:29Z")
This was fixed in 2.03.13.