# Transition Markers and Regions are not working as expected **URL:** \ **Category:** FMOD Studio\ **Created:** [September 29, 2025, 4:10pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410 "2025-09-29T16:10:17Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![modulesplusmusic](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@modulesplusmusic](https://qa.fmod.com/u/modulesplusmusic)\ **Post date:** [September 29, 2025, 4:10pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/1 "2025-09-29T16:10:17Z")
I just upgraded to the latest FMOD Studio and I’m experiencing something weird with the transition markers. I’m wrapping the entire music system in a single event so I have more control over transitions. I noticed when I put a transition marker at the beginning of the event and change the playlist parameter, that event plays (transport marker running through it) but it cannot be heard. Here’s how it looks when it does not work: **Destination Marker On Beginning Of Event:** ![D Marker Beginning](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/c/cabb7e157a5fac26bd995eff7118b89ba36a783c.png) However, if I put some time between the marker and the event itself it then plays as expected: **Destination Marker Before The Event:** ![D Marker Buffer](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/10065bad786a1cfdbc20d151022075b9256527f6.png) This alternative can work, but it’s bugging me from an organizational point of view. Is this a known bug? Or am I doing something wrong? I’ve included some other images to show how I have my logic set up to rule anything out. **Parameter Settings:** ![Param Sheet](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/7/7989149eecca5896b948a2d720184756caf91f02.png) **Logic Inside Transition Regions:** ![Second Transition Region Logic](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/a/a30037b8339638b21f8ddc866d558e1a660d0306.png) ![First Transition Region Logic](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/1281acab26aa711b2f32313b511489babaeb023f.png) **Fadeout Settings For Transitions:** ![Transition Fade](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/3/3e4dd18183d401941265c191ade9b0c7ed1880e2.png) **FMOD Studio Version:** ![Version](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/1248fe31206ab9e4e0f6e7cfb21324ffc4a3328d.png) ---
**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:** [October 8, 2025, 12:44am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/2 "2025-10-08T00:44:58Z")
Despite testing with a close replica of what you’ve shown in your screenshots, I’m afraid I haven’t been able to reproduce this issue. I must be doing something differently to you, but I’m not sure what. Could you please upload a project that exhibits this issue to the [uploads tab of your profile page](https://www.fmod.com/profile#uploads), so that we can investigate it in depth? ---
**Author:** ![modulesplusmusic](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@modulesplusmusic](https://qa.fmod.com/u/modulesplusmusic)\ **Post date:** [October 8, 2025, 7:31pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/3 "2025-10-08T19:31:41Z")
Thanks for the reply Joseph! Unfortunately I’m not sure if I can upload this particular project as we haven’t announced our title yet and I would have to check with our team before sharing content. However, I can work on recreating this project with some content not related to the game this week! Will repost another reply once I’ve done that. ---
**Author:** ![rukukun](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/rukukun/32/9215_2.png) [@rukukun](https://qa.fmod.com/u/rukukun)\ **Post date:** [November 2, 2025, 6:26pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/4 "2025-11-02T18:26:04Z")
Hi, can confirm that I am encountering this same issue after upgrading from FMOD 2.02.24 to FMOD 2.03.09 (Both studio and Unity integration). When a clip is aligned perfectly with a destination marker, the destination clip will not play at the end of the transition. The work around for me has been to offset the destination clip in the transition. See image below, when “BGM” changes to “Combat”, the clip on the “Wander” track fades out, but when the transition ends, the audio from “CombatA” does not play (also no activity on the meter) unless I have that small (orange) offset on the destination track. With the small offset on the “CombatA” track, the audio correctly plays as it did in FMOD 2.02.24. ![image_2025-11-02_192353695](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/3/30617bfa8bf0c9e07685cafdc2a70ba56ae9a21a.png) ---
**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:29am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/5 "2025-11-07T05:29:32Z")
Hey, I am facing the same issue as well. After updating to the latest fmod if the marker is ahead of the track, it works but when both are in conjunction it does not work. Has the fmod team be made aware of this issue? I had to update to the latest fmod since the older version was not 16kb page file compliant for google play store. ---
**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:38am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/6 "2025-11-12T03:38:24Z")
Thanks to your screenshot, @rukukun , I’ve been able to reproduce this issue, and it definitely seems like a bug. I’ve added it to our bug tracker, so it should be fixed in an upcoming version of FMOD Studio and the FMOD Engine. ---
**Author:** ![humblebeegames](https://avatars.discourse-cdn.com/v4/letter/h/c5a1d2/32.png) [@humblebeegames](https://qa.fmod.com/u/humblebeegames)\ **Post date:** [December 15, 2025, 2:49am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/7 "2025-12-15T02:49:20Z")
Hey Joseph I am also experiencing this problem in the latest 2.02.32 version as well. I tried to downgrade to the previous version that I already had which was 2.02.21 and there it works fine. However that version is no longer compliant with the 16kb requirement that Google has. Is there any ETA on when this issue might get resolved? Our FMOD studio project is built on 2.02.25, hence we did not try the 2.03.x version inside Unity and also I am not sure the version where it works is 16kb compliant with Google. ---
**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:** [December 16, 2025, 12:55am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/8 "2025-12-16T00:55:59Z")
> [@humblebeegames](#): > > Is there any ETA on when this issue might get resolved? Our agile development model means that the scope and schedule of each release is subject to change, so we can’t provide accurate estimates as to when specific features and fixes will be released. However, I can tell you that we consider this bug to be a critical issue, and a fix is already scheduled for development, though it has not yet been completed or tested. ---
**Author:** ![Maarti](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Maarti](https://qa.fmod.com/u/Maarti)\ **Post date:** [January 16, 2026, 5:22am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/9 "2026-01-16T05:22:41Z")
Hello, I am also affected by this issue for more than a month, and I was eagerly waiting for the next release but I don’t see the fix included in [today’s release](https://www.fmod.com/docs/2.03/studio/welcome-to-fmod-studio-revision-history.html). Isn’t this a critical regression? On our side, most of our audio is no longer functioning correctly because we rely heavily on transitions. **Is there any workaround other than adding a delay?** (Unfortunately, this is not an option for us: our transitions are _intros_ for the following content, which is a seamless loop. Adding a delay at the start of the loop would completely break it) 😔 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/4/43dc216b20a1b63291fd41f08960176afd4887e2.png) We also cannot downgrade, as we have moved to Unreal Engine 5.6, which is only supported starting from FMOD 2.03. Thank you for your help! ---
**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:** [January 20, 2026, 1:13am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/10 "2026-01-20T01:13:30Z")
> [@Maarti](#): > > Isn’t this a critical regression? We do consider it a critical issue, yes. Unfortunately, we are sometimes forced to reschedule even critical issues to later versions; looking at our records, that is what happened in this case. > [@Maarti](#): > > Is there any workaround other than adding a delay? According to our tests, the issue affects all instruments that start exactly at the destination a transition timeline that does not have a destination region. This means that the only ways to work around this issue are to either add a destination region to the transition timeline, or to move the instrument so that it starts at a slightly different point on the timeline, and both of those solutions will result in the instrument beginning play at a slightly different time. I suppose you could add a short period of silence to the start of the asset(s) associated with the instrument, and offset the instrument’s position by an amount of time equal to the length of that silence, ensuring that the audio starts at the same time? That solution might not be suitable if you need the instrument to loop, however. ---
**Author:** ![phbarralis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/phbarralis/32/9521_2.png) [@phbarralis](https://qa.fmod.com/u/phbarralis)\ **Post date:** [January 20, 2026, 3:37pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/11 "2026-01-20T15:37:04Z")
> [@joseph](#): > > I suppose you could add a short period of silence to the start of the asset(s) associated with the instrument, and offset the instrument’s position by an amount of time equal to the length of that silence, ensuring that the audio starts at the same time? That solution might not be suitable if you need the instrument to loop, however. That also not possible if everything needs to be always synced to the bar (as in, a rhythm based game) 😶. Anyway thanks for looking into it! ---
**Author:** ![Maarti](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Maarti](https://qa.fmod.com/u/Maarti)\ **Post date:** [January 20, 2026, 3:56pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/12 "2026-01-20T15:56:39Z")
> [@joseph](#): > > We do consider it a critical issue, yes. Unfortunately, we are sometimes forced to reschedule even critical issues to later versions; looking at our records, that is what happened in this case Thanks for the update and following up! 👍 ---
**Author:** ![phbarralis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/phbarralis/32/9521_2.png) [@phbarralis](https://qa.fmod.com/u/phbarralis)\ **Post date:** [February 19, 2026, 2:35pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/13 "2026-02-19T14:35:44Z")
hi there @joseph, gentle ping to know if you’ve got news about this bug fix. Otherwise, do you know in which version this was introduced, and if we could potentially downgrade the project/unity plugin to an earlier version? ---
**Author:** ![dishoa](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dishoa](https://qa.fmod.com/u/dishoa)\ **Post date:** [February 19, 2026, 2:51pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/14 "2026-02-19T14:51:53Z")
Hi, I’m also waiting for the fix and currently using version 2.03.08, where it works fine. I think the next version introduced this bug. ---
**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:** [February 24, 2026, 11:52pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/15 "2026-02-24T23:52:09Z")
> [@phbarralis](#): > > gentle ping to know if you’ve got news about this bug fix. Since the last time I provided an update, the bug fix was scheduled and assigned to a developer, who began work on the fix. > [@phbarralis](#): > > Otherwise, do you know in which version this was introduced, and if we could potentially downgrade the project/unity plugin to an earlier version? According to my tests, this issue was introduced in version 2.03.09. You should therefore be able to avoid the bug by using any earlier version. > [@dishoa](#): > > I’m also waiting for the fix and currently using version 2.03.08, where it works fine. I think the next version introduced this bug. You think correctly; the bug was, indeed, introduced in version 2.03.09. I’ll add you to the list of people who’ve reported this issue. ---
**Author:** ![phbarralis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/phbarralis/32/9521_2.png) [@phbarralis](https://qa.fmod.com/u/phbarralis)\ **Post date:** [February 25, 2026, 12:08am UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/16 "2026-02-25T00:08:22Z")
Thanks a lot for the update Joseph! ---
**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:** [October 4, 2026, 10:26pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/17 "2026-10-04T22:26:43Z")
FYI, this issue was fixed in 2.03.13. ---
**Author:** ![phbarralis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/phbarralis/32/9521_2.png) [@phbarralis](https://qa.fmod.com/u/phbarralis)\ **Post date:** [October 4, 2026, 10:45pm UTC](https://qa.fmod.com/t/transition-markers-and-regions-are-not-working-as-expected/23410/18 "2026-10-04T22:45:24Z")
Awesome, we’ll be able to update then. Thanks Andrew and Joseph!