similar to: Kenneth's commits

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

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

Here is patch with manpages for ogg123(1), mp3tovorbis(1) and vorbize(1). Manpages are in pod format, because it is the most readable man source, and are compiled by pod2man. all and clean for man/ work. Install and uninstall for man/ seem to work. Manpages are GPLed of course. <HR NOSHADE> <UL> <LI>text/plain attachment: manpages.diff </UL> -------------- next part

[I'm still poking around in vorbis-tools. Here's another trivial patch.] In ogg123.c, the function get_stream goes down a linked list looking for the nth stream. Currently it will run off the end of the list and dereference the NULL pointer if the list is smaller than n. Attached is a patch to check for a null list and abort. Would assert() be a better way to do this? -=-=- Stan

------- 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

Here's the error I get when trying to compile: gcc -O20 -ffast-math -D_REENTRANT -D__NO_MATH_INLINES -fsigned-char -I. -I../include -c ogg123.c ogg123.c: In function `main': ogg123.c:260: `AFMT_S16_NE' undeclared (first use this function) ogg123.c:260: (Each undeclared identifier is reported only once ogg123.c:260: for each function it appears in.) make[2]: *** [ogg123.o] Error 1

Tonight's commits so far: I finally wrote up the result of the comment header specification discussion. It's in the doc/ directory now. I plan on doing work in the libvorbis comment handling tonight to bring it up to date and make the interface more useful. gif->png conversion of the images in the docs Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg

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:

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

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

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

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

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

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,

Can anybody tell me where I can find some info on the new books? I noticed there are now A-E. What exactly does this mean? How does it translate to higher and lower sampling frequencies and bit rates? Ideally I'd like something in the 11kHZ, 8bit mono area... I also noticed this struct: /* CD quality stereo, no channel coupling */ vorbis_info info_B={ /* channels, sample rate, upperkbps,

A feature request that sounds reasonable and a bug report. ----- Forwarded message from Frank Klemm <pfk@fuchs.offl.uni-jena.de> ----- Delivery-Date: Sat Jan 6 06:35:21 2001 Date: Sat, 6 Jan 2001 15:26:43 +0100 From: Frank Klemm <pfk@fuchs.offl.uni-jena.de> To: xiphmont@xiph.org Subject: ogg123 X-Mailer: Mutt 1.0.1i For ogg123 I need the following feature: - Decode one .ogg file

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

I finally managed to compile ogg123 under MacOS X, after creating a PB project for it. Rillian, do you want to include the PB project in cvs? (it needs a LOT of polishing, though). ---------- Ogg123 from PACKAGE VERSION by Kenneth Arnold <kcarnold@arnoldnet.net> and others Usage: ogg123 [<options>] <input file> ... -h, --help this help -V, --version display

Merry Christmas, Vorbis folks! Here's bunches of cleanups to ogg123. I haven't changed much in the raw code, mostly a few places with broken implementations. I'm also trying to cleanup some places where we assume too much, because ogg123 might eventually be able to safely run suid (or sgid) (to access the audio devices). I think the next thing I'll attack is the buffering. --