Add -d command line option for Pipewire and Puslse Audio

[iVolt1]

Hi Mike,

I was hoping you might consider adding -d command line option for Pipewire and Puslse Audio. I think it is the last piece of the puzzle to start a shairport-sync instance for Pipewire or Pulse Audio without having to configure a shairport-sync.conf for each one.

I have seen somewhere where you expressed that you were reluctant to add more command line options so I hope you will consider this enhancement as it will give Pipewire and Pulse Audio the same options that are available for Alsa.

Thanks,

ivolt1

[mikebrady]

Thanks for the suggestion!

[mikebrady]

What should the argument to the -d option be? For PipeWire, should it be the same as the configuration file's sink_target? And for PulseAudio, should it be the same as the configuration file's sink?

[iVolt1]

Correct. Here are some examples I use below.

One possible command to find the pipewire sinks for the sink_target parameter:

root@DietPi:/# pw-top -b -n 1
S   ID  QUANT   RATE    WAIT    BUSY   W/Q   B/Q  ERR FORMAT           NAME 
C   30      0      0    ---     ---   ---   ---     0                  Dummy-Driver
C   31      0      0    ---     ---   ---   ---     0                  Freewheel-Driver
C   54      0      0    ---     ---   ---   ---     0                  Midi-Bridge
C   51      0      0    ---     ---   ---   ---     0                  alsa_input.usb-0d8c_USB_Sound_Device-00.analog-stereo
C   53      0      0    ---     ---   ---   ---     0                  alsa_output.platform-soc_sound.stereo-fallback
C   58      0      0    ---     ---   ---   ---     0                  output.LineInCapture
C   59      0      0    ---     ---   ---   ---     0                  input.LineInCapture
C   69      0      0    ---     ---   ---   ---     0                  Shairport Sync
root@DietPi:/# 

Example pipewire sink_target set in shairport-sync.conf.

pw =
{
//	application_name = "Shairport Sync"; // Set this to the name that should appear in the Sounds "Applications" or "Volume Levels".
//	node_name = "Shairport Sync"; // This appears in some PipeWire CLI tool outputs.
	sink_target = "alsa_output.platform-soc_sound.stereo-fallback"; //"<sink target name>"; // Leave this commented out to get the sink target already chosen by the PipeWire system.
};

One possible command to find the pulse audio sinks:

~ $ pactl list sinks short
2       alsa_output.pci-0000_00_1b.0.iec958-stereo      module-alsa-card.c      s16le 2ch 96000Hz       IDLE
3       alsa_output.usb-AudioQuest_AudioQuest_DragonFly_Black_v1.5_AQDFBL0120005724-00.analog-stereo    module-alsa-card.c      s24le 2ch 96000Hz       IDLE
~ $ 

Example pulse audio sink set in shairport-sync.conf.

pa =
{
//	server = "host"; // Set this to override the default pulseaudio server that should be used.
//	sink = "alsa_output.pci-0000_00_1b.0.analog-stereo"; 
//	sink =  "alsa_output.usb-AudioQuest_AudioQuest_DragonFly_Black_v1.5_AQDFBL0120005724-00.analog-stereo"; // Set this to override the default pulseaudio sink that should be used. (Untested)
	sink = "alsa_output.pci-0000_00_1b.0.iec958-stereo"; // Set this to override the default pulseaudio sink that should be used. (Untested)
	application_name = "Shairport Sync"; //Set this to the name that should appear in the Sounds "Applications" tab when Shairport Sync is active.
};

If the command shairport-sync -h could return the pipewire sink_target(s) or pulse audio sink(s) as appropriate, that would be helpful too.

Thanks again for considering this.