OCP-1 — the Virtual Media Player (OVOS Common Playback)

[JarbasAl]

Adds OVOS-OCP-1, a V1 (V0-compatible) specification formalizing the OVOS Virtual Media Player — the central concept of OVOS Common Playback.

The concept

Every media voice command targets one logical player per session. That player:

• arbitrates all media for a session regardless of which provider, backend, or output device serves a track (the media-stack analogue of "one utterance, one handler");
• distinguishes playback requests ("play X") from control requests ("pause", "next", "stop"), so transport control does not require OVOS to have started the media;
• integrates with the host OS over MPRIS in two separable roles — export (OVOS playback appears as a standard org.mpris.MediaPlayer2 controllable by desktop media keys) and control external players (so playback OVOS did not initiate — a browser tab, a desktop player — is still controllable by voice, as long as it speaks the open standard);
• is per-session and isolates state across concurrent sessions.

Scope

Defines the player abstraction + session scoping, the three-axis state model (PlayerState/MediaState/loop+shuffle), the reserved ovos.common_play. bus surface (playback vs. control requests, state reports), the MPRIS bridge (Role A export / Role B external control, the latter off-by-default), the stop relationship (OVOS-STOP-1 subscriber), and a conformance section. It deliberately does not define discovery/ranking (a provider concern), URI-to-bytes playback (a backend concern), or any implementation shape.

Dependencies: OVOS-MSG-1, OVOS-SESSION-1/2, OVOS-PIPELINE-1, OVOS-STOP-1.

One new spec file (ovos-ocp-1.md) + its README index registration.

[coderabbitai]

Warning

Review limit reached

@JarbasAl, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 53 minutes and 24 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c82fc37d-c798-4ef1-bdba-2328d8113389

📥 Commits

Reviewing files that changed from the base of the PR and between 54c6a0e and 2069913.

📒 Files selected for processing (3)

• CHANGELOG.md
• README.md
• ocp-1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/ovos-ocp-virtual-media-player

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}