Re: Re: Matroshka
Steve Lhomme <[email protected]> Thu, 28 Nov 2002 22:19:55 +0100
| Newsgroups | gmane.comp.video.mcf.general |
|---|---|
| Message-ID | <[email protected]> |
mf wrote:
> ChristianHJW wrote:
> I'd simply keep Media Container Format, with Encapsulation as the verb,
> adjective and process. I got this term from some guy (back in 2001) from
> OpenDivX saying that AVI is the encapsulating format. I think this is a
> perfect term, as it's easy to understand, yet sounds like a professional
> term. The BAD thing to do, then, is to start calling the files Capsules,
> and randomly improvising on the word to make it sound like toothpaste or
> lubricant ("Capsuline, now with improved anti-caries formula", or
> "Capsuline, new from Durex"). Really, no offense meant.
Well, encapsulation is even longer. And is much bigger than multimedia
muxing. Putting data in an IP packet (and then an ethernet packet, and
then an ATM packet) is also encapsulation. That's a good way to say :
MCF is a file format...
Also, as explained on IRC, MFC is Multimedia Container Format, not Media
Container Format (which is not what it does).
> mcf.sf.net. it's easier than any cjb.net or xrs.net or vze.com or
> whatever, and those URL services are super-popular too. Short things are
> easy to remember, and mcf.sf.net is as short as it gets. What's wrong
> with it?!
As you may have noticed, only a few person use sf.net. And even SF
redirects you which is *very* stupid.
> Matroshka would suggest a container in a container, like how MPEG4 is
> handled within AVI. This is a bad thing to be associated with :-P.
Actually it's matroska. Otherwise the real troubles will start.
It relates to the format itself, why it's good and different.
And you can actually put AVI data in MCF...
> > Dont panic guys !! Lets concentrate on the technical aspects for the
> > time being, and keep the name issue in the back of our minds. I am
> > sure one day somebody will come up with THE name, and will like it
> > and agree to it. There is no reaosn to hurry with this, as long as we
> > dont release a MCF parser version with automatic codec download from
> > MCF server and we have to include the URL into the parser.
>
> I think a simple redirect from http://mcf.sourceforge.net/codecs to a
> select list of mirrored codec download servers (that way sourceforge
sf, not soundforge ! (mistake on purpose as I've seen it)
> gets none of the real traffic, and people can set up mirrors on
> ultra-fast university or whatever servers, the location of which can
> change since the master list is on SF.net) would be fine.
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en