Kai Vehmanen <[EMAIL PROTECTED]> wrote: > For fullduplex to work at 44.1kHz, you need to set sampling rate to 44100 > with ALSA's snd_pcm_hw_params_set_rate_near() function. The closest > matching values are 44099.814 for capture and 44100.952 for playback.
Isn't this very strange? I thought that capture and playback on the ens1371 use the same clock. > To make alsa-lib's latency work, you need to make the following changes: > [snip patch] > With these code changes, cmdline > > ./latency -r 44100 -m 512 -M 512 -c 1 -s 2000 -p > > ... runs without problems. Btw; commenting out the period check is a hack. > The returned valued seemed strange, and I have no time to debug it now... Okay, obviously this should not work. If capture and playback rates are indeed different, and thus the periods, distortion should occur after a while. So the fact that it does work seems to indicate that the snd_pcm_hw_params_set_rate_near does not work correctly. I hope Jaroslav can look into this. Maarten _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
