ChristianHJW
5th May 2004, 18:04
Hi all,
the matroska container was recently celebrating its 1st birthday, and when looking back we are quite happy about the acceptance of the format from the users and developers, as well as the progress we made within a single year.
However, in our quest to replace the M$ AVI format we also noticed that there is no real future for matroska as long as it stays what it is right now, a container without media framework behind it, like AVI has/had with Video for Windows ( now DShow, at least partially ) and MOV has with Quicktime.
Now, what differentiates a container from a 'standard container' for a media framework you may ask ? Well, currently we, the matroska team, have to define a way to mux stuff into matroska ourselves, and specific for every new compression format. Of course, we have a VFW/DShow compatibility mode, allowing to mux all kind of stuff into matroska that way, and we plan to do the same for Quicktime, but this is not the same.
As soon as we can offer a real media framework with matroska becoming the standard container, people can start making their own codecs to be used in matroska, and still our video editors will be able to edit their stuff, and this is exactly what made AVI the most used container for the time being. Its also the reason why today we have the perverse situation that so-called hardware 'MPEG4 players' cant read MP4, the standard container for MPEG4, but will play MPEG4 video + MP3 in AVI. In this case the existing demand created the units, not the other way around, like normally. This demand was the result from the DivX codec ( a VfW codec ) being used to compress video with unknown compression ratios and quality, in combination with MP3 ACM codecs, on VfW based video compression/editing tools like Virtualdub, which were outputting into AVI format.
Inspired by the thought to have a real, x-platform media framework for matroska, we recently started to have a very close at Gstreamer, the media framework 'in spe' for Linux and part of GNOME already. robux4 is almost finished with porting it to Windows, and the patch is being looked at by the gstreamer dev team to find its way into their CVS. After that, the bigger part of the matroska dev team will start to port the existing plugins from Linux to win32, and also to create new plugins. Our goals are to
- make a nice player based on gstreamer, and usable for both Windows and Linux
- create a video editing tool ( TCME ) based on it, and again x-platform
- help improving Gstreamer
All this is necessary to ensure matroska's future, and to avoid it will just turn out to be a short movement with a number of suporters, until something more fancy see the light of day.
As a result of all of this, development work on a number of important new features like
- menues
- control tracks
- file linking support in players
- new tagging tools
- USF muxing
etc.
have more or less come to a halt ( there is hope for USF support, unmei has progressed here lately ), and we fear that our fans wont understand why after a year of fast development it all seems to have come to a sudden regression, just because of the gstreamer porting.
For that reason, we are asking
YOU
to join our team now, and help us progressing from where we have come already. Our focus is on people with C/C++ coding experience and, if possible, some background on multimedia coding. But also Java or Delphi coders can join the team, there are a couple of ideas for tools where those could be used nicely.
If you are interested, please email me to chris AT matroska.org
Thanks
Christian
matroska project admin
the matroska container was recently celebrating its 1st birthday, and when looking back we are quite happy about the acceptance of the format from the users and developers, as well as the progress we made within a single year.
However, in our quest to replace the M$ AVI format we also noticed that there is no real future for matroska as long as it stays what it is right now, a container without media framework behind it, like AVI has/had with Video for Windows ( now DShow, at least partially ) and MOV has with Quicktime.
Now, what differentiates a container from a 'standard container' for a media framework you may ask ? Well, currently we, the matroska team, have to define a way to mux stuff into matroska ourselves, and specific for every new compression format. Of course, we have a VFW/DShow compatibility mode, allowing to mux all kind of stuff into matroska that way, and we plan to do the same for Quicktime, but this is not the same.
As soon as we can offer a real media framework with matroska becoming the standard container, people can start making their own codecs to be used in matroska, and still our video editors will be able to edit their stuff, and this is exactly what made AVI the most used container for the time being. Its also the reason why today we have the perverse situation that so-called hardware 'MPEG4 players' cant read MP4, the standard container for MPEG4, but will play MPEG4 video + MP3 in AVI. In this case the existing demand created the units, not the other way around, like normally. This demand was the result from the DivX codec ( a VfW codec ) being used to compress video with unknown compression ratios and quality, in combination with MP3 ACM codecs, on VfW based video compression/editing tools like Virtualdub, which were outputting into AVI format.
Inspired by the thought to have a real, x-platform media framework for matroska, we recently started to have a very close at Gstreamer, the media framework 'in spe' for Linux and part of GNOME already. robux4 is almost finished with porting it to Windows, and the patch is being looked at by the gstreamer dev team to find its way into their CVS. After that, the bigger part of the matroska dev team will start to port the existing plugins from Linux to win32, and also to create new plugins. Our goals are to
- make a nice player based on gstreamer, and usable for both Windows and Linux
- create a video editing tool ( TCME ) based on it, and again x-platform
- help improving Gstreamer
All this is necessary to ensure matroska's future, and to avoid it will just turn out to be a short movement with a number of suporters, until something more fancy see the light of day.
As a result of all of this, development work on a number of important new features like
- menues
- control tracks
- file linking support in players
- new tagging tools
- USF muxing
etc.
have more or less come to a halt ( there is hope for USF support, unmei has progressed here lately ), and we fear that our fans wont understand why after a year of fast development it all seems to have come to a sudden regression, just because of the gstreamer porting.
For that reason, we are asking
YOU
to join our team now, and help us progressing from where we have come already. Our focus is on people with C/C++ coding experience and, if possible, some background on multimedia coding. But also Java or Delphi coders can join the team, there are a couple of ideas for tools where those could be used nicely.
If you are interested, please email me to chris AT matroska.org
Thanks
Christian
matroska project admin