All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David E. Storey" <dave@tamos.net>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa <alsa-devel@lists.sourceforge.net>
Subject: Re: 24bit hdsp
Date: 28 May 2003 21:03:06 -0400	[thread overview]
Message-ID: <1054170186.424.71.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

I was reading

http://petertodd.ca/hdsp.php

and the only place it mentioned 24 bit was down toward the bottom,
implying that it wasn't supported. But now that I know it is and looking
through the source for jack, it would appear that by default, it will
open the device in 24bit mode, that's good. It would appear that as
opposed to most other drivers, I shouldn't be using dithering on this
device as I'll loose my dynamic range, yes? (I noticed your name all
over the code, so I'm betting your probably the best to ask this
question...)

d!


On Wed, 2003-05-28 at 17:12, Paul Davis wrote:
> >what would it take to support 24bit audio in the hdsp driver? Would it
> >take away from the number of available channels? I'd like to use an
> >Alesis AI-3 (mostly due to cost) with my multiface, but I'd like to be
> >able to utilize all 18 channels the multiface provides. Is there any way
> >I can help?
> 
> the driver already supports 24 bit audio. if you use the hw layer, it
> must match the hw's definition of 24 bit: 24 bits packed in the upper
> bits of a 32 bit word. if you use the plughw layer, you can probably
> get "true" 24 bit audio (i doubt if this code path has been explored
> much). 


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-05-29  1:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29  1:03 David E. Storey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-28 19:20 24bit hdsp David E. Storey
2003-05-28 21:12 ` Paul Davis

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=1054170186.424.71.camel@localhost \
    --to=dave@tamos.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=paul@linuxaudiosystems.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.