On Sun, 23 May 2004 11:21:41 +0200 (CEST) Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> On Sat, 22 May 2004, Giuliano Pochini wrote: > > > Period 0 is 6624 frames and Period 1 is 6592 frames long (32 frames > > shorter). I put some debug code and this is the output for a the playback > > test above: > > ALSA does not know about this. All period sizes must be equal. > It's a bug in your driver which must avoid this configuration. Yep, there is a bug indeed. I just noticed that some dolt (me) wrote .periods_min=1 in the snd_pcm_hardware_t struct for some cards. Now running the same "aplay -B300000 -F200000" plays fine. Still, there is a thing which is not clear. When I type the command above I get: bufsize=52864 bytes periods=2 persize=26368 bytes allocated buffer size=131072 (pages=32) 52864 holds two periods 26368 bytes long, with a rest of 128 bytes. Have I to simply ignore the remaining space ? And the that case, must the .pointer callback return a value within 0..persize*2-1 or 0..bufsize-1 ? -- Giuliano. ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
