similar to: vorbiscomment

Some of these things may allready be addressed: Comments in oggfiles: (meaning the accutall keyword "comment(s)" With xmms you can edit oggtags, among artist and title you have "comment" * xmms creates comment attributes starting with "=" * freeamp does not seem to understand ogg-"comment" at all. * oggenc seems to like to put the comment as is without

Hi, The following changes allow vorbiscomment to read and edit the tags for the first occuring vorbis stream in a muxed (and chained) Ogg bitstream, while retaining the renormalisation. I've tested it on a number of combinations of muxed and chained streams, using the write comments from file option for vorbiscomment to rewrite the comment header and then cmp for binary differences. Seems

Since vorbiscomment is being resurrected in a new form, can someone please fix the vorbis-tools/vorbiscomment/Makefile.am? There's two things wrong: 1. Using _LDFLAGS doesn't allow the user to specify their own LDFLAGS. _LDADD or _LIBS should be used instead. 2. The order of libraries is wrong such that it won't link properly when compiled statically. Here's a trivial

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,

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

Hi All, The following patch is for the http://easytag.sourceforge.net/ software to add speex support. Since easytag uses vcedit.c & vcedit.h that are directly copied from http://svn.xiph.org/trunk/vorbis-tools/vorbiscomment/ the diff's that I made to add speex support, i thought that the diff I made would very much apply to the vorbiscomment developers. I was personally thing that

Hi All, The following patch is for the http://easytag.sourceforge.net/ software to add speex support. Since easytag uses vcedit.c & vcedit.h that are directly copied from http://svn.xiph.org/trunk/vorbis-tools/vorbiscomment/ the diff's that I made to add speex support, i thought that the diff I made would very much apply to the vorbiscomment developers. I was personally thing that

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

Hi, I guess you already know this, but src/plugin_common/vorbiscomment.h is missing from the 1.0.4beta tarball. The best thing would be to release a new beta ASAP, thanks. -- G?tz Waschk <> master of computer science <> University of Rostock http://wwwtec.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--

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:

I don't agree with the s/Ogg Vorbis/Vorbis/. vorbiscomment does edit Ogg Vorbis files, not Vorbis streams in any other encapsulation. -r On Mon, Nov 19, 2007 at 07:01:43AM -0800, ivo@svn.xiph.org wrote: > Author: ivo > Date: 2007-11-19 07:01:43 -0800 (Mon, 19 Nov 2007) > New Revision: 14188 > > Modified: > trunk/vorbis-tools/vorbiscomment/vorbiscomment.1 > Log:

On Fri, Jul 20, 2001 at 03:13:31PM -0700, Josh Coalson wrote: > --- Matt Zimmerman <mdz@debian.org> wrote: > > Basically, you are allowed to specify object code, whether in shared or > > static libraries, normal object files, libtool libraries, and libtool > > object files. libtool figures out any magic that needs to be done to > > actually link those objects

(w. quotes from the xiphmeet: <http://westfish.xiph.org/~giles/200603_meeting.txt>, I've tried to strip it down to relevant stuff) <xiphmont> "Is there any interest in extending vcedit/libvorbisfile to do basic handling of Vorbis streams from concurrently multiplexed Ogg?" < xiphmont> Yes, but that work was *also* tied to OggFile from way back when, and one

I've been looking at modifying vcedit so it will work on Ogg streams containing primarily Vorbis data (i.e. first page is the Vorbis header, most pages are Vorbis and a few are something else e.g. metadata or lyrics). I've managed to get something that works by: 1. During the header opening in vcedit_open push non-Vorbis pages onto a buffer added to vcedit_state and write them out after

I'm trying to write comment writer thing for zinf, because I love the program, but it doesn't fully support ogg. I've found how to read comments, but can't figure how to write them. There has been some discussion about this previously in the archives, but I couldn't find any specifics, only references to code not posted to the list. The api documentation page is (painfully)

As I understand it, any attribute=value line in a vorbis comment can be arbitrarily long (up to 2^32 -1 bytes). The easytag program allows adding the album cover art and other images into the vorbis comment as ALBUMART=xxxx where xxxx is a base64 encoded data of the image file. This makes for a very long line. If I do this to extract the vorbis comment of a file with an embedded cover art (the

--- vorbiscomment/vorbiscomment.1 | 4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/vorbiscomment/vorbiscomment.1 b/vorbiscomment/vorbiscomment.1 index 0108e78..2bceb83 100644 --- a/vorbiscomment/vorbiscomment.1 +++ b/vorbiscomment/vorbiscomment.1 @@ -39,13 +39,11 @@ Reads, modifies, and appends Ogg Vorbis audio file metadata tags. .IP "-a, --append" Append

Here's a patch that stops the flac binary from writing empty tag fields. At least in Windows world these come to files by accident. CD extraction programs pass all possible metadata entries they allow setting in the UI to flac binary and most of the time most fields are empty when basic info like artist, album, title, track number and release date are the only fields that are set.

I'm writing a couple of reader/writer functions for a music tag class for python that can read and write 'raw' vorbis comments to text files[1]. I want these text files to be basically the same as the output/input comments used by the vorbiscomment program, but while testing out multi line comments I discovered that while vorbiscomment can set them with a -t "tag=value"