You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wifi-issue is due to how rtp works (multicast). To have multiple receivers without bombarding your network you can use the classic native-tcp protocol instead and advertise those via avahi.
The crackling is due to the latency in your network and will disappear after a while or on a restart, because pulseaudio handles the buffer dropouts. Instead of experimenting with different buffer sizes you would have to apply to each client you can simply set the latency in the master which will sync the audio from start on and keep it while having no crackling distortions:
You can try smaller values ofc, but for my mpd server this is unnoticeable and if you take a look into your logs you will see the latency being anywhere between 100 and 200 after pulse handles the cracks.
I game on a client so the latency locally on this receiver / workstation connected to speakers is lower for everyday use - this is just for the server playing mpd. Other clients are usually openwrt compatible devices. To handle latency between the client and the speakers i use identical USB-optical sound cards on each receiver.
The text was updated successfully, but these errors were encountered:
Hey there.
The wifi-issue is due to how rtp works (multicast). To have multiple receivers without bombarding your network you can use the classic native-tcp protocol instead and advertise those via avahi.
Client native protocol for the local network:
Client Avahi publishing:
The crackling is due to the latency in your network and will disappear after a while or on a restart, because pulseaudio handles the buffer dropouts. Instead of experimenting with different buffer sizes you would have to apply to each client you can simply set the latency in the master which will sync the audio from start on and keep it while having no crackling distortions:
You can try smaller values ofc, but for my mpd server this is unnoticeable and if you take a look into your logs you will see the latency being anywhere between 100 and 200 after pulse handles the cracks.
I game on a client so the latency locally on this receiver / workstation connected to speakers is lower for everyday use - this is just for the server playing mpd. Other clients are usually openwrt compatible devices. To handle latency between the client and the speakers i use identical USB-optical sound cards on each receiver.
The text was updated successfully, but these errors were encountered: