search for: kkyzivat

IIRC, under ARM, I believe I was having issues with --without-libogg. I resorted to just downloading libogg sources, setting up my cross-compilation environment, and cross compiling it per the general build directions (./configure, make, make install), then went back to building speex -- everything worked like a charm for me then. So -- Conrad. *Make sure* that you have libogg cross-compiled and

On 02/04/2008, Alexander Chemeris <Alexander.Chemeris at sipez.com> wrote: > On 4/1/08, Keith Kyzivat <kkyzivat at sipez.com> wrote: > > IIRC, under ARM, I believe I was having issues with --without-libogg. > > I resorted to just downloading libogg sources, setting up my > > cross-compilation environment, and cross compiling it per the general build > > directions (./configure,...

...peexdec.d .... (see eventual error above: "...src/ffmpeg/libavcodec/libavcodec.a(libspeexdec.o): In function `libspeex_decode_close': /home/jsalsman/src/ffmpeg/libavcodec/libspeexdec.c:127: undefined reference to `speex_header_free') On Wed, Mar 11, 2009 at 7:14 PM, Keith Kyzivat <kkyzivat at sipez.com> wrote: > > I'm quite sure you won't find an answer to the first question here, you'll > have to ask in some Adobe-Flash centric forums. > As for the second question, once you have a file with speex audio, you can > use speexdec (included in speex distribu...

Hi, *"That's in general not very reliable. You can get PEAQ to say all sorts of silly things." Can you provide me links for any more effective tools other than PEAQ? Which is more reliable for Speex resampler? * *"strongly suspect that it's just not compensating for the delay introduced by the resampler. Because higher quality means higher delay, you'd find that PEAQ

...r above: > "...src/ffmpeg/libavcodec/libavcodec.a(libspeexdec.o): In function > `libspeex_decode_close': > /home/jsalsman/src/ffmpeg/libavcodec/libspeexdec.c:127: undefined > reference to `speex_header_free') > > > On Wed, Mar 11, 2009 at 7:14 PM, Keith Kyzivat <kkyzivat at sipez.com> wrote: >> >> I'm quite sure you won't find an answer to the first question here, you'll >> have to ask in some Adobe-Flash centric forums. >> As for the second question, once you have a file with speex audio, you can >> use speexdec (includ...

----- Original Message ----- From: "Alexander Chemeris" <Alexander.Chemeris at sipez.com> To: "Vincent Burel" <vincent.burel at vb-audio.com> Cc: "Conrad Parker" <conrad at metadecks.org>; <speex-dev at xiph.org>; "Jean-Marc Valin" <jean-marc.valin at usherbrooke.ca> Sent: Thursday, November 13, 2008 11:31 PM Subject: Re:

Pintu -- Speex is an audio codec that can encode and decode audio for transmission over network (or for storage). Specifically, it's called speex because it is tailored to work well at encoding speech at small bitrates. Speex does not do speech recognition or text to speech. You may wish to look at CMU's speech page: http://www.speech.cs.cmu.edu/(look at Sphynx). And I'll tell you -

The VS2005 project files are known to not be up-to-date, so I can understand that you'd need to fix some things. Can you verify with an import of the VS2003 project files, that there is no need for any fixes, and just works after importing? Managing multiple project files should be minimized if at all possible. If a straight import of vs2003 project files can be done without any changes

Something to look into perhaps is Trolltech's 'qmake' tool. It fills the role of something like autotools or now defunct imake. As far as I understand, you can indeed use it for projects that don't do anything with the Qt libraries. Now, it may not have the support for multiple targets that it sounds like are needed for speex, and I know it doesn't have as comprehensive of

On 11/29/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > qmake is just insanely limited in terms of the structure of your code > (can't have an executable if you have a library, ...). On top of that, > I've had way too many cases where it just "forgot" to recompile files > when a header file changed (causing strange segfaults) that I'm never

If you can split your .dcr files into the respective .wav files, you can process each one of those with the 'speexenc' command line encoder app included with the speex codec sources. Just configure, build, and go. speexenc should be self-explanatory -- run without args, and it will provide the usual cmd line opts help that *nix apps generally provide. On Dec 11, 2007 6:26 PM, Michael

This is best answered by the jspeex folks, as it is the interfacing code that you are having problems with. That being said, it looks like, just as it says, you have asked for a conversion it cannot do -- you want it to convert PCM data to speex data at 44.1kHz sample rate -- speex only supports 8kHz in standard operation. It can also support 16kHz (wb) and 32kHz (uwb), but nothing outside of

On 2/18/08, Premkiran Mannava <loverays@gmail.com> wrote: > > Hi, > > *"That's in general not very reliable. You can get PEAQ to say all sorts > of silly things." > > Can you provide me links for any more effective tools other than PEAQ? > Which is more reliable for Speex resampler?* I can already tell you what Jean-Marc will say -- use your ears :)

On Fri, Apr 11, 2008 at 6:53 PM, Joshua Gargus <schwa at fastmail.us> wrote: > Fantastic! Thanks Tom. > > (if only it was possible to change the VBR target on the fly for the > H264 codec we've licensed :-) ) Theora might be able to do that. Some other folks more closely tied with Xiph probably can comment more on that issue. -- Keith Kyzivat SIPez LLC. SIP VoIP, IM

On Thu, Oct 2, 2008 at 12:30 AM, Erik de Castro Lopo <mle+la at mega-nerd.com<mle%2Bla at mega-nerd.com> > wrote: > Keith Kyzivat wrote: > > > And Alex has told me that visual studio-built projects cannot link with > > mingw-win32-gcc produced DLLs... > > This is only true when the DLL being called exports C++ name mangled > symbols. Is there a way to get

On Fri, Nov 14, 2008 at 3:57 AM, Vincent Burel <vincent.burel at vb-audio.com>wrote: > > Speech compression algorithms always are tunned to particular freq, > > else they would take tons of time. That's because they use knowledge > > that speech pitch (and other params) lies in well specified regions. > > Thus if you feed algorithm with wrong freq, you'll

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

The short: Linking to libspeex.a when generating a .so using libtool results in a non-portability warning. This is due to PIC code and non-PIC code intermingling. How can I go about fixing this whilst still using an installed libspeex present on the user's system? The long: I am using autoconf + libtool to generate a codec plugin for speex (sipXmediaLib), and I'm trying to eliminate

On Thu, Oct 2, 2008 at 12:07 AM, Jean-Marc Valin < jean-marc.valin at usherbrooke.ca> wrote: > Tom Grandgent a ?crit : > > If you remove the project files, I doubt it's going to make things easier > > for anyone. You'll probably just increase the number of questions as > > people struggle to compile using less common and less user-friendly > > methods,