From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Courtier-Dutton Subject: Re: snd_pcm_delay() bug Date: Sun, 16 May 2004 03:06:35 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <40A6CCAB.1010907@superbug.demon.co.uk> References: <1084648674.15902.0.camel@shrek.bitfreak.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1084648674.15902.0.camel@shrek.bitfreak.net> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Ronald S. Bultje" Cc: alsa-devel@lists.sf.net List-Id: alsa-devel@alsa-project.org Ronald S. Bultje wrote: > Hi, > > for both my ALI 5451 and my Audigy 2 NX, snd_pcm_delay() sometimes > returns (in the second argument pointer) ridiculously high values in the > range of 2^32/bytes_per_sample (in my case, 16bitLE/stereo, that comes > down to roughly 1,1E9). I'm guessing there's some kind of > signed/unsigned or 32/64bit integer bug in this function? Is this a > known bug? Is there a fix? > > Ronald > after calling snd_pcm_delay(), call snd_pcm_state() and make sure it is in RUNNING state, otherwise, values returned from snd_pcm_delay() are meaningless. Cheers James ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click