[Bug 747426] New: decklink: video modes 14, 15, 16 do not work

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=747426

            Bug ID: 747426
           Summary: decklink: video modes 14, 15, 16 do not work
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: vliaskov at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Testing on a decklink Mini monitor card.

02:00.0 Multimedia video controller: Blackmagic Design DeckLink Mini Monitor
    Subsystem: Blackmagic Design DeckLink Mini Monitor
Capabilities: [40] Power Management version 3
    Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [58] Express Endpoint, MSI 00
    Kernel driver in use: blackmagic_driver


Most modes work. However modes 14, 15, 16:

 (14): HD1080 50p       - 1080p50
 (15): HD1080 59.94p    - 1080p5994
 (16): HD1080 60p       - 1080p60

do not work. E.g. for mode 14:

gst-launch-1.0 filesrc location=/opt/Videos/test.avi ! decodebin name=decoder  
! videoscale ! videoconvert   ! videorate  ! decklinkvideosink device-number=0 
mode=14

0:00:00.063610583 27603 0x7faa800061e0 DEBUG      decklinkvideosink
gstdecklinkvideosink.cpp:273:gst_decklink_video_sink_set_caps:<deck> Setting
caps video/x-raw, width=(int)1920, height=(int)1080,
pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive,
framerate=(fraction)50/1, format=(string)UYVY, colorimetry=(string)bt709,
chroma-site=(string)mpeg2
0:00:00.063679302 27603 0x7faa800061e0 WARN       decklinkvideosink
gstdecklinkvideosink.cpp:287:gst_decklink_video_sink_set_caps:<deck> Failed to
enable video output


dmesg output is "blackmagic[ERROR]: Failed to enable video output (1002)". I am
not sure if it's a wrong setting on gstreamer side or a driver issue. I haven't
found documentation for the 1002 error code yet. 

Tested on master repos from 5/5/2015

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.