Replies: 3 comments
-
Yes I'm considering this. Certainly it doesn't integrate very well with my "Just Works" philosophy due to the whole SDK thing, but I think we could work around that with some special treatment, so long as it doesn't affect anything else. Probably I'll just make it so the user has to include the necessary ASIO headers above the miniaudio implementation and do something like #define MA_ENABLE_ASIO. |
Beta Was this translation helpful? Give feedback.
-
Sorry for necromancy, but I also wanted to ask about this as it's been awhile now since the original post. What is the current situation regarding plans and/or efforts into ASIO support? |
Beta Was this translation helpful? Give feedback.
-
In version 0.12 (miniaudio is currently in the 0.11.x cycle) I've done a complete rework of the custom backend system. The new system allows you to very easily plug in your own custom backends, so if an ASIO backend is implemented, it'll most likely be placed in the extras folder and people who want to use will need to wire it up themselves. If you want a preview of how this new custom system works, take a look at the custom_backend example in the dev-0.12 branch and the SDL backend. As for when a possible ASIO backend might be done - it's a long ways away. Just not a high priority for me. |
Beta Was this translation helpful? Give feedback.
-
Have you considered added an ASIO backend? or is it an issue due to licencing?
Beta Was this translation helpful? Give feedback.
All reactions