gstreamer-devel Digest, Vol 97, Issue 63

David Ing ding at
Tue Mar 12 15:02:02 UTC 2019

I am sorry to jump into this conversation late.

I am currently using the binaries for 1.14.4 which are published here:  I believe they are
built using Cerbero and mingw (gcc, autotools, etc.).

I use these binaries in a VS 2017 C++ program (including the libav plugin),
but I am not using Matlab in any way.  Previously I was using earlier
binaries with VS 2015 before I moved to VS 2017.  In general, I have not
observed the kinds of problems that Marc is describing.  (Actually I have,
but it is always a bug in my own c++ code.)  However, I have
**occasionally** observed a problem where the program behaves strangely
when the native debugger (Visual Studio) is attached.  But it sounds like
you are not running with a debugger attached.

If you can run your program inside a debugger, you can use a tool called
AppVerifier or gflags to help diagnose heap corruption problems.  For

If you are really stuck you can try to learn how to use WinDBG ... It is
difficult to figure out but sometimes it is the only way to diagnose these
kinds of problems.

On Tue, Mar 12, 2019 at 4:58 AM Nirbheek Chauhan <nirbheek.chauhan at>

> On Tue, Mar 12, 2019 at 5:11 PM Marc Gelinas <mgelinas at> wrote:
> > Would it be possible for me then to build GStreamer with MSVC?
> You can do this starting with the 1.15.2 development release:
> > Any caveats?
> Some plugins are disabled, and only x86_64 is currently available. For
> more details, see:
> > Any plans in the very near future for the GStreamer team to provide
> libraries built with MSVC?
> The 1.15.2 release shipped with x86_64 binaries built with MSVC:
> Cheers,
> Nirbheek
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list