similar to: documentations

Dear Valin, Please, can you explain me the mean of the routines' parameters: 1. void vq_nbest(); 2. static void compute_weighted_codebook(); 3. static inline void target_update(); 4. void split_cb_search_shape_sign(); 5. void split_cb_shape_sign_unquant(); 6. void noise_codebook_quant(); 7. void noise_codebook_unquant(); and what they do briefly??? It's very difficult understand a

Hello! I'm an Italian student in computer engineering (University "Federico II" of Naples) and I have to write my graduation thesis in the field of signal processing. My teacher (Prof. Giovanni Poggi http://www.diet.unina.it/giovanni.poggi/) has published a research about multiple description vector quantizers by means of the self organizing maps, applying his idea to the images and

Hi all, I'm porting the Tremor code to an ARM platform. Unfortunately, we didn't use the low mem branch code for CPU performance consideration, and now I find the memory use in it is huge for the embedded system. After looking into the code, I found the header parse, especially, the codebook unpack part takes a lot of memory. Tremor decodes the codebooks to a cache to store

Hi guys, This is my first post, I?m a brazilian programmer and I think speex is a great project. :) I'm working on a free software project and I was planning to use speex on it. I have used the java speex version in another project and that worked well, and this time I was planning to use a JNI version to get the latest features. ok, lets get to the point. :) I would need to mix some audio

Hi, I am a bit confused on how code-words are derived from the codeword lengths. I will appreciate if someone can point me in the correct direction. I will take the example of an actual codebook that i found in a valid vorbis encoded file as shown below. [SK] +------Codebook [0] -------- [SK] Codebook Dimensions = 1 [SK] Codebook Entries = 8 [SK] Unordered [SK] 1, 6, 3, 7, 2, 5, 4, 7, [SK] NO

heh...:) maybe I?ll just answer "the number is 42". ;) well... some guys did mixing using *G.722 *encoded frames... maybe we could ask them: 8P http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/4054516/4054517/04054870.pdf?isnumber=4054517&prod=CNF&arnumber=4054870&arSt=2045&ared=2048&arAuthor=G.+Agnello%3B+R.+M.+Dansereau and a little off-topic, but fun for

Often it is useful to keep a "codebook" to document the contents of a dataset. (By "dataset" I mean a rectangular structure such as a dataframe.) The codebook has as many rows as the dataset has columns (variables, fields). The columns (fields) of the codebook may include: ? variable name ? type (character, factor, integer, etc) ? variable label

Anexed is my function for reading codebooks and the Vq Table. My problem is: I read a codeBook number of 41, so i called this function above 41 times. The firtst time, the sync patterns (BCV) is alligned correctly, so it reads correctly. the sencond time it is executed, the patter is not there anymore and there are only 8 BCV in my file. function fReadBits1 is the same as the ogg's read bit

Hello kind developers, I am planning on creating a steganographic extension for speex/CELP. Since speex/CELP is lossy, there should be quite many bits that one can use for hiding data. I'm familiar with the principles of CELP (two filter loops, one for pitch, the other for formants, let the raw speech frame run through those filter loops, take residue signal, map it on a codebook entry,

Hi all, I'm in the final stages of putting a new Vorbis RTP draft together, the new sections are below. There are a number of open questions: 1.) At present there is a 16 bit length field for the codebooks. As they are spec'd as being unbound in length, but typically around 15K, are there situations where they may be greater than 64KB? The size limit can be extended to 2MB as there

Hello folks, The codebook infrastructure for Vorbis is now well underway. This is it! The last piece needed for *real* bitstreams. To that end, I have a decent VQ codebook generator running. I was originally using some farily typical merge/split algorithms and then decided that the right way to do this was to model a VQ codebook as an m-dimensional set of bubbles (like a foam). I know there

I'm having trouble decoding the number of codebooks out of an ogg file, and was wondering if anyone here could lend a hand? I read in the sync pattern, and I think the codebook dimensions properly, but when I try and read in the number of codebook entries, I get a number larger than the number of bytes in the file, which I have to assume is wrong :) Anyway this is how I read in the numbers :

Hello, Jean-Marc Valin schrieb: >>I am planning on creating a steganographic extension for speex/CELP. >>Since speex/CELP is lossy, there should be quite many bits that one >>can use for hiding data. > > Quite the opposite. Speex uses very few bits, so every bit you corrupt > is likely to be heard. You would need to use "fractions of bits" at a > time.

hi, basically I am anyway using GMM based parametric VQ for LSF quantization so that is not a problem. Can you plz. tell me how to retrain the pitch codebook and innovation codebook. what are the tools to train the pitch and innovation codebook? Regarding the pitch prediction for high-band, I understand your reason of not using it for high-band. There is one paper, "A 14 kb/s wideband

Hi, I have some questions regarding Speex. please reply as soon as possible. where are the two filter loops applied to the raw signal? where is the residue (innovation) signal calculated? where is the innovation mapped on a codebook entry (key)? which bits of a transmitted frame are the two filters, which are codebook keys? Is the codebook from the beginning on static (so already known by

Hi all, Apologies in advance, this email is quite long. I've prepared an updated Vorbis RTP Internet Draft, which is a continuation of draft-moffitt-vorbis-rtp-00.txt which can be found below. If this new draft gets the ok I'd like to submit this to the AVT WG later this week. There are a number of changes over the original I-D, notably the changing of the M bit function in the RTP

Comments? ---------------------------------------- "Mark Taylor" <mt@sulaco.org> wrote: [...] > This is related to one minor objection I have to vector quantization > based codecs like Vorbis and the MPEG4 VQ codec: they do not compute > the quantization noise during the encoding process. The choice of > codebooks (use a big codebook: low quantization noise, use a

I've been trying to get some data from the National Survey for Family Growth into R - however, the data is in a .dat file and the data I need doesn't have any spaces or commas separating fields - rather you have to look into the codebook and what number of digits along the line the data you need is. The data I want are the following, where 1,12,int means that the data I'm interested

I have a patch for libspeex, which optimises some of the loops in vq_nbest and vq_nbest_sign that speeds up encoding - my results: test file: 10s wav file at 16000 Hz, mono encoding with wideband --quality 3, --comp 3 machine: PIII-900Mhz, 256MB RAM before: 2.78s after: 2.38s I'm still trying to grasp the code (I'm just a coder, no background in sound processing), and just optimised

Hi, Please brace yourselves for some possibly stupid questions. Why are there only 2 codebooks for floors and many more for residue values? What makes the encoding of floor values fundamentally different from encoding residue values? I have a basic understanding of VQ, and looking at the floor decode function, it all makes sense 1) Read the codebook index from the stream 2) Do a