You are not logged in.

#1 2023-07-01 04:46:26

parakovsky
Member
Registered: 2018-08-12
Posts: 5

pipewire modules rtp address not found

after today update my rtp modules for network audio stop working, nominally they work if not initiaite specific network addresses, which if not inputed will result in audio not transfered. here's waht i used to do

on host

pactl load-module module-null-sink sink_name=rtp
pactl load-module module-rtp-send source=rtp.monitor destination_ip=192.168.1.117

on reciever

pactl load-module module-rtp-recv latency_msec=50 sap_address=0.0.0.0

now if i do that in system logs it says address in use, this happened after today update when pipewire has been updated, the module that utilize tcp is working fine tho.

i wonder what initially i was doing wrong and what is the proper way toget rtp module back to work. thank you

Offline

#2 2023-07-01 05:03:14

krakenfury
Member
Registered: 2013-04-18
Posts: 15

Re: pipewire modules rtp address not found

No idea if it's related, but I had to downgrade all of the pipewire packages after upgrading. My problem was with my bluetooth headset, though. It would connect, but then drop immediately whenever I tested any audio, from any source. I investigated the problem assuming it was with bluez, since all of those got upgraded, too. When I saw pipewire in the mix in the pacman.log, I just did the lazy thing and downgraded/IgnorePkg all of these packages at the same time:

bluez
bluez-libs
bluez-utils
pipewire
pipewire-pulse
pipewire-audio
libpipewire
pipewire-jack

Yours is the only post I've seen about it, but I haven't looked far and wide. In hindsight, I probably should have looked at some pipewire logs, but alas, refer back to teh lazy.

The log I did bother checking was `journalctl -u bluetooth`. The offending lines appear to be related to plugins not being supported:

Jun 30 21:35:15 ToEE bluetoothd[1682]: src/plugin.c:plugin_init() System does not support csip plugin
Jun 30 21:35:15 ToEE bluetoothd[1682]: src/plugin.c:plugin_init() System does not support vcp plugin
Jun 30 21:35:15 ToEE bluetoothd[1682]: src/plugin.c:plugin_init() System does not support mcp plugin
Jun 30 21:35:15 ToEE bluetoothd[1682]: src/plugin.c:plugin_init() System does not support bass plugin
Jun 30 21:35:15 ToEE bluetoothd[1682]: src/plugin.c:plugin_init() System does not support bap plugin
Jun 30 21:35:15 ToEE bluetoothd[1682]: Bluetooth management interface 1.22 initialized
Jun 30 21:35:15 ToEE bluetoothd[1682]: Failed to set privacy: Rejected (0x0b)

and then some other insulting stuff about failing to keep private.

edit: i always assume i am in markdown land for some reason...

Last edited by krakenfury (2023-07-01 05:05:52)

Offline

#3 2023-07-01 06:15:07

ArchM
Member
Registered: 2018-02-09
Posts: 24

Re: pipewire modules rtp address not found

krakenfury wrote:

...

Same issues here. Not really sure but bluez seems to have a related sounding fix in 5.68?

ver 5.68:
	Fix issue with A2DP and handling of Transport.Acquire.

https://github.com/bluez/bluez/issues/542

Last edited by ArchM (2023-07-01 06:16:30)

Offline

#4 2023-07-01 17:59:42

krakenfury
Member
Registered: 2013-04-18
Posts: 15

Re: pipewire modules rtp address not found

ArchM wrote:

Same issues here. Not really sure but bluez seems to have a related sounding fix in 5.68?

ver 5.68:
	Fix issue with A2DP and handling of Transport.Acquire.

https://github.com/bluez/bluez/issues/542

Yeah that appears to be the fix, and it's already in the arch repo. Sorry to @parakovsky for hijacking your thread to fix a different problem, and hope you find an answer to yours.

Since the solution is already deployed in an update, I'm not going to bother creating a separate thread.

Offline

Board footer

Powered by FluxBB