Konflict:
It does, by using the WMF Media Player (2.0), and setting up a stream media source asset, a media sound component can be instantiated in a blueprint in order to provide the capture via selecting the sms asset. It is also possible to choose between different audio capture sources. Unless i’m mistaken here on the concepts the answer is yes.
Nice example!
I also have took your recommendation and implemented the RtAudio class on my own (using the copy you have provided earlier with the Editor only plugin) and after a little playing around it was possible to expose great many features of this class, which included the enumeration (probing) of the capture sources as well as multiple bit depths for higher quality sources.
Actually, this new audio capture module would also benefit of such options, where we can select the capture source instead of relying on the default device which is not reports the microphone but the line input unfortunately! Not to mention it won’t take care of the VR audio inputs either which can be a pain as well.
The media framework can help here a bit to fetch the list of devices that is blueprint compatible already. While it doesn’t specifically tells which is the default mic input (a missing feature?), but at least the developer would be able to set up a widget for the user to choose between devices. The RtAudio can then parse this input string to select the preferred input for capture.
Will you accept PRs for this plugin?
Yeah, I’ll accept PRs for anything
I wrote the Mic Capture Component in a day very quickly for an internal project that wanted to drive gameplay with microphone input via envelope following. There are obviously a ton of things we can do with it. Despite it being a bit thin on flexibility and features, I opted to ship with it since it does work as is but I knew it’d generate a lot of interest and feature requests.
I mean, “accept”, I’ll look at em.