On 7/7/20 2:53 PM, Richard Shaw wrote: Yes, you would need a special cable to cross-connect with the microphone input. If you had two of the 4-conductor splitters, that might work. What is the purpose of this? Are you wanting to hear something or is it some sort of communication channel between the computers? I have done it one-way before. If you explain what the objective is, I can try to figure it out again.

On 7/7/20 3:15 PM, Richard Shaw wrote: I figured out a working configuration using rtp. Follow the same process on both computers. Copy /etc/pulse/default.pa to ~/.config/pulse. Then add the following lines at the end of the new file: load-module module-null-sink sink_name=rtpout format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Out' device.bus='network' device.icon_name='network-server'" load-module module-rtp-send source=rtpout.monitor loop=0 load-module module-null-sink sink_name=rtpin format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast In' device.bus='network' device.icon_name='network-server'" load-module module-rtp-recv sink=rtpin load-module module-remap-source source_name=rtploop master=rtpin.monitor Run "pulseaudio -k" to restart pulseaudio. Now in the sound settings, you can pick the RTP Out for the output and the Remapped Monitor of RTP In as the input. I tested it with audacity and despite using the default pulse input, it kept insisting on reading the microphone. So I used pavucontrol to set its input to the right one. I was then recording what I was playing from the other computer. You could probably do this with one of the other transports as well, but paprefs almost made this setup work, so I only had to add a bit more to have it fully working.