From: Niklas Werner <bergtroll@gmx.li>
To: alsa-devel@lists.sourceforge.net
Subject: Re: usb-audio
Date: Tue, 28 Oct 2003 11:41:07 +0100 [thread overview]
Message-ID: <200310281141.07453.bergtroll@gmx.li> (raw)
In-Reply-To: <s5hn0bl659n.wl@alsa2.suse.de>
Am Dienstag, 28. Oktober 2003 11:11 schrieb Takashi Iwai:
> At Mon, 27 Oct 2003 20:53:08 +0100,
>
> Antonio Willy Malara wrote:
> > On 2003.10.27 19:16, Takashi Iwai wrote:
> > > > /* FIXME: correct endianess and sign? */
> > >
> > > could you give more information:
> > > which program, which device and what format doesn't it work?
> >
> > the system is a powermac, the device is a Griffin iMic, the app is
> > jack version 0.80, the output is:
> >
> > Sorry. The audio interface "hw:1"doesn't support either of the two
> > hardware sample formats that jack can use.
>
> then it's a problem of JACK, not ALSA.
> the hardware doesn't support 32bit integer but only 24bit packed in 3
> bytes.
No, I don't think it is.
I get similar problems with my emi 2|6 and alsaplayer, mplayer, xmms, ...
My impression is that ALSA assumes that the connected interfaces _always_
allow for the same Endianess as the system. This, of course, isn't always
so.
Mplayer:
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 emi
alsa-init: format Signed 16-bit (Big-Endian) are not supported by
hardware, trying default
alsa9: 44100 Hz/2 channels/4 bpf/65536 bytes buffer/Signed 16 bit Little
Endian
AO: [alsa9] 44100Hz 2ch Signed 16-bit (Little-Endian) (2 bps)
alsaplayer either dies with "FIXME: f_unsynchronization is set.Please
contact alsaplayer team." or produces static noise.
aplay does get this right, so it seems to use a different method of
querying the device.
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/
next prev parent reply other threads:[~2003-10-28 10:41 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 ` Niklas Werner [this message]
2003-10-28 11:10 ` usb-audio Takashi Iwai
2003-10-28 11:48 ` usb-audio Niklas Werner
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=200310281141.07453.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox