* Enabling LADSPA When Building a SOX Binary @ 2017-07-03 4:07 Christopher Stevens 2017-07-03 5:31 ` Eric Wong 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-03 4:07 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 2440 bytes --] Hello SOX gurus, I'm attempting to build an Amazon Linux binary of SOX with LADSPA plugin support, starting with helpful instructions found here for the SOX part: http://marcelog.github.io/articles/static_sox_transcoding_lambda_mp3.html I was able to follow the instructions with minor tweaks and also found a great introduction on installing LADSPA here: http://archive.oreilly.com/pub/a/linux/2001/02/02/ladspa.html So far I've made some progress... I think, with this: ==== sudo su wget http://www.ladspa.org/download/ladspa_sdk.tgz tar zxf ladspa_sdk.tgz cd ladspa_sdk/src #update all "-mkdirhier" to "mkdir -p" in makefile, then: make make install export LADSPA_PATH=/usr/lib/ladspa ==== After that, I run the configure file when preparing to build SOX. I'm getting this output in terminal: ==== ... BUILD OPTIONS Debugging build............no Distro name ...............not specified! Dynamic loading support....no Pkg-config location........$(libdir)/pkgconfig Play and rec symlinks......yes Symlinks enabled...........yes OPTIONAL DEVICE DRIVERS ao (Xiph)..................no alsa (Linux)...............no coreaudio (Mac OS X).......no sndio (OpenBSD)............no oss........................yes pulseaudio.................no sunaudio...................no waveaudio (MS-Windows).....no OPTIONAL FILE FORMATS amrnb......................no amrwb......................no flac.......................no gsm........................yes (in-tree) lpc10......................yes (in-tree) mp2/mp3....................no id3tag....................no lame......................no mad.......................no twolame...................no oggvorbis..................no opus.......................no sndfile....................no wavpack....................no OTHER OPTIONS ladspa effects.............no magic support..............no png support................no OpenMP support.............yes, -fopenmp ... ==== Note how ladspa effects is set to "no". I can confirm that there are a few default ones in LADSPA_PATH; sine.so, noise.so, filter.so, etc. Do you have an idea how I can include LADSPA support in my binary? I've never used a related plugin with SOX. If I could get this to work on Amazon Linux, I can create cool vocal effects for my automated-ish music project. If you could help me succeed, I'll respond with a customized, automated thank you song from my project. :D Many thanks in advance! Kind regards, Chris [-- Attachment #1.2: Type: text/html, Size: 3602 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 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 0 siblings, 1 reply; 11+ messages in thread From: Eric Wong @ 2017-07-03 5:31 UTC (permalink / raw) To: sox-users Christopher Stevens <owntheweb@gmail.com> wrote: > Hello SOX gurus, > I'm attempting to build an Amazon Linux binary of SOX with LADSPA plugin Hi Christopher, Not sure what Amazon Linux packages, but it doesn't include a LADSPA package? <snip> > export LADSPA_PATH=/usr/lib/ladspa You only need that at runtime, but I would make sure ladspa.h is locatable to your build. It's usually /usr/include/ladspa.h, or maybe /usr/local/include/ladspa.h. > After that, I run the configure file when preparing to build SOX. I'm > getting this output in terminal: You probably need ltdl, too; since LADSPA depends on dynamic loading. config.log can usually provide clues about what failed during ./configure Thanks for any updates and results you can provide! ------------------------------------------------------------------------------ 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-03 5:31 ` Eric Wong @ 2017-07-03 11:31 ` Christopher Stevens 2017-07-03 17:16 ` Eric Wong 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-03 11:31 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 878 bytes --] Hello Eric, Thank you for the lightning fast response! Regarding Amazon Linux, it's evolved from Red Hat Enterprise Linux (RHEL) and CentOS. While not my personal preference yet, it's required for my AWS Lambda project. Using yum, The following packages were *not *found: yum install ladspa ladspa-devel Thank you for the clarification on LADSPA Path. I'll be sure to set that when running, not worrying about it when building at this stage. You mentioned a need to install ltdl. I was able to install the following, also installing the libtool-ltdl dependency: sudo yum install libtool-ltdl-devel While unable to enable LADSPA yet when building SOX, I was able to locate config.log, posting the full log contents here for further troubleshooting: https://pastebin.com/XykNdexE Thanks again for the excellent support while troubleshooting this. :) Kind regards, Chris [-- Attachment #1.2: Type: text/html, Size: 1252 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-03 11:31 ` Christopher Stevens @ 2017-07-03 17:16 ` Eric Wong 2017-07-03 19:42 ` Christopher Stevens 0 siblings, 1 reply; 11+ messages in thread From: Eric Wong @ 2017-07-03 17:16 UTC (permalink / raw) To: sox-users Christopher Stevens <chris@christopherstevens.cc> wrote: > Hello Eric, > Thank you for the lightning fast response! No problem, caught me at a lucky time :) <snip> OK > While unable to enable LADSPA yet when building SOX, I was able to locate > config.log, posting the full log contents here for further troubleshooting: > > https://pastebin.com/XykNdexE It's probably --disable-shared breaking things, LADSPA relies on dynamic loading, and ltdl use won't be enabled w/o shared library support(*). Generally, I suggest trying default configs as much as possible when troubleshooting. (*) Theoretically, it ought to be possible to build sox as only a static library, but still have the static library enable dynamic loading of LADSPA and such... Build systems are a PITA and maybe it wasn't worth the effort. ------------------------------------------------------------------------------ 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-03 17:16 ` Eric Wong @ 2017-07-03 19:42 ` Christopher Stevens 2017-07-04 0:44 ` Christopher Stevens 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-03 19:42 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 557 bytes --] Aha! Good points indeed. I just had a first step towards success, thanks to your input! When running ./configure *without* "--prefix=/usr/sox-14.4.2 --disable-shared --enable-static" arguments, I'm seeing this: ==== ladspa effects.............yes ==== Yes! :D This also works still: --enable-static --prefix=/usr/sox-14.4.2 I'll now move on to installing, configuring and testing plugins, keeping you posted on the next wall or completion of this task. There are still some uncertainties on how this will work but I'm very close now. Cheers! Chris [-- Attachment #1.2: Type: text/html, Size: 2519 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-03 19:42 ` Christopher Stevens @ 2017-07-04 0:44 ` Christopher Stevens 2017-07-05 12:11 ` Christopher Stevens 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-04 0:44 UTC (permalink / raw) To: Christopher Stevens, sox-users [-- Attachment #1.1: Type: text/plain, Size: 2468 bytes --] Progress, hitting a final wall perhaps: It seems like everything is in order for enabling ladspa. Awesome! The last challenge I'm having is using a choice ladspa plugin to bring pitch to my currently narrative thank you song voices with the vocoder plugin found here: http://www.sirlab.de/linux/download_vocoder_ladspa.html Installation was pretty straightforward: wget http://www.sirlab.de/linux/download/vocoder-ladspa-0.4.tgz tar zxf vocoder-ladspa-0.4.tgz cd vocoder-0.4 #edit INSTALL_PLUGINS_DIR in Makefile to taste, then make make install Eric, It looks like the example I originally found from 2012 was written by you (cool!): https://sourceforge.net/p/sox/patches/92/ When I attempt to run this, I'm thinking some things have changed since then as I see errors (or I'm likely doing something wrong to start): 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 Result: sox FAIL rate: usage: ... Edit (rate to --rate): 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 Result: sox FAIL formats: can't open input file `1': No such file or directory If I run this: analyseplugin vocoder The ports hint to me that I'm using it out of order within SOX perhaps? Plugin Name: "Vocoder" Plugin Label: "vocoder" Plugin Unique ID: 1441 Maker: "Achim Settelmeier (adapted to LADSPA by Josh Green)" Copyright: "None" Must Run Real-Time: No Has activate() Function: Yes Has deactivate() Function: No Has run_adding() Function: No Environment: Normal or Hard Real-Time Ports: "Formant" input, audio "Carrier" input, audio "Output" output, audio "Number of bands" input, control, 1 to 16, integer "Band 1 Level" input, control, 0 to 1 "Band 2 Level" input, control, 0 to 1 "Band 3 Level" input, control, 0 to 1 "Band 4 Level" input, control, 0 to 1 "Band 5 Level" input, control, 0 to 1 "Band 6 Level" input, control, 0 to 1 "Band 7 Level" input, control, 0 to 1 "Band 8 Level" input, control, 0 to 1 "Band 9 Level" input, control, 0 to 1 "Band 10 Level" input, control, 0 to 1 "Band 11 Level" input, control, 0 to 1 "Band 12 Level" input, control, 0 to 1 "Band 13 Level" input, control, 0 to 1 "Band 14 Level" input, control, 0 to 1 "Band 15 Level" input, control, 0 to 1 "Band 16 Level" input, control, 0 to 1 Thanks much for your work on this project. Also, thanks again for taking a look at this thread! Kind regards, Chris [-- Attachment #1.2: Type: text/html, Size: 6719 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-04 0:44 ` Christopher Stevens @ 2017-07-05 12:11 ` Christopher Stevens 2017-07-05 14:24 ` Frank Williams 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-05 12:11 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 841 bytes --] 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 [-- Attachment #1.2: Type: text/html, Size: 2457 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-05 12:11 ` Christopher Stevens @ 2017-07-05 14:24 ` Frank Williams 2017-07-06 1:01 ` Christopher Stevens 0 siblings, 1 reply; 11+ messages in thread From: Frank Williams @ 2017-07-05 14:24 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 1880 bytes --] 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 [-- Attachment #1.2: Type: text/html, Size: 4369 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-05 14:24 ` Frank Williams @ 2017-07-06 1:01 ` Christopher Stevens 2017-07-06 20:02 ` Christopher Stevens 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-06 1:01 UTC (permalink / raw) To: sox-users [-- 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-06 1:01 ` Christopher Stevens @ 2017-07-06 20:02 ` Christopher Stevens 2017-07-10 19:41 ` Eric Wong 0 siblings, 1 reply; 11+ messages in thread From: Christopher Stevens @ 2017-07-06 20:02 UTC (permalink / raw) To: sox-users [-- Attachment #1.1: Type: text/plain, Size: 1681 bytes --] SUCCESS! LADSPA goodness is happening. Of course as creative projects go, I decided not to go with a vocoder... but I didn't give up until I got it to work first! Thank you everyone for the support. Here's the thank you song I promised at the resolution of my challenge. :D With vocoder, blended with voiceover as it was harder to understand vocoded words on their own after several variation trials (good for a future project though): https://s3.amazonaws.com/thank-you-song/vocoder-blended-test.mp3 With voiceover only, I personally like it better for my fun thank you song project: https://s3.amazonaws.com/thank-you-song/voice-over-test.mp3 Steps to make it work: ==== #where my plugins live export LADSPA_PATH=/home/ec2-user/plugins #ensure formant (mono voice) and carrier (mono pitch) audio files are set to the vocoder plugin's requirements sox formant.wav -b 16 formant1b.wav gain -1 rate 44100 dither -s sox carrier.wav -b 16 carrier1b.wav gain -1 rate 44100 dither -s #merge mono formant and carrier into a single audio stereo file left and right channel sox -M formant1b.wav carrier1b.wav formant_carrier.wav #apply ladspa plugin via ladspa utilities directly #!!! I'm stuck on how to make this work as part of sox, this gets the job done directly though applyplugin formant_carrier.wav final.wav vocoder vocoder 16 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 ==== If interested to see what the song mention of Patreon is about (basically a glorified tip jar to support electronic music habits), you're welcome to preview it here, going live later this month: https://www.patreon.com/preview/57d3ca9d09a64a8f97112c18cd914736 Thanks for what you do! Kind regards, Chris [-- Attachment #1.2: Type: text/html, Size: 2974 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Enabling LADSPA When Building a SOX Binary 2017-07-06 20:02 ` Christopher Stevens @ 2017-07-10 19:41 ` Eric Wong 0 siblings, 0 replies; 11+ messages in thread From: Eric Wong @ 2017-07-10 19:41 UTC (permalink / raw) To: sox-users Christopher Stevens <owntheweb@gmail.com> wrote: > SUCCESS! LADSPA goodness is happening. Great to know! > Steps to make it work: > ==== > #where my plugins live > export LADSPA_PATH=/home/ec2-user/plugins > > #ensure formant (mono voice) and carrier (mono pitch) audio files are set > to the vocoder plugin's requirements > sox formant.wav -b 16 formant1b.wav gain -1 rate 44100 dither -s > sox carrier.wav -b 16 carrier1b.wav gain -1 rate 44100 dither -s > > #merge mono formant and carrier into a single audio stereo file left and > right channel > sox -M formant1b.wav carrier1b.wav formant_carrier.wav > > #apply ladspa plugin via ladspa utilities directly > #!!! I'm stuck on how to make this work as part of sox, this gets the job > done directly though > applyplugin formant_carrier.wav final.wav vocoder vocoder 16 1 1 1 1 1 1 1 > 1 1 1 1 1 1 1 1 1 Did you try: sox -M formant1b.wav carrier1b.wav \ -b16 final.wav rate 44100 \ ladspa vocoder 16 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 At least I had that working when I made the following change for 14.4.2: https://bogomips.org/mirrors/sox.git/patch?h=58ab5ac87b86c897d9edd0cf6e8e98c0d6162bfb It's not in older versions, though. ------------------------------------------------------------------------------ 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2017-07-10 19:41 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2017-07-06 20:02 ` Christopher Stevens 2017-07-10 19:41 ` Eric Wong
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).