From: Daniel Mack <zonque@gmail.com>
To: Dan MacDonald <allcoms@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: bit depth issue for Scarlett 2i4
Date: Sat, 13 Oct 2012 10:00:44 +0200 [thread overview]
Message-ID: <50791FAC.6000408@gmail.com> (raw)
In-Reply-To: <CANOoOjtrGHCjtEjQ+6jAZ1un4pXsGD5=YyJV9F2mrUVbXpoO8w@mail.gmail.com>
On 13.10.2012 09:43, Dan MacDonald wrote:
> Hi ALSA devs!
>
> I recently bought a Focusrite Scarlett 2i4 which is advertised as being
> capable of recording at a max of 24bit/96Khz but when I run alsacap it
> reports it as 32bit:
>
> ./alsacap -R -d hw:1
> *** Exploring configuration space of device `hw:1' for recording ***
> 2 channels
> Sampling rate 44100..96000 Hz
> Sample formats: S32_LE
> Significant bits: 32
>
> It does seem to record OK but that output seems wrong and I'm slightly
> concerned about the waste of disk space when multitracking if I end up with
> 32bit files but only 24 of those bits per sample are actually being used.
The output lets you know about the format the hardware uses on the wire.
Nothing to be concerned about - if you want to record 24 bits only, you
can use the plughw plugin to do the sample format conversion.
Daniel
prev parent reply other threads:[~2012-10-13 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 7:43 bit depth issue for Scarlett 2i4 Dan MacDonald
2012-10-13 8:00 ` Daniel Mack [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=50791FAC.6000408@gmail.com \
--to=zonque@gmail.com \
--cc=allcoms@gmail.com \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).