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 782466 - ksvideosrc: Failed to start capture
ksvideosrc: Failed to start capture
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.12.0
Other Windows
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-05-10 17:17 UTC by Michael MacIntosh
Modified: 2018-11-03 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GST_DEBUG=ks*:4 output (14.80 KB, text/plain)
2017-05-10 17:17 UTC, Michael MacIntosh
Details

Description Michael MacIntosh 2017-05-10 17:17:21 UTC
Created attachment 351570 [details]
GST_DEBUG=ks*:4 output

I am on windows 10 using gstreamer 1.12 and I am trying to capture video from an Osprey 460e analog capture card, and I was running into any difficulties using the ksvideosrc element.

It appears to be finding the device but is running into some errors.

My test pipeline:

gst-launch-1.0.exe ksvideosrc device-index=0 ! autovideosink

After executing that, I get a warning that it cant create or open ksclock.

It gives a warning about how it doesn't recognize the GUID for rgb8.

And then it says it can't start capture because of reason 0x048f (ERROR_DEVICE_NOT_CONNECTED), even though the device is connected and I can capture it through VLC, directshow, and the Osprey capture card driver software.  My best guess (looking over the source code near https://github.com/GStreamer/gst-plugins-bad/blob/master/sys/winks/gstksvideosrc.c#L961 ), it appears to be getting the error from a call to GetOverlappedResult. 

I have tested with a USB webcam to verify that the ksvideosrc does at least work for something and it does work with a USB web camera. 

Also all devices on this card appear to have the same issue.  I also get this same behavior from autovideosrc as well.

Let me know if I can provide anymore information, or if anyone has any suggestions on things to try.

Attached is my GST_DEBUG=ks*:4 output.
Comment 1 Michael MacIntosh 2017-05-17 18:05:30 UTC
Apparently this issue is caused by the crossbar filter of the capture card is not being added to the graph, so it is causing a "not connected" error to occur.
Comment 2 Jey 2017-10-15 10:18:23 UTC
(In reply to Michael MacIntosh from comment #1)
> Apparently this issue is caused by the crossbar filter of the capture card
> is not being added to the graph, so it is causing a "not connected" error to
> occur.

Hello did you find a workaround by any chance? Thanks.
Comment 3 Michael MacIntosh 2017-10-16 16:26:21 UTC
(In reply to Jey from comment #2)
> (In reply to Michael MacIntosh from comment #1)
> > Apparently this issue is caused by the crossbar filter of the capture card
> > is not being added to the graph, so it is causing a "not connected" error to
> > occur.
> 
> Hello did you find a workaround by any chance? Thanks.

I am using dshowvideosrc (which I believe is depreciated) for this.  Which you need to compile with visual studio.  I would also recommend switching it from multi-threaded COM to apartment threaded, otherwise you get a nasty handle leak when you start and stop the element.  Hope that helps.
Comment 4 GStreamer system administrator 2018-11-03 14:08:21 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/555.