Skip to content

Update server bandwith table with correct values for existing and new audio quality settings#1133

Open
dingodoppelt wants to merge 3 commits intojamulussoftware:next-releasefrom
dingodoppelt:patch-1
Open

Update server bandwith table with correct values for existing and new audio quality settings#1133
dingodoppelt wants to merge 3 commits intojamulussoftware:next-releasefrom
dingodoppelt:patch-1

Conversation

@dingodoppelt
Copy link
Copy Markdown

@dingodoppelt dingodoppelt commented Apr 26, 2026

Short description of changes
Updated audio bandwidth table to include 'max' quality and adjusted buffer duration samples.

Context: Fixes an issue? Related issues
This is a follow up to #3653

Status of this Pull Request

Does this need translation?
Yes

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I'm sure that this Pull Request goes to the correct branch

dependabot Bot and others added 3 commits April 8, 2026 08:51
Bumps [addressable](https://github.com/sporkmonger/addressable) from 2.8.7 to 2.9.0.
- [Changelog](https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md)
- [Commits](sporkmonger/addressable@addressable-2.8.7...addressable-2.9.0)

---
updated-dependencies:
- dependency-name: addressable
  dependency-version: 2.9.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…ot/bundler/addressable-2.9.0

Bump addressable from 2.8.7 to 2.9.0
Updated audio bandwidth table to include 'max' quality and adjusted buffer duration samples.
@ann0see ann0see added this to the Release 4.0.0 milestone Apr 28, 2026
@ann0see ann0see added this to Tracking Apr 28, 2026
@github-project-automation github-project-automation Bot moved this to Triage in Tracking Apr 28, 2026
@@ -11,22 +11,24 @@ permalink: "/wiki/Server-Bandwidth"

The audio settings have an impact on the required network bandwidth. The table below summarises network requirements with respect to the configuration of:
* Channels : stereo/mono
* Quality : high/medium/low
* Audio buffer duration : 2.67 ms, 5.33 ms, 10.67 ms, 21.33 ms
* Quality : high/medium/low/max
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Quality : high/medium/low/max
* Quality : max/high/medium/low

Copy link
Copy Markdown
Contributor

@mcfnord mcfnord Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noting that max is not included in this network bandwidth section. That diagram is already pretty confusing. But is it reasonable to infer here that Max's larger requirements present new risk? Does running with Max make a server more likely to fail (degrade) where High succeeds today? I tend to experience very good results on the smallest Linux cloud instance available. Still true with Max?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

3 participants