Open Horizon Labs Unified Hifi Control
open-horizon-labs-unified-hifi-control is a Claude Code plugin for the Build phase that provides a source-agnostic hi-fi control bridge for playback, volume, and pipeline settings.
by open-horizon-labs · github.com/open-horizon-labs/unified-hifi-control
Control playback, volume, and pipeline settings across hi-fi sources including HQPlayer from Claude Code via a source-agnostic bridge.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install open-horizon-labs-unified-hifi-control@open-horizon-labs/unified-hifi-controlBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:open-horizon-labs/unified-hifi-control") and the paste-ready config with skillselion.get_install_config("plugin:open-horizon-labs/unified-hifi-control").
What it does
open-horizon-labs-unified-hifi-control is a niche Claude Code plugin that exposes a source-agnostic bridge for high-fidelity audio systems. Solo builders and enthusiasts who run HQPlayer or similar pipelines can let the agent adjust volume, playback state, and related settings through one integration instead of brittle one-off shell scripts per device. It is phase-specific: you install it when you are building or extending a personal automation stack that ties Claude to your listening environment, not when you need broad software engineering skills. The catalog lists one plugin, which keeps scope tight—control, hi-fi, pipeline, playback—so expectations stay realistic. It matters if you treat your desk or media room as a product surface and want agent-driven control with consistent verbs across sources.
Highlights
- Source-agnostic hi-fi control bridge for unified playback and system commands.
- HQPlayer-oriented pipeline and settings control keywords in the bundle.
- Volume and playback adjustment without swapping separate vendor-specific scripts.
- Single-plugin footprint focused on audio automation, not general dev skills.
- Fits personal desktop or listening-room setups where the agent acts as a control layer.
Why builders use it
Controlling HQPlayer and other hi-fi sources from an agent usually means fragile, vendor-specific scripts that do not share one interface.
After install, Claude can drive playback and volume through a single bridge abstraction across your hi-fi pipeline.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 11 stars, 0 votes.
FAQ
Who is open-horizon-labs-unified-hifi-control for?
It is for developers and audiophiles running HQPlayer or similar hi-fi pipelines who want agent-driven volume and playback control from Claude Code.
When should I use open-horizon-labs-unified-hifi-control?
Use it when you are wiring Claude into a local listening setup and need unified control verbs instead of separate scripts per audio source.
How do I add open-horizon-labs-unified-hifi-control to my agent?
Add the open-horizon-labs/unified-hifi-control plugin in Claude Code, ensure your hi-fi stack is reachable from the bridge, then invoke control commands through the plugin’s tools.
Comments
Share how you use open-horizon-labs-unified-hifi-control, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.