Replies: 1 comment
-
When you say "drift" you mean the samplerates are changing during playback or what? |
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
-
Hello!
I am using snapcast server on an ALSA loopback device to play a stream received by vlc media player. It seems there is a reasonable difference between the sample Rate of the source and the snapserver. I end up with continous messages:
2023-09-02 14-44-13.899 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-14.079 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-14.259 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-14.439 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-14.619 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-14.799 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-15.199 [Info] (AlsaStream) No data availabale, playing silence.
2023-09-02 14-44-15.379 [Info] (AlsaStream) No data availabale, playing silence.
which results in numerous clicks and distortions in the audo on receiver side.
I tried different sample rates in snapserver, also played with chunk_ms and buffer but with no result.
Is there any solution? Is there any external sample rate drift compensation to cope with this?
As there seems to be already a sample rate converter included, maybe the input sample rate could be adjusted according to the fill level of the buffer?
Here is a paper describing a solution with no audible effects:
http://eprints.gla.ac.uk/3603/1/skew_detection.pdf
Thanks a lot!
Gerald
Beta Was this translation helpful? Give feedback.
All reactions