All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, vorbis-dev@xiph.org
Subject: Re: libao problem (Re: No dmix/dsnoop on Intel ICH4/5 by default?)
Date: Thu, 17 Jan 2013 13:44:44 +0100	[thread overview]
Message-ID: <50F7F23C.4070006@gmail.com> (raw)
In-Reply-To: <50F7EAA1.7040504@ladisch.de>

On 17-01-13 13:12, Clemens Ladisch wrote:

> Rene Herman wrote:

>> I can mix as many streams as I want using just "aplay" but if I start
>> by playing one track with "ogg123" (which uses a default, unconfigured
>> libao as its backend), I can't start a second ogg123, which then says:
>>
>> ao_alsa WARNING: Unable to open surround playback.  Trying default device...
>
> The default dmix is for stereo only.  For a surround dmix device, you'd
> have to write your own definition.

Thank you. I didn't notice it was related due to the "trying default 
device" which I thought should've worked but the issue is that libao 
1.1.0 doesn't use the alsa "default" device by default. The first ogg123 
instance therefore keeps things busy.

There's a matching bug-rapport here, I see:

https://trac.xiph.org/ticket/1776

I can, now, set it to dev=default manually but what this means is that 
libao-1.1.0 by default kills alsa default software mixing. These days 
everybody seems to have regressed to using a soundserver again anyway 
and as such not many may notice, but this izz no good, I feel... :-/

In any case, hope this was useful to alsa-devel in the sense that this 
libao behavior is now known here, but this is otherwise libao related 
only, then.

Regards,
Rene

  reply	other threads:[~2013-01-17 12:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 19:26 No dmix/dsnoop on Intel ICH4/5 by default? Rene Herman
2013-01-16 20:52 ` Clemens Ladisch
2013-01-17 10:22   ` libao problem (Re: No dmix/dsnoop on Intel ICH4/5 by default?) Rene Herman
2013-01-17 12:12     ` Clemens Ladisch
2013-01-17 12:44       ` Rene Herman [this message]
2013-03-07  8:20         ` [Vorbis-dev] " xiphmont
2013-03-24 17:25           ` Rene Herman
2013-03-24 18:00             ` [alsa-devel] " xiphmont
2013-03-24 18:50               ` [Vorbis-dev] " Clemens Ladisch
2013-03-24 19:43                 ` [alsa-devel] " xiphmont
2013-03-24 20:01                   ` [Vorbis-dev] " Rene Herman
2013-03-24 21:28                 ` Alan Horstmann

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=50F7F23C.4070006@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=vorbis-dev@xiph.org \
    /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.