similar to: VORBISCOMMENT

Here's what we need for a BIG popularity boost: Good interfaces! Yeah yeah, i know, i'll be bitched at on how I should do it on my own, but one thing that always ticked me about MP3 - the lack of tools that do the job without the mess. What we need now is - an ID tag editor. Menu-driven, that means CLI or GUI. We need that, badly. Encoder - GUIs for X and MS Windows. Right now, encoding

Does win32 have pathconf() and _PC_NAME_MAX? I ask for ogg123 -- it uses "NAME_MAX" right now (already been mentioned on this list a few times), which does not exist everywhere. I've proposed changing it to use the pathconf() function, but I don't know if win32 has this or not (I don't have, or want, access to win32 compilers :-). If win32 doesn't have pathconf(), we

Hello All, I have created a Vorbis Comment Editor for the win32 environment. It is completely untested and undoubtedly has bugs. That said, it is fairly stable and functional. It is a simple single dialog based app. I have released it under the GPL and have made code available. It is compiled statically with the latest CVS version of libogg & libvorbis and it uses the vcedit.c routines

Hello All, I have created a Vorbis Comment Editor for the win32 environment. It is completely untested and undoubtedly has bugs. That said, it is fairly stable and functional. It is a simple single dialog based app. I have released it under the GPL and have made code available. It is compiled statically with the latest CVS version of libogg & libvorbis and it uses the vcedit.c routines

Hi Ralph, could you please set up a area at xiph.org, where you mirror some of the test sequences, just to be shure that everybody talks about the same sequence ? The license issues are not too important, I think if we should be allowed to use 'free for non-commercial use' sequences for our tests. Perhaps it's a good idea to seperate things in 'free', 'free for test

Use The Source, vorbis! Do vorbis have multistream capabilities in format? Does it include interleaved data? If so, what docs can i read about it? keep in touch. berk. * mailto:berk@nm.ru * http://berk.nm.ru * ICQ UIN: 49516372 * * The Go! operating system development: http://attend.to/go * --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

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

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:

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

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:

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.

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

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"

Hi! I think it is supposed to save all the comments in UTF-8 encoding. But I think all files I write to my files with 'vorbiscomment -w file.ogg -c tag' are saved in standard ISO-8859-1(5). How can I change this? Thanks for help. Stefan --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, how about adding an option to vorbiscomment that displays it's version? This would make it considerably easier to do version- checking. Right now, I'm looking for a string that is only available in vorbiscomment > RC1 but that's not really the cleanest solution ... - -- - -M - ------- Magnus von Koeller

I have written up a z shell completion function for the Ogg Vorbis metadata editing program, vorbiscomment. It is attached, and available at http://netwood.net/usr/jessw/_vorbiscomment The Z shell is an alternative shell, with a very powerful completion system. I look forward to any suggestions, bug reports, etc. Feel free to include the file in the distribution, or link to it, as you

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