similar to: Codecs defined for OGG

On 5/24/08, Ralph Giles <giles at xiph.org> wrote: > It's supposed to be finalized though there many be some granulepos > issues still in current implementations. I don't expect the BBCD\0 > magic to change. Great. > OggMNG defines the following magics: > > char[8]: "\211PNG\r\n\032\n" png > char[8]: "\212MNG\r\n\032\n" mng > char[8]:

2008/5/29 Ralph Giles <giles at xiph.org>: > On 28-May-08, at 6:20 PM, Conrad Parker wrote: > >> /* TODO: this should check against 42 for the relevant version numbers */ >> if (op->bytes < 41) return 0; > > I gather this means the USE_THEORA_PRE_ALPHA_3_FORMAT #if should instead be > based on the length of the header packet. I'm not sure why you're

On 5/24/08, Conrad Parker <conrad at metadecks.org> wrote: > The magic is not always char[8] -- it's an arbitrary number of > characters, and as far as I know there is no official limit. I was under the impression that 8 was the limit. Thus the extra white space JM adds on Speex and CELT magics. I may be wrong, though. > So it's 7 for Vorbis and Theora, 5 for FLAC So

On Sun, May 25, 2008 at 2:53 AM, Ralph Giles <giles at xiph.org> wrote: > On 24-May-08, at 9:26 AM, Ivo Emanuel Gon?alves wrote: > > And there's OggY4M which uses char[9]: "YUV4MPEG2" but that's in no > way finalized. I was unable to find any documentation on this on the Web. Would you have a link to the mapping? BTW, I have now finalized a first version of

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

I agree - we should use only hex or octal, but not mixed. Cheers, Silvia. On Sat, May 31, 2008 at 2:20 AM, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > I received the following comment regarding the table: > >> The table contains a mix of octal and hexadecimal 'escape sequences' >> for non-printable / non-ASCII octets. >> I strongly suggest to only

Hello everyone, As discussed on last Monthly Meeting, Monty settled on recommending the extension .v+ogg for Theora files IF it would work on Linux. Probably many have tested it already, but I haven't seen anything said publically, so for the record, v+ogg works on both Windows and Linux. Hadn't a chance to test it on Mac OS X, but I'm sure it should work there too. And Plan 9 :)

On 5/26/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: >> char[8]: 'kate\0\0\0\0' | kate > > This is incorrect, should be: > > char[9]: '\x80kate\0\0\0\0' | kate The last one is how it's listed on ogginfo code, but the first one (char[8]) is how it's described in the wiki page. I thought the

We interrupt your regularly scheduled program to bring you the following issue. RFC3534bis is on hold. I have addressed all feedback from Mr Westerlund, except for the following: From: Magnus Westerlund <magnus.westerlund[at]ericsson[dot]com> Date: Fri, 11 Apr 2008 13:55:28 +0200 Subject: Re: Updated 3534bis (was Re: Request for review of Ogg Media Types: video/ogg, audio/ogg,

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

Silvia, I don't think I follow your line of thought. On 5/27/08, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > I was just having a thought this morning: we should probably include > the version information into the codec identification bits. What version information? Like libvorbis 1.2.1? If so, I can't see much of a point in that. > It will make it easier to

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

Hello list, We have recently introduced the codecs (optional) parameter on the Ogg media types for easier identification of encapsulated codecs in conditions were it's not feasable to examine the streams directly. I received a comment from the IESG that we should have some sort of list to describe how Ogg mapping strings translate to codec parameter strings, so I went ahead and compiled a

Dear all seems impossible to enter in the pages ofthe icecast product can you advice them? i start from here http://dir.xiph.org/ regards --------------------------------- Yahoo! Mail: gratis 1GB per i messaggi, antispam, antivirus, POP3 -------------- next part -------------- An HTML attachment was scrubbed... URL:

Peter Saint-Andre a ?crit : > Ivo Emanuel Gon?alves wrote: >> Just a heads-up, I received confirmation that Speex is now the default >> codec for the Jabber's Jingle VoIP protocol. > > Which we hope to finalize soon for broader adoption. :) That's good to hear. Are you supporting wideband or just narrowband? Jean-Marc

Oh, hey, I'm more or less on the final stages of drafting the registration proposal that will be submitted to the IETF. If you have comments, suggestions, fixes, anything, this is it. https://trac.xiph.org/browser/experimental/ivo/drafts/draft-xiph-rfc3534bis.txt -Ivo

Oh, hey, I'm more or less on the final stages of drafting the registration proposal that will be submitted to the IETF. If you have comments, suggestions, fixes, anything, this is it. https://trac.xiph.org/browser/experimental/ivo/drafts/draft-xiph-rfc3534bis.txt -Ivo

Hi all, I am trying to set up the codecs table in the wiki and we have played a bit with Dirac to find out what existing tools write into the header. The Schroedinger implementation by Fluendo uses (or used to use) "KW-DIRAC" as the identifier in the Ogg header. "BBCD" is the identifier of each of the Dirac data packages. More recently, I read that the Dirac Sequence header

On 6/18/09, Conrad Parker <conrad at metadecks.org> wrote: > This sounds like it needs a new tool specifically for fixing broken > Ogg files. I see two solutions: 1) the new vcut which I reckon will fix the problem since it has to split and rebuild the audio in a new Ogg 2) an Hex editor, even if just to check what's wrong in the metadata section -Ivo