From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id C06051F5AE for ; Thu, 16 Jul 2020 10:28:19 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com) by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1jw17f-0000YI-RO; Thu, 16 Jul 2020 10:28:15 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-2.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jw17e-0000YA-18 for sox-devel@lists.sourceforge.net; Thu, 16 Jul 2020 10:28:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version :Message-ID:In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=4zzZGmkFNFX7jHrlgEAqa9NXyfJc9D1CQSkiEYSI9NY=; b=c0einm3tMlh760RRmRuHxikfCT kh9o2NiFwH8Q2Wm56Ar+Hr+32V+E783sumdjgv/dYUZRULPaBagVtPHdM+WRNOtVEipX21WYYA7Ag bzTgQM11zQI/ECB0H/5sMAteInjKnCbhtgRinL22dqb6WeXaKLFcjtGH7tWnQ3JuouZ0=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=4zzZGmkFNFX7jHrlgEAqa9NXyfJc9D1CQSkiEYSI9NY=; b=M/O8PVkHiz2/O1juP+uGfwhEaP FNawcAxiLDU3u/GyNfiNRSjuKk9n2I/ccRYN92YlPXl5eApFUzLsEBjQR/91UTey8O9aUILOFCOAI 7XnUrZAfeHhkmKWHIKmPZFRhsijPPkx4+C7HVAzgm5qx5NEAL5KQlNkpncQV8mguBXFg=; Received: from [81.2.72.234] (helo=unicorn.mansr.com) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.2) id 1jw17c-00A6vi-Pd for sox-devel@lists.sourceforge.net; Thu, 16 Jul 2020 10:28:13 +0000 Received: by unicorn.mansr.com (Postfix, from userid 65534) id 3971915361; Thu, 16 Jul 2020 11:27:49 +0100 (BST) Received: from raven.mansr.com (raven.mansr.com [81.2.72.235]) by unicorn.mansr.com (Postfix) with ESMTPS id 9302715360; Thu, 16 Jul 2020 11:27:47 +0100 (BST) Received: by raven.mansr.com (Postfix, from userid 51770) id 8727421A6F3; Thu, 16 Jul 2020 11:27:47 +0100 (BST) From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: manus@riseup.net References: <43c80d1476334f44480175be61a72165@riseup.net> Date: Thu, 16 Jul 2020 11:27:47 +0100 In-Reply-To: <43c80d1476334f44480175be61a72165@riseup.net> (manus@riseup.net's message of "Wed, 15 Jul 2020 08:50:32 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Headers-End: 1jw17c-00A6vi-Pd Subject: Re: RF64 support in Sox X-BeenThere: sox-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: sox-devel@lists.sourceforge.net Cc: sox-devel@lists.sourceforge.net Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: sox-devel-bounces@lists.sourceforge.net manus@riseup.net 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=E5ns Rullg=E5rd _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel