Am Mittwoch, 1. Februar 2006 04:55 schrieb Steffen Schwientek:
>
> If I work with ecasound I get the same message..
>
> > $ arecord -D plughw:1 -f dat /tmp/test-dat-quality.wav
>
> Works, but the frequency is wrong.
>
> arecord -D plughw:1  -f S16_LE -c2 -r32000 /tmp/test-dat-quality.wav
>
> works much better.
>
> OK,  I still need something to glue this together. Simply piping arecord |
> aplay results in a delay between tv and sound...

I don't get it. If I simply put this informations in an .asoundrc, ecasound 
refuse to work.

Here is my .asound:
pcm.tv {
        type rate               # Rate PCM
        
        slave {                 # Slave definition
                format "S16_LE"
                rate 32000
                pcm "hw:1,0"        # Slave PCM name
        }
}

And this happens, if I run ecasound -i alsa,tv:
- [ Session created ] 
----------------------------------------------------------
- [ Chainsetup created (cmdline) ] 
---------------------------------------------
- [ Connecting chainsetup ] 
----------------------------------------------------
(eca-chainsetup) 'rt' buffering mode selected.
(audioio_alsa) Warning! Period-size differs from current client buffersize.
ALSA lib pcm_mmap.c:363:(snd_pcm_mmap) mmap failed: Invalid argument
ERROR: Connecting chainsetup failed: "Enabling chainsetup: AUDIOIO-ALSA: Error
... when setting up hwparams: Invalid argument"


Somehow there is an error in .asoundrc...


Steffen


-------------------------------------------------------
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
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to