--- Jan Suhr <jan.suhr@usa.net> wrote:> It would be easier if FLAC understand the following command: "flac > *.wav *.flac" or "flac -d *.flac *.wav" > > for now I have to use some shell "tricks". >I assume you're using the DOS shell? because all unix shells I know will expand the globs first so this syntax cannot work anyway. but I know what you're saying. something 'flac -d *.flac' would be useful... I'll keep it in mind. Josh __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Hi, I notice that this still doesn't work: $ shorten -x a.shn - | flac -V - a.flac You have to put the -fw in there: $ shorten -x a.shn - | flac -fw -V - a.flac Could wav format not be the default. Or even better could flac not auto-detact wav input, which is relatively easy? Cheers. Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key
> I notice that this still doesn't work: > > $ shorten -x a.shn - | flac -V - a.flac > > You have to put the -fw in there: > > $ shorten -x a.shn - | flac -fw -V - a.flac > > Could wav format not be the default. Or even better could flac not > auto-detact wav input, which is relatively easy?yeah, it's on my list! (but further down). the detection will probably be pretty rudimentary (like checking for "RIFFWAVE" at the beginning). Josh __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
On Fri, Apr 27, 2001 at 11:31:43AM -0700, Josh Coalson wrote:> --- Jan Suhr <jan.suhr@usa.net> wrote: > > It would be easier if FLAC understand the following command: "flac *.wav > > *.flac" or "flac -d *.flac *.wav" > > > > for now I have to use some shell "tricks". > > > I assume you're using the DOS shell? because all unix shells I know will > expand the globs first so this syntax cannot work anyway. > > but I know what you're saying. something 'flac -d *.flac' would be useful... > I'll keep it in mind.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. -- - mdz
On Sat, Apr 28, 2001 at 05:01:25PM -0400, Matt Zimmerman wrote:> 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.I think the best option is keep flac as is and make some front-end, simple bash script (in future some GUI), which will do this handling wav, cdr, flac, shn in user-customizable way. -- Miroslav Lichvar mirator@upcase.inf.upol.cz
Josh Coalson
2004-Sep-10 16:45 UTC
[Flac-dev] flac command line usage (was: the road to 1.0...)
> > > It would be easier if FLAC understand the following command:"flac *.wav> > > *.flac" or "flac -d *.flac *.wav" > > > > > > for now I have to use some shell "tricks". > > > > > I assume you're using the DOS shell? because all unix shells Iknow will> > expand the globs first so this syntax cannot work anyway. > > > > but I know what you're saying. something 'flac -d *.flac' would beuseful...> > I'll keep it in mind. > > I think the easiest way to make all of this "just work" would be toprovide> 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 arepossible,> 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. Josh __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/