Lines Matching refs:capture

4 This driver emulates video4linux hardware of various types: video capture, video
5 output, vbi capture and output, radio receivers and transmitters and a software
7 testing capture and output overlays.
11 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
12 capture device. Each output can be an S-Video output device or an HDMI output
33 - Raw and Sliced VBI capture and output support
83 By default the driver will create a single instance that has a video capture
85 S-Video and HDMI outputs, one vbi capture device, one vbi output device, one
106 	So to create four instances, the first two with just one video capture
113 	are created for each video capture device. At most 16 inputs can be created,
127 	So to create a video capture device with 8 inputs where input 0 is a TV
152 vid_cap_nr: give the desired videoX start number for each video capture device.
154 	you to map capture video nodes to specific videoX device nodes. Example:
158 	This will attempt to assign /dev/video2 for the video capture device of
166 vbi_cap_nr: give the desired vbiX start number for each vbi capture device.
178 sdr_cap_nr: give the desired swradioX start number for each SDR capture device.
181 ccs_cap_mode: specify the allowed video capture crop/compose/scaling combination
182 	for each driver instance. Video capture devices can have any combination
255 This is probably the most frequently used feature. The video capture device
305 standards. This is what capture hardware does as well.
379 Like with video capture the framerate is also exact in the long term.
416 There are three types of VBI capture devices: those that only support raw
535 The following controls are specific to video capture.
561 The following controls are specific to video capture and output and radio
578 The Test Pattern Controls are all specific to video capture.
612 These controls are all specific to video capture.
714 The following two controls are only valid for video and vbi capture.
730 The following two controls are only valid for video capture.
748 capture and output streams and for the SDR capture device except for the
912   sequence and field counting in struct v4l2_buffer on the capture side may not
928 capture device.
931 output must be configured for sliced VBI. The VBI capture side can be configured
1011 Note: capture overlay support is implemented primarily to test the existing
1012 V4L2 capture overlay API. In practice few if any GPUs support such overlays
1019 This driver has support for a destructive capture overlay with bitmap clipping
1022 setting: if it is set to FIELD_TOP or FIELD_BOTTOM and the capture setting is
1030 In addition, the pixelformat of the capture format and that of the framebuffer
1035 instances: the first with a framebuffer enabled. You configure the capture
1038 the output overlay for the video output, turn on video looping and capture
1088 pixelformat of the capture format and that of the framebuffer must be the
1098 on the capture side. The use of the clipping, chromakeying or alpha processing