V4L IEEE1394 devices: Difference between revisions
Jump to navigation
Jump to search
m (fixed link) |
m (minor edit) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
The [[Development:_Video4Linux_APIs|V4L API]] in itself does not support any [[IEEE1394]] (also known as |
The [[Development:_Video4Linux_APIs|V4L API]], in of itself, does not support any [[IEEE1394]] (also known as [[FireWire]] or [[i.LINK]]) devices. However, in the case of some devices, V4L applications can obtain access to video via ieee1394, using either a [[Loopback|loopback]] or LD_PRELOAD method. |
||
== via Loopback == |
== via Loopback == |
||
Line 11: | Line 11: | ||
* V4L with ieee1394 camcorders: |
* V4L with ieee1394 camcorders: |
||
** using DV4Linux's [http://dv4l.berlios.de dv4lstart] |
** using DV4Linux's [http://dv4l.berlios.de dv4lstart] |
||
[[Category:IEEE1394]] |
Latest revision as of 19:26, 22 August 2010
The V4L API, in of itself, does not support any IEEE1394 (also known as FireWire or i.LINK) devices. However, in the case of some devices, V4L applications can obtain access to video via ieee1394, using either a loopback or LD_PRELOAD method.
via Loopback
- V4L with ieee1394 camcorders:
- using DV4Linux's dv4l
- using dvgrab and dv2vloopback
- V4L with ieee1394 cameras:
- using Coriander
via LD_PRELOAD
- V4L with ieee1394 camcorders:
- using DV4Linux's dv4lstart