It would be nice to have a definable-length “cooldown” to reset global sequential playlists.
Is there an API command to reset the global playlist, say, after 1 second?
All I’m trying to achieve is a sound attached to a game object that when hit, it plays a tone, and each successive time you hit it, it plays up a chromatic scale. But after a certain time passes where you don’t hit it, I want the scale to reset to the first pitch in the playlist.
Not sure I fully understand the effectiveness of local playlists as they currently function. In Studio, if you click play repeatedly, even if the event has not yet finished plating out, it still plays the first file in the playlist. So obviously each click is representing the in-game creation of a new instance of the event. So, if you want use Sequential-local effectively, it has to trigger the same instrument more than once in a single instance of the event. The only method to do that is a loop or transition, which of course has its uses. I’d love to hear an example of how someone has used Sequential - Local Scope in practice, in a non-theoretical way. In the API is it possible to, instead of triggering an event repeatedly (causing multiple instances), keep it alive after the first trigger and reset the playhead to 0 for successive triggers (effectively different than hitting the play button over and over in Studio)?
To use sequential-local in the case I described at the top and keep it within FMOD as much as possible, I would have to create an instrument with the sequential playlist, move it slightly forward from 0sec on the timeline, place a sustain point very shortly after 0sec, then place a transition to a “start” destination marker which sits at 0sec. Then use a “key off” trigger to retrigger the sound. After 1 second passes, instead of triggering the key off, just replay the event. This is so cumbersome and kinda feels like a hack of the use of the sequential local playlist, and still requires the engineer to program in the cooldown which would be frustrating if there are hundreds of triggers like this each with different cooldown times. Could cause a memory leak as well with the event being kept alive. Would be so much easier if there was a non-API global playlist reset cooldown option/value.