Re: aucat options parsing
On Thu, Mar 21, 2024 at 10:10:03AM +0100, Jan Stary wrote: > On Mar 21 10:07:08, h...@stare.cz wrote: > > This seems strange: > > > > $ aucat -n -d -i input.wav -c -r 8000 -o out.wav > > input.wav: skipped unknown chunk > > input.wav: play, chan 0:3, 48000Hz, s16le, bytes 80..1920080, vol 8388608 > > -r: channel range expected > > > > It is an ommited number in -c 1 of course, > > not a missing sample rate. > > Sorry, my bad; it is a missing channel range of course. > Without using the new -m, it seems that one _must_ > use the old -c syntax of -c lo:hi; in particular, > > -c 1 -o out.wav > > is illegal, even though it is a valid (new) syntax. > If that is the case, shouild the manpage mention that? > '-c 1' is the right syntax for all cases. The old syntax (-c lo:hi) still works only to not break existing scripts until they are updated. It is not documented anymore.
Re: aucat options parsing
On Mar 21 10:07:08, h...@stare.cz wrote: > This seems strange: > > $ aucat -n -d -i input.wav -c -r 8000 -o out.wav > input.wav: skipped unknown chunk > input.wav: play, chan 0:3, 48000Hz, s16le, bytes 80..1920080, vol 8388608 > -r: channel range expected > > It is an ommited number in -c 1 of course, > not a missing sample rate. Sorry, my bad; it is a missing channel range of course. Without using the new -m, it seems that one _must_ use the old -c syntax of -c lo:hi; in particular, -c 1 -o out.wav is illegal, even though it is a valid (new) syntax. If that is the case, shouild the manpage mention that? Jan
aucat options parsing
This seems strange: $ aucat -n -d -i input.wav -c -r 8000 -o out.wav input.wav: skipped unknown chunk input.wav: play, chan 0:3, 48000Hz, s16le, bytes 80..1920080, vol 8388608 -r: channel range expected It is an ommited number in -c 1 of course, not a missing sample rate. Jan
