Skip to content

Mopidy extension for controlling a local Snapcast client

License

Notifications You must be signed in to change notification settings

daniele-athome/mopidy-snapduck

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Mopidy-Snapduck

Mopidy extension that controls its own instance of the Snapcast client.

In a multi-room multi-Mopidy configuration the sound card of a room speaker is either owned by Snapcast client or by the local Mopidy instance. This extension will start snapclient when Mopidy is stopped and stop it when Mopidy is playing.

Installation

Install by running:

sudo python3 -m pip Mopidy-Snapduck

Configuration

Before starting Mopidy, you must add configuration for Mopidy-Snapduck to your Mopidy configuration file:

[snapduck]
snapclient_path = /path/to/snapclient
snapclient_args = arguments_for_snapclient

The following configuration values are available:

  • snapduck/enabled: If the snapduck extension should be enabled or not. Defaults to true.
  • snapduck/snapclient_path: Path to the snapclient executable. Defaults to /usr/bin/snapclient.
  • snapduck/snapclient_args: Arguments for snapclient. Defaults to none.

ALSA

When using ALSA Mopidy will not release the sound card immediately after stopping, so it is recommended to configure a dmix device to enable shared access between Mopidy and the Snapcast client.

About

Mopidy extension for controlling a local Snapcast client

Resources

License

Stars

Watchers

Forks

Languages