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 740620 - decklinksink 59.94i and 60i are 30 fps.
decklinksink 59.94i and 60i are 30 fps.
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-11-24 12:34 UTC by Dušan Poizl
Modified: 2018-01-25 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dušan Poizl 2014-11-24 12:34:22 UTC
This commit http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/sys/decklink/gstdecklink.cpp?id=a8f94fe1e153c615f8991d5828e379fdeacda614

change framerate of 1080 59.94i/60i modes to 60000/1001 and 60/1. But it should be 30000/1001 and 30/1. The last chage for progressive mode is correct.

If you run "gst-launch-1.0 videotestsrc num-buffers=60 ! decklinksink mode=11" or mode=12 it takes 2 seconds to complete and not 1 second as you would expect.
Comment 1 Sebastian Dröge (slomo) 2014-11-24 13:00:38 UTC
Here it takes 1 second instead of 2 as expected:

$ gst-launch-1.0 videotestsrc num-buffers=60 ! decklinksink mode=12
Setting pipeline to PAUSED ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:01.003848638

This is on Linux with a 4k Extreme via HDMI. What are you running?
Comment 2 Dušan Poizl 2014-11-24 13:12:44 UTC
Decklink Mini Monitor and Intesity Pro both HDMI. Can you try mode=10 because 1080 50i have on other hand 25/1
Comment 3 Dušan Poizl 2014-11-24 13:13:51 UTC
I forgot I run Linux too with latest blackmagic driver.
Comment 4 Sebastian Dröge (slomo) 2014-11-24 13:14:47 UTC
Yes, I had to change it to 50/1 too to make it work properly here. Also using the latest driver here.

The Mini Monitor and Intensity Pro, are they using the blackmagic or blackmagic-io driver?
Comment 5 Dušan Poizl 2014-11-24 13:59:20 UTC
lsmod show only blackmagic
Comment 6 Sebastian Dröge (slomo) 2014-11-24 14:14:58 UTC
Hmmm, but the synchronization in there is fishy anyway :) I'm going to work on cleaning all that up a bit in the next weeks, hopefully that will magically make this bug / inconsistency go away. Or maybe the blackmagic (not blackmagic-io) driver expects different settings than the other.
Comment 7 Sebastian Dröge (slomo) 2014-12-19 13:58:40 UTC
Please test if this is still a problem with latest GIT master. The decklink elements were rewritten and handle synchronization properly now (hopefully).
Comment 8 Tim-Philipp Müller 2018-01-25 12:48:11 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!