0
0

If you want to design an event that is a sequence of sounds that is controlled by different parameters, as I see it, problems will arise. Imagine the case where you make a reload sound for a weapon which normally consists of a number of clicks that are positioned over time. Now, if you want to add a parameter like "distance" that adds attenuation and some low-pass filtering these effects will only be applied if the values are within the range of the sounds duration, that is a sound in the sequence will only be affected by paramter-values ranging from sample-start <->sample-start + (sample-length). This is rather bad and makes the sequencer feature rather useless in more complex situations. A fix would be either to have a seperate sequencer view or to allow events to be triggered within events, which means that you make the sequence as a simple event that is only controlled by time and then add it to an event where you add paramteres that aren’t in the time-domain.

  • You must to post comments
0
0

[quote:2wfg8uei]Now, if you want to add a parameter like "distance" that adds attenuation and some low-pass filtering these effects will only be applied if the values are within the range of the sounds duration[/quote:2wfg8uei]

No, your distance parameter doesn’t need to be "time-based" and is completely independent of your pimary parameter that’s controlling what sounds get played. Check out the "car" example that ships with the API. The "rpm" parameter is the "control" parameter in this case – it controls what sounds get played. The "load" parameter is completely indpendent and uses volume envelopes to effectively crossfade between the two layers. One way of thinking about it is that each parameter has its own "cursor" that can be controlled independently.

Cheers,

  • You must to post comments
0
0

You are actually right about that. Maybee I should do some better testing my end before I spam complaints :) Looking at it now the eventeditor view feels really cool. All I would like to see now is nested events and some updates of the gui so it gets more userfriendly and effective to work with.

  • You must to post comments
0
0

Don’t know about nested events but we’re definitely planning a lot more work on the GUI in the weeks and months to come.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.