Displaying 20 results from an estimated 700 matches similar to: "memory usage"
2005 Feb 19
0
memory usage
Hi Alfred,
First thing I'd like to ask is whether you're trying to achieve
real-time performance, as I find it very unlikely that Speex could run
in real-time on a micro-controller.
Regarding bufSize, no you can't just make it the size you like. Now,
it's possible to decrease the amount of memory allocated if e.g. you
only use complexity 1. You can also assume that the stack is
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 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
>> There is a bit of work remaining to get the memory usage down for a
>> multichannel application. There have been some good posts over the
>> last couple of months about reducing memory usage.
>
> I think 1.1.8 incorporates all memory reductions proposed. Let me know
> otherwise.
For the persistent storage, the only change that I have made is to
MAX_CHARS_PER_FRAME,
2004 Aug 06
2
Port to uClinux
Hi,
I'm trying a quick port of this terrific codec to uClinux, a Linux-derivate
for mmu-less systems. I'm particulary interested in the alloc()'s the
library does, and it's stack usage.
In nb_celp.c I found two lines of code doing memory allocation :
nb_celp.c: st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(float));
nb_celp.c: st =
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
Hi Jean-Marc, Hi Jim,
I have also seen some problems with the 1.1.8 release on the C55x. So far I
have boiled down the issues to the following:
1) We need our own "fixed_xx.h" header file. I don't know why, and haven't
had time to investigate, but there is a definite improvement when I use the
attached fixed_c55x.h file which has turned all the maths into inline
functions.
2005 Apr 20
2
Speex-1.1.7 seems to crash with --enable-sse (on P3/GCC-3.2)..
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<b></b>Hi,<br>
<br>
I also tried to build speex
2005 Jul 18
1
[PATCH] remove unused encoder buf in sb_celp.[hc]
diffed against http://svn.xiph.org/trunk/speex r9583
Index: libspeex/sb_celp.c
===================================================================
--- libspeex/sb_celp.c (revision 9583)
+++ libspeex/sb_celp.c (working copy)
@@ -272,7 +272,6 @@
st->g0_mem=speex_alloc((QMF_ORDER)*sizeof(spx_word32_t));
st->g1_mem=speex_alloc((QMF_ORDER)*sizeof(spx_word32_t));
-
2006 Jan 19
0
Compile error (svn 10743)
Sorry.
First error file is not "modes.c" but "modes_noglobals.c".
________________________________
From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of ¼Õ½Â¿ø
Sent: Friday, January 20, 2006 11:40 AM
To: speex-dev@xiph.org
Subject: [Speex-dev] Compile error (svn 10743)
Hi,
I've received svn 10743 revision.
But there are compile errors at
2007 Mar 14
2
Memory Allocation to St
Can anyone tell me why the size of st is defined as:
st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(float));
Reference: nb_encode_init function.
Specifically, I would like to know why 8000 floats are allocated?
Thanks and regards,
Vinay
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2006 Jan 19
1
Compile error (svn 10743)
Hi,
I've received svn 10743 revision.
But there are compile errors at three files with VS2005.
Please check these reports.
Sohn,
Platform system engineer.
=============================================================================
1. modes.c
- nb_mode_new()
SpeexNBMode * nb_mode;
nb_mode = (SpeexNBMode *) speex_alloc (sizeof (SpeexNBMode));
if (nb_mode == NULL) return NULL;
2004 Aug 06
4
Framesize for UWB vs. WB encoding
Hi there.
I am having a little trouble understanding the frame sizes chosen
by the codec.
testenc_uwb.c from the speex-1.0 source distribution has a framesize
of 640 hardcoded and makes use of this value exclusively.
However, a mode query on the actual codec returns 320 as a framesize
for this mode.
int tmp;
speex_mode_query(&speex_uwb_mode, SPEEX_MODE_FRAME_SIZE, &tmp);
2007 Sep 13
2
innov_save, what is it? why does it hurt me so?
hi,
I am using speex1.2beta2 on a TI 54x on narrow band
I have been trying to get speex to work for a while now, and it's been
a real teeter-totter ride. For a long time I noticed that I will get a
project to work and then without changing any code and programming it to
an eprom/flash the project will not work. It turns out it was a value
called innov_save. I found this bugger by zero
2005 Mar 11
1
DSP c5x
I'm finding it dificult to get the code to fit within c5x dsp, especially
due to the large heap necessary for the huge allocations in
nb_encoder_init and nb_decoder_init.
Are the people that have this running using additonal external ram?
Has anyone experimented with reducing the internal encoder/decoder stack
sizes
for narrow band... is there a practical minimum that is usable?
Also,
2005 Jul 20
1
Speex Windows from 1.1.6 source
Hi All,
I am using Speex for encoding/decoding the audio stream for
my streaming application. I have used almost the same code
In the sampleenc.c and sampledec.c, except that I have used
The buffers from the mic as input for encoder and encoded audio
As input for decoder, instead of files input.
My Problem is the audio played on the receiving side after decoding
Is only a "hush" or it
2005 Mar 09
2
Valin 2.0 released
Hi everyone,
I'm pleased to announce the new and improved Valin 2.0, codename
"Alexandre", released March 7th, featuring:
- 6 lbs (2.7 kg) at birth
- Pretty face
- Built-in crying algorithm
Screenshots are available at http://people.xiph.org/~jm/alexandre/ .
Note that this new release is not open-source and only has two "users".
Both co-authors are fine, but tired at
2007 Aug 29
2
high-pass filter issues
Hi, I am using 1.2beta2 on a C5416 doing narrowband
in the decode function I am having a problem with the execution of my
program vectoring off to random interrupts that are not used. I have
tracked down the error to the highpass function called in nb_decode
-very close to the end of the function-context:
it is called here: ln 1719 for me
if (st->highpass_enabled)
highpass(out,
2005 Feb 28
2
memory usage
hi,
jean-marc: i think we can remove spx_sig_t *orig.
but am not sure about exc2Buf. is it for extension?
rgds,
tk
On Mon, 28 Feb 2005 12:42:38 -0500, Jean-Marc Valin
<Jean-Marc.Valin@usherbrooke.ca> wrote:
> Hi,
>
> I looked at the code I think there are still places where you can reduce
> memory. For example, I think bufSize can be reduced to around 400
> (instead of
2008 Mar 29
0
GCC/ELF Visibility patch
Hi,
I've attached a patch against SVN r14645 which adds GCC visibility
information to all symbols exported from libspeex.so and libspeexdsp.so.
It includes a configure.ac change to test that both the compiler flags and
__attribute__((visibility)) works, and if so will
#define EXPORT __attribute__((visibility("default")))
and if not
#define EXPORT
I've attached a diff output
2006 Nov 15
2
Quick survey for Speex 1.2
> Another issue is the memory allocations distributed so many places that
> it's hard to provide a single memory initial function interface.
>
> In a VoIP case on ARM, the total memory size for speex codec should be
> known at the inital stage since all the memories are allocated
> at the initial stage.
If you want everything in the same big block, all you need to do is
2008 Mar 29
2
GCC/ELF Visibility patch (fwd)
Hi,
I've attached a patch against SVN r14645 which adds GCC visibility information
to all symbols exported from libspeex.so and libspeexdsp.so. It includes a
configure.ac change to test that both the compiler flags and
__attribute__((visibility)) works, and if so will
#define EXPORT __attribute__((visibility("default")))
and if not
#define EXPORT
I've attached a diff output