Hi, Myself being new to SoX and unfamiliar with the code, my advice would be to try all three ways, then run a few tests to find any bad behavior. Trust, but verify. file A = one call with several switches. file B = several calls with one switch. file C = several calls with one switch, piped together. Null test Invert the phase of B, combine with A, listen for problems. Invert the phase of C, combine with A, listen for problems. Invert the phase of C, combine with B, listen for problems. Spectrograph I would also load files A, B and C into spectrograph software to see what information is present at the very bottom bits of the bit depth. Try the conversions without dither to see if the spectrographs show different levels of truncation noise. -James On Sat, Nov 25, 2017 at 1:50 PM, Glenn English wrote: > I'm getting ready to ask sox to do several things: EQ, compression, > normalization, speed change, etc. I see on the web, suggestions of > several different ways to do this: make one call to sox with several > switches, make several calls to sox with one switch, or pipe those > several calls together. > > Which of these works best? Does it matter? Does sox just figure all > this out and fork several times if it needs to? (multi-core CPU and > lots of RAM on Debian Linux, and the file is ~1G FLAC, if any of that > makes any difference) > > -- > Glenn English > > ------------------------------------------------------------ > ------------------ > 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 >