From: Jan Stary <hans@stare.cz>
To: sox-users@lists.sourceforge.net
Subject: Re: 32 bit float truncated to 24 bit int with no parameters
Date: Tue, 8 Nov 2022 23:03:19 +0100 [thread overview]
Message-ID: <Y2rSJhZSmkA+JfDK@www.stare.cz> (raw)
In-Reply-To: <CAE44+pL9tgEZCQ7SV6-HN0sqPFVyQmTbiFRLmEMFqjhhJzyjXA@mail.gmail.com>
On Sep 12 22:45:27, debrebeuf01@gmail.com wrote:
> However, when I try to save my file as 32 bit float, the audio is truncated
> to 24 bit int. Even if I have no parameters and just input output a 32f
> file, the audio is truncated to 24 bit int. Here's the command, where
> in.wav is a 32 bit float file with content more precise than 24 bit int:
>
> sox "in.wav" "out.wav"
I cannot reproduce this:
$ sox -n orig.wav synth 1 sin gain -6
$ sox orig.wav copy.wav
$ soxi orig.wav copy.wav
Input File : 'orig.wav'
Channels : 1
Sample Rate : 48000
Precision : 32-bit
Duration : 00:00:01.00 = 48000 samples ~ 75 CDDA sectors
File Size : 192k
Bit Rate : 1.54M
Sample Encoding: 32-bit Signed Integer PCM
Input File : 'copy.wav'
Channels : 1
Sample Rate : 48000
Precision : 32-bit
Duration : 00:00:01.00 = 48000 samples ~ 75 CDDA sectors
File Size : 192k
Bit Rate : 1.54M
Sample Encoding: 32-bit Signed Integer PCM
Total Duration of 2 files: 00:00:02.00
> To be clear, the output file IS a 32 bit float file,
> but the audio is truncated to 24 bit.
Meaning what, exactly? A 32bit float is a 32bit float.
If the files are small enough,
can you post them somewhere to be looked at?
> I have been using Bitter VST in iZotope RX to view the actual depth of the
> audio file. One more thing, saving a 32 bit float as a 32 bit int file is
> truncated as intended. It's only when saving as 32f that the audio is
> truncated to 24 bit int.
I don't know what you mean by "truncated"?
Please post an example file.
> Here are some screenshots of Bitter to ease your understanding (note that
> foo.wav is out.wav): > https://imgur.com/a/wWlwk6T
I have no idea what those images are supposed to show.
Jan
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2022-11-08 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 3:45 32 bit float truncated to 24 bit int with no parameters Sean Hurley
2022-09-13 9:14 ` Thomas Förster
2022-09-14 18:07 ` Sean Hurley
2022-11-08 22:03 ` Jan Stary [this message]
2022-11-09 14:54 ` Måns Rullgård
2022-11-09 23:22 ` Sergei Steshenko via Sox-users
2022-11-14 13:59 ` Måns Rullgård
2022-11-30 20:03 ` Jeff Learman
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=Y2rSJhZSmkA+JfDK@www.stare.cz \
--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).