RTPCs and blends at the time of writing, but still quite a lot is possible. WAAPI is a client-server API to manipulate such hierarchies: renaming or removing objects, change their properties, etc. - not everything is accessible though, e.g. All of this defines sound playback rules and configurations for the audio engine at runtime. child objects inherit values from their parents. Relative position in the hierarchy defines property value inheritance, i.e. Wwise projects are organized into hierarchies of objects, objects can be of several types ( Event, RandomSequenceContainer, etc.), object types describe which properties objects have ( BusVolume, IsStreamingEnabled, etc.). I think it may be worth it to go through basic information about Wwise and WAAPI first. You’ll need to set up your PC environment in order to run them, please refer to instructions in the Appendix.
Make new audio bar python code#
I wrote a few code examples just for this article, so be wary that this code hasn’t been extensively tested. I’ll also touch on the basics of how WAAPI works and hopefully demonstrate how actual useful WAAPI scripts look and feel like, - thus this article might also be useful for beginners who just started learning WAAPI, or as a “getting started” kind of a guide for people outside the audio team who happen to be helping their colleagues with workflow tools and automation. Consisting of Python, command add-ons and a small helper library, the approach helps me write new WAAPI scripts a bit faster than with vanilla waapi-client, and share them with teammates with little to no friction in most cases. In this article, I’d like to describe a somewhat opinionated approach to working with WAAPI that I’ve been using for quite some time already.
0 kommentar(er)
