--- Matt Zimmerman <mdz@debian.org> wrote:> On Tue, Jul 30, 2002 at 09:04:38PM -0500, Brady Patterson wrote: > > > The patch I submitted only reads AIFF files. I'm about to start > the patch to > > write AIFF files. > > > > To do so, we need a command-line option to specify AIFF. My > inclination is to > > add an option: > > > > -ff { raw | wav | aif } > > > > In some sense, "-ff" is silly since it probably stands for "format > format". > > Still, I think it's better than just "-f", since the first "f" > specifies the > > entire format option group. > > > > Does this seem reasonable? > > > > Initially, the default will still always be wav. OSX users are > likely to want > > AIFF as the default, though, so eventually I'll add a configuration > option to > > set the default format for decompression. > > A more flexible approach might be to use libaudiofile or a similar > facility, > so that multiple input formats can be automatically recognized, and > future > formats supported in a generalized way. > > I have meant to write this support for some time, but have not had > the > opportunity. It would also be nice to have a simple command-line > player > using libao (a la ogg123).hmm, where to start... Brady, I would say for now, your proposal is fine. I am going to move flac to getopt soon but you will probably be finished first. in any case both will be done before the next release. this is a good temp solution until... Matt, that would be cool if you wanted to take on the audiofile support. I have actually been waiting to ask you for that, waiting until I got the getopt support done, and the new higher-level encoder layers in libFLAC that will pull in some of the madness from flac in a structured way. the flac code should be in much better shape then for the audiofile rework. right now it's just embarassing. Josh __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com
On Tue, 30 Jul 2002, Josh Coalson wrote: (Matt wrote):> > A more flexible approach might be to use libaudiofile or a similar facility, > > so that multiple input formats can be automatically recognized, and future > > formats supported in a generalized way.Agree completely. I did this because I wanted to get something working with as small a change as possible.> Brady, I would say for now, your proposal is fine. I am going > to move flac to getopt soon... > > Matt, that would be cool if you wanted to take on the audiofile > support. I have actually been waiting to ask you for that, > waiting until I got the getopt support done, and the new > higher-level encoder layers in libFLAC that will pull in some > of the madness from flac in a structured way. the flac code > should be in much better shape then for the audiofile rework.Given all that, there's not much point in me doing this now. Josh, have you started with the getopt work? If not, I can do that, presumably allowing you to switch to the higher-level libFLAC interface quicker. Once all that's done, I'd be willing to do the audiofile work myself or jointly with Matt. -- Brady Patterson (brady@spaceship.com) How come I can't hurt this damn turtle?
--- Brady Patterson <brady@spaceship.com> wrote:> > Brady, I would say for now, your proposal is fine. I am going > > to move flac to getopt soon... > > > > Matt, that would be cool if you wanted to take on the audiofile > > support. I have actually been waiting to ask you for that, > > waiting until I got the getopt support done, and the new > > higher-level encoder layers in libFLAC that will pull in some > > of the madness from flac in a structured way. the flac code > > should be in much better shape then for the audiofile rework. > > Given all that, there's not much point in me doing this now. Josh, > have you > started with the getopt work? If not, I can do that, presumably > allowing you > to switch to the higher-level libFLAC interface quicker. Once all > that's done, > I'd be willing to do the audiofile work myself or jointly with Matt.I'm doing getopt now as part of the flac overhaul. I'd say that if you do the stopgap aiff write support now it can go in the next release, where as the audiofile support will probably take longer. the former I can merge in relatively easy but the latter would be better off starting after the overhaul is done. CVS will likely be broken for the next couple of days as I get the new encoder layers in. I don't like to check in stuff that doesn't compile but logistically right now it's much easier for me to do it in pieces. Josh __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com