Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MiniAudio #2264

Open
Faolan-Rad opened this issue Aug 8, 2024 · 1 comment
Open

MiniAudio #2264

Faolan-Rad opened this issue Aug 8, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Faolan-Rad
Copy link

I am asking to add the generator to include MiniAudio because it is a nice cross platform audio solution that isn't bulky I have generated binding myself for it before but now that I have moved to silk.net for Vulkan and OpenXR I would like to sort of bring all of the native libraries I use together into silk I will work on trying to add the generator with silk.net generator system mind you a don't really have experience with it I have used ClangSharp.PInvokeGenerator and also used clang sharp directly to make bindings to steam audio

@Faolan-Rad Faolan-Rad added the enhancement New feature or request label Aug 8, 2024
@Perksey
Copy link
Member

Perksey commented Aug 8, 2024

Miniaudio does not currently meet our barrier for inclusion in the library. However, I’ll keep this open as we’re discussing expanding this in 3.0 provided that community members are willing to own such bindings for as long as they’re shipped. See #2030. As with all bindings though, they should use the Silk.NET specific generators. For this reason I don’t think we’ll be accepting PRs at this time, as SilkTouch in 3.0 is still under heavy development and we’re not adding new bindings for 2.X.

As an aside, last time we investigated this I think there were some MiniAudio specific issues preventing us from binding it properly. Namely, last time we tried MiniAudio did not expose “allocate” functions, expecting your code to know the struct size and pass in your own memory, which is contrary to how we do xplat as typically these are opaque handles. Work in MiniAudio itself would have to be done to combat this if this is still the case i.e. exposing methods to get object sizes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants