Repository navigation
Refresh mixer documentation for the 192-input L4 demo - #40
Merged
Merged
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
1 participant
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 mixer documentation still pointed to the older September walkthrough and did not explain the current two-viewer layout. Link the new 10-second recording of the real 192-input L4 show and document Program/Preview alongside dirty Program, direct cuts and four downstream keys.
Record the observed 192-input / 256-scene / 26-output configuration separately from historical capacity qualification. Clarify HEVC viewer requirements, fix the moved GUI command and L4 capacity anchor, and document the media publication layout. The corresponding Pages redesign and cookbook refresh are published on gh-pages.
Validation: checked the live configuration and restored its original Program, Preview and key states after capture; no setup, service or code changes on the instance. Verified the MP4 is 1920×1080, 25 fps, 250 frames, 10 seconds. Browser checks passed on desktop and mobile for playback, seeking, replay, reduced-motion behavior and horizontal overflow. Checked source targets and media checksums.