Pipewire audio driver #375
Open
Conversation
This file contains 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.
This is an implementation of a PipeWire audio driver for MilkyTracker. I've been looking for a week or so for people to test it, but haven't received any responses yet.
From what I can tell, it works just as well as it does when using the SDL driver, where the routing of the audio is MilkyTracker -> SDL -> PulseAudio compat -> PipeWire, but with this driver the routing is simply MilkyTracker -> PipeWire. So, ostensibly, things could now be more efficient for PipeWire users running MilkyTracker, especially under small block sizes.
With all that being said, I'm a single user, and before anything like this is merged in I think we'd all like to see how it performs under differing configurations. I'm hoping that by getting this onto the PR page I could accrue more feedback.