similar to: [PATCH 1/6] Remove the --quiet (-q) option from vorbiscomment.1 man page.

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on

Hello, I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature). The essence of the tools is that it builds and install everything locally, and, of course, it uses the available mechanisms to specify search paths for both headers and libraries; the tool first builds dependencies abd then the target itself. So, for example, 'configure' for vorbis-tools-1.1.1 is

Hi every body , ( Please forgive my dumb poor english ) I got many tracks in ogg/vorbis format . I would like to make a "preview" of them . I mean : I have a track : foo.ogg ( wich is 3:00 minutes long ) i want to have : preview_foo.ogg ( wich is foo.ogg but from 1:00 -> 1:15 ) I read man oggdec , man ogg123 , man oggenc but i did not see what suits me . I use zsh shell , on a

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

Dear vorbis-dev lurkers, I bring you the first beta release of vorbis-tools 1.3.0. It has quite a few new features and the final version will have even more, so I am sure it is to everyone's benefit that it gets as much tested as possible so we can do a quick release. Here's the changelog so far: * Fixed an error in configure.ac; --with-speex/flac work again (#1319) * Corrected

I think that vorbiscomment should really use -c "this=that" to specify tags on the commandline, consistent with oggenc. That displaces the tag source file, so I'd suggest -f, consistent with at least some other programs (although I can only think of tar, right now). I'd also suggest that it use -o for an output filename rather than splattering the second file on the

Could someone please tell me what I'm doing wrong here? I have some oggs tagged using other applications and ogginfo doesn't give me any warnings when I use UTF-8 in them. I did the following: $ vorbiscomment --raw -a test.ogg -t "test=åäö" $ vorbiscomment --raw -l test.ogg test=åäö $ ogginfo -v test.ogg Processing file "test.ogg"... New logical stream (#1, serial:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, as I said before on this list I use the vorbiscomment utility in my music file management perl script and I've just noticed that it has huge problems with German umlauts. "ö", for example, becomes "ö", which is QUITE annoying. In xmms, the tags are displayed correctly, though. I'm using the newest libraries and

Some detailed feedback that looks useful. ----- Forwarded message from Michael Semon <wayfarer42@postmaster.co.uk> ----- Delivery-Date: Tue Jul 16 05:29:37 2002 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Michael Semon" <wayfarer42@postmaster.co.uk> Subject: CVS: ogg123 rocks! vcut no so much so... To: feedback@vorbis.com Hi! Being impatient for RC4, I downloaded

Hi I've a bug in vorbis-tools's libutf8 - some share/*.[ch] files don't include config.h; as a result, utf8.c:convert_set_charset doesn't try charset = nl_langinfo(CODESET) which would correctly return UTF-8, because HAVE_LANGINFO_CODESET isn't defined (it's defined in config.h, but config.h is not included). So, the bugfix is simple - just include config.h everywhere

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've been working towards a mp3info like tool, OggInfo, which will surplant vorbiscomment in functionality, and also incorportate mp3info like featuers. Looking at existing vorbis api calls, i find: vorbis_comment_add() /* unsupervised string insertion */ vorbis_comment_add_tag() /* formated TAG=text insertion */ vorbis_comment_query() /* scans for matching tag (up to count duplicates) and

As far as I could find, nowhere in the documentation or even source does it actually explain how to use vorbiscomment. Just a simple "vorbiscomment reads TAG=VALUE pairs on separate lines from stdin" would save people a lot of time. Of course, this is still a painful tool to use, and since I had some .ogg's lying around with broken comments (from my first ogg vorbis patch to grip),

Hi, I have made a small patch for enabling repeating in ogg123. It adds the parameter "--repeat n" or "r n" where n indicates how many times it repeats the playlists. Zero in forever. Apply it if you like, I find it very convenient. -- Regards Niels Sandmann Jabber: sandmann@jabber.dk, Email: sandm@nn.dk -------------- next part -------------- Only in ogg123: .deps Only in

Are oggdec and ogg123 supposed to be able to extract or play audio from an Ogg Theora+Vorbis file? OggDec 1.0 and ogg123 from vorbis-tools 1.0.1 don't seem to be able to do so. If the programs are not supposed to do this job now, are any improvements planned so they can do this job in the future? Thanks for info on this.

I bumped the version number of vorbis-tools and am preparing it for an eventual release in a few days. A changelog of what's new may be found at [1]. Meanwhile, what's in SVN is a "Release Candidate" to find out if anything was broken since version 1.1.1. Report any (or lack of) problems you may find, so we'll be able to put out a new version of vorbis-tools. -Ivo [1]