diff options
-rwxr-xr-x | soxdial | 11 |
1 files changed, 6 insertions, 5 deletions
@@ -300,7 +300,7 @@ These options affect B<sox>; see the B<sox>(1) man page for details. =head1 NOTES -B<1.> B<soxdial> works by iterating over the words on the command +B<2.> B<soxdial> works by iterating over the words on the command line, and building up an array of B<sox> commands for each dial string or segment of dial tone. At the end, all the B<sox> commands are run and their combined output (as raw samples) is piped to another B<sox> @@ -312,17 +312,17 @@ expected, or at all). Because the final B<sox> command reads only raw audio, it's impossible to change the bitrate or sample size in between dial strings. -B<2.> If anything on the command line starts with B<-> but isn't +B<3.> If anything on the command line starts with B<-> but isn't a recognized option, it's not an error: it gets treated as a dial string. This allows e.g. I<555 -1212> to work correctly, but mistyped options will result in them being dialled as alphabetic characters. This may be a bit surprising the first time it happens. If you use B<-v>, B<--verbose>, you'll get warned about it at least. -B<3.> I haven't been able to test this with a real land-line phone to +B<4.> I haven't been able to test this with a real land-line phone to see whether it will actually dial out. -B<4.> I know nothing about blueboxes other than what I've read on +B<5.> I know nothing about blueboxes other than what I've read on Wikipedia, and there's no way I know of to test whether the bluebox tones are correct (you'd need a time machine). @@ -557,7 +557,8 @@ sub make_sox_cmd { $remix = "remix 1v0 1"; } - # the reverse/silence stuff trims trailing silence. we don't trim leading silence. + # the reverse/silence stuff trims trailing silence. + # we don't trim leading silence. my $cmd = "$SOX -traw -b$bits $encoding -r$rate -c1 - " . "$output $ch $remix reverse silence 1 0 0 reverse"; my $subcmds = join(" ; ", @sox_subcmds); |