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 732109 - d3dvideosink corrupted decoded video frames - NVIDIA
d3dvideosink corrupted decoded video frames - NVIDIA
Status: RESOLVED DUPLICATE of bug 712809
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.2.4
Other Windows
: Normal critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-23 14:42 UTC by voskater15
Modified: 2014-06-23 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
corrupted video frames mp4 (245.47 KB, image/png)
2014-06-23 14:43 UTC, voskater15
Details

Description voskater15 2014-06-23 14:42:23 UTC
D3DVideoSink plugin does not work properly when decoding and displaying video frames when playing MP4 files at some computers with nVidia graphics cards.

This occurs when using gst-launch and playbin or a custom pipeline that involves d3dvideosink and MP4 video files.

For example the following input generates the following output:

input: gst-launch-1.0 -vvvv playbin uri=file:///C:\users\xxxx\videos\sample.mp4 

output screenshot: http://oi57.tinypic.com/ruu2bk.jpg

It seems that this bug is related with this one -> https://bugzilla.gnome.org/show_bug.cgi?id=712809

I have to remark that this behaviour only happens in certains computers.

This bug was reproduced on the following machine:

OS: Windows 7 Ultimate SP 1 x64
Graphics Card Device Driver: Nvidia GT 630 version 9.18.13.1106
Comment 1 voskater15 2014-06-23 14:43:46 UTC
Created attachment 279030 [details]
corrupted video frames mp4
Comment 2 Sebastian Dröge (slomo) 2014-06-23 15:14:35 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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