PulseAudio RTP unicast poor sound quality - frequent pops
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am doing multi-room audio in my house as described at posts like this one:
Multi-room audio with multicast RTP
http://www.danplanet.com/blog/2014/11/26/multi-room-audio-with-multicast-rtp/
My problem is that sound quality is poor. In particular, there are frequent pops. I have a Gigabit wired LAN and all computers are Intel Core i5 or i7 (no Raspberry Pi's or other low power devices). (I believe Intel CPU's are little endian.)
My PA configuration is described in more detail here:
https://unix.stackexchange.com/a/471787/15010
Since then I have added latency_msec=1000
to module-rtp-recv on each receiver.
On the sender, I am thinking about adding rate=44100 channels=2 format=s16le
. However, those are already the defaults on all devices:
- PulseAudio Version: 12.2
- Default Sample Specification: s16le 2ch 44100Hz
Also, all are synchronized with an NTP server:
sudo timedatectl status
System clock synchronized: yes
NTP service: active
First question: how do I add rate=44100 channels=2 format=s16le
when loading the module using pactl
instead of changing /etc/pulse/default.pa
?
Second, am I on the right track with those proposed changes? What else could be responsible for my poor sound quality? My hardware is pretty high end and the GigE network has good performance (although I would have to learn how to quantify that performance if that becomes necessary).
networking audio pulseaudio
add a comment |Â
up vote
1
down vote
favorite
I am doing multi-room audio in my house as described at posts like this one:
Multi-room audio with multicast RTP
http://www.danplanet.com/blog/2014/11/26/multi-room-audio-with-multicast-rtp/
My problem is that sound quality is poor. In particular, there are frequent pops. I have a Gigabit wired LAN and all computers are Intel Core i5 or i7 (no Raspberry Pi's or other low power devices). (I believe Intel CPU's are little endian.)
My PA configuration is described in more detail here:
https://unix.stackexchange.com/a/471787/15010
Since then I have added latency_msec=1000
to module-rtp-recv on each receiver.
On the sender, I am thinking about adding rate=44100 channels=2 format=s16le
. However, those are already the defaults on all devices:
- PulseAudio Version: 12.2
- Default Sample Specification: s16le 2ch 44100Hz
Also, all are synchronized with an NTP server:
sudo timedatectl status
System clock synchronized: yes
NTP service: active
First question: how do I add rate=44100 channels=2 format=s16le
when loading the module using pactl
instead of changing /etc/pulse/default.pa
?
Second, am I on the right track with those proposed changes? What else could be responsible for my poor sound quality? My hardware is pretty high end and the GigE network has good performance (although I would have to learn how to quantify that performance if that becomes necessary).
networking audio pulseaudio
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am doing multi-room audio in my house as described at posts like this one:
Multi-room audio with multicast RTP
http://www.danplanet.com/blog/2014/11/26/multi-room-audio-with-multicast-rtp/
My problem is that sound quality is poor. In particular, there are frequent pops. I have a Gigabit wired LAN and all computers are Intel Core i5 or i7 (no Raspberry Pi's or other low power devices). (I believe Intel CPU's are little endian.)
My PA configuration is described in more detail here:
https://unix.stackexchange.com/a/471787/15010
Since then I have added latency_msec=1000
to module-rtp-recv on each receiver.
On the sender, I am thinking about adding rate=44100 channels=2 format=s16le
. However, those are already the defaults on all devices:
- PulseAudio Version: 12.2
- Default Sample Specification: s16le 2ch 44100Hz
Also, all are synchronized with an NTP server:
sudo timedatectl status
System clock synchronized: yes
NTP service: active
First question: how do I add rate=44100 channels=2 format=s16le
when loading the module using pactl
instead of changing /etc/pulse/default.pa
?
Second, am I on the right track with those proposed changes? What else could be responsible for my poor sound quality? My hardware is pretty high end and the GigE network has good performance (although I would have to learn how to quantify that performance if that becomes necessary).
networking audio pulseaudio
I am doing multi-room audio in my house as described at posts like this one:
Multi-room audio with multicast RTP
http://www.danplanet.com/blog/2014/11/26/multi-room-audio-with-multicast-rtp/
My problem is that sound quality is poor. In particular, there are frequent pops. I have a Gigabit wired LAN and all computers are Intel Core i5 or i7 (no Raspberry Pi's or other low power devices). (I believe Intel CPU's are little endian.)
My PA configuration is described in more detail here:
https://unix.stackexchange.com/a/471787/15010
Since then I have added latency_msec=1000
to module-rtp-recv on each receiver.
On the sender, I am thinking about adding rate=44100 channels=2 format=s16le
. However, those are already the defaults on all devices:
- PulseAudio Version: 12.2
- Default Sample Specification: s16le 2ch 44100Hz
Also, all are synchronized with an NTP server:
sudo timedatectl status
System clock synchronized: yes
NTP service: active
First question: how do I add rate=44100 channels=2 format=s16le
when loading the module using pactl
instead of changing /etc/pulse/default.pa
?
Second, am I on the right track with those proposed changes? What else could be responsible for my poor sound quality? My hardware is pretty high end and the GigE network has good performance (although I would have to learn how to quantify that performance if that becomes necessary).
networking audio pulseaudio
networking audio pulseaudio
asked Sep 27 at 20:28
MountainX
4,7562369120
4,7562369120
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
As stated in the question, I added latency_msec=1000
to module-rtp-recv on each receiver and that did not resolve the issue. Since then, I changed it to latency_msec=4000
and that did resolve the issue. I did not try intermediate values.
I consider this only half an answer. I would still like to fine tune other parameters such as rate and format, but so far I have come across the correct instructions for doing so. If anyone comes up with a better answer, I'll accept yours. For now, this is the best answer I came up with through trial and error; it was enough to make the music experience significantly better.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As stated in the question, I added latency_msec=1000
to module-rtp-recv on each receiver and that did not resolve the issue. Since then, I changed it to latency_msec=4000
and that did resolve the issue. I did not try intermediate values.
I consider this only half an answer. I would still like to fine tune other parameters such as rate and format, but so far I have come across the correct instructions for doing so. If anyone comes up with a better answer, I'll accept yours. For now, this is the best answer I came up with through trial and error; it was enough to make the music experience significantly better.
add a comment |Â
up vote
0
down vote
As stated in the question, I added latency_msec=1000
to module-rtp-recv on each receiver and that did not resolve the issue. Since then, I changed it to latency_msec=4000
and that did resolve the issue. I did not try intermediate values.
I consider this only half an answer. I would still like to fine tune other parameters such as rate and format, but so far I have come across the correct instructions for doing so. If anyone comes up with a better answer, I'll accept yours. For now, this is the best answer I came up with through trial and error; it was enough to make the music experience significantly better.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
As stated in the question, I added latency_msec=1000
to module-rtp-recv on each receiver and that did not resolve the issue. Since then, I changed it to latency_msec=4000
and that did resolve the issue. I did not try intermediate values.
I consider this only half an answer. I would still like to fine tune other parameters such as rate and format, but so far I have come across the correct instructions for doing so. If anyone comes up with a better answer, I'll accept yours. For now, this is the best answer I came up with through trial and error; it was enough to make the music experience significantly better.
As stated in the question, I added latency_msec=1000
to module-rtp-recv on each receiver and that did not resolve the issue. Since then, I changed it to latency_msec=4000
and that did resolve the issue. I did not try intermediate values.
I consider this only half an answer. I would still like to fine tune other parameters such as rate and format, but so far I have come across the correct instructions for doing so. If anyone comes up with a better answer, I'll accept yours. For now, this is the best answer I came up with through trial and error; it was enough to make the music experience significantly better.
answered Oct 1 at 0:47
MountainX
4,7562369120
4,7562369120
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471930%2fpulseaudio-rtp-unicast-poor-sound-quality-frequent-pops%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password