René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Sendspin playback source not shown in pulseaudio or pipewire GUI tools?","articleBody":"So I am going to preface this with a boxed warning label that I am experienced enough to be dangerous, but to not truly understand what is going on with the backend when it comes to alsa, pulseaudio, and especially pipewire. I generally know how to get things from whatever source to whatever sink(s) I want them to go, but........\n\nNo matter which --audio-device option I start sendspin with, sendspin never shows up in pavucontrol, nor helvum. I am accustomed to being able to route playback from my laptop's speakers, wired aux output jack, bluetooth headset, etc using the pavucontrol tool. I will go to helvum if I really need something crazy weird like multiple sink outputs of the same source input. Yes, I can get into command line to move sendspin --audio-device to something else with typing, but sometimes that is far less practical than a couple of clicks...\n\nIs there a different device I should be targeting the sendspin client to in order to expose it to pavucontrol and/or helvum? Is this just never going to be possible with sendspin-cli (if so that is quite disappointing)? Is there something sendspin-cli could do in order to surface itself better to other audio routing tools like pavucontrol and helvum?","author":{"url":"https://github.com/fhteagle","@type":"Person","name":"fhteagle"},"datePublished":"2026-04-29T01:59:50Z","url":"https://github.com/Sendspin/sendspin-python-cli/issues/239"}