From: Claude Warren <claude@xenei.com>
To: sox-devel@lists.sourceforge.net
Subject: Re: RF64 support in Sox
Date: Wed, 15 Jul 2020 23:01:32 +0100 [thread overview]
Message-ID: <CAOQrJk6jLKSqy9Ubm5a74S6fvG2=q21VvvAMoK_csYRmP12ikg@mail.gmail.com> (raw)
In-Reply-To: <43c80d1476334f44480175be61a72165@riseup.net>
[-- Attachment #1.1: Type: text/plain, Size: 1496 bytes --]
I don't have any suggestions for how to get a patch accepted, but I will
say that I have written a VU meter effect (because I needed to write the
meter to a custom device) and found that the system is not that hard to
work with. I believe that you will be well served to do your extension
here rather than in an in house tool.
All that being said, the traffic on this list is so low as to be dead. I
am not certain that anyone is still doing official work, though I suspect
that someone is because I saw a release in the recent past.
Good luck, and let me know if I can be of assistance,
Claude
On Wed, Jul 15, 2020 at 4:50 PM <manus@riseup.net> wrote:
> 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?
>
> Thank you!
>
> Best,
> Manus
>
>
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
[-- Attachment #1.2: Type: text/html, Size: 2474 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next prev parent reply other threads:[~2020-07-15 22:56 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 [this message]
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
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:
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='CAOQrJk6jLKSqy9Ubm5a74S6fvG2=q21VvvAMoK_csYRmP12ikg@mail.gmail.com' \
--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).