From: Danijel DOMAZET <p-danijel.domazet@devialet.com>
To: sox-users@lists.sourceforge.net
Subject: Prevent SoX from doing the clipping?
Date: Fri, 5 Jun 2020 08:54:48 +0200 [thread overview]
Message-ID: <CAB+hYN3xi5BDCpw04KCCv9bZfr1m4gUf=xaUYf6VRJYSsQ-mnQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
Hi list,
I have a heavily "overflowed" WAV file (samples written in float 32-bit
format): instead of [-1.0,+1.0], the samples range goes as far as
[-5.0,+5.0].
Using SoX to get raw PCM audio samples from WAV file:
`sox --bits 32 --channels 1 --encoding floating-point --rate 48000
input.wav output.raw`
I get warnings:
sox WARN sox: `input.wav' input clipped 1163400 samples
sox WARN sox: `output.raw' output clipped 605664 samples; decrease
volume?
When I look into the output, I see the samples were clipped, and the range
is [-1.0,+1.0] now. However, that is not what I want.
I would like to have exactly the same output as input, just in different
format (RAW instead of WAV). Is there a way to prevent SoX from doing the
clipping?
Thanks!
Danijel Domazet
--
- Confidential -
[-- Attachment #1.2: Type: text/html, Size: 1263 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next reply other threads:[~2020-06-05 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 6:54 Danijel DOMAZET [this message]
2020-06-05 8:05 ` Prevent SoX from doing the clipping? Peter P.
2020-06-05 8:31 ` Måns Rullgård
2020-06-05 8:39 ` Danijel DOMAZET
2020-06-06 18:02 ` Jan Stary
2020-06-06 18:03 ` Jan Stary
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB+hYN3xi5BDCpw04KCCv9bZfr1m4gUf=xaUYf6VRJYSsQ-mnQ@mail.gmail.com' \
--to=sox-users@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).