similar to: Speex 1.0 RC2 released

Displaying 20 results from an estimated 7000 matches similar to: "Speex 1.0 RC2 released"

2004 Aug 06
2
minor suggestions
I did some modifications to address the problems you have. I think I fixed the alignment problem without the pragma you suggested, but I don't have the setup to test it. It's in CVS, so tell me if there are still some problems left. Jean-Marc <p>Le jeu 30/01/2003 à 18:58, Daniel Vogel a écrit : > I just compiled the current code in CVS with VS.NET on Windows and here are
2004 Aug 06
0
minor suggestions
I just compiled the current code in CVS with VS.NET on Windows and here are some minor annoyances: You might want to put the below code in a central header which is included by every file though NOT by speex.h so including speex.h doesn't mess with my warning levels. #if _MSC_VER #pragma warning(disable : 4244) /* conversion to float, possible loss of data */ #pragma warning(disable : 4305)
2004 Aug 06
1
minor suggestions
> How did you do it without the pragma? I understood that the problem was a mismatch between the the declaration and definition in for some codebooks (exc_*_tables.c). > I saw you added the pragmas to disable the float/double warnings to misc.h > though that header isn't included by the files that generate the warnings. What are the offending files then? BTW, aside from the
2008 Nov 11
1
visual studio 2005 - help getting speex workin'
Hey there, I'm having trouble getting speex working with a project that uses it. For some quick background, the game Quake 3 was GPL'ed a while ago. Some programmers decided to throw it into a public svn and improve on it, called it ioquake3. One of the blokes integrated speex into ioquake3 and it works, but I have troubles getting it to compile/link properly with Visual Studio 2005. I
2004 Aug 06
3
libspeex crash with RC3
I tried to compress 160 samples of random garbage (range 0-500.f) at 4kbps and got a crash in nb_encode -> forced_pitch_quant because start was -858993460 (== ol_pitch). -- Daniel, Epic Games Inc. --- >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@xiph.org'
2004 Aug 06
2
What is the format of the PCM/WAV dataforspeex_encode & speex_decode?
I thought it would be more update/better/faster, any thing wrong? In the future, would you use short, and forget about float? If so, I use 1.1.4, I wouldn't need to change my code in the future, right? You said, it's unstable, yes, I got compiling errors with MsVC6 and MsVC.net And I modified it a bit to get it compiled. Should I post the errors here? <p>-----Original Message-----
2006 Sep 06
1
problem linking new beta version
hello everybody, i've download the new 1.2beta1, and compile it with VC++ 6.0, at this point, all ok. i get the libspeex.lib and when i link it to my project (that was using speex 1.1.12) it reports an error: "unresolved external symbol lpc_window" this symbol is defined in window.c and its referenced in sb_celp.c and nc_celp.c, but im not sure if im doing something wrong or
2004 Aug 06
3
size speex file encoded
Hi, I am working with libspeex api. I would like compare the size of speex file encoded with libspeex and the size of speex file encoded with speexenc. For example, I encode with speexenc (narrowband, quality 1) a wav file of 1.43 MB (17 seconds) output a spx file weight 21KB, for other hand I encode with libspeex the same wav file with same characteristics in arm processor, pocket pc and the
2004 Aug 06
1
Re: speex 1.1.4 compile fails/vq.h parse error
It's not really documented, but when you compile with --enable-sse, you need to add -march=pentium3 to the compile switches. That's actually a gcc requirement. Jean-Marc Le mer 21/01/2004 à 04:22, war a écrit : > gcc-3.2.2 + slack 9 + p4 2.6ghz (has sse/2) > > ./configure --prefix=/app/speex-1.1.4 --enable-shared --enable-sse > --with-ogg-dir=/app/libogg-1.1 >
2004 Aug 06
1
patch for compiling on IRIX
The following patch (based off of the current CVS tree) is necessary to compile Speex on IRIX (or any other system that doesn't include getopt_long in the system libraries). I would suggest further that src/getopt_win.h be renamed to getopt_long.h since it's not just Windows that lacks getopt_long. Michael Index: configure.in
2007 Apr 02
1
Problems with stereo data
Hi all, I have a problem when I am encoding (or decoding) stereo audio. With mono data, things are fine and everything works without any problems. When I try to decode stereo data, all I get is a static sound - similar to that of a radio not tuned to any specific station. I wonder what might be wrong? Below is the code, first, of the encoder and next that of the decoder. Any information or
2004 Aug 06
2
[lists] Speex & Java ...
> > >> You might like to write a JNI Wrapper. > > > That's what I'm doing now to get things rolling but I > was talking about a pure java solution. So is there any such > project underway? I wrote a JNI wrapper for speex a few months ago, it's not finished but it does work and i don't think it would need much work to be update it to speex 1.0 and
2004 Aug 06
1
speex and thread question.
Hy, I'm writing a application using speex. This app have two threads one is encoding the other one decoding using speex. I dont know why but I got segfault on some systems. If I juste take off one of the thread like encoding and lauchin the decoding part in a thread and the application is still segfaulting. But if I just launch the decoding process with out a thread every thing is going
2004 Aug 06
3
Speex 1.1.4 is out
> Is it a problem if all the files are compiled with -march=pentium3 > ? The patch that we sent in already detects in the configure.in script > which system you are on and sets a define correctly, i.e. _USE_SSE. Well, if what you want is auto-detection, turning on -march=pentium3 means that the code will crash on anything lower than a pentium3. Not really useful. Of course,
2004 Aug 06
2
Bitrate in encoder
Hi, I'm using the latest version of libspeex (checked out today) and have some problems with checking the target bitrate in the encoder. Calling: peex_encoder_ctl(globals->enc_state,SPEEX_GET_BITRATE, &bitrate); Seems to set bitrate to 24600 no matter what the qualitysetting is.. The functions used previous to this call is: peex_bits_init(&globals->bits);
2004 Aug 06
4
libspeex/SSE Intrinsics with GCC 3.3.x
When compiling Speex 1.1.4 with GCC 3.3.2, the option -msse must be added to the CFLAGS in libspeex/Makefile. GCC 3.1.1 added a new option "-msse" (see http://gcc.gnu.org/gcc-3.1/changes.html , specifically under "New Targets and Target Specific Improvements") to enable SSE instructions within the compiler's output (for appropriate architectures). Compiling speex on
2007 Nov 28
7
[PATCH] Add Visual Studio 2008 Prject files
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: speex_vs2008.diff Type: application/octet-stream Size: 165590 bytes Desc: speex_vs2008.diff Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj
2004 Aug 06
2
Speex for videoconferencing
Hi all, <p>im new on the list and want to introduce my self. Im a software developer working on engine control software for a german car manufacturer. I want to use speex for a privat videoconferencing project and faces some problems with it. First of all the projects in Visual-C++ doesn't work. I don't mean the path an dependecy problems. That is easy. But there are some errors.
2004 Aug 06
2
LP64 fix
Casting a pointer to an int is a bad idea on 64-bit platforms. --- libspeex/stack_alloc.h.orig Wed Jun 11 17:10:53 2003 +++ libspeex/stack_alloc.h Wed Jun 11 17:11:12 2003 @@ -48,7 +48,7 @@ #else /*Aligns the stack to a 'size' boundary */ -#define ALIGN(stack, size) ((stack) += ((size) - (int)(stack)) & ((size) - 1)) +#define ALIGN(stack, size) ((stack) += ((size) - (long)(stack))
2004 Aug 06
2
Speex beta 3 is out
Hi, I'd like to announce Speex beta 3: This is the third beta for Speex, implementing what should be the last new features before 1.0. These new features are a new "ultra-wideband" mode for encoding at 32 kHz (up to 48 kHz) and an intensity stereo mode. Both of these are implemented to preserve both backward and forward compatibility with other releases. This means that it is now