search for: adslbqmr

...s, 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? YES, kindly post the errors that you encountered. - Abhishek <p><p><p>---------- Original Message ----------- From: "Kenji Chan" <adslbqmr@tpg.com.au> To: <speex-dev@xiph.org> Sent: Sat, 17 Apr 2004 07:09:47 +1000 Subject: RE: [speex-dev] 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, an...

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-----

I always think short is better over float, because most of the time we don't get float form data, from, e.g microphone / wav files <p>-----Original Message----- From: owner-speex-dev@xiph.org [mailto:owner-speex-dev@xiph.org] On Behalf Of Conrad Parker Sent: Monday, April 26, 2004 12:58 AM To: speex-dev@xiph.org Subject: Re: [speex-dev] speex_encode / speex_encode_int ... already sorry

It's the case now, MS's compilers don't support long long type So in the arch.h file I posted. Since _WIN32_WCE is defined for every Windows CE platform (including PocketPC), we can be sure if the following are defined, then it's ms's eMbedded Visual C++ compiler 1. _WIN32_WCE, meaning on Windows CE platform 2. _MSC_VER, meaning ms's compiler // the code in arch.h

Given ONLY an ogg packet, can one be able to decode the packet to PCM? And how ogg vorbis know the info of it (bitrate..etc) in order to decode it? <p><p>--- >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 'vorbis-dev-request@xiph.org' containing only the word

Can I join many ogg_packet together and decode it to PCM? Or I have to encode each ogg_packet at a time? If each packet is 1024 long, can I join 1.5 of packet (1024+512), and decode that 1024+512 packet, and then decode the 512 left? Or I must decode a whole packet, and can't cut it or decode only some of it (not all) Thank you, <p><p>--- >8 ---- List archives:

I'm looking for detailed reference on every libvorbis function calls, just like MS's MSDN, so I can "read" what a function dose and how to use it or even with some sample of use or recommendation I have seen the document come with ogg vorbis, but it's . not a complete document (some pages are missing.or not clear) It's also hard (or can't find) any tutorial

Ok, I'm using 1.1.4, so I should pass signed short(wav data) directly to speex_encode()? But the samplecode that comes with 1.1.4 shows me to put short in float array, and pass the float array to speex_encode() <p>-----Original Message----- From: owner-speex-dev@xiph.org [mailto:owner-speex-dev@xiph.org] On Behalf Of Jean-Marc Valin Sent: Saturday, April 17, 2004 6:25 AM To: speex

I'm confused about the format of the PCM/WAV data for speex_encode & speex_decode speex_encode(enc_state, input_frame, &bits); In the manual, it says "input_frame is a (float *) pointing to the beginning of a speech frame" (for encode) But I've found that in speexenc.c and testenc.c, short* is used instead of float* So, isn't it signed 16 bit samples(if

I emailed Jean-Marc the arch.h about one week ago, not quite sure whether he actually received that email. Anyway, here I have an improved version of arch.h that I believe that it would be better, to use __int64 only if compiling on eMbedded Visual C++ compiler, so for any other compiler, keep it the same (use long long) ---------------------------------- Chan Kei Yuen (Kenji)