similar to: final changes to mimetypes rfc

On Thu, Aug 14, 2008 at 9:14 PM, Silvia Pfeiffer wrote: > The IETF has a final draft of our RFC at > ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes > from 3534 to 5334 - funny!). Didn't we decide YUV4MPEG should be 8 octets as well? -r

On Fri, Aug 15, 2008 at 8:42 PM, Ian Malone <ibmalone at gmail.com> wrote: > 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> Hi all, >> >> The IETF has a final draft of our RFC at >> ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes >> from 3534 to 5334 - funny!). >> >> If you have anything in need of change,

On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: >>> Just one small question, 10.3: "In particular, .ogg is used for Ogg >>> files that contain only a Vorbis bitstream, while .spx is used for Ogg >>> files that contain only a Speex bitstream." >>> >>> Should that be a "Vorbis

On Mon, Aug 18, 2008 at 9:59 PM, Ian Malone <ibmalone at gmail.com> wrote: > 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com >> <ogg.k.ogg.k at googlemail.com> wrote: >>>>> Just one small question, 10.3: "In particular, .ogg is used for Ogg >>>>> files

On Sat, Aug 16, 2008 at 12:23 AM, Silvia Pfeiffer wrote: > Have we got a spec? If not, we may want to remove it altogether and > make the fixes in our wiki as the spec develops. We have a draft spec with no implementation. I can't imagine the magic changing, so I think it's ok to leave it in, but I'm ok to remove it if you think that's best. I do think there's little

Excellent, thanks for noticing - will add that. Also: question about the Dirac codec identifier in Ogg. It is currently char[5]: 'BBCD\0' - but in your spec it is char[4]: 'BBCD'. Which one should we put in? Cheers, Silvia. On Sat, Aug 16, 2008 at 5:31 PM, David Flynn <davidf+nntp at woaf.net> wrote: > On 2008-08-16, Ralph Giles <giles at xiph.org> wrote:

On 8/17/08, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > OK, then yuv4mpeg will have the magic number: char[8]: 'YUV4MPEG'. Which was previously for those not paying attention char[9]: 'YUV4MPEG2'. > Also, can you put the link to the spec into > http://wiki.xiph.org/index.php/MIMETypesCodecs ? AFAIK, that is just a matter of putting a [[OggUVS]] in

> container format are called. CMML as a timed text codec has a mime > type of text/cmml. Similarly, the textual representation of Kate > should be text/x-kate. Agree, as both of these are text. > When you encode Kate in Ogg, it would not normally be expected to come > without audio or video. Thus, if it's an audio file, it should be > video/ogg - for a video file it should

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 7/23/13, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > On 23 Jul 2013 15:17, "Martin Leese" <martin.leese at stanfordalumni.org> > wrote: ... >> Information about Metadata >> has been collected together in the Xiph Wiki >> at: >> https://wiki.xiph.org/Metadata > > That page is a bit outdated. It has CMML in it which we

On 17-Aug-08, at 1:11 AM, Silvia Pfeiffer wrote: > OK, then yuv4mpeg will have the magic number: char[8]: 'YUV4MPEG'. > Is that ok? Yes, I'm good with that. > Also, can you put the link to the spec into > http://wiki.xiph.org/index.php/MIMETypesCodecs ? Thanks! Sorry, I thought I'd dumped the spec into the wiki. It's there now, and linked from the

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

I'm trying to create files that contain a video stream, one or more audio streams, subtitles, and DVD-like chapter information. ATM, I use ogm containers that can handle all this. But although ogm is supported e.g. by xine (including chapters), it seems to be an unofficial hack. Is that correct? I'd like to move to ogg containers, since ogm doesn't support theora videos. My final

2008/8/18 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: > On Mon, Aug 18, 2008 at 9:59 PM, Ian Malone <ibmalone at gmail.com> wrote: >> 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >>> On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com >>> <ogg.k.ogg.k at googlemail.com> wrote: >>>>>> Just one small

Brendan Bolles wrote: > Hey everyone, according to Wikipedia's 4-year-old information, there is no > standard for putting metadata into an Ogg file. True. > That metadata must be > included in the codec. More generally, in a stream in the Ogg file. Codecs are streams, but so are things like Ogg Skeleton. Information about Metadata has been collected together in the Xiph Wiki

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

On Thu, 25 Aug 2011 20:01:11 +1000 Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote: > Hi BCXA, > > CMML is deprecated. You should use KATE instead. > > Cheers, > Silvia. ok i admit this statement came as a surprise for me. cmml is about metadate/annotations, how can it be replaced by KATE ( which is mainly about subtitles as far as i can see? startx

"Silvia Pfeiffer" <silviapfeiffer1 at gmail.com> wrote: ... > Also, it would be good if we can keep > our magic numbers to the first 8 bytes. So Kate and Yuv4mpeg both need to be trimmed. ... >>> char[9]: '\x80kate\0\0\0\0' | kate >>> char[9]: 'YUV4MPEG2' | yuv4mpeg Regards, Martin -- Martin J Leese E-mail: martin.leese

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

Ralph Giles wrote: > > A URI/URL scheme for referencing streams would be a generally useful > thing. Should we override the query mechanism like the time fragment > draft? "?oggserial=0x15323421" ? > This is roughly what was suggested the last time around. A possible refinement is to provide a mapping from identifiers to IDs so you could say "?oggid=myvideo".