similar to: what script or command makes the codebooks? (fwd)

Hi, I'm trying to build an lsp codebook to learn about the process, and I'm afraid that the vq hints http://www.xiph.org/archives/vorbis-dev/0000.html talk rather about residual training. So I can now produce .vqi files and add to them with lspvqtrain, but can anyone supply hints for the rest of the procedure? vqbuild will only produce a "cloud"-type quantlist, and sequencep

ltconfig placeholder shoud be removed. Makefile.am : some stuff copied from branch_beta3 ogg lib must be added only where necesary. vq subdir Makefile.am'ized, (but installs nothing) made distclean target slightly more clean -- check it by hand first, please --- also you'll want to remove vq/Makefile if the ...am passes inspection ------------------------------------------------- diff

please add the following diffs to the vorbis/vq dir. - include files changed so things actually compile in new scheme - _ogg_...alloc cleanups caught a half-dozen typos or so - minor Makefile touchup. (stuff is still not tested, but this will compile at least) Would someone with cvs write access commit them for me please? Erik diffs: ------------------------ diff -bBu2r vorbis/vq/Makefile

Hi again! I have some other suggestions/modifications. 1. Bitrate scaling by frequency in vorbis_encode_init: bpch=(long)((float)nominal_bitrate/(float)channels*44100.0f/(float)rate); With this modification, if we use -b128 at 22khz files, the OGG file will be 128kbit/s, not 64kbit/s ... 2. Probable quality bug: I tested some floating point constants (recalculated them (see below) and encoded

Hi there, I just built libvorbis from anoncvs and found that a) some files are missing from lib/books when making dist and b) the GNU GPL instead of the LGPL is included in the package (contrary to what the README says). If you reply, please includ me in the Cc: because I'm not on the list. The missing files are: res0_160_1024_1.vqh res0_160_1024_2.vqh res0_160_1024_3.vqh

The VQ codebook generation utilities are more or less ready to go. Minor things are left to do, but those will have to be handled as I to them :-) The next thing to do is complete the interface to get compression modes and codebooks to the library for encoding (minor stuff), and then arrange how exactly the MDCT residue is filtered through the codebooks. VQ codebook util instructions:

Hi, I have a Win32 folder in libvorbis folder in which i have dsw executable file, I have Visual studio 2008 so I ported that into VS2008, then I downloaded ogg lib and included that also. After that _V_SELFTEST has been defined, then its asking the definition of these two header files #include "vorbis/book/lsp20_0.vqh" #include "vorbis/book/res0a_13.vqh" I commented this and

Hi, I have a Win32 folder in libvorbis folder in which i have dsw executable file, I have Visual studio 2008 so I ported that into VS2008, then I downloaded ogg lib and included that also. After that _V_SELFTEST has been defined, then its asking the definition of these two header files #include "vorbis/book/lsp20_0.vqh" #include "vorbis/book/res0a_13.vqh" I commented this and

Hello! 1. You should modify the 'vorbis_ftoi(f)' for the undefinied OS/compiler in the 'os.h' on this way: old: static int vorbis_ftoi(double f){ return (int)(f+.5); } new: #define vorbis_ftoi(f) ((int)(f+.5f)) Because in some cases we don't use this function, and the compiler writes many error messages. 2. Could you write a frequency and bitrate independent

Hi, I've been using the Vorbis codec for a while and recently I got the source code and had a look at the spec (great job on the doc BTW). I don't have any former experience with audio compression, but I do know what a DCT does and I totally grok Huffman coding (so I guess I'm not that much of a newbie, am I?). Anyway I just had some questions about how VQ works on the encoding side.

Hello! First of all a question: When you make the encoder tables (ie: mode_e.h) do you use the mapping0_forward function? Because you made the encoder tables, and after this you did a minor correction in the final beta4 ... (this correction was: additional[0]=fabs(additional[0]*scale); in the mapping0_forward function) (I see this was a bug, and the modification was correct, but this correction