From: Paul Davis Subject: Re: Re: (Fwd) ALSA related comments - please correct [wulfram-26284] Date: Mon, 29 Dec 2003 11:19:51 -0500 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <200312291619.hBTGJqgr015398@dhin.linuxaudiosystems.com> References: <200312291508.hBTF7xdB022388@dhin.linuxaudiosystems.com> Return-path: Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA02768 for ; Mon, 29 Dec 2003 17:20:56 +0100 In-reply-to: Your message of "Mon, 29 Dec 2003 10:07:58 EST." <200312291508.hBTF7xdB022388@dhin.linuxaudiosystems.com> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: Cc: Jaroslav Kysela , Peter Hunnisett , Ove Kaaven , ALSA development List-Id: alsa-devel@alsa-project.org >although i agree that from a pragmatic perspective, it would be good >to understand how to use ALSA to do this. > >however, this model of audio programming is not portable, and has >gotten people into trouble before, not just under Linux. > >making the assumption that direct access at all times to the full >hardware buffer is not a valid assumption to make. there is a very sorry, terrible english. i hope you know what i meant :) ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click