AHDSR and instrument sync issues

Hey friends. Need some help here.

I got a 2D music event containing 8 tracks (layers) with nested instruments.

I’ve also set a parameter to switch between layers and markers (values 0-7) and also conditioned the instruments to trigger based on a certain value.

I used nested instruments so I could use the AHDSR when I switch between layers.
I couldn’t find a better way.

So… the AHDSR behaves like it should now, but the tracks are out of sync now and I’m at a dead end.

I’m sure there is a better way to do this, but I just miss it.

How would you guys best approach this?

Thanks in advance!


Apologies for the delayed response.

Is it possible to get a screenshot of the event and how you have the AHDSR is set up? Could you also elaborate on the aim of your set up?


Basically, I just want to be able punch in and out, back and forth between the tracks and markers with applied ahdsr (for transition) without losing sync.

I managed to make the ahdsr behave like I wanted by putting it on the nested instruments (not on master).

However, I also set trigger conditions on the instruments as well and when they are triggered they are not in sync. I’m aware that that’s a problem, but I cant find a way where they are triggered at the same time and the ahdsr works as intended.

1 Like

Any solutions? @Connor_FMOD

I don’t get the event structure. Since nested events are always async, they will play all along and nothing will happen when you transition from One to Seven or anything else. Am I missing something?

When you transition between the instruments (the nested events) the tracks get out of sync, because they are trigger conditioned. The only way for them to be in sync is if they are all triggered in the same time.
I don’t want that.
I want to be able punch in and out (transition) between them back and forth with AHDSR applied and for them to be in sync.

So here is an example.
I have 8 markers and a “Intensity” parameter set (none to seven).
“None” plays track one only , “One” plays tracks one and two, “Two” plays track one, two, three and so on.

Lets say I want to get back to parameter “None”, tracks two, three and four should fade out (AHDSR). Then I wan to to go to “Six”, tracks two, three, four, five and six should slowly fade in (AHDSR)

I think I get it: the purpose of the timeline is to execute the conditional trigger behavior.
But what do you mean exactly by “in sync”? Do you want the new track to begin at start, in sync with the beat? Do you want the new track to begin where it should be if it had played from the beginning when the event has started?

The second one, yes. I want the next track to begin where it should be, just like if it had played from the beginning when the event has started.

In fact, no, I still don’t see the purpose of your timeline. The instruments conditional trigger behavior comes from a parameter, not from the regions. So what’s the point with those regions?

It’s not a full screen.

This approach is for both vertical and horizontal music composition.

The regions are for certain other SFX instruments which are not sync dependent.
Ignore the regions for now.

Even without the regions, I’m still not able to punch in and out between the nested music tracks, where sync and ahdsr are important.

Ok. You can’t do that by punching-in nested events, cause nested events are async, which means they always start at their beginning. You can use nested events but you’ll have to play them from the beginning, and automate the volume. Note that the synchronisation between tracks will never be checked anymore, so it can be somewhat risky ; it’s safer to use synced instruments. Either ways, the problem is the volume automation (or AHDSR). In fact you’ll be facing the problem that FMOD lacks an essential feature, which I asked for almost 2 years ago, and which is the most asked feature on this forum :


You’ll find some workarounds on those links, though.

That’s exactly what I need.
It would be great if this feature could be added this year.
I have a workaround, a less elegant one, but good enough.
But it is what it is, I guess.
Thank you for your time and response.

1 Like


@Goran1, apologies for not getting back to you.

@Alcibiade, thank you for your help!

I can confirm this feature is in development.