problem with GST_DEBUG_DUMP_DOT_DIR & v4l2src

[somanath sahoo-2]

Hi,

I have two scenario w.r.t GST_DEBUG_DUMP_DOT_DIR which causes problem while displaying video from webcam using v4l2src and xvimagesink.

scenario 1.     If i set GST_DEBUG_DUMP_DOT_DIR environment variable before launching gst-launch-0.10 with v4l2src in order to send video data from my webcam to xvimagesink, video output window is not being displayed at all and gst-launch throwing error. the log is below

$ export GST_DEBUG_DUMP_DOT_DIR=/path-to-dot-file-dir/

$ gst-launch-0.10 v4l2src ! 'video/x-raw-yuv,width=640,height=480,framerate=30/1' ! xvimagesink

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to get value for control 9963778 on device '/dev/video0'.
Additional debug info:
v4l2_calls.c(773): gst_v4l2_get_attribute (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: Invalid argument
WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to get value for control 9963779 on device '/dev/video0'.

.......

...same error is coming endlessly..

scenario 2.     Whereas if i set GST_DEBUG_DUMP_DOT_DIR to nothing, then video window is being displayed the incoming video from my webcam with above pipeline. Hence No problem in this case. Log is below --

$ export GST_DEBUG_DUMP_DOT_DIR=
somanath@somanath:~/som_streaming/test_gst_som$ gst-launch-0.10 v4l2src ! 'video/x-raw-yuv,width=640,height=480,framerate=30/1' ! xvimagesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: Output window was closed
Additional debug info:
xvimagesink.c(1326): gst_xvimagesink_handle_xevents (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0
Execution ended after 8208983368 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Hence could any one can give me some pointer about the inconsistency between scenario 1 and 2 wrt GST_DEBUG_DUMP_DOT_DIR variable set/reset ? 

I am beginner in gstreamer, please excuse me for the way in which i am representing my queries.

PS: with GST_DEBUG_DUMP_DOT_DIR, all other src element is working fine, like videotestsrc, playbin2, etc

Thanks & Regards,
Somanath

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[oernii]

I am having this exact problem with DOT debug and v4l2src.

[Stefan Sauer]

Am 21.03.2013 11:47, schrieb oernii:
> I am having this exact problem with DOT debug and v4l2src.
By default the dot dump include element properties that are different
from the defaults. I sounds to me that reading the properties on your
life v4l2src trips it up.

I wonder if some variables are marked as readable, but in fact are not.
Can you please try a
$ export GST_DEBUG="*:6"
$ export GST_DEBUG_NO_COLOR=1
$ export GST_DEBUG_DUMP_DOT_DIR=/path-to-dot-file-dir/
$ gst-launch-0.10 2>debug.log v4l2src num-buffers=1 !
'video/x-raw-yuv,width=640,height=480,framerate=30/1' ! xvimagesink

and make the log file available (it is going to be large).

Stefan
>
>
> --
> View this message in context: http://gstreamer-devel.966125.n4.nabble.com/problem-with-GST-DEBUG-DUMP-DOT-DIR-v4l2src-tp4656432p4659206.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Arjen Veenhuizen]

For future reference, this problem appears to be still around in 1.x. See this bug report: 765801

[Nicolas Dufresne-4]

Le vendredi 29 avril 2016 à 02:14 -0700, Arjen Veenhuizen a écrit :
> For future reference, this problem appears to be still around in 1.x.
> See
> this bug report:  765801 <https://bugzilla.gnome.org/show_bug.cgi?id=
> 765801>  

Can you clarify what version / git commit you are running. I have
retested the fix that was merged:

    commit df9eed0ab55917b0719d784156d8d11f9b8b0136
    Author: Dimitrios Katsaros <    [hidden email]    >
    Date:   Thu Nov 26 13:15:06 2015 +0100

        v4l2: Change warning handling to break infinite message loop

Still work as expected. I just backported it to 1.8 branch, it will be
released in 1.8.2.

cheers,
Nicolas



_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Arjen Veenhuizen]

I was on a5369c6be36fb22b505bb765f987212b39bcf408 (Feb 10, 2016)
I just applied the patch in 758703 and I can confirm that this solves the problem.

[Nicolas Dufresne-4]

Le mardi 03 mai 2016 à 00:07 -0700, Arjen Veenhuizen a écrit :
> I was on a5369c6be36fb22b505bb765f987212b39bcf408 (Feb 10, 2016)
> I just applied the patch in  758703
> <https://bugzilla.gnome.org/show_bug.cgi?id=758703>   and I can
> confirm that
> this solves the problem.

Great, thanks for reporting back.

Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel