unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <>
Subject: Re: RF64 support in Sox
Date: Thu, 16 Jul 2020 11:27:47 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> ('s message of "Wed, 15 Jul 2020 08:50:32 -0700") writes:

> Hi everyone,
> we (my colleagues and I) are in need of some Sox functionality with
> support for RF64 files and are thinking about adding proper (reading and
> writing) support for RF64 files to sox instead of extending our own
> in-house tool. Before diving in head-first, I wanted to ask around if
> there are some reasons for not doing this or pointers on how to do this,
> to make sure our patch will not be rejected.
> It seems to me libsndfile also supports writing RF64 files already?

There is already support for reading RF64 files, or so it seems.
Writing is not implemented, so that would be a welcome patch.
Be warned, the current handling of oversized data is rather broken, so
don't bother trying to preserve any existing behaviour.

Måns Rullgård

SoX-devel mailing list

  parent reply	other threads:[~2020-07-16 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 15:50 RF64 support in Sox manus
2020-07-15 22:01 ` Claude Warren
2020-07-16 10:10   ` Måns Rullgård
2020-07-16 10:12     ` Claude Warren
2020-07-16 10:27 ` Måns Rullgård [this message]
2020-07-16 12:23   ` Måns Rullgård

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:

  List information:

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