enzienaudio
Unity: Understanding the two different plugin types that are generated.
Why the heavy compiler generates three files (two approaches) ? I understand that the approach using the .dll and the c# script adds the plugin as a audio source object while the other one adds the plugin as an audio effect (using the new native audio plugin SDK). Is it possible to use the second one also as an audiosource ? In general, what are the differences between both ways and is the first one is meant to disappear ?
Hi @theodupre take a look at the docs, it gives a brief overview of the two plugin types https://enzienaudio.com/docs/index.html#06.unity#getting-started
Is it possible to use the second one also as an audiosource?
As far as I know it's not possible as the Audio Mixer plugin system has a fixed structure. However, you can create audio mixer plugins that only generate sound, i.e. it ignores it's input. Though there will be no positional information available at that point.
In general, what are the differences between both ways and is the first one is meant to disappear?
Not sure what you mean by 'meant to disappear' but the idea is that the plugins we generate support as much of the features in Unity as possible. You can mix and match as you choose and can even use both at the same time if you want. It's not necessary to keep the ones you aren't using around.
Hope that helps!
Thank you @diplojocus ! If I understood correctly the second way is a new feature of Unity 5, so I was wondering why keeping both ways while they can have only one. (i.e. 'meant to disappear'). But as you said, features from the old way aren't available in the new approach.
My understanding is the intention behind the Audio Mixer API is to a) provide a low-level interface to generating audio b) create a system for bus effects and music applications.
The native plugin interface (C# wrapper + dll) is not particular to only audio, so the new Audio Mixer API isn't thought of as a replacement.