All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Werner <bergtroll@gmx.li>
To: alsa-devel@lists.sourceforge.net
Subject: Re: usb-audio
Date: Tue, 28 Oct 2003 12:48:17 +0100	[thread overview]
Message-ID: <200310281248.17285.bergtroll@gmx.li> (raw)
In-Reply-To: <s5hk76pliro.wl@bari.suse.de>

Am Dienstag, 28. Oktober 2003 12:10 schrieb Takashi Iwai:
> 
> > No, I don't think it is.
> > I get similar problems with my emi 2|6 and alsaplayer, mplayer, xmms,
> > ...
>
> did you use plughw instead of hw in all cases?
> otherwise they won't work always.
plughw doesn't work at all!

> mplayer has an option to specify the device name.
> it'd be better to define a new pcm in ~/.asoundrc such as
>
> 	pcm.emi26 {
> 		type plug
> 		slave.pcm "hw:0"
> 	}
>
> (where "hw:0" should be changed to the corresponding one)
>
> and run like
>
> 	% mplayer -ao alsa9:emi26 ...
>
gives:
Checking audio filter chain for 44100Hz/2ch/16bit -> 44100Hz/2ch/16bit...
AF_pre: af format: 2 bps, 2 ch, 44100 hz, big endian signed int 
AF_pre: 44100Hz 2ch Signed 16-bit (Big-Endian)
alsa-init: requested format: 44100 Hz, 2 channels, Signed 16-bit 
(Big-Endian)
alsa-init: soundcard set to emi26
alsa9: 44100 Hz/2 channels/2 bpf/32768 bytes buffer/Signed 16 bit Big 
Endian
AO: [alsa9] 44100Hz 2ch Signed 16-bit (Big-Endian) (2 bps)
Building audio filter chain for 44100Hz/2ch/16bit -> 44100Hz/2ch/16bit...
Video: no video
Starting playback...


MPlayer interrupted by signal 11 in module: play_audio

and no sound, whereas accessing hw:1 directly at least produces output.
playing through plug-hw with aplay works, though
alsaplayer doesn't like the card with plug-layer. (alsaplayer seems to 
have deeper problems, since its doesn't work on the internal snapper, as 
well.

(Oh: kernel 2.6-test8-benh from bitkeeper, if that is of any interest)

Have fun*

Niklas



-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/

  reply	other threads:[~2003-10-28 11:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 18:03 usb-audio Antonio Willy Malara
2003-10-27 18:16 ` usb-audio Takashi Iwai
2003-10-27 19:53   ` usb-audio Antonio Willy Malara
2003-10-28 10:11     ` usb-audio Takashi Iwai
2003-10-28 10:41       ` usb-audio Niklas Werner
2003-10-28 11:10         ` usb-audio Takashi Iwai
2003-10-28 11:48           ` Niklas Werner [this message]
2003-10-28 12:13             ` usb-audio Takashi Iwai
2003-10-28 12:42               ` usb-audio Niklas Werner
2003-10-28 13:28                 ` usb-audio Takashi Iwai
2003-10-28 18:25                   ` usb-audio Takashi Iwai
2003-10-28 19:18                     ` usb-audio Niklas Werner
2003-10-29 18:24                       ` usb-audio Takashi Iwai
2003-10-29 22:26                         ` usb-audio Niklas Werner
2003-10-30 12:17                           ` usb-audio Takashi Iwai
2003-10-30 12:42                             ` usb-audio Niklas Werner
2003-10-30 19:46                               ` usb-audio Takashi Iwai
2003-10-31  8:23                                 ` usb-audio Niklas Werner
2003-10-31 11:02                                   ` usb-audio Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200310281248.17285.bergtroll@gmx.li \
    --to=bergtroll@gmx.li \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.