@@ -52,10 +52,13 @@ fed by various programs.
52
52
tested feeders:
53
53
GStreamer: using the "v4l2sink" element
54
54
Gem(>=0.93) using the "recordV4L2" plugin
55
- in theory most programs capable of _writing to_ a v4l2 device should work
55
+ in theory most programs capable of _writing to_ a v4l2 device should work.
56
56
57
57
the data sent to the v4l2loopback device can then be read by any v4l2-capable
58
- application
58
+ application.
59
+
60
+ you can find a number of scenarios on the wiki at
61
+ http://github.com/umlaeute/v4l2loopback
59
62
60
63
--- OPTIONS ---
61
64
if you need several independent loopback devices, you can pass the "devices"
@@ -66,6 +69,10 @@ you can also specify the device IDs manually; e.g.
66
69
# modprobe v4l2loopback video_nr=3,4,7
67
70
will create 3 devices (/dev/video3 /dev/video4 & /dev/video7)
68
71
72
+ --- ATTRIBUTES ---
73
+ you can set and/or query some per-device attributes via sysfs, in a human
74
+ readable format. see
75
+ /sys/devices/virtual/video4linux/video*/
69
76
70
77
--- KERNELs ---
71
78
the original module has been developed for linux-2.6.28;
@@ -94,8 +101,6 @@ In this case you should be able to simply do (as root):
94
101
--- DOWNLOAD ---
95
102
the most up-to-date version of this module can be found at
96
103
http://github.com/umlaeute/v4l2loopback/.
97
- the original code for the v4l2loopback module can be found at
98
- http://code.google.com/p/v4l2loopback/.
99
104
100
105
--- LICENSE/COPYING ---
101
106
Copyright (c) 2010-2011 IOhannes m zmoelnig <
[email protected] >
0 commit comments