Displaying 20 results from an estimated 4000 matches similar to: "Fwd: final changes to mimetypes rfc"
2008 Aug 17
1
Fwd: final changes to mimetypes rfc
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
2008 Aug 17
1
Fwd: final changes to mimetypes rfc
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
2008 Aug 16
2
Fwd: 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
2008 Jun 06
3
How Ogg mappings translate into the codecs parameter in Ogg media types
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
2008 Aug 16
2
Fwd: final changes to mimetypes rfc
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:
2008 Aug 15
4
final changes to mimetypes rfc
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, speak up now.
I have one question in particular: Ogg.k.ogg.k: is the kate codec
parameter now down to 8 bytes? If so, it's ok, since I've already made
that change.
Cheers,
Silvia.
2008 Aug 15
2
final changes to mimetypes rfc
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
2008 Aug 18
4
final changes to mimetypes rfc
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
2008 Jun 07
2
How Ogg mappings translate into the codecs parameter in Ogg media types
"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
2008 May 29
3
How Ogg mappings translate into the codecs parameter in Ogg media types
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
2008 May 30
3
How Ogg mappings translate into the codecs parameter in Ogg media types
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
2008 Aug 15
3
final changes to mimetypes rfc
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,
2008 Jun 06
2
How Ogg mappings translate into the codecs parameter in Ogg media types
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
2008 May 24
3
How Ogg mappings translate into the codecs parameter in Ogg media types
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
2008 Aug 19
0
final changes to mimetypes rfc
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
2003 Jan 11
3
Update on IETF Internet-Drafts
Good day,
FYI, I've just sent the attached email to IETF to progress our I-Ds.
There are also links to updated documents in this email.
Cheers,
Silvia.
-------- Original Message --------
Subject: New I-Ds for Ogg technologies (Vorbis over RTP, Ogg file
format, Mimetypes)
Date: Sun, 12 Jan 2003 01:36:31 +1100
From: Silvia Pfeiffer <Silvia.Pfeiffer@csiro.au>
Organization: CSIRO
To: AVT
2003 Jan 11
3
Update on IETF Internet-Drafts
Good day,
FYI, I've just sent the attached email to IETF to progress our I-Ds.
There are also links to updated documents in this email.
Cheers,
Silvia.
-------- Original Message --------
Subject: New I-Ds for Ogg technologies (Vorbis over RTP, Ogg file
format, Mimetypes)
Date: Sun, 12 Jan 2003 01:36:31 +1100
From: Silvia Pfeiffer <Silvia.Pfeiffer@csiro.au>
Organization: CSIRO
To: AVT
2011 Aug 26
3
ask for one ogg test stream with cmml subtitle
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
2008 May 24
2
How Ogg mappings translate into the codecs parameter in Ogg media types
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]:
2013 Jul 24
2
Metadata
On 7/23/13, Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote:
> On Wed, Jul 24, 2013 at 3:59 AM, Martin Leese
>> ...
>>>> Information about Metadata
>>>> has been collected together in the Xiph Wiki
>>>> at:
>>>> https://wiki.xiph.org/Metadata
>> Page updated. See what you think.
>
> M3F is also not used anywhere