search for: vorbized

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

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

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

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

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

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

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

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

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

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 just commited my modifications: vorbis-tools is back in the main build, but ogg123 is out of the vorbis-tools build. I am investigating the cross-platform libraries suggested. ogg123 silences "Clipping in frame x", can now play multiple files at once, and has a new stream handling format (resolves the get_stream() bug mentioned earlier). Vorbize has options for no comment and

Hello, I have been following Ogg Vorbis for about two months now. I like it. A lot. I can't wait to use it. I want to use it so bad it hurts. The only thing stopping me at this point is the inability to add artist, title, and album information to the file. I consider that a must before I start ripping files into the .ogg format. Does anyone have *any* kind of a timeframe on an encoder (for

Hi, all. I'm new to this list, and I know that my question touches on a FAQ. I'm just hoping to get more information than "it's a priority item, but it's not done yet." (Basically what the FAQ says.) I've been encoding about 20 minutes of mono audio each week to as small a file as I can, so it can be served via html. As long as the result is understandable,

I'm going to gather that no work has been done to make the vorbis stuff work on Alpha, I've got an XL366 on which I will donate an account if anyone would like to attempt to get it working. --- >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 'vorbis-request@xiph.org' containing

I'm going to gather that no work has been done to make the vorbis stuff work on Alpha, I've got an XL366 on which I will donate an account if anyone would like to attempt to get it working. --- >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 'vorbis-request@xiph.org' containing