During the last couple of months we have been working on porting
GStreamer to Windows using the OAbuild project. We introduced some
modifications to OAbuild in order to improve compatibility and provide
video decoding and encoding in a larger number of codecs.
Changelog: ·Compile ffmpeg with mingw/msys with full codec support. ·Remove the ffmpeg project from OAbuild and link the ffmpeg plugin to the mingw/msys ffmpeg libraries. ·Remove the GLib project from OAbuild and link GStreamer to the GLib version provided
·Update liboil to a newer version to compile the volume plugin.
·Compile libmad for Windows and add the libraries to the Gstreamer's dependencies to provide mp3 decoding support.·Change the ffmpeg plugin code to compile it using VS. ·Change the qtdemux plugin code to compile it using VS.
·Add the mad plugin to OAbuild.
To do:·Add the asfdemux plugin to OAbuild. ·Remove the Direct Show wrapper and use the ffmepg plugin for all the decoding stuff. ·Add the xvid plugin to OAbuild. ·Change the xvid plugin code to complile it usin VS. ·Add the mpeg2decoder plugin to OAbuild. ·Add the mpegstream plugin to OAbuild. ·Make the x264 plugin work ·Improve mpeg2 decoding/demuxing support ·Add dvd navigation support You can find the installers at: http://forja.rediris.es/frs/?group_id=96 Andoni Morales Alastruey Andrés Colubri ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Hi
Nice, could you plan to add opengl plugin in the next release ? http://diracvideo.org/git?p=gst-plugins-gl.git;a=summary Sincerely Julien 2009/1/7 Andoni Morales <[hidden email]> During the last couple of months we have been working on porting GStreamer to Windows using the OAbuild project. We introduced some modifications to OAbuild in order to improve compatibility and provide video decoding and encoding in a larger number of codecs. ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Sure!
We are planning to create a project in sourceforge to encourage every to work on adding new plugins. Regards Andoni Morales 2009/1/7 Julien Isorce <[hidden email]> Hi ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Administrator
|
Hi,
We're about to switch the whole of GStreamer to git soon, I think it would be nice if we could centralize OABuild alongside GStreamer in the same repositories. We already have a jhbuild module there. Tell us if you're interested, and other GStreamer hackers/devs can also raise their voice if they're against/for that idea, Edward On Wed, 2009-01-07 at 17:36 +0100, Andoni Morales wrote: > Sure! > We are planning to create a project in sourceforge to encourage every > to work on adding new plugins. > > Regards > Andoni Morales > > 2009/1/7 Julien Isorce <[hidden email]> > Hi > > Nice, could you plan to add opengl plugin in the next > release ? > > http://diracvideo.org/git?p=gst-plugins-gl.git;a=summary > > Sincerely > > Julien > > 2009/1/7 Andoni Morales <[hidden email]> > > During the last couple of months we have been working > on porting GStreamer to Windows using the OAbuild > project. We introduced some modifications to OAbuild > in order to improve compatibility and provide video > decoding and encoding in a larger number of codecs. > > Changelog: > > ·Compile ffmpeg with mingw/msys with full codec > support. > ·Remove the ffmpeg project from OAbuild and link the > ffmpeg plugin to the mingw/msys ffmpeg libraries. > ·Remove the GLib project from OAbuild and link > GStreamer to the GLib version provided > > with the GTK+ win32 installer (in this way GStreamer > can be used by GTK applications). > ·Update liboil to a newer version to compile the > volume plugin. > ·Change the ffmpeg plugin code to compile it using VS. > ·Change the qtdemux plugin code to compile it using > VS. > > ·Compile libmad for Windows and add the libraries to > the Gstreamer's dependencies to provide mp3 decoding > support. > ·Add the mad plugin to OAbuild. > ·Add the asfdemux plugin to OAbuild. > ·Remove the Direct Show wrapper and use the ffmepg > plugin for all the decoding stuff. > ·Add the xvid plugin to OAbuild. > ·Change the xvid plugin code to complile it usin VS. > ·Add the mpeg2decoder plugin to OAbuild. > ·Add the mpegstream plugin to OAbuild. > > > To do: > ·Make the x264 plugin work > ·Improve mpeg2 decoding/demuxing support > ·Add dvd navigation support > > > You can find the installers at: > http://forja.rediris.es/frs/?group_id=96 > > > Andoni Morales Alastruey > Andrés Colubri > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Andoni Morales
hi,
do you have any description what you change and what you made? i'm mainly working with the mingw sig for fedora to be able to push mingw-gstreamer* into fedora. most of the basic stuff are ready and it's only time when we able to push gstreamer stuff too. but it'd help a lot if you can send patches and compile commands what you used to create these builds. thanks in advance. yours. Andoni Morales wrote: > During the last couple of months we have been working on porting > GStreamer to Windows using the OAbuild project. We introduced some > modifications to OAbuild in order to improve compatibility and provide > video decoding and encoding in a larger number of codecs. > > Changelog: > > ·Compile ffmpeg with mingw/msys with full codec support. > ·Remove the ffmpeg project from OAbuild and link the ffmpeg plugin to > the mingw/msys ffmpeg libraries. > ·Remove the GLib project from OAbuild and link GStreamer to the GLib > version provided > with the GTK+ win32 installer (in this way GStreamer can be used by GTK > applications). > ·Update liboil to a newer version to compile the volume plugin. > ·Change the ffmpeg plugin code to compile it using VS. > ·Change the qtdemux plugin code to compile it using VS. > ·Compile libmad for Windows and add the libraries to the Gstreamer's > dependencies to provide mp3 decoding support. > ·Add the mad plugin to OAbuild. > ·Add the asfdemux plugin to OAbuild. > ·Remove the Direct Show wrapper and use the ffmepg plugin for all the > decoding stuff. > ·Add the xvid plugin to OAbuild. > ·Change the xvid plugin code to complile it usin VS. > ·Add the mpeg2decoder plugin to OAbuild. > ·Add the mpegstream plugin to OAbuild. > > To do: > ·Make the x264 plugin work > ·Improve mpeg2 decoding/demuxing support > ·Add dvd navigation support > > > You can find the installers at: > http://forja.rediris.es/frs/?group_id=96 > > > Andoni Morales Alastruey > Andrés Colubri > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > > > ------------------------------------------------------------------------ > > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Edward Hervey
We're about to switch the whole of GStreamer to git soon, I think it
would be nice if we could centralize OABuild alongside GStreamer in the I think it's a good idea to centralize OABuild along GStreamer in the same repository. The problem is that the OABuild "method" requires changes in the code of some plugins. A posible solution is to use preprocesor directives as these changes just affect to 3 or 4 plugins. Besides this methods requires external depencies (GLib, xvid, x264, oil, etc..), that cannot be complied with Visual Studio and must me complied with mingw/msys. This is not a big problem as they can be added in the OAbuild module. Regards, Andoni Morales ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Administrator
|
On Thu, 2009-01-08 at 14:31 +0100, Andoni Morales wrote:
> We're about to switch the whole of GStreamer to git soon, I think it > would be nice if we could centralize OABuild alongside > GStreamer in the > same repositories. We already have a jhbuild module there. > > Tell us if you're interested, and other GStreamer > hackers/devs can > also raise their voice if they're against/for that idea, > > I think it's a good idea to centralize OABuild along GStreamer in the > same repository. The problem is that the OABuild "method" requires > changes in the code of some plugins. A posible solution is to use > preprocesor directives as these changes just affect to 3 or 4 > plugins. Can those changes be pushed upstream ? > Besides this methods requires external depencies (GLib, xvid, x264, > oil, etc..), that cannot be complied with Visual Studio and must me > complied with mingw/msys. This is not a big problem as they can be > added in the OAbuild module. > > Regards, > Andoni Morales > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
On Thu, Jan 8, 2009 at 3:01 PM, Edward Hervey <[hidden email]> wrote:
> On Thu, 2009-01-08 at 14:31 +0100, Andoni Morales wrote: >> I think it's a good idea to centralize OABuild along GStreamer in the >> same repository. The problem is that the OABuild "method" requires >> changes in the code of some plugins. A posible solution is to use >> preprocesor directives as these changes just affect to 3 or 4 >> plugins. > > Can those changes be pushed upstream ? For ffmpeg for example, no. They are syntax changes needed to make msvc happy but that compile just fine with gcc. And they are A LOT (thousands of lines). Ciao Alessandro ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
I don't use MSVC to build ffmpeg. All the external libraries are built using mingw/msys and then I add to the OAbuild "builddeps" dir the includes, dll's and impot libraries used by OABuild. The problem with the original OABuild method is that all the external libraries are built using MSVC, and that's why it doesn't provide support for many external plugins, because not all the external dependencies can be compiled using MSVC. The changes in the GStreamer code are just a few lines. Take a look at http://codeanticode.wordpress.com/2008/09/12/the-gstreamer-adventure-part-i-creating-a-windows-installer/. For the ffmpeg plugin the lines to changes are 4:
------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Andoni Morales
Fra: Andoni Morales
[mailto:[hidden email]] We're about to switch the whole of GStreamer to git
soon, I think it
------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Andoni Morales
By the way,
It would be nice to update in the web page the windows binaries with these ones. Regards, Andoni Morales ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Andoni Morales
(Sorry for spamming the list with an empty reply before sending this one,
I was fighting with a brain-dead e-mail client to get the quoting right and ended up hitting the wrong hotkey.) On Thu, Jan 8, 2009 at 2:31 PM, Andoni Morales <[hidden email]> wrote: > We're about to switch the whole of GStreamer to git soon, I think it >> >> would be nice if we could centralize OABuild alongside GStreamer in the >> same repositories. We already have a jhbuild module there. >> >> Tell us if you're interested, and other GStreamer hackers/devs can >> also raise their voice if they're against/for that idea, > > I think it's a good idea to centralize OABuild along GStreamer in the same > repository. The problem is that the OABuild "method" requires changes in the > code of some plugins. A posible solution is to use preprocesor directives > as these changes just affect to 3 or 4 plugins. > Besides this methods requires external depencies (GLib, xvid, x264, oil, > etc..), that cannot be complied with Visual Studio and must me complied with > mingw/msys. This is not a big problem as they can be added in the OAbuild > module. I would vote against pushing the project files upstream as OABuild's basic design is broken (see below). As of recently, pending announcement today actually :), OABuild is officially dead and no longer maintained by me. Its replacement is OAHBuild, which is OABuild completely redone from scratch by Haakon Sporsheim. Some of its advantages: - Isn't monolithic like OABuild, so the different modules are independent in the sense that you no longer need them placed in a certain layout in the filesystem. In other words you can choose to install GLib and GStreamer -core from MSIs, and build /only/ -bad yourself if you're fixing bugs in a plugin, you don't need to build any of the dependencies. This also means that the project files are completely local to the module and can thus be pushed upstream. The only dependency if you want to build things yourself is the common OAH component. - Integrates with, and makes heavy use of, pkg-config. - Integrated easy way of building .msm packages. - Designed to work with the Express Edition of MSVS 2008, the commercial version is no longer a requirement to build it using the IDE. - Cleaner, less project files. OAHBuild can be found here: https://code.launchpad.net/oah The existing GStreamer modules in OABuild aren't yet forward-ported to OAH, but this is work in progress. Cheers, Ole André ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
On Thu, Jan 8, 2009 at 5:14 PM, Ole André Vadla Ravnås <[hidden email]> wrote:
> (Sorry for spamming the list with an empty reply before sending this one, > I was fighting with a brain-dead e-mail client to get the quoting right and > ended up hitting the wrong hotkey.) > > On Thu, Jan 8, 2009 at 2:31 PM, Andoni Morales <[hidden email]> wrote: >> We're about to switch the whole of GStreamer to git soon, I think it >>> >>> would be nice if we could centralize OABuild alongside GStreamer in the >>> same repositories. We already have a jhbuild module there. >>> >>> Tell us if you're interested, and other GStreamer hackers/devs can >>> also raise their voice if they're against/for that idea, >> >> I think it's a good idea to centralize OABuild along GStreamer in the same >> repository. The problem is that the OABuild "method" requires changes in the >> code of some plugins. A posible solution is to use preprocesor directives >> as these changes just affect to 3 or 4 plugins. >> Besides this methods requires external depencies (GLib, xvid, x264, oil, >> etc..), that cannot be complied with Visual Studio and must me complied with >> mingw/msys. This is not a big problem as they can be added in the OAbuild >> module. > OAHBuild can be found here: > https://code.launchpad.net/oah Oops, not quite the right URL, should've been: https://launchpad.net/oah Cheers, Ole André ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Ole André Vadla Ravnås
Good to know this! I'll be waiting until it's ready to port all these changes to OAH. ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Ole André Vadla Ravnås
Its replacement is OAHBuild, which is OABuild completely redone from scratch I would also like to point out (once again) that OAH uses pkg-config for compiler and linker switches instead of project dependencies/references in Visual Studio. Hence, there is no monolitic "master" build/solution file, but separate build/solution file for each module which could reside in each respective module repository. For GStreamer this would be (to follow the OAH convention) in win32/oah, which is beside the existing win32/vs*. The existing GStreamer modules in OABuild aren't yet forward-ported to OAH, but Yes, I've already started the work, but currently I'm sort of waiting for the upcoming cvs->git migration. Ref. Edward Hervey's mail to mailinglist a couple of days ago. :) Regards, Haakon ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
I would also like to point out (once again) that OAH uses pkg-config for compiler and linker switches instead of project dependencies/references in Visual Studio. Hence, there is no monolitic "master" build/solution file, but separate build/solution file for each module which could reside in each respective module repository. For GStreamer this would be (to follow the OAH convention) in win32/oah, which is beside the existing win32/vs*. I think the adoption of pkg-config for compiler and linker switches is an exelent choice as it will make easier to compile plugins with external depencies, which was one the problems of OABuild. ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by Andoni Morales
Hi,
I was trying to use your packages ... but You are using glib 2.16.1 according to the "glibconfig.h" which is deployed with your installers (http://forja.rediris.es/frs/?group_id=96) In this doc page http://library.gnome.org/devel/glib/stable/glib-Threads.html#g-once-init-enter we can read that there is a function called g_once_init_enter since glib 2.14. I go into "gthread.h" (which is deployed with your installers) I cannot see any g_once_init_enter definition. It causes a failure when using gstutils.h: "#if GLIB_CHECK_VERSION (2, 14, 0) #define __gst_once_init_enter(val) (g_once_init_enter (val)) #define __gst_once_init_leave(val,newval) (g_once_init_leave (val, newval)) #else #define __gst_once_init_enter(val) (G_UNLIKELY (*(val) == 0)) #define __gst_once_init_leave(val,newval) (*(val) = newval) #endif " Any explanations ? Sincerely Julien Le 7 janvier 2009 12:42, Andoni Morales <[hidden email]> a écrit : During the last couple of months we have been working on porting GStreamer to Windows using the OAbuild project. We introduced some modifications to OAbuild in order to improve compatibility and provide video decoding and encoding in a larger number of codecs. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Hi all,
I am trying to build some gstreamer plug-ins under Windows Vista using the installers at (http://forja.rediris.es/frs/?group_id=96), and the same compilation errors appears: error C3861: 'g_once_init_enter': identifier not found regarding g_once_init_enter not being present, just as Julien explained on his mail. Any help would be much appreciated, Best, --Xavier Grasa > Hi, > > I was trying to use your packages ... but > > You are using glib 2.16.1 according to the "glibconfig.h" which is > deployed with your installers (http://forja.rediris.es/frs/?group_id=96) > > In this doc page > http://library.gnome.org/devel/glib/stable/glib-Threads.html#g-once-init-enter > we can read that there is a function called g_once_init_enter since > glib 2.14. > I go into "gthread.h" (which is deployed with your installers) I > cannot see any g_once_init_enter definition. > > It causes a failure when using gstutils.h: > > "#if GLIB_CHECK_VERSION (2, 14, 0) > #define __gst_once_init_enter(val) (g_once_init_enter (val)) > #define __gst_once_init_leave(val,newval) (g_once_init_leave (val, > newval)) > #else > #define __gst_once_init_enter(val) (G_UNLIKELY (*(val) == 0)) > #define __gst_once_init_leave(val,newval) (*(val) = newval) > #endif > " > > Any explanations ? > > Sincerely > > Julien ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Thanks for the advice...
I was using the gtk binaries provided by the mono installer which are a little bit updated. I'll recompile GSStreamer using the binaries provided by the GTK+ team which usesthe 2.18 version of GLib. I think it will be ready for the next week
2009/1/19 xavier grasa <[hidden email]> Hi all, ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by xavier grasa
The solution is to replace all glib .dll, .h, .a, .lib by the last glib packages (2.18.4) from http://www.gtk.org/download-windows.html.
So : - install the 2 packages ( http://forja.rediris.es/frs/?group_id=96) - remove include/glib - remove glib .dll(s), .lib and .a (and .def) . I mean keep only gstreamer dev. - unzip glib glib_2.18.4-1_win32.zip and glib-dev_2.18.4-1_win32.zip There is no pb with this because of "acsendent compatibilty" of glib2.x.x. Note I advise you to rebuild everything by your self. Cheers J. 2009/1/19 xavier grasa <[hidden email]> Hi all, ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |