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.
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?
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?
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 :
and
You’ll find some workarounds on those links, though.
Damn.
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.
Cheers!
