Re: [Cellar] CodecIDs for non-standard and unregistered data formats

2017-02-14 7:46 GMT+01:00 Matt Gruenke <matt.gruenke@gmail.com>:
> Related to my recent query about TrackTypes for non-standard data formats,
> I'd like to discuss CodecIDs.  I had previously raised this issue, on the
> matroska-devel list, and was advised to take it up, here.  In the interim,
> my thinking on the matter has evolved.
>
> I wonder why not allow IANA Media Types (aka MIME types), as a sub-class of
> CodecIDs?  Of course, the official Matroska CodecID would be preferred, for
> all formats for which one has been designated.  However, this would enable
> broader use of Matroska files, including for private, application-specific
> data stream formats.

The main goal of Matroska is multimedia interleaved/timestamped data.
It's possible to have "complex" track and put in it whatever you want.
If a timestamp is required. If it's not, using attachment is what you
want and it already has a MIME type.

> Perhaps a prefix like 'X_MEDIATYPE/' could simply be prepended to media type
> names conforming with RFC 6838.  The value of TrackType would still
> determine whether video, audio, or any other type-specific elements can be
> used in such tracks.

Although tempting I think it's better to avoid interleaving all kinds
of stuff with audio/video. You could want to embed a "video/quicktime"
but it would not be interleaved, or you'd need to parse/mux the data
and then it's not a clean "video/quicktime" you get anymore.

> Thank you for considering my suggestion.
>
>
> Matt
>
>
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar
>

-- 
Steve Lhomme
Matroska association Chairman