Here you go

ioctl: VIDIOC_ENUM_FMT
    Index       : 0
    Type        : Video Capture
    Pixel Format: 'YUYV'
    Name        : YUYV 4:2:2
        Size: Discrete 640x360
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 320x240
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 640x480
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 960x720
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 1280x720
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)

    Index       : 1
    Type        : Video Capture
    Pixel Format: 'MJPG' (compressed)
    Name        : Motion-JPEG
        Size: Discrete 640x360
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 320x240
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 640x480
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 960x720
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)
        Size: Discrete 1280x720
            Interval: Discrete 0.033s (30.000 fps)
            Interval: Discrete 0.040s (25.000 fps)
            Interval: Discrete 0.050s (20.000 fps)
            Interval: Discrete 0.067s (15.000 fps)
            Interval: Discrete 0.100s (10.000 fps)
            Interval: Discrete 0.200s (5.000 fps)


2015-11-25 12:12 GMT-07:00 Éloi Bail <eloi.b...@savoirfairelinux.com>:

> Hi Ales,
>
> Thanks for your answer.
>
> Could you please give me the result of command :
>
> v4l2-ctl --list-formats-ext
>
> Regards,
>
> Eloi
>
> Eloi BAIL
> Consultant en logiciel libre
> Savoir-faire Linux
> Tel: + 1 (514) 276 5468 ext. 175
>
> ----- Le 25 Nov 15, à 14:02, Stepan Salenikovich
> stepan.salenikov...@savoirfairelinux.com a écrit :
>
> > Hmm... can you try changing the resolution in the yaml to see if that
> works?
> > Maybe try setting it to something really low so that its obvious whether
> it
> > worked or not. Again, make sure its a valid resolution in cheese.
> >
> > -stepan
> >
> > ----- Original Message -----
> > From: "Ales Katona" <almin...@gmail.com>
> > To: "Stepan Salenikovich" <stepan.salenikov...@savoirfairelinux.com>
> > Cc: ring@lists.savoirfairelinux.net
> > Sent: Wednesday, November 25, 2015 1:55:25 PM
> > Subject: Re: [Ring] 10 FPS?
> >
> > The yaml edit doesn't seem to work.
> >
> > I used 30 for FPS but it's still choppy. It doesn't revert to 5 or 10
> > however, even if I set it back to 5 and save. Also if I restart ring the
> > selections are blank, as if it didn't save anything. I wonder if it maybe
> > auto-detects, goes to lowest FPS and then just doesn't save/load the
> stored
> > settings properly?
> >
> > My yaml file still has 30 in it after my edit, even when I set it back
> to 5
> > in the UI and saved.
> >
> > Ales
> >
> > 2015-11-25 11:49 GMT-07:00 Stepan Salenikovich <
> > stepan.salenikov...@savoirfairelinux.com>:
> >
> >> Hi,
> >> I think I've seen this issue before and I think there is definitely a
> >> problem in the Ring user interface occasionally when changing the video
> >> settings. For some reason it doesn't always happen, or not on all
> >> machines... its something we need to investigate further.
> >>
> >> I think there could also be a second issue in the Ring daemon (dring) in
> >> that it doesn't always seem to detect all the possible resolutions. I've
> >> noted before that on some cameras when I set the resolution to the
> highest
> >> possible, I am only able to select a low frame rate, and a higher frame
> >> rate only on lower resolutions. But in cheese I was able to select a
> high
> >> frame rate on the highest resoltion.
> >>
> >> Either way, Ales, one thing you could try is to quit Ring (make sure the
> >> dring process has quit as well). And then edit the dring.yml file found
> in:
> >> $HOME/.config/ring/dring.yml
> >>
> >> The end of the file should contain the video settings. Try setting the
> >> 'video_size' and 'framerate' to a resolution and framerate,
> respectively,
> >> which are valid in cheese. Then start Ring again and see if these
> settings
> >> have taken effect.
> >>
> >> -stepan
> >>
> >> ----- Original Message -----
> >> From: "Ales Katona" <almin...@gmail.com>
> >> To: "Jérôme Oufella" <jerome.oufe...@savoirfairelinux.com>
> >> Cc: ring@lists.savoirfairelinux.net
> >> Sent: Wednesday, November 25, 2015 1:39:07 PM
> >> Subject: Re: [Ring] 10 FPS?
> >>
> >> This is the output of v4l2-ctl --all
> >>
> >> NOTE: if I query after running ring/settings I get 5 FPS in the
> streaming
> >> report. If I run cheese and run it afterwards (or during) I get 30 FPS.
> So
> >> it's def. a question of setting it wrong.
> >>
> >> Driver Info (not using libv4l2):
> >> Driver name : uvcvideo
> >> Card type : Live! Cam Chat HD VF0790
> >> Bus info : usb-0000:00:1a.0-1.6
> >> Driver version: 4.2.5
> >> 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 : 1280/720
> >> Pixel Format : 'MJPG'
> >> Field : None
> >> Bytes per Line: 0
> >> Size Image : 1843200
> >> Colorspace : SRGB
> >> Flags :
> >> Crop Capability Video Capture:
> >> Bounds : Left 0, Top 0, Width 1280, Height 720
> >> Default : Left 0, Top 0, Width 1280, Height 720
> >> Pixel Aspect: 1/1
> >> Selection: crop_default, Left 0, Top 0, Width 1280, Height 720
> >> Selection: crop_bounds, Left 0, Top 0, Width 1280, Height 720
> >> Streaming Parameters Video Capture:
> >> Capabilities : timeperframe
> >> Frames per second: 30.000 (30/1)
> >> Read buffers : 0
> >> brightness (int) : min=-64 max=64 step=1 default=0 value=0
> >> contrast (int) : min=0 max=50 step=1 default=0 value=0
> >> saturation (int) : min=0 max=100 step=1 default=55 value=55
> >> hue (int) : min=-100 max=100 step=1 default=0 value=0
> >> white_balance_temperature_auto (bool) : default=1 value=1
> >> gamma (int) : min=100 max=300 step=1 default=100 value=100
> >> power_line_frequency (menu) : min=0 max=2 default=2 value=2
> >> white_balance_temperature (int) : min=2800 max=6500 step=10 default=4500
> >> value=4500 flags=inactive
> >> sharpness (int) : min=0 max=10 step=1 default=2 value=2
> >> backlight_compensation (int) : min=0 max=4 step=1 default=1 value=1
> >> exposure_auto (menu) : min=0 max=3 default=3 value=3
> >> exposure_absolute (int) : min=5 max=10000 step=1 default=166 value=166
> >> flags=inactive
> >> brightness (int) : min=-64 max=64 step=1 default=0 value=0
> >> contrast (int) : min=0 max=50 step=1 default=0 value=0
> >> saturation (int) : min=0 max=100 step=1 default=55 value=55
> >> hue (int) : min=-100 max=100 step=1 default=0 value=0
> >> white_balance_temperature_auto (bool) : default=1 value=1
> >> gamma (int) : min=100 max=300 step=1 default=100 value=100
> >> power_line_frequency (menu) : min=0 max=2 default=2 value=2
> >> white_balance_temperature (int) : min=2800 max=6500 step=10 default=4500
> >> value=4500 flags=inactive
> >> sharpness (int) : min=0 max=10 step=1 default=2 value=2
> >> backlight_compensation (int) : min=0 max=4 step=1 default=1 value=1
> >>
> >>
> >> 2015-11-25 10:51 GMT-07:00 Ales Katona < almin...@gmail.com > :
> >>
> >>
> >>
> >> I've looked at the terminal output. This is the section of mostly Qt5
> >> related "warnings" I see when I open the video settings and click on the
> >> various camera settings.
> >>
> >> QObject: Cannot create children for a parent that is in a different
> thread.
> >> (Parent is Video::ShmRenderer(0x19b0840), parent's thread is
> >> QThread(0x15ab650), current thread is QThread(0xb3dd80)
> >> QItemSelectionModel: Setting the current index when no model has been
> set
> >> will result in a no-op.
> >> QItemSelectionModel: Setting the current index when no model has been
> set
> >> will result in a no-op.
> >> QItemSelectionModel: Setting the current index when no model has been
> set
> >> will result in a no-op.
> >> QItemSelectionModel: Setting the current index when no model has been
> set
> >> will result in a no-op.
> >>
> >> The no-op one always happens when I change any camera setting, makes me
> >> think maybe it just doesn't do anything?
> >>
> >> Running Cheese (the gnome camera snapshotter) I get fluent video (30+
> fps
> >> I'd guess) with 1280x720 which is the highest res for this webcam
> (creative
> >> live! HD VF0790)
> >>
> >> The client version (built from AUR on arch) is 0.4.0
> >>
> >> Ales
> >>
> >> 2015-11-25 10:48 GMT-07:00 Jérôme Oufella <
> >> jerome.oufe...@savoirfairelinux.com > :
> >>
> >>
> >>
> >>
> >>
> >> Ales, you can try connecting a second (different) webcam on the same
> >> platform, check if you have the same fps limitations. In any case, I'm
> sure
> >> someone here can point to a debugging path. First thing that comes to my
> >> mind is querying the webcam's caps from a cli tool in a way similar to
> ring
> >> to see what it reports.
> >>
> >> @eloi: any hint?
> >>
> >>
> >>
> >> --
> >> Feel the power of Opensource.
> >> Feel the power of Free Pascal.
> >>
> >>
> >>
> >> --
> >> Feel the power of Opensource.
> >> Feel the power of Free Pascal.
> >>
> >> _______________________________________________
> >> Ring mailing list
> >> Ring@lists.savoirfairelinux.net
> >> https://lists.savoirfairelinux.net/mailman/listinfo/ring
> >>
> >
> >
> >
> > --
> > Feel the power of Opensource.
> > Feel the power of Free Pascal.
> > _______________________________________________
> > Ring mailing list
> > Ring@lists.savoirfairelinux.net
> > https://lists.savoirfairelinux.net/mailman/listinfo/ring
>



-- 
Feel the power of Opensource.
Feel the power of Free Pascal.
_______________________________________________
Ring mailing list
Ring@lists.savoirfairelinux.net
https://lists.savoirfairelinux.net/mailman/listinfo/ring

Reply via email to