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 697336 - d3dvideosink: respect PAR in navigation coordinates
d3dvideosink: respect PAR in navigation coordinates
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.x
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-05 12:09 UTC by Andoni Morales
Modified: 2018-05-07 15:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
d3dvideosink: respect PAR in navigation coordinates (2.74 KB, patch)
2013-04-05 12:09 UTC, Andoni Morales 		none Details | Review
d3dvideosink: respect PAR in navigation coordinates (2.75 KB, patch)
2013-04-12 11:25 UTC, Andoni Morales 		needs-work Details | Review

Description Andoni Morales 2013-04-05 12:09:11 UTC 
Created attachment 240724 [details] [review]
d3dvideosink: respect PAR in navigation coordinates

Fix navigation respecting the pixel aspect ratio in the coordinates.
Comment 1 Sebastian Dröge (slomo) 2013-04-06 07:45:56 UTC 
Please update this patch to apply cleanly to latest GIT master
Comment 2 Andoni Morales 2013-04-12 11:25:33 UTC 
Created attachment 241341 [details] [review]
d3dvideosink: respect PAR in navigation coordinates

-sink->width
-sink->height
+sink->info.width
+sink->info.height
Comment 3 Sebastian Dröge (slomo) 2013-04-15 06:46:32 UTC 
Comment on attachment 241341 [details] [review]
d3dvideosink: respect PAR in navigation coordinates

This doesn't apply against latest master
Comment 4 Alexandre Franke 2017-07-17 18:33:54 UTC 
Andoni, can you please update the patch?
Comment 5 Sebastian Dröge (slomo) 2018-05-07 15:39:52 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!