After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712592 - d3dhelpers.c(2221): d3d_class_init: Failed to register window class: 1410 on second creation of a simple pipeline
d3dhelpers.c(2221): d3d_class_init: Failed to register window class: 1410 on ...
Status: RESOLVED DUPLICATE of bug 726026
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.2.1
Other Windows
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-18 13:44 UTC by Pzkfw
Modified: 2016-06-15 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pzkfw 2013-11-18 13:44:28 UTC
Here is another one with the same problem (has full example):
http://stackoverflow.com/questions/19478692/gstreamer-video-playback-fails-in-windows-at-second-play-time-when-the-video-fi

The way I do it is basically:

    GstElement* pipeline;
    gst_init(NULL, NULL);
    pipeline = gst_element_factory_make("playbin", "player");
    GstElement *sink = gst_element_factory_make ("d3dvideosink","video-sink");
    g_object_set(GST_OBJECT(pipeline),"video-sink",sink,NULL);
    g_object_set(GST_OBJECT(pipeline), "uri",g_filename_to_uri(fileName.c_str(),
                 NULL, NULL), NULL);
    g_object_set(GST_OBJECT(sink), "force-aspect-ratio", TRUE, NULL);
	gst_object_unref(sink);

and deallocating with: 

    gst_element_set_state (pipeline, GST_STATE_NULL);
    gst_object_unref (GST_OBJECT (pipeline));

I made sure the refcount is 0 there so there's no memory leak. The next time I go through the same procedure I get the error.
Comment 1 Tobias 2016-06-15 10:55:01 UTC
I had a similar error on my windows machine and just wanted to point out that this issue seems to be resolved with newer version of GStreamer. I switched from 1.2.3 to 1.4.0 and did not see this error again.

Please also refer to https://bugzilla.gnome.org/show_bug.cgi?id=726026
Comment 2 Tim-Philipp Müller 2016-06-15 11:05:32 UTC
Thanks Tobias!

*** This bug has been marked as a duplicate of bug 726026 ***