Description
Issue migrated from trac ticket # 1030
component: core | priority: major | resolution: fixed
2015-11-13 06:41:26: antoine created the issue
So that applications that want to access the webcam can be made to work (ie: skype, etc). Scanners use the same framework as webcams, so maybe we can handle those too? (means potentially more than one device...)
We will need a simplified "window video source" class that the client can use to send pixel data with the same adaptability as the server (but maybe simplified a bit when it comes to batch delay, speed and quality tuning). It would be good if we could know when frames are being consumed from the server device so that we don't bother updating it when no-one is watching.
It will only deal with full frames, and only using a video encoder (if one is available) and no mmap.
It should have the same controls as sound: on, off or disabled.The server should only need to pass the frames to a virtual video device for this to work:
- v4l2loopback
- Motion - Video Four Linux Loopback Device API
- v4l2vd "V4L2 Virtual Device"
- webcamstudio
The initial version should not worry about:
- switching resolutions and formats: just one format will do
- controls such as showing the whole desktop instead of the video input
- sound sync!
etc..