linux-kernel - ALSA: arecord : silennce recorded as 0x80

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAHhAz+haVH-4Hgsz0PpTgUSW1pX4XxwxXwEd7nLVb0sFFwQwCg@mail.gmail.com>
Date:   Thu, 13 Apr 2023 19:19:52 +0530
From:   Muni Sekhar <munisekharrms@...il.com>
To:     alsa-devel <alsa-devel@...a-project.org>,
        linux-sound@...r.kernel.org
Cc:     LKML <linux-kernel@...r.kernel.org>,
        kernelnewbies <kernelnewbies@...nelnewbies.org>
Subject: ALSA: arecord : silennce recorded as 0x80

Hi all,

I recorded the silence on the default audio card by running "arecord
-d 5 test.wav."

Once it exited, I checked the contents by running "hexdump test.wav,"
and I see that silence is recorded as a sequence of 0x80 instead of
0x00.

0000000 4952 4646 0024 8000 4157 4556 6d66 2074
0000010 0010 0000 0001 0001 1f40 0000 1f40 0000
0000020 0001 0008 6164 6174 0000 8000 8080 8080
0000030 8080 8080 8080 8080 8080 8080 8080 8080
0000040 8080 8080 8080 8080 8080 8080 8080 8080
...

What might be the reason for silence being recorded as 0x80 instead of 0x0?


-- 
Thanks,
Sekhar