Lines Matching refs:video
53 This extension provides a mechanism for streaming video data
55 then display video streams in interactive 3D scenes and/or
56 manipulate the video data using the GL's image processing
238 "Video capture can be used to transfer pixels from a video input
240 accessed by binding them to a valid video capture slot in a context
241 using window-system specific functions. Valid video capture slots
243 maximum number of slots, inclusive. Trying to perform video
244 capture operations on an invalid video capture slot or a video
250 Each video input device can have an implementation-dependent number
254 "Video capture can be started and stopped on a specified video
265 raw buffers with incoming video data. If capture is already in the
269 textures must be bound to the individual video capture streams. A
270 video capture stream refers to a single video source. Each video
271 capture slot must provide one or more video capture streams.
303 at frame capture time. To unbind a buffer object from a video
355 video capture destinations. If <target> is not TEXTURE_2D or
358 INVALID_ENUM is generated. To unbind a texture from a video capture
363 "Captured video data will have 2, 3, or 4 components per pixel. The
365 format of the data output by the video capture device. This may
366 differ from the data format of the data received by the video
411 "After objects have been bound to the video capture streams,
416 can be called to capture one frame of video. If no frames are
459 nanoseconds, that the video capture device began capturing the
462 to when the video frame first reached the capture hardware, not when
483 conversion offset for the video capture stream, respectively, and
486 <Cmax> for the video capture stream. Each component of <Cmin> is
496 internal storage, the captured video data will be converted to a
503 are the minimum and maximum values, respectively, that the video
518 can be used to specify video capture stream parameters. The value
519 or values in <params> are assigned to video capture stream parameter
523 4 x 4 column-major matrix. If the video capture stream's data
526 a 4x4 identity matrix when a video capture device is bound.
528 "To specify the video capture stream color conversion offset vector,
530 an array of 4 consecutive values. If the video capture stream's
535 "To specify the video capture stream color conversion clamp values,
538 consecutive values. If the video capture stream's data format does
546 "To set the orientation of the captured video data, set <pname> to
549 left of the captured region of the video image will be at texture
581 returns properties of the video capture device bound to
588 video capture streams on the device bound to <video_capture_slot> is
597 returns properties of an individual video stream on the video
624 bound video capture device is configured to capture, respectively,
647 GLX_NUM_VIDEO_CAPTURE_SLOTS_NV int number of video capture slots
654 "GLX video capture devices can be used to stream video data from an
663 "to generate an array of video capture devices. The number of
665 the array is a video capture device on <screen>. Use XFree to free
668 "GLX video capture devices are abstract objects that refer to a
672 physical device backing a GLX video capture device, use
680 If <device> does not refer to a video capture device GLX_BAD_VALUE
681 will be returned. If <attribute> does not name a video capture
684 "Before using a video capture device, it must be locked. Once a
685 video capture device is locked by a client, no other client can lock
686 a video capture device with the same unique ID until the lock is
688 the X server is broken. To lock a video capture device to a display
694 "If <device> does not name a video capture device, BadValue is
697 "After successfully locking a video capture device, use
706 it will be unbound first. To unbind a video capture device, bind
707 device None to the video capture slot the device is bound to. If
711 context, BadMatch is generated. If <device> does not name a video
713 to a video capture slot, GLX_BAD_VALUE is returned. If <device> is
716 "GLX does not provide a mechanism to configure the video capture
719 the incoming video signal and data format. However, GLX does expect
722 captured data will cause the results of video capture to be
725 "When finished capturing data on a locked video capture device, use
732 name a video capture device, BadValue is generated. If <device>
1022 "If <iAttribute> is WGL_NUM_VIDEO_SLOTS_NV, the number of valid video
1024 WGL_NUM_VIDEO_CAPTURE_SLOTS_NV, the number of valid video capture
1029 "WGL video capture devices can be used to stream video data from an
1036 "to query the available video capture devices on <hDc>. The number
1043 "WGL video capture device handles refer to a physical capture
1047 WGL video capture device handle, use
1056 "Before using a video capture device, it must be locked. Once a
1057 video capture device is locked by a process, no other process can
1058 lock a video capture device with the same unique ID until the lock
1059 is released or the process ends. To lock a video capture device,
1065 "After successfully locking a video capture device, use
1075 To unbind a video capture device, bind device NULL to the
1076 video capture slot the device is bound to.
1078 "WGL does not provide a mechanism to configure the video capture
1081 the incoming video signal and data format. However, WGL does expect
1084 captured data will cause the results of video capture to be
1087 "When finished capturing data on a locked video capture device, use
1098 greater than the number of video capture slots supported by the
1105 INVALID_OPERATION is generated if there is no video capture device
1113 video capture slot that is already capturing or if EndVideoCaptureNV
1114 is called on a video capture slot that is not capturing.
1117 streams provided by the currently bound video capture device when
1139 INVALID_ENUM is generated if <pname> does not name a valid video
1141 valid video capture stream parameter when calling
1142 GetVideoCaptureStream{i,f,d}vNV or a settable video capture stream
1173 to the video capture slot do not match the dimensions of the region
1177 bound to the video capture slot has not been defined when
1181 textures bound to a given video capture stream does not match when
1185 to the video capture slot is not color renderable when
1189 enabled on any of the textures bound to the video capture slot when
1219 next video
1231 last video
1235 video
1242 video
1252 bound video
1259 bound video
1266 bound video
1273 bound video
1279 video image
1327 video capture
1329 this video
1334 This example demonstrates binding a video capture device to a
1366 This example demonstrates capturing 1080p video data from two
1368 second with the NV_present_video extension. It assumes video
1369 capture and video output devices are already bound to the current
1377 // Create a video output buffer object.
1380 // Create and init a video output texture object.
1391 // Get the video buffer pitch
1400 // Bind the buffer object to the video capture stream.
1415 // Capture the video to a buffer object
1418 // Pull stream 0's video data back to local memory
1423 // Present stream 1's video data using NV_present_video
1453 How should video capture devices be presented to the application?
1455 [RESOLVED] In GLX, video capture devices are X resources
1463 same video device, but only one X client or handle at a time
1479 configurable per-stream or is per-video-capture device sufficient?
1489 [RESOLVED] Yes. Some video specifications require color data to
1499 Does video capture slot state belong to the context or the video
1502 [RESOLVED] The video capture state lives in the context. Setting
1503 video capture slot state does not affect the video capture device
1504 itself. Any video capture slot state that affects the video
1508 What happens to video capture slot state when a device is unbound,
1509 or, does video capture slot state persist across device bindings?
1511 [RESOLVED] Since much of the video capture slot state depends on
1515 Is video capture slot state defined when no device is bound to the
1516 slot? Should querying video capture slot state when no device is
1522 video capture state on a slot with no bound device should
1524 essentially be the video capture equivalent of making GL calls
1527 What should the default values for all the video capture per-slot
1536 -Fixed video slots used in second usage example