search for: galileog

Hi! I would like to share with you an interesting test result. I re-encoded a song 10 times (the 2. made from the 1., the 3. made from the 2.,... the 10. made from the 9.), with a beta4 (CVS 20010620) and with an RC2 (CVS 20010817) library version, 256 kbit/s mode, channel coupling disabled at RC2. The beta4 is very good at the 10. encoding too, but the RC2 has some interesting quality bugs. So,

...s encoder source. (The new functions are in the first 500 lines of the oggenc.c, some definitions are in the oggenc.h) I hope, you can use it. Here is the full source (same source on 3 locations): http://www.geocities.com/mpxplay/oggenc.zip http://www.tar.hu/mpxplay/oggenc.zip http://www.extra.hu/galileog/oggenc.zip what's new or modified: - wav-header and wav-data-len handling - multichannel encoding - header update (after encoding) with an average bitrate value (into the vi.bitrate_nominal variable) - 64bit floating point precision (maybe you say that it is not important, but I'd li...

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

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

Hello! Some minor bugfixes... source: psy.c function: _vp_psy_init 1. '-' or '+' in this line? maxoc=toOC((n*.5f - .25f)*rate/n)*(1<<(p->shiftoc+1))+.5f; maxoc=toOC((n*.5f + .25f)*rate/n)*(1<<(p->shiftoc+1))+.5f; 2. I know: sizeof(float *) and sizeof(float) are 4 bytes long, but... old lines: p->noisemedian=_ogg_malloc(n*sizeof(float *));

Hi, I encoded some songs into 350 kbit/s with beta2 and beta3 too, and I don't know why, but it seems the b2 sounds better (makes a better quality ogg file)... The b2 contains more the b3 contains less high sounds. And with the b3, the size of file is smaller with 4-5%... Do you know this problem, or do you think so, that the sound quality is good (or better in the b3) ?? Please be carefull

Hello, You know, I always worry about the precision and the float constants... and there is a large lookup table in the floor1.c ... and I figure out a way to keep the code size and speed, but to improve the precision at this lookup table. (the difference is small, but audible) Here is the modifications in the floor1.c: tatic unsigned long FLOOR_fromdB_LOOKUP[256]={

Hello! I would like to send some bugs and bugfix(es): 1. There is an encoding bug in the beta 3 (downloaded exe from the vorbis.com) and in the latest CVS (jan. 10.) too (compiled with MSVC 6.0): If the file contains some non-audible noise at the begin or at the end, the encoder/decoder makes some large clips in the output file, if the bitrate is 350kbit/s . If I use 256kbit/s or

Dear Developer Team (Monty/Michael Smith/and others), It seems you get angry for me, but I don't understand why. I don't want to dispute with you, but maybe I forgot to say some things... Here they are: 1. My program (clone) is not a finalized, and NOT A RELEASED (public) program. This is just a test, I wrote it to myself, to the (sound quality) comparsion of MP3 and OGG. 2.

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