From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Daniel Yek <dyek@real.com>,
Alsa Developement <alsa-devel@lists.sourceforge.net>
Subject: Re: 5.1 surround sound playback XRUN / snd_pcm_writei() didn't unblock immediately / small 114 msec buffer
Date: Mon, 09 Oct 2006 17:21:29 +0200 [thread overview]
Message-ID: <1160407289.6513.272893861@webmail.messagingengine.com> (raw)
In-Reply-To: <6.2.1.2.2.20061006123102.428226e0@mailone.real.com>
Daniel Yek wrote:
> At 06:09 AM 10/6/2006, Clemens Ladisch wrote:
> >Daniel Yek wrote:
> > > I opened "surround51" PCM device and set the sampling rate to 48000, S16_LE
> > > format.
> >
> >Better use "plug:surround51". There are chips like ICE1712 that do not
> >support any format except S32_LE.
>
> It would be great if somebody could suggest an easy way for a media
> application to identify if the system is 5.1-channels capable. After making
> sure that 5.1-channels playback is preferable over 2-channels playback, I
> can then use "plug:surround51" PCM device. I assume that Plug will convert
> all 6 channels without dropping any here. If not, it is not usable.
>
> Right now, I'm depending on opening "surround51" PCM device to fail to
> indicate that the system isn't 5.1-channels capable. "plug:surround51" PCM
> wouldn't open-fail even if the system isn't 5.1-channels capable, resulting
> in a poor playback experience. Do you have a suggestion for me?
The configuration files won't define a "surround51" device if the
hardware is not capable of accepting 5.1 sound, so opening
"plug:surround51" should fail as expected.
HTH
Clemens
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-10-09 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 8:54 _test_channels() / plug:surround51 / Hardware Mixing And dmix / SW or HW Resampling / Volume Control Daniel Yek
2006-09-28 13:17 ` Takashi Iwai
2006-09-28 14:40 ` Lee Revell
2006-09-28 14:46 ` Takashi Iwai
2006-09-28 14:58 ` Takashi Iwai
2006-09-28 15:06 ` Default soundcard (UDEV?) Jaroslav Kysela
2006-09-28 15:15 ` Lee Revell
2006-09-28 15:27 ` Takashi Iwai
2006-09-28 16:00 ` Jaroslav Kysela
2006-09-28 16:30 ` Takashi Iwai
2006-09-28 23:44 ` _test_channels() / plug:surround51 / Hardware Mixing And dmix / SW or HW Resampling / Volume Control Daniel Yek
2006-09-29 11:38 ` Takashi Iwai
2006-10-06 8:52 ` 5.1 surround sound playback XRUN / snd_pcm_writei() didn't unblock immediately / small 114 msec buffer Daniel Yek
2006-10-06 13:09 ` Clemens Ladisch
2006-10-06 20:34 ` Daniel Yek
2006-10-09 15:21 ` Clemens Ladisch [this message]
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=1160407289.6513.272893861@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dyek@real.com \
/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.