[BUG] No sound on Arch Linux

[airisama019]

Describe the bug
as-cmd starts and shows no errors, I can also connect with android device and it says "started" but there is no sound.
It works on Debian and Fedora. Fedora pipewire version is same as arch linux but still works. Was working on arch linux untill a few months ago.

To Reproduce
Steps to reproduce the behavior:

1. Install arch linux with Installation Guide.
2. Install pipewire with "sudo pacman -S pipewire wireplumber pipewire-pulse pipewire-jack pipewire-alsa"
3. Enable pipewire service with "systemctl enable --user pipewire wireplumber pipewire-pulse"
4. Start as-cmd with "./as-cmd -b [your-ip]"

Screenshots

Server (please complete the following information):

• OS: Arch Linux
• GUI or CMD: CMD
• Version: v0.0.17

Android (please complete the following information):

• Device: Moto G5S
• OS: Android 12L and 11 tested
• Version: v0.0.17

Additional information
Add any other information about the problem here, such as server.log or stdout.
There is no such option on as-cmd usage help.

more
It's fine if you don't want to fix, I'll just reinstall debian or something.

[airisama019]

There is sound if I plug headphones so it's not a driver issue.

[mkckr0]

Run pw-play -v test.wav to check whether playback works normal.
#31 (comment)

[airisama019]

here is output file

seems to be working fine.

Also I thought issue would be their recent change from dbus to dbus-broker but I rolled back and still no sound on as-cmd.

Edit: what distro do you use for testing?

[mkckr0]

Use pw-record --target 310 --format f32 out.wav to record the playing audio. After several seconds, press Ctrl-C to stop. Then send out.wav to phone to play it.

If you enable the firewall, check the firewall rules.

Use a network traffic monitor to see whether the audio data is trasfering.

[airisama019]

out.mp4

I used "ffmpeg -i out.wav out.mp4" so I can upload the file.
Sent to phone through smb share and it plays just fine.

Edit: the firewall is the same I used on Debian and Fedora, "firewalld" and there was no issues with it. After opening default port 65530 it works well.

[airisama019]

Nevermind I'm dumb
I forgot it uses both tcp and udp and I forgot to enable udp as well.
After enabling both it started working again.
Sorry for wasting your time.

[airisama019]

Maybe say "Error: can't connect to udp port" on android app and "[warning] 192.168.x.x:xxxxx UDP failed" on as-cmd to make it easier.