similar to: Low bitrate encoding

Hi, I'd like to contribute to Vorbis and I think this may be of some interest for low bitrate coding. I have been experimenting with low bit-rate coding for the high-band (11 kHz to 22 kHz) and, though I haven't yet started quantizing my coefficients (a gain and an LPC filter), I expect to be able to approximate the whole 11-22 kHz band with around 1000 bits/s per channel (maybe even 500

In case people on the list don't know it, A Vorbis tester (who's email I've lost! If you're on the list, speak up!) is maintaining a vorbis audio quality test page: http://hem.passagen.se/ingets1/vorbis.htm He's doing us the great service of hunting down samples that break Vorbis (so we don't have to :-) In any case, it turns out that the trumpets in the dr4 sample

------- Forwarded Message The following patches should fix vorbis-tools to build on NetBSD. I'm not including the diff to the configure scripts, so you'll need to rerun autoconf in the toplevel and libao directory after applying these patches to the configure.in files. It also appears that vorbis-tools/libao/ao_libs.inc is automatically generated by a configure script but checked into

I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you

Hello, I've been trying to compile some things but have run into some problems. I've have the vorbis directory inside of /usr/src. I have compiled vorbis itself with no problems. I've also copied the results to their respective directories as per the README file. I've also compiled the XMMS plugin with no problem. However when it is installed in the

Howdy.. I've got a couple little patches here. 1. vorbis-tools needs getopt. Since it's already sitting in the source tree for cmdline I set up cmdline to make a getopt.a that gets used for both. Also, since mp3tovorbis is a shell script, it needs to be installed 755 not 711 (unless I'm missing something). 2. I've found that both tru64 and irix 5.3 won't give int64_t

Hi! Dear all I compressed an audiu(wave) with libvorbis1.1.1 and found that the pre-echo was longer than the one which was compressed with MP3 at the same bitrate(128kbps),I am now confused aboout the pre-echo preventing scheme. Can you tell me what method does Ogg Vorbis adopt besides the auto windowsize switch? Looking forward to your letter! Thank you! ??????? Lisa (^_^)

Are there any attempts currently being worked on to make Vorbize Visual C++ compatable? Or for that matter non-GNU compatiable? I guess I never realized that getopt.h was a GNU thing. What would be the suggested course of action to get vorbize to cross compile on VC++ or other non-GNU platforms? If not I can certainly do this because I'd like to be able to run this on Windows but I

I've fixed a heck of a lot of stuff in the time frame of just over ten minutes. And you all care... right. I actually ran Vorbize, and discovered some stupid bugs (e.g., segfault???). Fixed. Both Vorbize and Ogg123 should now speak fluently in Monty's comment-eese. I'll be working on getting both to implement all the comment tags; I'm seriously considering dropping all comment

Hi there. First of all, I'd like to congratulate to developers for making a free specification and LGPLed decoder/encoder. :-). I did some test, ripping 17 tracks of my CD and converting them to both MP3 and OGG format. MP3 encoder/player was Lame 3.70 OGG encoder/player was from a Saturday nightly tgz package. ------------------------------------ MP3: LAME-3.70 mpg123-0.59r-4 MP3: lame -S

Hi there. First of all, I'd like to congratulate to developers for making a free specification and LGPLed decoder/encoder. :-). I did some test, ripping 17 tracks of my CD and converting them to both MP3 and OGG format. MP3 encoder/player was Lame 3.70 OGG encoder/player was from a Saturday nightly tgz package. ------------------------------------ MP3: LAME-3.70 mpg123-0.59r-4 MP3: lame -S

Hi! I want to pipe stdout/stderr from vorbize for wrapper scripts. But as it doesn't send any "\n"s it doesn't work correctly. I solved it by adding if (param.verbose == 1) { fprintf (stderr, "\n"); } into appropriate position in vorbize.c. Could somebody please implement this nicely? Something like "-e" option in cdparanoia. Thnx. Bye, Peter Surda

It looked like ogg123 was expecting an out-of-date set of headers. I've updated the printout section to expect the canonical set from docs/v-comment.html. I also found vorbize's use of "track" for the title tag confusing. The second patch is just a rename in the code and ui. Cheers, -ralph -- giles@ashlu.bc.ca <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment:

I finally got around to getting this to a more-or-less working state. Right now, it does most of what vorbize does, plus support for encoding multiple files (this works, but needs some additions to sanely handle titles, etc. for multiple files). The name is temporary, until I think of something better. http://www.labyrinth.net.au/~msmith/oggenc-0.1.tar.gz Hopefully, it's mostly portable,

I first downloaded Vorbis about a month ago, around the time Rok Papez posted comparisons of Ogg and Lame [*]. Here's my much rougher test on a single file. CPU: AMD K6-233 MP3: LAME 3.70, mp3blaster 2.0b6 Ogg: Vorbize 0.6 (Xiphophorus libVorbis I 20000718), ogg123-0.1 Data set: Ministry, "The Fall" (51,955,724 byte WAV) * * * Ogg Vorbis command line: time vorbize -v -w

Hello, I am author of a Morse code training software written in Perl at http://starling.ws/morse Currently I output to *.wav and, if on Unix, convert to *.ogg. And that's okay for a trainer. But I have desire to upgrade the project to a real-time communication tool...or at least a Morse code audio mail routine. And I should like to avoid *.wav. I'd like some means of writing a pure

hi; i'm a lurker & trying to make sense of the discussion... is there a glossary of terms available somewhere? mdct, wavelets, 4th dimensions & preechoes remind me of my time in the twilight zone;) thanks peter --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

Hi. Since I'm new to this mailing list, I don't know whether this was discussed in this mailing list, or if it is already fixed. Anyway, the problem is that all audio encoders out there add a small amount of silence to the start/end of the encoded file. This is usually a small amount, around 0.03 seconds. Most of the time it goes unnoticed, BUT when you have tracks that flow into one

Hi folks, some notes about goings on. After opportunity to think aloud, I have the pieces of the VQ system more or less in place. I need to finish the codebook generation core (this is not libvorbis code, but an external utility). I then need to write the encode/ decode/packing code that makes use of the codebook. This future code is already specced. Tony: I haven't worked on the xmms