Skip to main content

mopidy-alsamixer

Latest PyPI version CI build status Test coverage

Mopidy extension for ALSA volume control.

Maintainer wanted

mopidy-alsamixer is currently kept on life support by the Mopidy core developers. It is in need of a more dedicated maintainer.

If you want to be the maintainer of mopidy-alsamixer, please:

  1. Make 2-3 good pull requests improving any part of the project.

  2. Read and get familiar with all of the project's open issues.

  3. Send a pull request removing this section and adding yourself as the "Current maintainer" in the "Credits" section below. In the pull request description, please refer to the previous pull requests and state that you've familiarized yourself with the open issues.

    As a maintainer, you'll be given push access to the repo and the authority to make releases to PyPI when you see fit.

Installation

Install by running:

python3 -m pip install mopidy-alsamixer

See https://mopidy.com/ext/alsamixer/ for alternative installation methods.

Configuration

To use mopidy-alsamixer the audio/mixer configuration value must be set to alsamixer in the Mopidy configuration file:

[audio]
mixer = alsamixer

The default mopidy-alsaMixer configuration will probably work for most use cases. If not, the following configuration values are available:

  • alsamixer/device: Which soundcard should be used, specified by its string alias. Defaults to default.

  • alsamixer/card: Which soundcard should be used, specified by its index. Numbered from 0 and up. If specified, alsamixer/device is ignored.

  • alsamixer/control: Which ALSA control should be used. Defaults to Master. Other typical values includes PCM. Run the command amixer scontrols to list available controls on your system.

  • alsamixer/min_volume and alsamixer/max_volume: Map the Mopidy volume control range to a different range. Values are in the range 0-100. Use this if the default range (0-100) is too wide, resulting in a small usable range for Mopidy's volume control. For example try min_volume = 30 and max_volume = 70 to map Mopidy's volume control to the middle of ALSA's volume range.

  • alsamixer/volume_scale: Either linear, cubic, or log. The cubic scale is the default as it is closer to how the human ear percieves volume, and matches the volume scale used in the alsamixer program.

Example alsamixer section from the Mopidy configuration file:

[alsamixer]
card = 1
control = PCM
min_volume = 0
max_volume = 100
volume_scale = cubic

Project resources

Development

Set up development environment

Clone the repo using, e.g. using gh:

gh repo clone mopidy/mopidy-alsamixer

Enter the directory, and install dependencies using uv:

cd mopidy-alsamixer/
uv sync

Running tests

To run all tests and linters in isolated environments, use tox:

tox

To only run tests, use pytest:

pytest

To format the code, use ruff:

ruff format .

To check for lints with ruff, run:

ruff check .

To check for type errors, use pyright:

pyright .

Making a release

To make a release to PyPI, go to the project's GitHub releases page and click the "Draft a new release" button.

In the "choose a tag" dropdown, select the tag you want to release or create a new tag, e.g. v0.1.0. Add a title, e.g. v0.1.0, and a description of the changes.

Decide if the release is a pre-release (alpha, beta, or release candidate) or should be marked as the latest release, and click "Publish release".

Once the release is created, the release.yml GitHub Action will automatically build and publish the release to PyPI.

Credits

Release files for mopidy-alsamixer 3.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mopidy-alsamixer 3.0.0
File Size Uploaded
mopidy_alsamixer-3.0.0.tar.gz 15.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mopidy-alsamixer 3.0.0
File Interpreter ABI Platform
mopidy_alsamixer-3.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 26.5 kB

Release files / mopidy_alsamixer-3.0.0.tar.gz

Download URL mopidy_alsamixer-3.0.0.tar.gz
Size 15.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6ef0a0a5cbefb4b8a2f7258d9f844dd7cac0d9e825f0a86354f09b4f4b739e87
BLAKE2b-256 checksum
How to use checksums
b506f2d2982aac394595e3d22c2635a4fd63b7934adfbb030177b38e9ada4308
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 24, 2026.

Transparency log

Release files / mopidy_alsamixer-3.0.0-py3-none-any.whl

Download URL mopidy_alsamixer-3.0.0-py3-none-any.whl
Size 10.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
02ea240dd69ab4086fe1016f4c3370ed4cfbef5b587159fbcb127bba636828dd
BLAKE2b-256 checksum
How to use checksums
d671b544e0c068be1a2589af96d08cf89e66712563522e3517b4f2c98ac8d850
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 24, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page