Use whenever support or development work needs SRS or Oryx project documentation, or when that documentation must be created, updated, or reviewed. Covers the C++ media server, State Threads, Oryx (deployment, streaming, authentication, recording to local or…
Use when a task needs Chrome or Edge as a test client for SRS, such as publishing over WHIP or playing over WHEP, HTTP-FLV, HTTP-TS or HLS in a headless browser, or reading the browser's WebRTC stats in a manual or automated test.
Develop, modify, debug, review, maintain, and explain the SRS and Oryx codebases, the SRS Docker image toolchain, and the State Threads coroutine library. Use for planned changes to the SRS Go proxy, SRS browser player, ossrs/dev-docker images,…
Use to check one SRS commit or review group for defects before the user reads it or before a merge, when the srs-autopilot review workflow or the srs-develop Review a PR and Scan PRs workflows ask for an audit, after a cherry-pick to another branch, or when…
Use whenever support, development, debugging, review, or maintenance work needs to locate, read, modify, test, or verify SRS or Oryx code. Covers the C++ origin and edge media server, its State Threads dependency, the Go proxy server, browser publishers and…
Use when a task needs OBS Studio, such as live streaming from OBS or publishing RTMP, SRT or WHIP to SRS from OBS in a manual, automated or parallel test, including setting up OBS profiles, scenes, sources and stream outputs.
Answer SRS (Simple Realtime Server) and Oryx questions for users, operators, and DevOps. Covers SRS protocols, configuration, codecs, deployment, monitoring, performance, troubleshooting, ecosystem tools, and community support, plus Oryx deployment, dashboard…
Use for SRS performance work - when asked to load test, benchmark or profile the SRS C++ media server or the Go server (the proxy), find or fix a performance bottleneck, compare performance between versions or changes, or run or resume a performance round.…