similar to: vorbiscomment long string bug?

Displaying 20 results from an estimated 2000 matches similar to: "vorbiscomment long string bug?"

2011 Jan 20
1
Flac] Where Cover Art?
"Santiago Jimeno" wrote: > Flac files, as us knows, follows the Vorbis Tags system included in block 4 > Recently Vorbis has established the possibility to include picture files by > means of 2 Tags: COVERARTMIME AND COVERART. > To work therewith is quite easy. No. this in incorrect. The VorbisComment "COVERART" was only ever unofficial, and has been deprecated
2007 Nov 19
1
Re: [xiph-commits] r14188 - trunk/vorbis-tools/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/vorbiscomment/vorbiscomment.1 > Log:
2008 Apr 15
1
base64 ALBUMART vorbiscomment (was Re: [ogg-dev] Ogg/Spots and Ogg/MNG)
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:
2008 Apr 12
1
base64 ALBUMART vorbiscomment (was Re: [ogg-dev] Ogg/Spots and Ogg/MNG)
Silvia, This discussion has moved to vorbis-dev. You may want to reply further there. On 4/12/08, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > Even with putting the picture into vorbiscomment, the software would > need to be smart enough to uudecode the picture and display it. A url > is much simpler I believe. I had thought of this approach myself, too, and while
2013 May 28
5
[PATCH 1/6] Remove the --quiet (-q) option from vorbiscomment.1 man page.
--- 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
2008 Oct 15
0
Album art - requirements
>I have more than once said I'm in favor of the vorbiscomment solution. >It's ugly, it will break this and that one other player, but these >people want the feature that bad so they won't mind about any of those >issues. Plus it means little or no work for a feature the people who >actually do code care little about, and it certainly helps that >there's already
2011 Jan 23
0
Flac] Where Cover Art?
OK Martin. Thank you for the explanations and for your time. I am writing a program that reads and writes all existent Tags types. It lacks only to end the edition (rewriting) of "Native" Flac and Matroska. Both cases for the same problem: the separation of Tags and Picture in different blocks. In Flac I resolved it, but now I have to add METADATA_BLOCK_PICTURE. Reading Vorbis
2008 Oct 13
10
Album art - requirements
Hi, there was a thread a few months ago about album art, and how to embed it in an Ogg stream. The outcome was unconclusive, and kind of settled on the existing practice of adding a uuencoded image in a Vorbis comment, or similar. A better solution would be to embed those images as a separate stream, including hints as to what image represents (front cover, back cover, etc). The obvious
2004 Sep 17
3
newlines in vorbis comments
Is there any way to put a newline character in comments for ogg vorbis files in Linux? I can't see any way of doing it with vorbiscomment. Easytag would work, but has other problems (like concatenating comment fields with the same tag name). If I wanted to put together a quick hack to add a such a comment (I'm thinking read the comment from a file, with the tag name specified at the
2004 Sep 17
3
newlines in vorbis comments
Is there any way to put a newline character in comments for ogg vorbis files in Linux? I can't see any way of doing it with vorbiscomment. Easytag would work, but has other problems (like concatenating comment fields with the same tag name). If I wanted to put together a quick hack to add a such a comment (I'm thinking read the comment from a file, with the tag name specified at the
2008 Apr 12
1
base64 ALBUMART vorbiscomment
" 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
2008 Apr 11
4
Ogg/Spots and Ogg/MNG
On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On 4/11/08, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > > > uuencode ^_^ > > > > Hmm... > > Yes! A Vorbis Comment tag called ART or ALBUMART with a Base64 string > would do the trick and it would not choke existing players. No, vorbiscomments are meant to be
2005 Sep 04
0
[Patch] for easytag tag editor to add speex tagging
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
2005 Sep 04
0
[Patch] for easytag tag editor to add speex tagging
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
2006 Feb 22
2
vcedit/vorbiscomment heterogeneous streams
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
2008 Oct 14
1
Album art - requirements
On 13-Oct-08, at 2:10 PM, Silvia Pfeiffer wrote: > is coverart a header-type content or a time-aligned type content? Well, it's collection-level metadata, so it doesn't belong in files at all. :) > It was my impression that it is mostly header-type content, i.e. > concerns the full file rather than segments of it. It makes sense to reference it per-chain-segment in an Ogg
2009 Mar 26
8
Cover art
Hello to the people reading this list! I am developing tagging support for ogg vorbis in Nero products and we are currently thinking of supporting cover art in ogg files. What is the current state of proposal for cover art in ogg files? Is this http://wiki.xiph.org/index.php/VorbisComment#Cover_art still the latest information? Regards, Goran -------------- next part -------------- An HTML
2008 Oct 13
0
Album art - requirements
I think we have to discuss a fundamental question about coverart first: is coverart a header-type content or a time-aligned type content? It was my impression that it is mostly header-type content, i.e. concerns the full file rather than segments of it. Therefore, embedding it into any of the time-aligned streams (Kate, CMML, OggMNG) doesn't make much sense to me. It should be in a header.
2011 Jan 22
0
Flac] Where Cover Art?
You said "With the exception of where to put a picture file, VorbisComments in a Vorbis stream are the same as VorbisComments in a FLAC stream." In METADATA_BLOCK_PICTURE case they would not be the same. Up to now we could exchange the complete block of VorbisComments. But with the addiction of METADATA_BLOCK_PICTURE doesn't happen this way. In Ogg files the METADATA_BLOCK_PICTURE
2003 Jul 06
1
vorbiscomment causes &quot;Illegal UTF-8 sequence in comment&quot;
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: