From: Eric Wong <email@example.com>
Subject: Re: 64bit audio read and write
Date: Wed, 6 Jul 2016 07:29:34 +0000 [thread overview]
Message-ID: <20160706072934.GA24278@dcvr.yhbt.net> (raw)
Matt Flax <firstname.lastname@example.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'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
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.
next prev parent reply other threads:[~2016-07-06 7:29 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 [this message]
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
2016-09-19 21:20 ` Jan Stary
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:
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 \
* 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
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).