Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Harman Kalra <harman4linux@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Selecting Audio formats
Date: Thu, 19 Jul 2012 20:35:36 +0200	[thread overview]
Message-ID: <50085378.5000300@ladisch.de> (raw)
In-Reply-To: <CAA4JwzW3zNOCWeFoaCSxnx8WzsQTbu1+rOuq2jFxdt043MWSaQ@mail.gmail.com>

Harman Kalra wrote:
>     Can you please explain difference between signed and unsigned PCM
> formats,

Signed PCM formats have a sign, unsigned don't.  S16 allows values in the
range -32768..32767, U16, 0..65535.

> in what cases does unsigned is used,

In practice, never.  It was historically used by some 8-bit cards.

> which is more efficient (memory and sound clarity)

I refer the honourable gentleman to the reply I gave in the last mail.

>> If you tried to set MPEG format, ALSA would inform you that the device
>> does not support this.
>
>         But when I queried the hardware regarding the supported audio
> formats using the api " snd_pcm_format_name", it responded with a list of
> formats, including , A-law, u-law-, IMA_ADPCM, MPEG, GSM, so what does it
> mean.

It means that the sample format identified by the constant
SND_PCM_FORMAT_MPEG is indeed named "MPEG".  This has nothing to do
with what formats some particular hardware supports.

>       What would be audio sample file size in case of A-law, will it be
> same as U8.

I refer the honourable gentleman to the reply I gave in the last mail.


Regards,
Clemens

      parent reply	other threads:[~2012-07-19 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 14:21 Selecting Audio formats Harman Kalra
2012-07-19 15:00 ` Clemens Ladisch
     [not found]   ` <CAA4JwzW3zNOCWeFoaCSxnx8WzsQTbu1+rOuq2jFxdt043MWSaQ@mail.gmail.com>
2012-07-19 18:35     ` Clemens Ladisch [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=50085378.5000300@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=harman4linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox