Open
Conversation
This section doesn't ring true: https://bevy.org/examples/audio/audio-control/
The "better audio working group" is cooking up the following, under the same premise that abandoning rodio is the way forward. https://github.com/corvusprudens/bevy_seedling |
Author
|
@rparrett Thank you! I'm now switching my project to Seedling and in communication with the developer to start contributing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendered.
This RFC proposes a new system to handle audio, leveraging relationships and the ECS to define how audio is routed, and the Web Audio API (potentially implemented on desktop with the
web-audio-apicrate) to ensure high performance both natively and on the brower.