Mopidy-ALSAMixer
Mopidy extension for ALSA volume control.
Dependencies
A Linux system using ALSA for audio playback.
pyalsaaudio. Bindings for using the ALSA API from Python. The package is available as python-alsaaudio in Debian/Ubuntu.
Installation
Install by running:
sudo python3 -m pip install Mopidy-AlsaMixer
See https://mopidy.com/ext/alsamixer/ for alternative installation methods.
Configuration
The default configuration will probably work for most use cases.
The following configuration values are available:
alsamixer/card: Which soundcard to use, if you have more than one. Numbered from 0 and up. 0 is the default.
alsamixer/control: Which ALSA control to use. 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
Credits
Original author: Stein Magnus Jodal
Current maintainer: Stein Magnus Jodal
Metadata
Release files for mopidy-alsamixer 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Mopidy-ALSAMixer-2.0.0.tar.gz | 11.9 kB | Without provenance | Details for Mopidy-ALSAMixer-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Mopidy_ALSAMixer-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for Mopidy_ALSAMixer-2.0.0-py3-none-any.whl |
Total release size: 21.7 kB
Release files / Mopidy-ALSAMixer-2.0.0.tar.gz
| Download URL | Mopidy-ALSAMixer-2.0.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce199799fa9df354f999d1d03b437bd639b4dbf69edf513979d95485c4a731d9
|
|
BLAKE2b-256 checksum How to use checksums |
b966e43534c100f48f0779191d3e7819e909ce39eff7f8eba71dc218897131fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.7.5
|
Release files / Mopidy_ALSAMixer-2.0.0-py3-none-any.whl
| Download URL | Mopidy_ALSAMixer-2.0.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c8bb6627daa990d43e50e693611b67f927c00deab27bc571170dc3257736f4b
|
|
BLAKE2b-256 checksum How to use checksums |
168e4741d0625e628ce55f41583b57269172ec9bfe14412d05cf9ecd698d2ef5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.7.5
|
Security for mopidy-alsamixer 2.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.