Skip to main content

Mopidy extension for controlling a local Snapcast client

Project description

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

Mopidy-Snapduck-1.0.0.tar.gz (16.5 kB view hashes)

Uploaded Source

Built Distribution

Mopidy_Snapduck-1.0.0-py3-none-any.whl (16.2 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page