search for: vorbiscomment

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/vorbi...

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

...="yes") -AC_ARG_ENABLE(ogginfo,[ --disable-ogginfo Skip building ogginfo], build_ogginfo="$enableval", build_ogginfo="yes") -AC_ARG_ENABLE(vcut, [ --disable-vcut Skip building vcut], build_vcut="$enableval", build_vcut="yes") -AC_ARG_ENABLE(vorbiscomment, [ --disable-vorbiscomment Skip building vorbiscomment], build_vorbiscomment="$enableval", build_vorbiscomment="yes") - +AC_ARG_ENABLE(ogg123, [ --disable-ogg123 Skip building ogg123], build_ogg123="$enableval", build_ogg123="yes" OGG123=ogg123) +AC_ARG...

...ows 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 image is over 60K bytes in size): $ vorbiscomment -l file.ogg > commentfile It dumps the contents correctly. However, if I try writing that result back to the file: $ vorbiscomment -w -c commentfile file.ogg This fails with the error: bad comment: "xxxx" bad comment: "xxxx" bad comment: "xxxx" bad comment: "...

-----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 <magnus@vonk...

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

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

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: 0e0c0b11): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis...

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 shouldn't i...

...loudness at > content provider side, but our application takes different approach. It is > designed to normalize the loudness at player side, according to the metadata > embedded within the content, which could be relatively big in its size, so > it will be unfit for Vorbis comment. A VorbisComment can store upto 2^64 bytes (16 exabytes). A FLAC metadata block is limited to 2^24 bytes (16 megabytes). Therefore, a VorbisComment can be orders of magnitude bigger than a FLAC metadata block. Visit: https://wiki.xiph.org/Metadata The advice to use a VorbisComment still looks good. Regards,...

Hello, I am writing a script which reads and writes vorbis comments using the vorbiscomment utility from vorbis-tools. I have just one question regarding the --raw switch. Raw mode (--raw, -R) will read and write comments in utf8, rather than converting to the user's character set. This is useful for using vorbiscomment in scripts. However, this is not sufficient for gene...

Hello, I am writing a script which reads and writes vorbis comments using the vorbiscomment utility from vorbis-tools. I have just one question regarding the --raw switch. Raw mode (--raw, -R) will read and write comments in utf8, rather than converting to the user's character set. This is useful for using vorbiscomment in scripts. However, this is not sufficient for gene...

...grams 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. -------------- next part -------------- diff --git a/src/flac/vorbiscomment.c b/src/flac/vorbiscomment.c index ed9f710..0e99267 100644 --- a/src/flac/vorbiscomment.c +++ b/src/flac/vorbiscomment.c @@ -243,7 +243,7 @@ FLAC__bool flac__vorbiscomment_add(FLAC__StreamMetadata *block, const char *comm return false; } - if(!set_vc_field(block, &parsed, &dummy, raw...

...th 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 a "=" at all * vorbiscomment isn't capable of this and needs "keyword=value" This is what it looks like in oggenc (rc3 with utf8patch) Playing: 01.Fantomas_-_Page_3.ogg Album: Fantômas Title: Page 3 Track number: 01 Artist: Fantômas Comment: Comment with With oggenc -c Comment: =Comment from xmms Comment: Com...

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" option, and can write them out, it can't subsequently read them again. Fair enough, as '=' is a valid comment value character; vorbiscomment couldn...

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 message to 'vorbis-request@xiph.org...

Attached is a patch that adds 5 missing FLAC__metadata_object_vorbiscomment_* functions to the VorbisComment class. In my previous message I stated 8 functions were missing, but on closer inspection, 3 of those belong in the VorbisComment::Entry class, and 2 of them already have equivalent functions in there. The last one (FLAC__metadata_object_vorbiscomment_entry_matches(...

I'm trying to use libFLAC++ v1.1.2, to read Song information (like artist, trackname etc..). So.. I read metadata from file FLAC::Metadata::get_streaminfo("somefile.flac", infosik); and It's ok - no error, then I read vorbis info: FLAC::Metadata::VorbisComment vorbis_kom(infosik); int number_of_comments = vorbis_kom.get_num_comments(); and after that I have number_of_comments=14 when I try to read entry using get_comment method I got segfault vorbis_kom.get_comment(number); I was trying all numbers from 0, to 14 and it always segfaults Is that a righ...

...cut/vcut.c (revision 11702) +++ vcut/vcut.c (working copy) @@ -10,6 +10,10 @@ * last modified: $Id: vcut.c,v 1.9 2003/09/03 07:58:05 calc Exp $ */ +#ifdef HAVE_CONFIG_H +#include <config.h> +#endif + #include <stdio.h> #include <stdlib.h> #include <ogg/ogg.h> Index: vorbiscomment/vcedit.c =================================================================== --- vorbiscomment/vcedit.c (revision 11702) +++ vorbiscomment/vcedit.c (working copy) @@ -9,6 +9,10 @@ * last modified: $Id: vcedit.c,v 1.23 2003/09/03 07:58:05 calc Exp $ */ +#ifdef HAVE_CONFIG_H +#include <confi...

...cut/vcut.c (revision 11702) +++ vcut/vcut.c (working copy) @@ -10,6 +10,10 @@ * last modified: $Id: vcut.c,v 1.9 2003/09/03 07:58:05 calc Exp $ */ +#ifdef HAVE_CONFIG_H +#include <config.h> +#endif + #include <stdio.h> #include <stdlib.h> #include <ogg/ogg.h> Index: vorbiscomment/vcedit.c =================================================================== --- vorbiscomment/vcedit.c (revision 11702) +++ vorbiscomment/vcedit.c (working copy) @@ -9,6 +9,10 @@ * last modified: $Id: vcedit.c,v 1.23 2003/09/03 07:58:05 calc Exp $ */ +#ifdef HAVE_CONFIG_H +#include <confi...