[Flac-dev] flac command line usage (was: the road to 1.0...)

Josh Coalson xflac at yahoo.com
Tue May 1 14:01:04 PDT 2001


> > I think the easiest way to make all of this "just work" would be to
> provide
> > a default output filename for both encoding and decoding, e.g.:
> > 
> > flac file.wav
> > 
> > would produce file.flac, and
> > 
> > flac -d file.flac
> > 
> > would produce file.wav.  That way, flac *.wav and flac -d *.flac
> are
> possible,
> > and their behavior easily understood.
> > 
> 
> OK, I kind of like Matt's usage idea best.  I think there are only
> two minor downsides:
> 
> 1. You won't be able to do basename renaming within the command
> anymore, i.e. 'flac 01.wav songname.flac', you have to do a
> 'flac 01.wav && mv 01.flac songname.flac'
> 
> 2. This one's way out there, but I guess if someone were on DOS then
> .flac will be too long and there's no way to get around that unless
> I add some option to specify a default extension.
> 
> So unless there's a really big objection I think I'll go and make
> the changes so that the output file name is automatically determined
> and you can specify multiple input files.
> 
Now, that I've gone to implement it, there's a problem it creates
with piping, that flac doesn't know what to name an output file
when the input is stdin, and there would be no clean way to tell
to write a decoded file to stdout.  Any suggestions?

Josh


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/




More information about the Flac-dev mailing list