Alsa: limit buffer size, so shairport can start in time #345
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
increase period size 64 to as big as HW supports: a small period only makes sense for extremely low latency applications. due to shairport's internal 352 buffer size it makes even less sense
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.
part1 of the patch series created in my sntp branch but are not necessary to enable the time sync feature
Some USB have a very deep (>2s) buffer.
Having a deep buffer eats up the receiver buffer, so lost packet have less chance of being re-sent in time.
Also, if buffer is 2+s deep, the upcoming time synchronized version will not be able to start in time
increase period size 64 to as big as HW supports: a small period only makes sense for
extremely low latency applications. due to shairport's internal 352 buffer size it makes even less sense