Displaying 20 results from an estimated 300 matches similar to: "A question about speex_bits_write function"
2006 Dec 11
0
A question about speex_bits_write function
Thanks a lot for your explanations. Is it right I understand? if I've set
SPEEX_SET_BITRATE to 16000(bps) this means that output is 16000/8=2000 bytes
and I should set MAX_FRAME_BYTES and the length of cbits to 2000. Is it
right? Maybe it is simple question but your answer is important for me,
actually thanks a lot for your helps.
Yasemin
The last argument should simply be the size of your
2009 Oct 29
1
speex_bits_write_whole_bytes problem
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tmezo.vcf
Type: text/x-vcard
Size: 345 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20091029/e587399d/attachment.vcf
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
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
2010 Jul 20
1
BYTES_PER_CHAR
Hello,
I'm porting CELT 0.7.1 to an embedded platform and unfortunately (at least
for me) CHAR is defined as 16 bits. I now got the vocoder compiling but
when i compare the encoded output with a windows build, they don't match.
Among the other problems i think that the char definition is one of the
biggest players. I've seen in arch.h the following definitions:
/* 2 on TI C5x DSP */
2004 Sep 16
3
speex on TI C5x fixed-point DSP
Greetings,
I've just started porting speex to a TI C5509 DSP. It doesn't look like
it's going to be too painful, but there are a couple of quirks about the
C5x.
1) chars are 16 bits because memory addresses are for 16bit words
2) ints and short are also 16 bits (so sizeof(char) = sizeof(short) =
sizeof(int) = 1)
3) the c5x is essentially big endian
My plan is to change int and
2006 Aug 01
2
bits.c problem
I'm trying to use speex on OMAP's DSP using dsp gateway, and have some
questions. The code almost works (within few next days I'll post a some kind
tutorial and patches), but it seems to be a little bug in bits.c. The code
looks like this
void speex_bits_read_from(SpeexBits *bits, char *chars, int len)
{
////////////////// bla-bla-bla ///////////////////
for (i=0;i<len;i++)
2004 Aug 06
2
SPEEX_SET_USER_HANDLER once again
Hi,
Sorry! Marc Gimpel. I wrote it in a false thread before. It was my
first time. :-)
I have to write a small programm which should be able to record speeches
and in addition synchronize the recorded speeches with measuring data.
My idea is to record the speech in the normal way with speex and without
ogg. If a sync message was received, i write a custom in-band messages
using mode 13
2004 Sep 16
0
speex on TI C5x fixed-point DSP
Hi Jamey,
Really cool to see Speex being ported to the C55xx and I'd be glad to
integrate the changes required in Speex (and the style's fine with me).
Here are a couple comments on the patch you sent (I looked at it, but
haven't compiled).
1) The changes you made to the pack un unpack functions would only work
if the 16-bit chars are "big endian" (relative to the two bytes
2011 Jul 26
3
More frames in one packet
After searching the mailing list archive (I forgot to do that before posting, sorry!) I found the solutions:
1) The documentation has a mistake: The bit terminator is NOT set automatically! (I'm using the latest speex version!) It has to be set manually using speex_bits_insert_terminator(&bits);
2) speex_decoder_int() has to be called as long, as it returns -1. After that, all frames
2011 Dec 22
2
Decoding only a certain frame results in different values than when decoding the entire file
To make it complete, here is the code that I am using to encode a large
file:
int __stdcall SpxEncode(unsigned char* inBuf, unsigned char* outBuf,
unsigned int inlen)
{
//char *testFile;
//FILE *ftest;
//testFile = "test";
//ftest = fopen(testFile, "wb");
//fwrite(inBuf,1,inlen,ftest);
//take every 320 bytes
//copy every short to float
2013 May 09
1
Moving from Speex to Opus (question 2)
Hello!
I was using Speex all the time, and I am now moving to Opus.
I had encapsulated the decoder a bit, I had the following cpp file:
#include "StdAfx.h"
#include "spxcodec.h"
#define MAX_FRAME_SIZE 2000
#define MAX_FRAME_BYTES 2000
CSpxCodec::CSpxCodec() : enh(1), rate(8000)
{
}
CSpxCodec::~CSpxCodec()
{
}
void CSpxCodec::Init()
{
speex_bits_init(&bits);
2004 Aug 06
2
speed and memory
hello,
i switched to use the encoder.processData() and
encoder.getProcessedData() of jspeex. however it looks to me like a
memory leak ... memory usage is increasing very fast and there is no
visible stop ... after about five minutes java.lang.OutOfMemory occurs.
I think it must be the jspeex component, because before i added jspeex
to my app usage was constant at about 5mb.
is it possible
2006 Dec 09
1
one more question about speex_bits_insert_terminator and speex_bits_write
Hi everybody,
I have been examining on how I can use speex completely so I have one more
question. I looked at examples and source code and it goes on.
speex_bits_insert_terminator is called in speex_bits_write function. Shall I
call this method one more time anywhere? Because in speexenc project,
firstly speex_bits_insert_terminator is called then speex_bits_write is
called when we assume that
2004 Aug 06
2
bug found in speex_bits_read_whole_bytes
Hello there,
I thought I would contribute to this wonderful project
but noting a simple but problematic bug in
speex_bits_read_whole_bytes().
SITUATION:
I have a large stream of frames with NO breaks or
length indicators inbetween each frame. For this
reason, I call speex_bits_read_whole_bytes() and fill
it to MAXIMUM in a loop while calling speex_decode()
until there are no more bytes to read.
2011 Dec 21
3
Decoding only a certain frame results in different values than when decoding the entire file
Sorry, it seems I have only replied to Lakhdar, not to the newsgroup.
Below is my reply to Lakhdar, and I would like to make it more clear
now, using some pseudo values for simplicity:
I read bytes 1 to 124 from my encoded spx file.
I decode themt and get the values:
---Frame 1----
-293
-8234
2134
17
---Frame 2----
-9323
-732
189
2329
Both frames are just perfect as I need them.
But now when I
2013 May 22
1
column width in .dbf files using write.dbf ... to be continued
Hello Arnaud,
You posted this question a long long time ago, however I found your answer so I decided to post it anyway in case somebody else have the same problem as you and me.
You were actually very close in finding your solution. The function DoWritedbf is an internal function from the foreign package. To access it outside of the package just do:
foreign:::DoWritedbf
so in your line:
2006 Dec 29
0
using speex in C#
Hi SAITAMA Taro,
I have been using speex-1.2beta1 dll in our voice application written with
C#. In order to use Speex correctly firstly I advice to you examination
speexenc and speexdec projects.
I have used unsafe code and fixed statements in C#. I have added following
method to library and I used that instead of speex_encoder_init simply.
void *speex_encoder_init_new(int modeID)
{
const
2004 Aug 06
0
SPEEX_SET_USER_HANDLER once again
Hi,
I think what happened is that you did not write the "message" length.
With user-callbacks, you also need to say how large the message. The
size is in bytes and encoded in 4 bits.
Besides, you're probably the first one to use user-callbacks. BTW, why
didn't you want to use Ogg. It's much simpler to use and overhead can be
made minimal anyway.
Jean-Marc
Le ven
2006 Dec 09
1
New function for manipulating SpeexBits
It would be nice to have the following function added to the speex
bits...
void speex_bits_read_from_buffer(
SpeexBits * const bits,
void * const buff,
const int buf_size)
{
bits->bytes = (char*)buff;
bits->buf_size = buf_size;
bits->nbBits = buf_size << 3;
bits->bytePtr = 0;
bits->bitPtr = 0;
bits->owner = 0;