search for: best_ntarget

...cb_search_shape_sign (cb_search.c:414). 409 break; 410 } 411 for (j=0;j<N;j++) 412 { 413 /*previous target (we don't care what happened before*/ 414 for (m=(i+1)*subvect_size;m<nsf;m++) 415 nt[j][m]=ot[best_ntarget[j]][m]; 416 417 /* New code: update the rest of the target only if it's worth it */ 418 for (m=0;m<subvect_size;m++) And the crash is at line 414. Digging through the disassembly, the crash seems to be the ot[best_ntarget[j]] lookup, ie: best_ntarget[j] returns...

...wrote: > That's quite strange. The only thing I can say is that the bug is most > likely *not* around line 414. It's probably some sort of memory > corruption somewhere else (quite possibly outside of Speex). Do you have > any more information? What CPU? What's the value of best_ntarget[j]? Is > SSE enabled? What's the allocation method (VAR_ARRAYS/USE_ALLOCA)? What > compiler. > gcc: Reading specs from c:/MinGW/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=...

That's quite strange. The only thing I can say is that the bug is most likely *not* around line 414. It's probably some sort of memory corruption somewhere else (quite possibly outside of Speex). Do you have any more information? What CPU? What's the value of best_ntarget[j]? Is SSE enabled? What's the allocation method (VAR_ARRAYS/USE_ALLOCA)? What compiler. Jean-Marc Thorvald Natvig a ?crit : > Ok, I got a strange case.. > > I got a bugreport from a user about my application crashing on him. > After a bit of trouble, I got him to report back th...

...asked for testers of this and I volunteered :) So far, my testers seem positive, but I have no idea if that is because I told them to expect better quality or if the quality actually is better. But if you think it's related, I can disable it again. >> As for the CPU and the values of best_ntarget[j], I have no way to find >> out. I almost had to bully the enduser in question just to get the >> offset from the windows crash dialog :( .. But apparantly it crashed at >> that exact spot several times. > > Hmm... Can you tell me what bit-rate/sampling rate you're usi...

...xc[subvect_size*i+j]+=s*0.03125*shape_cb[ind[i]*subvect_size+j]; 2. How does the CB search function split_cb_search_shape_sign work? I know the parameter N defines the number of candidates for each of the nb_subvect CB line numbers which are later on written into the stream. But especially, how the best_ntarget list is being updated, I am a little clueless. Regards, Bj?rn PS: for me personally, I'd like to know how to change the cb id found while keeping the error introduced by this low. -- Many a writer seems to think he is never profound except when he can't understand his own meaning. -...

...xc[subvect_size*i+j]+=s*0.03125*shape_cb[ind[i]*subvect_size+j]; 2. How does the CB search function split_cb_search_shape_sign work? I know the parameter N defines the number of candidates for each of the nb_subvect CB line numbers which are later on written into the stream. But especially, how the best_ntarget list is being updated, I am a little clueless. Regards, Bjvrn PS: for me personally, I'd like to know how to change the cb id found while keeping the error introduced by this low. -- Many a writer seems to think he is never profound except when he can't understand his own meaning. -...

...+=s*0.03125*shape_cb[ind[i]*subvect_size+j]; > 2. How does the CB search function split_cb_search_shape_sign work? I > know the parameter N defines the number of candidates for each of the > nb_subvect CB line numbers which are later on written into the stream. > But especially, how the best_ntarget list is being updated, I am a > little clueless. > > Regards, > > Bjvrn > > > PS: for me personally, I'd like to know how to change the cb id found > while keeping the error introduced by this low. >

...entries and subvect_size samples per entry. > 2. How does the CB search function split_cb_search_shape_sign work? I > know the parameter N defines the number of candidates for each of the > nb_subvect CB line numbers which are later on written into the stream. > But especially, how the best_ntarget list is being updated, I am a > little clueless. Hard to explain simply. It's a fundamental thing in CELP. > PS: for me personally, I'd like to know how to change the cb id found > while keeping the error introduced by this low. That's for steganography? I'd say you just...

...+=s*0.03125*shape_cb[ind[i]*subvect_size+j]; > 2. How does the CB search function split_cb_search_shape_sign work? I > know the parameter N defines the number of candidates for each of the > nb_subvect CB line numbers which are later on written into the stream. > But especially, how the best_ntarget list is being updated, I am a > little clueless. > > Regards, > > Bjvrn > > > PS: for me personally, I'd like to know how to change the cb id found > while keeping the error introduced by this low. >

Hi, Jean-Marc Valin wrote: > Not sure I understand your question. Change the order of what within what? In cb_search, we iterate nb_subvect times over a codebook, finding nb_subvect codebook entries to quantize the excitation signal. After finding these nb_subvect codebook entries, they're written into the stream: /*save indices*/ for (i=0;i<nb_subvect;i++) {