sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Matt Flax <flatmax@flatmax.org>
To: sox-devel@lists.sourceforge.net
Subject: Re: 64bit audio read and write
Date: Wed, 6 Jul 2016 19:57:37 +1000	[thread overview]
Message-ID: <577CD611.80007@flatmax.org> (raw)
In-Reply-To: <20160706072934.GA24278@dcvr.yhbt.net>

On 06/07/16 17:29, Eric Wong wrote:
> Matt Flax <flatmax@flatmax.org> wrote:
>> Hi there,
>>
>> I currently use libsox to load and save audio data. I was wanting to
>> write and read 64bit data, however the generic sox sample type is 32 bit
> Correct, sox does some calculations internally in 64-bit double,
> but data which flows in between the effects is all 32-bit int.
>
>> (from sox.h) :
>> typedef sox_int32_t sox_sample_t;
>>
>> The basic format of the read (and write) functions are :
>> size_t sox_read(
>>       sox_format_t * ft,
>>       sox_sample_t *buf,
>>       size_t len
>>       );
>>
>> Can anyone tell me the basic methodology for reading/writing 64bit audio ?
> It would probably reworking a lot of sox internals and would
> require increased memory bandwidth, hurting performance for
> common <= 32-bit processing.
>
> But, where and how are you working with 64-bit audio
> and what 64-bit audio formats are there?
I think there are 64 bit file formats, aiff-c perhaps ? Also matlab file 
formats should be supporting 64 bits.
Personally, working with filters and various signal processing 
algorithms like that. It is handy being able to save double length 
words, possibly which are generated and synthesised in one way or other ...

>
> 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.

Actually, I am not proposing we change the bit depth of sox in its 
signal processing system, however perhaps we can introduce functions to 
read and write 64 bit audio ?
Something like functions to read64 and write64 perhaps ?

>
> On the other hand, moving to 32-bit float would make sense for
> compatibility with 3rd-party plugins (LADSPA for sure, maybe
> LV2?).  Right now, we're constantly converting between
> float/integer in effects chains which hurts performance.
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel


------------------------------------------------------------------------------
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

  reply	other threads:[~2016-07-06 10:52 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 [this message]
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
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=577CD611.80007@flatmax.org \
    --to=sox-devel@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).