similar to: base64 ALBUMART vorbiscomment (was Re: [ogg-dev] Ogg/Spots and Ogg/MNG)

Displaying 20 results from an estimated 1000 matches similar to: "base64 ALBUMART vorbiscomment (was Re: [ogg-dev] Ogg/Spots and Ogg/MNG)"

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
2008 Apr 11
1
base64 ALBUMART vorbiscomment (was Re: [ogg-dev] Ogg/Spots and Ogg/MNG)
[Cc: changed to vorbis-dev] On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On Fri, Apr 11, 2008 at 10:11 PM, Conrad Parker <conrad at metadecks.org> wrote: > > No, vorbiscomments are meant to be human-readable. > > > But I CAN read base64! :-) > It's a win-win situation, with the added bonus that it wouldn't > require
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
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
0
Ogg/Spots and Ogg/MNG
On Fri, Apr 11, 2008 at 10:11 PM, Conrad Parker <conrad at metadecks.org> wrote: > No, vorbiscomments are meant to be human-readable. But I CAN read base64! ... Seriously now, this is a good idea. Just the right (if not perfect) solution for this issue. See, those players that can read Vorbis Comments already limit what the user sees to the basic ones like Artist, Album, Comment,
2008 Apr 11
2
Ogg/Spots and Ogg/MNG
On 4/11/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: > how (or do you mean ogg/mng or spots) ? People want an official standard on how to embed JPEG/PNG in single stream Vorbis files, because one of the extensions/hacks of MP3 ID3 allows it. > uuencode ^_^ Hmm...
2008 Apr 11
1
Ogg/Spots and Ogg/MNG
Hi, please ignore this message if this is a stupid question: Would supporting APNG instead be any easier? Cheers, KJ On Fri, Apr 11, 2008 at 3:52 PM, Ian Malone <ibmalone at gmail.com> wrote: > On 11/04/2008, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: > > > Ogg/Spots has no implementation since we agreed that Ogg/MNG would > > >
2008 Apr 11
2
Ogg/Spots and Ogg/MNG
Hi, are these two dead, or just progressing slowly ? The only code I've seen about Ogg/MNG was a player in ogg-tools, and I've seen nothing for Ogg/Spots. I'd looked at those before adding bitmaps to Kate, and I went back to that a few days ago (storing subtitles as images from a dvd - works great in vlc, but I store images without compression). If they are dead, I'd be inclined
2008 Apr 11
1
Ogg/Spots and Ogg/MNG
> The thing about the mng libraries is they seem designed in such a way > the using them to do simple timed display of mng is fairly easy, but > extracting static images becomes painful. I had been thinking about > doing something to read only the jpeg/png subset, but thesis writing > has taken me off ogg stuff for the past few months. I'm still of the > opinion this might
2008 Apr 11
0
Ogg/Spots and Ogg/MNG
On 11/04/2008, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: > > Ogg/Spots has no implementation since we agreed that Ogg/MNG would > > fully cover all the functionality of Ogg/Spots. However, Ogg/MNG has > > not progressed as much as we would all have liked. > > > > So, if you would like to get images into Ogg, I'd recommend >
2008 Apr 11
2
Ogg/Spots and Ogg/MNG
On 4/11/08, Ian Malone <ibmalone at gmail.com> wrote: > I'm still of the opinion this might be a useful thing to do (to provide the > album art and things that crazy people want to put into sound files). Ah, album art. People won't shup up about it, even though it has always been theoretically possible to embed pictures in Ogg. I hope we can establish this year how to do
2008 Apr 11
4
Ogg/Spots and Ogg/MNG
> Ogg/Spots has no implementation since we agreed that Ogg/MNG would > fully cover all the functionality of Ogg/Spots. However, Ogg/MNG has > not progressed as much as we would all have liked. > > So, if you would like to get images into Ogg, I'd recommend > improving/implementing Ogg/MNG support. :-) I'd looked at MNG (which I didn't know about at the time) and to
2011 Nov 01
1
vorbiscomment long string bug?
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
2007 Apr 22
4
embedded pictures in vorbis comments?
Hello, I'd like to ask about the possibility of embedding pictures like an album cover artwork into a vorbis comment header. Since the data in a comment string after the separating "=" has a defined length, this could theoretically also be binary picture data. For example "PICTURE=[...any binary data...]" It only would be a problem for existing software which isn't
2007 Nov 22
2
Contrinued work with Multimedia Metadata Format (M3F)
Hi again Ivo and the Xiph ogg-dev emailing list, This email is meant to present two blockers for continued development of the XML based Multimedia Metadata Format (M3F) (MDMF page in the wiki). This format is intended to replace comments as a way of including descriptions of metadata contained in the Ogg container format. For instance title, production year, actors, producers, and so on for
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
2007 Apr 11
1
FLAC: software for displaying embedded picture
hi, does somebody else knows more software that can display the embedded picture in FLAC files? The software must run on windows. thx 2007/4/10, Jud White <jwhite@cdtag.com>: > > I just installed foo_ui_columns and foo_uie_albumart, however the > albumart plugin only supports images in the directory. Thought I'd let > you know that path is a dead end (for embedded art) :)
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
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
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: