Distortion on RaspberryPi4 #436
Unanswered
OkenKhuman
asked this question in
Q&A
Replies: 8 comments 3 replies
-
|
Hi, thanks for report. Could you paste logs from roc-recv during first few minutes? Could you also check what happens if you add |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Sorry for late reply. but |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
With --beeping I can hear single beep sound at start. Just cannot Identify what happen today . Suddenly it works without any changes. 😄 |
Beta Was this translation helpful? Give feedback.
1 reply
-
That's expected. |
Beta Was this translation helpful? Give feedback.
-
|
I extracted some snap from last time it does not work via nohup.out , |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is there other debug option I can try to test the fault? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Converting this to discussion (new github feature). |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for these logs, they were helpful! Here is the key point: The same pattern repeats many time: latency goes out of bound, and the session is restarted. We can see that the latency becomes larger than maximum. It means that at some point, a lot of packets are accumulated in incoming queue but are not played yet. There are two common reasons for that:
The first is possible if there are load peaks on the system because of some CPU-heavy process, or/and because the processing itself is slow. The second is also possible on load peaks, and on problems with driver or device. Here is what we can test to understand the problem:
If the problem is with load peaks and/or too heavy processing, you can try:
If the problem is with ALSA or hardware, you can try to use larger frame size ( It's also possible that the problem is with our SoX backend which we're using for ALSA. We have good backend for PulseAudio, but not so good for ALSA. We'll change it at some point: #231 |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
See also: #299 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I wil keep this as reference when I setup new sound streaming system. |
Beta Was this translation helpful? Give feedback.
-
|
Hello there! Previously native pulse tcp connections worked mostly reliably with pulseaudio on my pi4, and then considerably more reliable with Pipewire. Now I’ve tried this project and I’m running into what I think might be this issue. (Same session recreation due to out of bound latency) Writing to a file with roc-recv produces a perfectly fine audio file even when played back on the pi itself and resampling makes zero influence. As to the specific audio issue, it just constantly cuts out. Small segments are played undistorted (I think, anyway) and then there’s a pause. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When I stream audio from docker container with
pulseaudio module-roc-sinkto RaspberryPi4 withroc-recv, I am having too much distortion. [auto fixed after nearly 1 hour]Last time (nerly 1 moth back) when I did it was fixed just by few seconds...
the commands I run on docker container
pacmd load-module module-roc-sink remote_ip=192.168.29.3 sink_properties=device.description=Raspberrythe command I run on RPi4
/home/pi/proj/speech_processing/roc_alsa/roc-recv -vv -s rtp+rs8m::10001 -r rs8m::10002 -d alsaHow to save state/configuration so that it will work perfectly without delay on next startup?
Beta Was this translation helpful? Give feedback.
All reactions