I am trying to use delays for command instruments, but it seems like it does not work. If I e.g. use a command instrument to set a parameter to 1 and that parameter trigs an instrument, I hear the intsrument play as soon as the playhead hits the command instrument, even though I put a 2 second delay interval on it.
Is this a bug?
Hi,
Unfortunately, I haven’t been able to reproduce the issue on the latest release (2.02.17), or 2.02.03, which you said you’ve used in a previous post.
On further testing, I’ve been able to reproduce an issue similar to what you’re describing, but only when playing a command instrument on one parameter sheet and moving the cursor/parameter value off the command instrument.
Could you please provide your FMOD Studio version, as well as some more details on where you’re observing this issue (parameter sheets, timeline, etc.) and a simple list of steps that consistently reproduces the issue for you?
Hi Louis.
I found out when it is happening:
In this case the delay does not work. Did that make sense?
I am on 2.02.12 btw
Thanks for the additional information, that does makes sense. To clarify, are you observing that the delay is ignored at all/any points in timeline region the command instrument occupies? Or is it only when the end of the loop is reached, and as a result the command instrument untriggers and then retriggers?
The delay is ignored any time in the timeline when the command istrument is trigged by setting a parameter
Hi, have there been any solutions to this issue? I think it is the only way to complete my project.
Unfortunately, while the issue has been noted, I can’t offer any exact time frame that a fix will become available. In the meantime, so that I can potentially help you to work around it, can I get you to elaborate on the context of the exact issue that you’re running into?
Yep sure. I’ve got a relatively simple unity game that plays looped music depending on which box the player has collided with most recently. In FMOD, the entire thing is on a parameter sheet, where a global variable is responsible for which music segment currently plays. I need to quantise these changes, so that the music seamlessly transitions from segment to segment. I have tried quantising with nested events and command instruments, however the quantisation doesnt work and the audio files immediately transition. When using just the quantisation of the single/multiple instrument tracks, the audio cut out as soon as the parameter changed. Are there any other ways to do this?
The simplest way to handle this would be to set up the quantized transitions in a single timeline, i.e. something like the following:
In this example, I have 3 separate audio files that are set up with corresponding magnet and loop regions. The magnet regions will transition the timeline cursor to them when the parameter GlobalParam equals the corresponding value (i.e. 1 = “Track 1”). The magnet region transitions are also quantized to a bar, and each one has a one bar transition region to crossfade the transition.
If you instead wanted to stick with nested/referenced events, you could set up a parent event as follows:
Each of event instruments is quantized to a bar, and I’ve added a timeline to the parent event with a temp marker to ensure the parent event is quantizing to the correct tempo.
Then, I’ve set the nested events to use a one bar transition region to fade in/out when the they start and end, though you could opt to use an AHDSR on the master track volume for this instead. The transition region is quantized to a bar, and transitions when the global parameter no longer corresponds to that nested event.
If neither of these examples fits your use-case, what issues are you running into that they don’t address?
Thank you, I will try out the first method.
