From: "Måns Rullgård" <mans@mansr.com>
To: Matt Flax <flatmax@flatmax.org>
Cc: sox-devel@lists.sourceforge.net
Subject: Re: 64bit audio read and write
Date: Wed, 06 Jul 2016 13:22:56 +0100 [thread overview]
Message-ID: <yw1xoa6blzvj.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <577CF6B0.2010107@flatmax.org> (Matt Flax's message of "Wed, 6 Jul 2016 22:16:48 +1000")
Matt Flax <flatmax@flatmax.org> writes:
> On 06/07/16 21:41, Måns Rullgård wrote:
>> Matt Flax <flatmax@flatmax.org> writes:
>>
>>> On 06/07/16 17:29, Eric Wong wrote:
>>>> I'm not up-to-date with the latest technology, but even 32-bit
>>>> is far beyond the range of human hearing; and last I checked;
>>>> available ADC/DACs can't even make full use of 24-bit (nor
>>>> our ears).
>>> 120 dB SPL (threshold of discomfort) is around 20 billion times louder
>>> then 20 dB SPL (a whisper). That is approximately 24 bits.
>>> However, we can hear down to 10 dB SPL, or lower for young people ...
>>> that is approximately 40 bits of dynamic range.
>> 120 dB is outright painful and damages the ears. 100 dB is already
>> unpleasant.
>>
>> You should also check your calculations. With your limits, the required
>> dynamic range would be 110 dB, which comes out to 20 bits with a bit of
>> margin.
>>
> http://www.nal.gov.au/images/diagram-of-noise.jpg
> Anything above 75 dB SPL has potential to damage your hearing,
> depending on exposure time. The fact that we can hear with clarity
> over such large dynamic range is extraordinary isn't it !
I tend to think it's a natural result of evolution in an environment
where those sound levels occur regularly.
> I think the point I am making is that you can't capture 64 bit words
> of data in audio files with only 32 bit word reads/writes from file. I
> wasn't aware that sox didn't have any methods for 64 bit audio data
> file read and writes. From a pure data perspective, no qualms right ?
Adding support for some file format with 64-bit samples is easy if you
accept truncating the values to 32 bits on read and padding on write.
--
Måns Rullgård
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
next prev parent reply other threads:[~2016-07-06 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 0:02 64bit audio read and write Matt Flax
2016-07-06 7:29 ` Eric Wong
2016-07-06 9:57 ` Matt Flax
2016-07-06 11:41 ` Måns Rullgård
2016-07-06 12:16 ` Matt Flax
2016-07-06 12:22 ` Måns Rullgård [this message]
2016-09-19 21:20 ` 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-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xoa6blzvj.fsf@unicorn.mansr.com \
--to=sox-devel@lists.sourceforge.net \
--cc=flatmax@flatmax.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.
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).