Repository navigation
Request 30 FPS for Office screen sharing - #365
Closed
KajoVanBuyten wants to merge 1 commit into
Closed
KajoVanBuyten wants to merge 1 commit into
KajoVanBuyten wants to merge 1 commit into
Conversation
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
2 participants
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.
The Office screen share requested 15 FPS, making animated browser tabs visibly choppy on both the lounge TV and the full-screen viewer. Request 30 FPS from the browser instead; the same stream already feeds both views. The browser and source content still determine the actual delivered frame rate.
Validation:
npm run typecheckandnpm run buildpassed. A headless Chrome smoke screenshot of the isolated Office scene was captured. The fullnpm testrun was attempted but did not finish in the repository's long-running DSH/repository/worker tests; no screen-share-specific test was added for this one-line capture constraint.