nils/shairport-sync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify D-Bus interface usage in Shairport Sync [skip ci]

Browse Source 
Reorganize content for clarity regarding the D-Bus interface.
This commit is contained in:
Mike Brady
2026-05-10 08:25:44 +01:00
committed by GitHub
parent 4a4c887bdc
commit 48559c45df
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documents/D-Bus.md
+3 -1
View File
@@ -1,6 +1,8 @@
## Shairport Sync D-Bus Interface ## Shairport Sync D-Bus Interface
Shairport Sync can have a D-Bus interface, which can be used to control aspects of its operation and get status information from it. For Classic AirPlay only, remote control commands, for example `play`, `pause` and volume control, can be sent to the player. Shairport Sync can have a D-Bus interface, which can be used to control aspects of its operation and get status information from it.
For Classic AirPlay only, remote control commands, for example `play`, `pause` and volume control, can be sent to the player.
To include the D-Bus interface at build time, add the `--with-dbus-interface` flag at the `./configure…` stage. When the D-Bus interface is included in Shairport Sync, its Version String will include the term `dbus`, for instance: To include the D-Bus interface at build time, add the `--with-dbus-interface` flag at the `./configure…` stage. When the D-Bus interface is included in Shairport Sync, its Version String will include the term `dbus`, for instance:
``` ```