search for: mathiaskunter

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

...ogg vorbis + theora file so that only the music could be played afterwards, but not the video any more). My .NET tagging library can handle it correctly now by the way ;-) Cheers, Mathias ----- Urspr?ngliche Mail ---- Von: Silvia Pfeiffer <silviapfeiffer1@gmail.com> An: Mathias Kunter <mathiaskunter@yahoo.de> CC: ogg-dev@xiph.org Gesendet: Samstag, den 28. April 2007, 03:31:13 Uhr Betreff: Re: [ogg-dev] embedded pictures in vorbis comments? Hi Mathias, The solution you are suggesting won't work because it will not only "not work" in existing players, but probably break them...

...a >> qestion of displaying the tag as text (although that is a concern) >> it's that most hardware players that only have 10-20kB available for >> stream buffering won't be able to decode the headers and thus won't be >> able to play the file. Mathias Kunter <mathiaskunter at yahoo.de> wrote: ... > Since MP3 and FLAC have well-supported > standards about cover art, why not simply > adopting this for OGG too? Placing the binary > coverart structure from > http://flac.sourceforge.net/format.html#metadata_block_picture > within a vorbis comment woul...

Hi all, I've got a question on regarding how to find out the duration of an ogg vorbis file. Sorry if it should already be mentioned somewhere in the docs, but I couldn't find out how to do it the best way. So, I can read the [bitrate_nominal] field from the identification header (if it is set), find out the size of the audio data (by subtracting the size of the three headers from the

Thank you very much for your help, it worked that way. Mathias ----- Urspr?ngliche Mail ---- Von: "xiphmont@xiph.org" <xiphmont@xiph.org> An: Conrad Parker <conrad@metadecks.org> CC: Mathias Kunter <mathiaskunter@yahoo.de>; vorbis-dev@xiph.org Gesendet: Donnerstag, den 20. M?rz 2008, 12:49:16 Uhr Betreff: Re: [Vorbis-dev] Determining the duration of an ogg vorbis file On Thu, Mar 20, 2008 at 4:34 AM, Conrad Parker <conrad@metadecks.org> wrote: > The granulpos field of the last page in the vor...

Hello, I've mainly finished the native ogg Vorbis tagging .NET library. It already works well for reading and writing the vorbis comments for the files I tested. The library only rewrites the entire file if it has to, and adds 2 K padding in this case so that further changes of the comments won't make it nescessary to rewrite the whole file again. I found out foobar2000 also does it this

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:

>> So, a possible way to encode album art would be: >> >> - a Skeleton stream with appropriate header messages >> - one Kate stream per image, carrying a PNG image >> (alternatively, use Ogg/MNG, if someone brings it from the dead) >> [...] Silvia wrote: >Interesting proposal. Not sure it won't over-complicate album art though... Well yes, of course

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

Hello all, my name is Mathias, I'd like to ask about some details of the OGG format because I'm quite new to it. I'd like to write a native .NET library for reading and writing Vorbis comments. It's going to be open-sourced as soon as it's finished. So here it goes: 1) When packing (Vorbis) packets to OGG pages, does a new packet always begin on a fresh OGG page? Within the

>Searching for 'vorbis' to find the packet boundary is wrong however. >The lacing values in the Ogg page header tells you exactly where the >division is. OK, so given the fact that a page can also contain multiple packets this means that the lacing values of one page could be like the following example: 255 255 189 (something less than 255, indicating that a new packet starts

>That would be great! We always need help improving our documentation. OK. I'm going to start writing this lib now, and as soon as it works well I'm going to write specs about how to tag vorbis files. I'll let you know then. Maybe I have to ask you some further questions during development. Let's see. Thank you so far, Mathias

>> 1) Is it valid to insert an "empty" page into the stream which simply contains the binary value 0 for the page_segments counter, and which therefore contains no segment table nor any packet data? I'd like to do this to produce a gapless page sequence number so that I don't have to re-number all following pages, so that I don't have to re-compute the checksums of all

> 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. :) Well right, but the problem is that external coverart files are unhandy (broken links!!, streaming...) Users therefore want to embed them most times, as you can tell from other audio file formats: the majority of cover art is

>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

Hello all, there is an ambiguity within the Vorbis specification regarding the granule position of the Ogg encapsulation. I'm referring to section "A.2. Encapsulation" of the Vorbis I specification, as found here: https://xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-132000A.2 The specification both says > The granule position of these first pages containing only headers > is

OK, I've found the answer for one of my previous question myself in the meantime. The comment header can of course be split over more than 1 ogg page since the comment header can be greater than 64K. It also seems to be possible that both comment AND setup headers are placed on a single ogg page only (as stated in the Voribs specs). Due to the fact that the first audio packet also begins on

Hello, I'm still working on the native .NET ogg tagging library. It already works well for non-multiplexed ogg vorbis, ogg flac and native flac files. Concerning multiplexed files, I've got two short questions: 1) Is it valid to insert an "empty" page into the stream which simply contains the binary value 0 for the page_segments counter, and which therefore contains no segment

Ralph, thanks for your help. >>Since the length of the precedent identification header is fixed, this even is a fixed offset >>into the logical ogg stream. >This will work for all the vorbis-only files I've seen (because no one >pads the first packet). You should really implement a proper ogg parser, >but by all means get a hack working first. I will of course use the

>I don't mind (and approve of) the idea of reusing as much of proven >standards as we can. But putting it in a Vorbis comment will in fact >piss off people who then can't play the file. It's not as much a >qestion of displaying the tag as text (although that is a concern) >it's that most hardware players that only have 10-20kB available for >stream buffering