Replies: 1 comment 1 reply
-
|
That's a very outdated video, the wwise integration has been completely rewritten since then :) One issue is that the wwise sdk is closed source, which means that we cannot ship it with the plugdata toolchain. However another issue is that wwise sdk requires the user to have python installed. Together with how paths are dealt with would make it pretty hard to get consistent output for all platforms. We could also only provide source output and then it's up to the user to figure out how to use it, but that's not a very friendly UX. Current documentation for wwise integration: https://wasted-audio.github.io/hvcc/docs/03.gen.wwise.html |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The AudioKinetic Wwise , which is the middleware audio engine used by most gaming studios today, has made a guide about how to export a pure data patch to a wwise plugin format, see here , using the Heavy compiler. Since plugdata has Heavy Compiler integration believe it would be very popular amongst game devs if this was an option as well.
Beta Was this translation helpful? Give feedback.
All reactions