I wrote a little proggy which does something similar to kazaa... except it's not dynamic. You can statically change *all* text in a html page to links to
google/
bablefish/
everything2 etc.
It's as useless as hell, but i'll think of a use for it someday...
later
mike
(and yes, i realise it could probably be done in one line of perl)
There's some confusion about bit rates as expressed in this post. If you *tell* the encoder to work at 128kbps then *no matter what encoder you use* it will take up the same amout of space. ie by telling the compressor what the bit rate is, you are actually *specifying* what the resultant file size is. The line "smaller files than MP3 by half, with the same quality" means that you could encode using MS Audio at 64kbps and get the same quality as an mp3 at 128kbps.
Slashdot Mirror
no further comment.
I wrote a little proggy which does something similar to kazaa... except it's not dynamic. You can statically change *all* text in a html page to links to google/ bablefish/ everything2 etc. It's as useless as hell, but i'll think of a use for it someday... later mike (and yes, i realise it could probably be done in one line of perl)
... a lot of people think that song is called "Go with him".. but it's not. And now for 50000 in a row. (single funniest ep of MWC) mike
What about giving the option for text versions of presentations/speeches? Information density of compressed audio is woeful for speech :)
(Don't ask me who's going to transcribe it though.)
There's some confusion about bit rates as expressed in this post. If you *tell* the encoder to work at 128kbps then *no matter what encoder you use* it will take up the same amout of space. ie by telling the compressor what the bit rate is, you are actually *specifying* what the resultant file size is.
The line "smaller files than MP3 by half, with the same quality" means that you could encode using MS Audio at 64kbps and get the same quality as an mp3 at 128kbps.