From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3561 216.34.176.0/20 X-Spam-Status: No, score=-3.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from lists.sourceforge.net (lists.sourceforge.net [216.34.181.88]) (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 D7DC31FF72 for ; Tue, 24 Oct 2017 19:45:18 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=sfs-ml-3.v29.ch3.sourceforge.com) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.89) (envelope-from ) id 1e758X-00038Z-Jp; Tue, 24 Oct 2017 19:45:17 +0000 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1e758W-00037d-8w for sox-users@lists.sourceforge.net; Tue, 24 Oct 2017 19:45:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Message-ID:References:In-Reply-To:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=ZLCv47vzwpguKNZMTDhG4CTH9xA/3id7BMK42v2+2UE=; b=JXxMJbvP+uJ7cAwYVCbzo4xQEcta3WLg6204cOygGzeXX/9Kwk/uZmAJCyO90DdDeNoEmtL/4wVcVLmtyhVXH7zVg0UZTeD7xX7a1K2lxLGzM6WXqMu/UsY7ZDhQ7F1cFMVxMCSz5TBX0y2PsOUdPuyYvyF2f5cMozEMEoMTE6Q=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x; h=Message-ID:References:In-Reply-To:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=ZLCv47vzwpguKNZMTDhG4CTH9xA/3id7BMK42v2+2UE=; b=AjNDvlh2gBAJ9tfZErbiEHBcpu0L24VpW2MvcYFdT/OLt4advSJtP6JHsMBLB+cRq1kT8iycX+R/3fgY5QmbZfpk5322xU0r9/stX/vLz/mVqh01VvzUn3gPZy+texUJcvsl9ATpMS3jhhpOtN6w7fSQvqQ/jbEWkCETBOOO+qY=; X-ACL-Warn: Received: from b-painless.mh.aa.net.uk ([81.187.30.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1e758U-00022m-9A for sox-users@lists.sourceforge.net; Tue, 24 Oct 2017 19:45:16 +0000 Received: from a-webmail.mh.aa.net.uk ([2001:8b0:0:30::75] helo=webmail.aa.net.uk) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.0:ECDHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.89) (envelope-from ) id 1e758J-0000Bs-FP for sox-users@lists.sourceforge.net; Tue, 24 Oct 2017 20:45:04 +0100 Received: from cpc132346-sgyl43-2-0-cust166.know.cable.virginm.net ([82.42.23.167]) by webmail.aa.net.uk with HTTP (HTTP/1.1 POST); Tue, 24 Oct 2017 20:44:55 +0100 MIME-Version: 1.0 Date: Tue, 24 Oct 2017 20:44:55 +0100 From: Jeremy Nicoll - ml sox users To: sox-users@lists.sourceforge.net In-Reply-To: References: Message-ID: <82af7d1a9ad07b0bd46d7d9c99ddcf75@wingsandbeaks.org.uk> X-Sender: jn.ml.sxu.88@wingsandbeaks.org.uk User-Agent: Roundcube Webmail/1.1.5 X-Headers-End: 1e758U-00022m-9A Subject: Re: multitasking X-BeenThere: sox-users@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-users@lists.sourceforge.net Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: sox-users-bounces@lists.sourceforge.net On 2017-10-24 20:00, Glenn English wrote: > I'm writing a wrapper around SoX, and I've come to the point where a > number of it's capabilities are required at the same time (eq, > bandpassing, speech rate change, etc.) and I'm confused about the best > way to get these all done. I can't answer the question, but I think whoever does will need to know more. Are these multiple capabilities needed on different pieces of audio, but all being processed at the same time? - which to me would suggest one sox command per audio stream, and surely they'd be likely to run on different cores Or do you mean that for one audio source a whole sequence of things are to be done to it? - which seems to me to be one sox command with various effects coded one afetr another Or something else? > There's talk of a 'chain' in the dox consisting of a number of args > with ':' between them, but I'm not sure what this means. Does just > asking for a number of actions enable some kind of threading, using > several cores in parallel? And if so, does it sort them so > normalization happens after eq after concatenation, etc.? There two sorts of chain mentioned; one is the "chain of effects" which is (I think) analogous to having a whole series of effects boxes wired up so that sound after it is processed by the first box is cabled to the next box which does something else, then that output is cabled to the next one... Anywhere you see a series of effects each with their parameters specified, is that sort of chain. Effects like normalisation, eq etc happen in the order you specify them, except for the automatic processing implicit in various ways (say) of combining input files. (I think.) The ones with ":" between them confuse me too. Although I can sort of see how the ones in the manual might work, I don't think I'm capable of working out other ways to use ":". -- Jeremy Nicoll - my opinions are my own ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Sox-users mailing list Sox-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-users