search for: bassrumble

...kbps and it becomes more apparent with lower bitrates. At 64kbps, I assume, everybody should be able to hear it. This is not a stereo related artifact that has been introduced by the lossy channle coupling, because encoding a mono version of the clip doesn't make it go away. I deleted the old bassrumble demo on my university account. The new demo can now be found at ftp://instinct.student.utwente.nl/pub/groups/kolabore/ogg/ - the .WAV clip is smaller and instead of a 350kbps demo it contains one encoded with -b 64 and even a LAME encoded MP3 at the same average bitrate. Check out the .txt for more...

Hi, maybe this is of interest for someone out there. I found that taking the difference between an original sample and its decoded Vorbis counterpart is a cool way to mangle sounds (especially voice samples get a nice weird touch :] ). A side effect is that the result is not only exactly what information the encoder omits, it also contains things that it adds to the sample (artifacts). Leaving

I'm a bass player, I admit it. I came across a number of people talking about bass response with Ogg Vorbis and it piqued my interest, I live for this stuff. I am using the Ogg files to distribute songs as converted right from the 32 bit masters. This is a much different thing than ripping a 16 bit CD audio file that has been mushed and compressed much before it winds up as an Ogg file. When

...- oggdrop couldn't encode this file, it kept crashing. This is the clip that exposes clipping artifacts. udial.wav - this killer clip is almost transparent (there are no horrible clipping artifacts anymore). The only artifact is in the second string of tones - they sound a bit blurry/watery. bassrumble.wav - sounds fine! horn.wav - there's still a small amount of noise/fluttery added. Maybe the bitrate is too low? (59kbps) glitch.wav - high-frequency glitch in the left channel when the cymbals are hit (at 0:03s). You can get this file from here: http://solair.eunet.yu/~aldov/glitch.pac (it...