Re: [Audacity-devel] what's left for 0.98?

[Joshua H. <jo...@de...>]

* Matt Brubeck (mbr...@hm...) wrote:
> On Dec 20, Joshua Haberman wrote:
> 
> > 2. Writing a universal commandline encoder that interfaces with outside
> >    programs through stdout.
> >
> > How should the second one be worked out? It's not clear to me how it
> > would be configured by the user. Would there be just a textbox to fill
> > out? How would the user activate this method of export?
> 
> Here's what I would like:
> 
> In the "lossy compression" preferences, the user can choose
> 
>  1. MP3 (built-in)
>  2. Ogg Vorbis (built-in)
>  3. External program
> 
> If they choose 3, they can then select from a menu of presets, or select
> "custom.." to enter a command line on their own.  We might provide some
> environment variables for optional use in the command line (e.g. bitrate).

I have this feature mostly implemented, but there are a few remaining
issues. I'm wondering if it will be solid enough for 0.98.

I've successfully exported a FLAC file using this method. At the moment,
the CL is hard-coded, but it shouldn't be hard to make it configurable,
though updating the preferences dialog is a pain.

Right now it writes a minimal wav header, then the samples raw. I believe
this means byte-swapping will be required for big-endian machines. What's
the best, most efficient way to do this?

My plan is to have a variable $FILENAME to control where the filename, I
don't think any other variables should be necessary. Anything more
fine-tuned wouldn't be easy to generalize, and it would be simpler
to adjust by adjusting the command line.

Comments?

Also, I should have mentioned this earlier, but I will be out of town
from Dec. 26 to Jan. 3. I should upload something to Debian before I
leave, though I will upload again when I return if I still can. For the
Debian tarball, I'll remove id3lib and xaudio. If 0.98 isn't ready by the
26, I can call it 0.97b, or whatever better name will sort lower than
0.98.

Joshua

-- 
Joshua Haberman  <jo...@ha...>