similar to: vorbize and os_type patches + general build issues

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

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

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

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

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

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,

Hi all: OK, I was curious to see if I could hear any of the quality loss when going from MP3 to vorbis (a friend wants to know). I used the following command: mpg123 -s 07-Dont_Let_It_Bring_You_Down.mp3 |oggenc -o down.ogg -m2 -r - The encode worked just fine, but at the end oggenc printed up the following: Done encoding file "down.ogg" File length: 0m 00.0s

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

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

ltconfig placeholder shoud be removed. Makefile.am : some stuff copied from branch_beta3 ogg lib must be added only where necesary. vq subdir Makefile.am'ized, (but installs nothing) made distclean target slightly more clean -- check it by hand first, please --- also you'll want to remove vq/Makefile if the ...am passes inspection ------------------------------------------------- diff

The debian vorbis-tools package is labeled version 1.0beta2-1 - does this mean that better compression for stereo has been implemented? (I forgot what the correct term for this was.) I am waiting with a couple of CD's I would have ripped and made mp3's of (I don't have a multi-cd shuttle in my laptop... ;), so that I can rather make ogg files, but I don't want to make them now and

I'm trying to clean up CVS, getting everything where it should be, because pretty soon we're going to have to build SDK's and whatnot, and I want that to be easy. We're basically going to have 3 libraries: 1) libogg 2) libvorbis 3) libvorbisfile I have separated libogg out from the rest of the code, cleaned it up, got it doing 'make dist' and rpms and imported this into

We've now implemented an OS_type field in a package's DESCRIPTION file, which if set has to match .Platform$OS.type (possible values "unix" and "windows"). CRAN has set up some overrides and added this field to packages known to be Unix-only or Windows-only, but authors should do so for themselves in future. Unsuitable packages will not be offered by