similar to: Changing comment-tags

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)

Ok, so I finally got the id3/mp3 end of things worked out for the next release of QTagger and I'm back to implementing tag reading for Ogg Vorbis. I've got some code that will read tags, but I haven't been able to figure out how to write them. Here's the code that I'm using. It's a fine C/C++ mix. The code will eventually be in a C++ app, so I don't mind

After looking through the documentation of vorbisfile, it appears that all comments are readonly using that api. I checked the code for vorbiscomment and it appears to it needs to rewrite the entire file when editing comments. Does a description or API of in--place editing and updating of comments exist? Thx. -- --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

This patch (along with all the previous patches) gets oggenc and ogg123 working. This does not get vorbiscomment working, although I assume that would be trivial -- just add the getopt stuff to the project just like I did in ogg123. In addition to this patch, as I just mentioned, getopt1.c getopt.h and getopt.c need to be copied from oggenc to ogg123 and added. The host check in

I'm working on a win32 C++/MFC program, and I'm having trouble getting rid of a memory leak when writing vorbis comments. I've cut away everything except reading the file and then writing it out, and I still have a 256 byte mem leak (appended below). The code was modeled after vorbiscomment. It uses all the oggvorbis-win32sdk-1.0 static libs. I tried checking the mailing list

I've attached updated patches (against vorbis-tools 1.3.0b3.5) to support comment padding. No changes to libvorbis are necessary. The padding is added in the same way as oggenc2 (null bytes within the packet, at the end) and shouldn't cause problems with any reasonable decoder or comment editor implementations. Padding is enabled by default, except for small files (less than 30 s for

Hi, Attached are patches for the beta 4 distribution, fixing minor problems in RPM spec files. One question: are there any reasons not to include vorbiscomment in the vorbis-tools binary package? I've added the long-awaited utility program into the revised spec file, but I wonder if it is a wrong change... Regards, -- KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp> diff -ru

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

Hi All, Can I update the header of the already existing Ogg-Vorbis file with the new comments? When we add new entries in the header, will it not overwrite the data? does the vorbis library takes care of this? can someone also please give me the call sequence on how i can do that? Thanks in advance. regards, Pavan. --------------------------------- Enjoy this Diwali

Howdah... I am working on adding configuration and comment editing to the OggVorbis Winamp plugin. However I have currently banged my head against one major problem. How the h... do you update an .ogg with the new comments. Do I use the source in vorbiscomment (which doesn't work with any .ogg I've tested) - or is there a better alternative? A function for simply updating an ogg

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

I've written a simple combined HTTP/MP3/OGG server for streaming audio to clients, which is working well. It parses the tag information contained in MP3 files so that it can display files in a more descriptive fashion than 'filename.mp3', and now I'd like to do the same for OGG files. So that I don't need to impose a dependency I'd like to implement the parsing

Using metaflac (1.0.3) like this: metaflac file.flac --set-vc-field=title=test??????e? The vorbiscomment will not be UTF8-encoded, instead they will be stored directly as ANSI. When trying to add some more comment, it gave the following error: ERROR: writing FLAC file file.flac, error = FLAC__METADATA_CHAIN_STATUS_OK Does that mean that weren't enough room for the comments? But

Hello, I am new to using opus but so far I really am loving it. At 16kbps spoken content sounds fabulous. I am using opusenc on 64-bit linux - mostly with flac input. The one thing I can't figure out how to do is add album art. I tried passing the vorbis way of adding a metadata_block_picture comment field to opusenc but it complained about the length. I can't seem to find any

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

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, I've written some code to validate comments passed to libkate, which happens to use the Vorbis comments format (apart from the framing bit, which I dumped rather early). While coding this, I wondered if I should allow empty tags (eg, '=foo'). I had a look at liboggz and vorbiscomment, and they both allow it (I didn't test vorbiscomment, just looked at the source). However,

Hi, I released Squelch 1.0beta9. It's a multi-platform Ogg Vorbis player, if you haven't heard of it. [1] Find it here: http://www.geoid.clara.net/rik/squelch.html Differences from beta8: * Vorbis comment editor ! [2] * More intelligent re-initialisation of output driver. * Stupid bugs in auto-update of master track list resolved. * Some bugs fixed, some more introduced ;) In theory,

(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

Hi Would you please CC me answers to this, I'm not subscribed to the list... I'm pondering writing a GUI program for editing Ogg file comment fields, but I can't find any functions in the API documentation for saving the comment structure to file. Is there an easy way to do this (except for copying vcedit.c from vorbis-tools as I've seen others do!) Thank you, Martin Sjögren