From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Talbut Subject: Re: Setup when compiled in 2.6 kernel Date: Sun, 19 Feb 2006 19:46:42 +0000 Message-ID: <43F8CB22.4060202@dpets.demon.co.uk> References: <43F8A917.8010008@dpets.demon.co.uk> <1140375659.2733.338.camel@mindpipe> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1140375659.2733.338.camel@mindpipe> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Lee Revell Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Thanks, Lee Lee Revell wrote: > This is not how ALSA works, you can't just cat things to the device > file. The interface to ALSA is through alsa-lib. Can you or anyone explain this, or point to an explanation? > > What happens if you start SIMPLE: > > aplay file.wav # aplay /dos/Workspace/Music/originaldedodedo.wav ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:544: audio open error: No such file or directory ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642