I've created a list called "sox-commits" to forward the emails to... As
you said, I suspect some people are not interested in seeing those.
Reuben Thomas wrote:
> To help us keep abreast of each others' changes, I've changed the
> CVSROOT/loginfo file in the way recommended by SourceForge to use syncmail
> to send commit messages to sox-devel. I'm not sure if it's preferable to do
> it like this (it's simple) or to have a separate sox-cvs list (for e.g.
> advanced users who want to be on sox-devel but not get all the CVS commits).
> Since I can't create new mailing lists, I thought I'd start with what I
> could do. Opinions welcome.
> By the way, an update on my direction: I'm fairly happy with the build
> system now (you may have noticed I just added libtool support, which will
> make SoX build its libraries better, and hopefully please its packagers).
> I'm now going to concentrate on Lua scripting: my idea is that at the very
> least all non-CPU intensive code ought to be implementable in Lua. This
> means effects like stat and formats like .dat (which are unlikely to be used
> interactively), as well as things like the play script and sox.c. The
> advantage of rewriting this sort of thing in Lua is the usual ease of
> programming of a scripting language, better modularity (because the
> front-end, currently sox.c, won't be able to call arbitrary bits of the
> back-end, but only the official API), and because I've used Lua, which runs
> on any system that SoX runs on, better portability (no more shell needed to
> run play).
> As usual, comments appreciated.
> On the performance-intensive side, I would like to try to make Lua good for
> that too. My idea here is that if I can get within a factor of 2 or so of C
> performance, I'm doing OK: if performance matters beyond that, you can just
> get a faster computer. Or wait 18 months for computer speeds to double. I
> have some tricks up my sleeve (well, actually explained in lua.c) to speed
> things up, and further options include using LuaJIT on platforms that
> support it, or other techiques. In any case, Lua should encourage more
> contributions to SoX, as it'll be very quick to hack up an effect in Lua,
> and most of the time, unnecessary to rewrite it in C.
> The other thing I'd like to investigate is the separation of format and
> effects code into two different libraries: ideally it'd be nice to send the
> format code to an existing library like libsndfile.