similar to: Adding a --version option to vorbiscomment

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 all, I just committed some big changes to vcedit (the core of vorbiscomment, and also the core comment rewriting functionality used by a number of other programs (xmms, for instance). It's now able to handle several nasty cases that it couldn't before, but it may have new problems - so, everyone, go and throw nasty or broken input files at it, and see if it breaks. Please. And those

> While you are at it, can you check/fix the following warning > ? > > metadata.cpp:812:98: warning: narrowing conversion of > 'strlen(((const > char*)string))' from 'size_t {aka long unsigned int}' to > 'FLAC__uint32 > {aka unsigned int}' inside { } is ill-formed in C++11 > [-Wnarrowing] > > > Thanks ! Yeah sure! I don't get

Bastiaan Timmer wrote: > Attached is a patch that adds 5 missing Patch applied. Thanks. > Looking at the FLAC__metadata_object_cuesheet_* FLAC__metadata_ > object_picture_* functions, it looks like the corresponding FLAC++ > classes are already complete. Maybe some functions are missing from > CueSheet::Track. If nobody objects, I will take a look later this > week. Thanks.

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

David K. Gasaway wrote: > Daniel Aleksandersen wrote: >> On Monday 17. September 2007 07:47:19 David K. Gasaway wrote: >>> Even today, I use my own "metadata format" -- essentially a superset of >>> vorbis comments. There is one file per release, even with a multi-disc >>> release. As a final part of the ripping process, I apply this metadata

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

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

" Ivo Emanuel Gon?alves " <justivo at gmail.com> wrote: ... > To be fair, only the Vorbis users requested albumart. FLAC users > should in theory be able to use the tag too if they want, but this > wouldn't be something we'd see in other codecs like Speex and Theora. This is a minor point, but FLAC users can already do this using METADATA_BLOCK_PICTURE (which

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

First, the in the links section of www.vorbis.com is a link to http://www.vorbislinks.com/ which no longer a vorbis dedicated site (it's one of those general dns parking/general index). I don't know who's the webmaster, it is implied that's Simon Yorkston, but I'm not sure. Anyway, the real rason of this mail is that I'm ripping my CDs collection, and I'm taking a

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:

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

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

Heya guys, How long until we get a WORKING Vorbis Comment editor? For Windows? -- Robert J. Lynn, Jr. Brainbench Certified Computer Technician, Linux Administrator, and Master Windows 98 User PGP Key ID: 0xCDE22CFB (RSA) rjlynn@suscom.net, rjlynn@crosswinds.net EFNet: Vegeta99 --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

Sorry for spamming but in the haste I forgot the stream_decoder part out. On 26.9.2014 15:47, Janne Hyv?rinen wrote: > On 26.9.2014 15:21, Erik de Castro Lopo wrote: >> Janne Hyv?rinen wrote: >> >>> Patch v2, now handles more malformed cases. Original patch was for a >>> file for which I had a sample from a user but this allows handling some >>> manually

Beside that, multiplexed logical streams suffer from pretty bad software / hardware support, isn't it? It's better to display album art as text if the player doesn't recognize the base64 album art, than being unable to even play the file. ----- Urspr?ngliche Mail ---- Von: Kyungjun Lee <kjoonlee at gmail.com> An: xiphmont at xiph.org CC: vorbis-dev at xiph.org Gesendet: