[speex-dev] preliminary Speex support in Sweep
conrad at vergenet.net
Tue Oct 22 16:40:49 PDT 2002
I've fixed the library check, it was a very simple autoconf matter which
for some reason I overlooked.
I guess I can put my last week down to: sweep, speex, sleep -- choose two :)
anyway, that's fixed now for sweep-0.5.9 -- it will build against the stock
speex beta one.
(Details: I wasn't including "-lm -logg" in the other libraries part of
AC_CHECK_LIB; shared libs resolve these automatically on Linux, hence the
shared version worked. Of course exactly the same checks for Vorbis libs
already had "-lm -logg" a few lines above ...)
On Sat, Oct 19, 2002 at 06:00:11PM +1000, Conrad Parker wrote:
> Hi Jean-Marc and others,
> I put Speex support in Sweep (a sound editor) yesterday, and had some
> fun with it :) I'd like to get some feedback before releasing it
> I'm not really used to speech codecs (I work more with music) but I've
> been quite impressed at the file size and quality (especially when you
> hear what I did with some of the sample files ;)
> I didn't have any problems working with the library; as I knew the general
> structure of Ogg, everything else was very well explained in the Speex
> So far there's decoding and encoding, with a GUI for encoding including
> all the options speexenc has:
> (The only thing really missing is comments/metadata, which I need to catch
> up on in other formats too :)
> Here's a source tarball (builds against a *shared* lib of Speex Beta One):
> and this page contains some info on other libraries needed (not many!):
> Now then, three questions:
> * configure.in defines AC_DISABLE_SHARED; for some reason I
> couldn't run AC_CHECK_LIB against the static library, so I
> uncommented that line (built a shared libspeex.so) -- you will
> probably need to do that too to configure sweep with speex
> support. How intentional is this -- do you intend that shared
> libraries not be built (yet)?
> * for decoding a speex file into an editor, would you want
> perceptual enhancement to be turned on by default?
> * is the range for COMPLEXITY 1-10? I assume so because the
> other parameters have this range (and it seems to work :), but
> this was missing from the manual.
> Ok, now the fun stuff. Why Speex support in sweep? sure you can edit files,
> and even though it's bad to transcode between voice formats, you can at
> least use sweep to graphically compare files encoded with speex with
> those encoded in other formats including GSM 6.10, G721/G723 ADPCM and
> 12/16/24 bit DWVW (those from libsndfile), as well as Vorbis and MPEG.
> plus, sweep is just cool fun for playing with audio files. There's now
> a couple of interesting Speex files on sweep's demo page:
> you might recognise the origins of those files :) I hope you find Sweep's
> scrubbing useful for manually analysing files, or at least just for
> having fun with them.
> oh yeah; a related question to those demos:
> * what mime type should speex files have? I'm guessing
> That's enough questions for now :) please let us know if you have any
> troubles building sweep. Once the shared/static library thing is sorted
> out (eg. if someone knows how to check against static libraries) then
> speex support will be in the next release of sweep :)
> --- >8 ----
> List archives: http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to 'speex-dev-request at xiph.org'
> containing only the word 'unsubscribe' in the body. No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'speex-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the Speex-dev