[aravis] Re: Does the aravis GStreamer plugin implement a GstDeviceProvider and register it?

  • From: Emmanuel Pacaud <emmanuel.pacaud@xxxxxxxxxxxxx>
  • To: aravis@xxxxxxxxxxxxx
  • Date: Tue, 11 Sep 2018 14:38:37 +0200

Hi Matthew,

Le lun. 3 sept. 2018 à 2:35, Matthew Thyer <matthew.thyer@xxxxxxxxxxxxxxx> a écrit :

I’m now trying to validate whether a user supplied FOURCC is valid for the camera but this seems to rely on the aravis plugin including a GstDeviceProvider and registering it. You can see why this is required from GStreamer-devel mailing list message: https://lists.freedesktop.org/archives/gstreamer-devel/2018-August/069054.html

So far I have tried to query the device using the commandline gst-device-monitor-1.0 as follows but I cannot get the camera to appear:
$ gst-device-monitor-1.0 --gst-plugin-path=/usr/local/aravis-0.5/lib/gstreamer-1.0 --gst-plugin-load=aravis --follow

I am able to successfully query the camera with arv-tool-0.6:
$ /usr/local/aravis-0.5/bin/arv-tool-0.6
PointGrey-0115138B (USB3)

The Gstreamer plugin bundled in aravis is quite simple, and does not support device discovery.

A simple pipeline would be:

gst-launch-1.0 aravissrc camera-name="PointGrey-0115138B" ! videoconvert ! xvimagesink

You can check which pixel format are supported by your camera using:

arv-tool --name="PointGrey-0115138B" control PixelFormat

The correspondance between aravis pixel formats and GStreamer formats are unfortunately only available in aravis sources:

https://github.com/AravisProject/aravis/blob/9d21cda6499ab49ba10a6a0cbb3b317149b70b33/src/arvmisc.c#L590-L687

Cheers,

        Emmanuel.

Other related posts: