All of lore.kernel.org
 help / color / mirror / Atom feed
From: dave murray-rust <hdsp@mo-seph.com>
To: alsa-devel@lists.sourceforge.net
Subject: HDSP OSS Emulation
Date: Fri, 14 Jan 2005 11:40:34 +0000	[thread overview]
Message-ID: <200501141140.34929.hdsp@mo-seph.com> (raw)

Hi there,

First of all, many thanks to all for getting the HDSP working on
linux, it's looking lovely.

I'm having a problem with the OSS emulation, however, in that it
outputs on all 18 channels simultaneously. I read something about this
on the list archives [1], and I was wondering if any progress has been
made, or if there are any workarounds? The application I'm running is
based on the (rather outdated) xaudio library, and responds badly to
'aoss'.

Any thoughs?

Cheers,
dave

[1]
(Question from Ed Wildgoose, response from Thomas Charbonnel, May
2004)

> 4) Why does the OSS emulation write to all (16)  channels when an app
> opens it in 2 channel mode?  It's very easy to do something really silly
>  as a result (I got a rather nasty burning smell from my expensive
> speakers after inadvertently putting a lot of clipped signal through
> them at high power...)  Is this an OSS issue, or just the way this
> driver works?  (I don't have any other multichannel cards to compare
> against!)

I'm aware of this problem, but still have to track it down. I guess it's
related to the fact that the card can only be opened using all available
channels. I don't know if oss emulation uses the plughw facility, but
there must be something similar because non-interleaved streams are
handled properly, there just lacks something to deal with the number of
channel.
-- 
He who laughs last thinks slowest.
  - forwarded email




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

                 reply	other threads:[~2005-01-14 11:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200501141140.34929.hdsp@mo-seph.com \
    --to=hdsp@mo-seph.com \
    --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.