Displaying 14 results from an estimated 14 matches for "spx_word64_t".
Did you mean:
spx_word16_t
2005 Jan 10
3
64 bit integer spx_word64_t
hi,
I am currently trying out speex version of 1.1.6 FIXED_POINT.
noticed there's a 64 bit integer being used in the long term prediction.
any chance of using a 32 bit integer without incurring some major side-effects?
cheers,
tk
2005 Jan 11
0
64 bit integer spx_word64_t
hi,
jean-marc: am interested in just integer implementation.
is the 64 bit used more for possibility of large values rather
than accuracy? could give me a rough idea of the
range, typical value and the extremes off-hand? i take it
your workaround involves some complex manipulations
instead of just using the 32bit to represent the more significant
bits of 64-bit integer. if yes, could you
2005 Jan 10
2
64 bit integer spx_word64_t
On Tue, 2005-01-11 at 02:07 -0500, Jean-Marc Valin wrote:
> > noticed there's a 64 bit integer being used in the long term prediction.
> > any chance of using a 32 bit integer without incurring some major side-effects?
>
> A 32-bit integer may overflow (which is why I used a 64-bit int). Of
> course, it's possible to emulate it using 32-bit arithmetic. Otherwise,
>
2004 Aug 06
2
[ANNOUNCE] PocketPC Port for speex-1.1.5 with sample code
Actually, the best thing do to would be to use __int64 *unless* it's not
supported. So there needs to be a configure check...
Jean-Marc
Le mar 01/06/2004 à 14:50, Kenji Chan a écrit :
> 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
2004 Aug 06
0
[ANNOUNCE] PocketPC Port for speex-1.1.5 with sample code
...f FIXED_POINT
typedef signed short spx_word16_t;
typedef signed int spx_word32_t;
/*long long is not recognized by
eMbedded Visual C++ compiler;
so use MS's __int64 instead of long long,
if compiling on that compiler
*/
#if defined(_WIN32_WCE) && defined(_MSC_VER)
typedef __int64 spx_word64_t;
#else
typedef long long spx_word64_t;
#endif
typedef spx_word32_t spx_mem_t;
typedef spx_word16_t spx_coef_t;
typedef spx_word16_t spx_lsp_t;
typedef spx_word32_t spx_sig_t;
#define LPC_SCALING 8192
#define SIG_SCALING 16384
#define LSP_SCALING 8192.
#define GAMMA_SCALING 32768.
#define GAI...
2004 Aug 06
0
[ANNOUNCE] PocketPC Port for speex-1.1.5 with samplecode
...Windows CE platform
2. _MSC_VER, meaning ms's compiler
// the code in arch.h
/*long long is not recognized by
eMbedded Visual C++ compiler;
so use MS's __int64 instead of long long,
if compiling on that compiler
*/
#if defined(_WIN32_WCE) && defined(_MSC_VER)
typedef __int64 spx_word64_t;
#else
typedef long long spx_word64_t;
#endif
<p>------------------------------------
Chan Kei Yuen (Kenji)
<p>> Actually, the best thing do to would be to use __int64
> *unless* it's not supported. So there needs to be a configure check...
>
> Jean-Marc
>...
2005 Aug 19
1
Re: Patch, related to TI DSP C54x C55x C6x builds
...tes. If I
haven't done so after a few weeks, please send it again. I'm in the
process of relocating to Australia, so everything's a bit of a mess
around here. Also, please post the c5X-specific files to the list
(.cmd, .pjt, ...) so they'll be archived. Last thing, I see you defined
spx_word64_t as long long for the C5X, isn't there a way to tell the
compiler that the 40-bit accumulator is fine?
Jean-Marc
Le jeudi 18 ao?t 2005 ? 16:18 -0400, Jim Crichton a ?crit :
> Jean-Marc,
>
> I have attached a small patch with modifications to arch.h, bits.c, and
> misc.c. This c...
2004 Aug 06
2
[ANNOUNCE] PocketPC Port for speex-1.1.5 with sample code
Hi Jean-Marc,
Based on the wonderful Speex project, I've created SpeexOutLoud, essentially a Speex codec port for Windows Mobile 2003 devices.
I've included a sample project intended to show the usage of SpeexOutLoud codec in a Pocket PC application based on .NET Compact Framework.
I'd request you to please go through the attached build, and include it as a contribution to the
2005 Aug 17
2
Updated MIPs and memory requirements for TI c54x or c55DSPs
...so two specific things I would watch. First,
there is at least one CPU-intensive place (inner_prod) where I have to
use many shifts in a loop to prevent overflows, but those could be
replaced by a single shift at the end when using a 40-bit accumulator
(which can also replace the only use I have of spx_word64_t). The second
thing is in the filters (*_mem2() functions). The reference
implementation assumes that writes are as fast as reads. This is often
not true on DSPs (at least on Blackfin), so it is possible to re-write
the algorithm to take that into account. There is an example (in C) for
filter_mem2(...
2005 May 24
2
Speex on TI C6x, Problem with TI C5x Patch
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: maleout12may.wav
Type: audio/wav
Size: 95884 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20050524/57112d0c/maleout12may-0001.bin
2005 Aug 15
2
Updated MIPs and memory requirements for TI c54x or c55 DSPs
Hi,
I can see that there has been some effort to compile the SPEEX codec to
operate on the TI c54x and c55x DSPs and I am wondering if anyone would
be able to update the mailing list with their current MIPs and Memory
resource requirements for their c54x and/or c55x compilation? The only
estimate I was able to find in the mailing list archive was 42MIPs but
I'm not sure if this is an
2005 May 24
0
Speex on TI C6x, Problem with TI C5x Patch
...es
> not support any 64-bit integer types. For the moment I am using
> "double" which maps to a 32-bit floating point on the C54x and C55x.
> The C55x compiler does support "long long".
>
> Question 1: Is there anything wrong with using a 32-bit float for
> spx_word64_t (other than MIPs)? This type is used only in two places
> in ltp.c.
No problem replacing with a float. The reason for the 64 bits is not the
precision but only the range. A 40-bit accumulator would work too.
Eventually, this could probably made to fit in a 32-bit int, but I
haven't done th...
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
...return NULL;
st->stack = ((char*)st) + sizeof(EncState);
#endif
Note that I also moved the "if (!st)" check to before st-stack is set, since
a write to a bad location would occur otherwise.
>> Question 1: Is there anything wrong with using a 32-bit float for
>> spx_word64_t (other than MIPs)? This type is used only in two places
>> in ltp.c.
>
> No problem replacing with a float. The reason for the 64 bits is not the
> precision but only the range. A 40-bit accumulator would work too.
> Eventually, this could probably made to fit in a 32-bit int, bu...
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
...EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
#ifndef ARCH_H
#define ARCH_H
#include "speex/speex_types.h"
#define ABS(x) ((x) < 0 ? (-(x)) : (x))
#ifdef FIXED_POINT
typedef spx_int16_t spx_word16_t;
typedef spx_int32_t spx_word32_t;
#ifdef _MSC_VER
typedef __int64 spx_word64_t;
#else
typedef long long spx_word64_t;
#endif
typedef spx_word32_t spx_mem_t;
typedef spx_word16_t spx_coef_t;
typedef spx_word16_t spx_lsp_t;
typedef spx_word32_t spx_sig_t;
#define LPC_SCALING 8192
#define SIG_SCALING 16384
#define LSP_SCALING 8192.
#define GAMMA_SCALING 32768.
#define GAI...