Re: [Alsa-user] snd_pcm_hw_params_set_buffer_size returns -EINVAL
On Tuesday 27 September 2016 08:28:42 Clemens Ladisch wrote: > And you must set a buffer size that is supported by the device. Thanks, I just found snd_pcm_hw_params_set_buffer_size_near(). However, for our app, it would be nice to get the preferred buffer size before any PCM handle and params are created. Is this possible? -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] snd_pcm_hw_params_set_buffer_size returns -EINVAL
Johannes Lorenz wrote: > this happens in [1]. You can also call snd_pcm_hw_params_set_buffer_size() > before snd_pcm_hw_params() (that's probably better?), it always results in (- > EINVAL). Calling snd_pcm_hw_params_set_*() after snd_pcm_hw_params() does not make sense. And you must set a buffer size that is supported by the device. Regards, Clemens -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] snd_pcm_hw_params_set_buffer_size returns -EINVAL
Hello, this happens in [1]. You can also call snd_pcm_hw_params_set_buffer_size() before snd_pcm_hw_params() (that's probably better?), it always results in (- EINVAL). The google-answers did not help. Any idea? In my case, the buffer size is 256, but it also fails is I use 32768. Thanks on advance! - Johannes [1] https://github.com/zynaddsubfx/zynaddsubfx/blob/master/src/Nio/AlsaEngine.cpp#L331-L335 -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
