Hi everyone, I’m currently refining a music system combining horizontal, vertical and generative technics. Since I do not really like the way transition timelines work (this is just a matter of taste, the technical aspect is perfect), I’m working with async events scattered through the timeline. I…

You have to dimension your instrument less than one beat (while being async and uncut, so it will play entirely), and set trigger behavior quantized to the beats. By doing that, there will be only one point where the instrument will be allowed to start. Alternatively, though it’s less elegant, you …

As Alcibiade says, if you want an instrument to trigger only on a certain beat, you should quantize the instrument to trigger on beats, and reduce the size of its trigger region to only cover the specific beat you want it to be triggered on. This works because a trigger region represents the region …

This is indeed a perfect solultion Alcibiade and Joseph. Thank you very much for the tip. I’m gonna test this out a bit more in depth ( I only made a quick test ), as soon as I got something that works, I’ll mark one of your answer as the solution. Thank you!

It works perfectly ! Thank you very much Alcibiade and Joseph.

You are indeed, right, there is a situation I did not thought of… I’m gonna answer in your thread.

In your case, note that my other solution still stands: make your instruments as little as possible, in place of (or in top of) quantization. That’s not a very elegant solution (especially for OCD people :wink: ) but it works.

Indeed :smiley: ! That said, it becomes really hard to be efficient (when duplicating containers) if the things are super tiny. Especially in really complex sequences like music. The problem you’re refering to in your thread still exists tho. Your solution works perfectly to ensure that the layer …

As mentioned in the other thread, tempo-quantized asynchronous instrument playing even if their trigger conditions cease to be met is a bug, and will be fixed in an upcoming release of FMOD Studio.

Async events, quantization and starting point

FMOD Studio

Alcibiade October 14, 2021, 8:51pm 6

In fact I’m afraid the solution we gave, using quantization, wasn’t correct. Could you please check the case I describe in that post and tell me if you notice the same problem?

Topic		Replies	Views
Quantized async instruments strange behavior FMOD Studio	8	563	March 22, 2022
Trigger behavior + parameter issue FMOD Studio	10	463	September 23, 2024
Nested-Looped-Quantized Event Problem FMOD Studio	2	4121	February 27, 2017
Quantisation settings based on another events tempo FMOD Studio	7	431	December 7, 2023
[2.02.04] Quantization bug affected by time signature position FMOD Studio	22	702	September 25, 2024

Async events, quantization and starting point

Related topics