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

Update D-Bus.md [skip ci]

Browse Source
This commit is contained in:
Mike Brady
2026-02-19 09:17:59 +00:00
committed by GitHub
parent 531459eb75
commit 95a637417c
1 changed files with 8 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documents/D-Bus.md
+8 -11
View File
@@ -136,10 +136,10 @@ The examples below are based on Shairport Sync running as a system service and u
```
dbus-send --system --print-reply --type=method_call --dest=org.gnome.ShairportSync '/org/gnome/ShairportSync' org.gnome.ShairportSync.DropSession
```
#### Control the player using Remote Control.
Remote Control commands are sent as requests to the player (iOS, iTunes, macOS Music, etc.). Different versions of the players implement different subsets of the following commands.
#### Remote Control
Remote Control commands are sent as requests to the player (iOS, iTunes, macOS Music, etc.). Different versions of the players implement different subsets of the following commands.
**Note** Unfortunately, at this time -- early 2026 -- these requests are ignored, so remote control doesn't work.
**Note** Unfortunately, at this time -- early 2026 -- these requests are ignored, so remote control doesn't work.
* Send the `play` command to the player:
```
@@ -151,9 +151,12 @@ The examples below are based on Shairport Sync running as a system service and u
```
dbus-send --system --print-reply --type=method_call --dest=org.gnome.ShairportSync '/org/gnome/ShairportSync' org.gnome.ShairportSync.RemoteControl.SetAirplayVolume double:-10.0
```
AdvancedRemoteControl interface. Some commands and properties are accessible only through the AdvancedRemoteControl interface. However, support for this is very limited in recent implementations.
#### Advanced Remote Control
Some commands and properties are accessible only through the `AdvancedRemoteControl` interface.
* You can check to see if AdvancedRemoteControl is available using the command:
**Note** Unfortunately, at this time -- early 2026 -- these requests are ignored, so remote control doesn't work.
* Check to see if AdvancedRemoteControl is available using the command:
```
dbus-send --print-reply --system --dest=org.gnome.ShairportSync /org/gnome/ShairportSync org.freedesktop.DBus.Properties.Get string:org.gnome.ShairportSync.AdvancedRemoteControl string:Available
```
@@ -161,9 +164,3 @@ AdvancedRemoteControl interface. Some commands and properties are accessible onl
```
dbus-send --system --print-reply --type=method_call --dest=org.gnome.ShairportSync '/org/gnome/ShairportSync' org.gnome.ShairportSync.AdvancedRemoteControl.SetVolume int32:50
```
MPRIS interface commands. For MPRIS support, Shairport Sync must be built with the MPRIS interface support. Add the `--with-mpris-interface` flag at the `./configure…` stage. There is a simple test client that you can have built -- add the '--with-mpris-test-client' flag at the ./configure stage. You'll get an executable called shairport-sync-mpris-test-client. This is mostly compatible with the MPRIS standard, except that Volume is read-only, with a separate SetVolume method.
* Set Volume, which must be between 0.0 and 1.0 and maps linearly onto the slider.
```
dbus-send --system --print-reply --type=method_call --dest=org.mpris.MediaPlayer2.ShairportSync '/org/mpris/MediaPlayer2' org.mpris.MediaPlayer2.Player.SetVolume double:0.3
```