Sendspin on Pi doesnt allow fixed usb hardware name, relies on USB number
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, python, raspberry-pi
- Domain
- audio-video-rtc, cli, operating-systems
Research direction
Start by tracing how the sendspin daemon handles --audio-device and compare that with the device names shown by aplay -l. Reproduce the service configuration using /etc/asound.conf and the sendspin.service override, including a USB device reorder. Done means the named USB audio device remains usable after reordering and the service starts successfully.
Written by the indexing model from the issue text.
Description
I have a soundblade installed via usb to Pi P400, its currently usb device 3.
I have the following configuration in /etc/asound.conf as the soundblade only accepts 48khz:
pcm.upsampler {
type plug
slave.pcm "softvol"
# The 'plug' plugin is the only one that understands the 'rate' field
slave.rate 48000
}
pcm.softvol {
type softvol
slave {
pcm "hw:3,0"
}
control {
name "Master"
card 3
}
}
pcm.!default {
type copy
slave.pcm "upsampler"
}
In sudo systemctl edit sendspin.service
[Service]
User=sendspin
Group=audio
ExecStart=
ExecStart=/home/sendspin/.local/bin/sendspin daemon --audio-device=upsampler
Restart=on-failure
RestartSec=5
# No ExecStartPost - no timeout issues
ExecStopPost=/usr/bin/pkill -u sendspin sendspin
While this works, its not robust enough to survive a new USB device inserted, using the name of the device in aplay -l , causes an error and the service doesnt load.
Aplay -l ouput:
card 3: SOUNDBLADE [BLUEANT SOUNDBLADE], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
- Dominant language
- Python
- Stars
- 190
- Forks
- 36
- Avg merge
- 11d 19h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Sendspin/sendspin-python-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Sendspin/sendspin-python-cli#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Sendspin/sendspin-python-cli#278 · 2 comments · 5 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Sendspin/sendspin-python-cli#257 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Sendspin/sendspin-python-cli#256 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Sendspin/sendspin-python-cli#113 · 10 comments ·
All issues in Sendspin/sendspin-python-cli
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·