[Bug 758219] uvch264src freezes when using its "vidsrc"

[GStreamer (GNOME Bugzilla)]

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

Herb Peyerl <hpeyerl+gst at beer.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hpeyerl+gst at beer.org

--- Comment #5 from Herb Peyerl <hpeyerl+gst at beer.org> ---
Created attachment 332105
  --> https://bugzilla.gnome.org/attachment.cgi?id=332105&action=edit
GST_DEBUG=*:6 output of same behavior.

I have the same problem.  OS is Ubuntu 16.04, kernel is "Linux python
4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux", gstreamer is 1.9.1 with all 1.9.1 plugins built natively.

Camera is a Logitech C930e.  v4l2-ctl --all says:

Driver Info (not using libv4l2):
    Driver name   : uvcvideo
    Card type     : Logitech Webcam C930e
    Bus info      : usb-0000:00:14.0-3
    Driver version: 4.4.13
    Capabilities  : 0x84200001
        Video Capture
        Streaming
        Extended Pix Format
        Device Capabilities
    Device Caps   : 0x04200001
        Video Capture
        Streaming
        Extended Pix Format
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
    Width/Height      : 320/240
    Pixel Format      : 'YUYV'
    Field             : None
    Bytes per Line    : 640
    Size Image        : 153600
    Colorspace        : sRGB
    Transfer Function : Default
    YCbCr Encoding    : Default
    Quantization      : Default
    Flags             :
Crop Capability Video Capture:
    Bounds      : Left 0, Top 0, Width 320, Height 240
    Default     : Left 0, Top 0, Width 320, Height 240
    Pixel Aspect: 1/1
Selection: crop_default, Left 0, Top 0, Width 320, Height 240
Selection: crop_bounds, Left 0, Top 0, Width 320, Height 240
Streaming Parameters Video Capture:
    Capabilities     : timeperframe
    Frames per second: 10.000 (10/1)
    Read buffers     : 0
                     brightness (int)    : min=0 max=255 step=1 default=128
value=128
                       contrast (int)    : min=0 max=255 step=1 default=128
value=128
                     saturation (int)    : min=0 max=255 step=1 default=128
value=128
 white_balance_temperature_auto (bool)   : default=1 value=1
                           gain (int)    : min=0 max=255 step=1 default=0
value=185
           power_line_frequency (menu)   : min=0 max=2 default=2 value=2
      white_balance_temperature (int)    : min=2000 max=7500 step=1
default=4000 value=3168 flags=inactive
                      sharpness (int)    : min=0 max=255 step=1 default=128
value=128
         backlight_compensation (int)    : min=0 max=1 step=1 default=0 value=0
                  exposure_auto (menu)   : min=0 max=3 default=3 value=1
              exposure_absolute (int)    : min=3 max=2047 step=1 default=250
value=666
         exposure_auto_priority (bool)   : default=0 value=1
                   pan_absolute (int)    : min=-36000 max=36000 step=3600
default=0 value=-36000
                  tilt_absolute (int)    : min=-36000 max=36000 step=3600
default=0 value=0
                 focus_absolute (int)    : min=0 max=255 step=5 default=0
value=35 flags=inactive
                     focus_auto (bool)   : default=1 value=1
                  zoom_absolute (int)    : min=100 max=400 step=1 default=100
value=100



Command line is:

DEBUG="*:6"
GST_DEBUG=$DEBUG GST_DEBUG_NO_COLOR=1
/home/hpeyerl/gst/runtime/bin/gst-launch-1.0 -v -e uvch264src
initial-bitrate=5000000 average-bitrate=5000000 iframe-period=3000 \
    device=/dev/video0 name=src auto-start=true \
    src.vfsrc ! queue !
video/x-raw,format=\(string\)YUY2,width=320,height=240,framerate=10/1 !
xvimagesink sync=false \
    src.vidsrc ! queue ! video/x-h264,width=1920,height=1080,framerate=30/1 !
h264parse ! avdec_h264 ! xvimagesink sync=false


guvcview can successfully display the h264 stream at 1920x1080x30 with almost
no perceptible latency and low CPU.

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