well, it's not unnecessary but too strict.
Yes.
the problem is that this check is too strict when only two periods are used. since buffer_size/2 == period_size, if the update of hwptr is delayed even for one sample, it won't pass.
This is exactly what happens in my case.
Anyway, I think that we should leave the check as is for debugging purposes (we should know that something is failing).
sure, it's harmless message (as long as it comes from snd_pcm_update_hw_ptr()) but too annoying. there are too many sloppy hardwares...
After printing the error message is printed, the function returns immediately. Can you confirm that this does not have negative side effects like dropped frames?
Besides, the error messages popping up in the console interfere visually with the text mode interface of the sound app that I use.
Tobias
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
