[Matroska-general] Get matroska in the news again

Jory jcsston at wiesneronline.net
Thu Mar 25 04:32:00 CET 2004


----- Original Message -----
From: "Steve Lhomme" <steve.lhomme at free.fr>
To: "General talk about Matroska and other products"
<matroska-general at lists.matroska.org>
Sent: Wednesday, March 24, 2004 9:59 AM
Subject: Re: [Matroska-general] Get matroska in the news again


> >> 2. TCME :
> >>
> >> After the meeting last friday night it became obvious that jcsston has
> >> done some great work with respect to TCME already. His work was based
> >> on robux4's native MSVC port, and he has successfully ported many
> >> different plugins already. Only a nasty bug in the matroska muxer
>
> It's good if the Windows port can help to improve the GStreamer plugin.
> The first positive point (before many others ?).
>
> >> makes it impossible to release a first beta version already, including
> >> the capability to make a simple transcoder based on a XviD encoder
> >> plugin, allowing to create native MPEG4 MKV files from AVIsynth ( AVI
> >> ) input files.
>
> AVISynth in GStreamer ? How does it work ? Or GStreamer can read .avs
> natively under windows (or under all platforms) ?
>
> >> I will talk to Jory how we proceed here now, as it was decided that
> >> Gstreamer will be ported using mingw instead, making most of jcsston's
>
> It's sad to restrict to only one compiler when it's quite easy to have
> MSVC7 and MSVC6 support. Only the log can be a problem, otherwise it
> should work fine and everyone can have it's preferred development
> environment.
>
> >> have a working solution based on a fork of Gstreamer, than no solution
> >> at all IMO. Mosu promised to try to port Gstreamer via mingw this
> >> weekend, but i know he was busy with other stuff.
>
> I'm back at work these days, I can help there. I have 3 development
> machines now (and only just one brain), which an different OS for each.
>
> >> Jory also was briefly mentioning the possibility to use something like
> >> a hybrid solution, where the gstreamer core gets ported via mingw, but
> >> the plugins are ported natively, using MSVC for the compilation. I
>
> If the plugins are DLLs, then yes, you can use whatever compiler you want.
>
GStreamer plugins use vararg marcos to declare the pads and types the plugin
supports. The DLL exporting is not the problem. :/




More information about the Matroska-general mailing list