All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alien <alien999999999@users.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Subject: OSS/ALSA issue
Date: Tue, 6 Jun 2006 21:57:37 +0200	[thread overview]
Message-ID: <200606062157.43489.alien999999999@users.sourceforge.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]

I don't know if this is true on any driver, but here's what happend yesterday: 
(i have au8810 driver; on x86_64 system)

i was watching google video on my system

(google video is a flash thing; thus emulated and uses OSS (the only app that 
needs it))

and suddenly gaim reconnected a network and beeped using aplay (ALSA)

as a result, the sound was played, all sound looped (also flash), and a few 
hours later, my /var/log/kernel/warnings was > 600MB (kernel warnings).


Now, we all know that:

1. ALSA has hardware mixing if the chipset/driver supports it (i know mine 
does).

2. OSS does not do any multiple sounds


so, the OSS application is continually using soundcard. and aplay plays a 
short one... should it work or must aplay be denied???

(i'm using latest alsa)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

             reply	other threads:[~2006-06-06 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 19:57 Alien [this message]
2006-06-06 20:37 ` OSS/ALSA issue Lee Revell
2006-06-06 21:29   ` Alien
2006-06-06 21:31     ` Lee Revell
     [not found]   ` <200606062332.55293.alien999999999@users.sourceforge.net>
2006-06-06 21:40     ` Lee Revell
2006-06-07  6:56       ` Alien

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=200606062157.43489.alien999999999@users.sourceforge.net \
    --to=alien999999999@users.sourceforge.net \
    --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.