From: Christopher Stevens <chris@christopherstevens.cc>
To: sox-users@lists.sourceforge.net
Subject: Re: Enabling LADSPA When Building a SOX Binary
Date: Thu, 06 Jul 2017 01:01:18 +0000 [thread overview]
Message-ID: <CAFHRK0cs+Z2QgjOvFDWk42kxd1oTasFhsrYaA+oBY588=MCq1Q@mail.gmail.com> (raw)
In-Reply-To: <6B62AC12-B32D-4F5F-AAAD-E3DE44B47F57@me.com>
[-- Attachment #1.1: Type: text/plain, Size: 2455 bytes --]
Hello Frank,
Thanks for the great discussion link! I see some new things experiment
with. Absorbing now...
Kind regards,
Chris
On Wed, Jul 5, 2017 at 8:26 AM Frank Williams <francolargo@me.com> wrote:
> Chris, I wonder if this discussion from a while ago might relate usefully
> to your intended uses for LADSPA plugins in SoX...
>
>
> http://sox.10957.n7.nabble.com/implementing-loudspeaker-crossovers-using-Sox-LADSPA-plugins-td5464.html
>
> As for my own use, I did not pursue the discussed application further
> because of the problem of precisely synchronizing each individual stream.
> I may at some point revisit the issues, but not for some months at least.
>
> Frank
>
>
> Frank Williams
> Via iPhone
>
> On Jul 5, 2017, at 7:11 AM, Christopher Stevens <
> chris@christopherstevens.cc> wrote:
>
> I'm still looking into this and haven't given up:
>
> sox -M formant.wav carrier.wav \
> -b 16 result.wav --rate 44100 \
> ladspa vocoder 16 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
>
> "sox FAIL formats: can't open input file `1': No such file or directory"
>
> I'll let you know if I find a solution first. So far it seems that the
> vocoder plugin is unusual in that it takes multiple input files. Most
> ladspa discussion I see out there takes one and outputs one.
>
> I haven't tried the other ladspa plugins yet either within SOX. Maybe I
> should find and test one first there (searching for examples now).
>
> I'm also going to play with the built-in ladspa commands separate with
> some good reading here:
> http://archive.oreilly.com/pub/a/linux/2001/02/02/ladspa.html
>
> From what I can see though, the applyplugin command likes one input as
> well.
>
> Kind regards,
>
> Chris
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
> ------------------------------------------------------------------------------
> 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
>
[-- Attachment #1.2: Type: text/html, Size: 5807 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2017-07-06 1:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 4:07 Enabling LADSPA When Building a SOX Binary Christopher Stevens
2017-07-03 5:31 ` Eric Wong
2017-07-03 11:31 ` Christopher Stevens
2017-07-03 17:16 ` Eric Wong
2017-07-03 19:42 ` Christopher Stevens
2017-07-04 0:44 ` Christopher Stevens
2017-07-05 12:11 ` Christopher Stevens
2017-07-05 14:24 ` Frank Williams
2017-07-06 1:01 ` Christopher Stevens [this message]
2017-07-06 20:02 ` Christopher Stevens
2017-07-10 19:41 ` Eric Wong
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-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFHRK0cs+Z2QgjOvFDWk42kxd1oTasFhsrYaA+oBY588=MCq1Q@mail.gmail.com' \
--to=sox-users@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).