Development: Discussion of Video4Linux API Version 3: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
m (fixed formatting for better visibility, including 800x600 screen resolutions)
 
m (Added category: Development)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Although probably some day analog television will became completely obsolete, the need for an analog video capture API (such as the [[Development:_Video4Linux_APIs|Video4Linux API)]] will live on, as there will still be several practical needs for such. Consequently, we need still plan for the development of future v4l APIs.
Although probably some days v4l and television will became obsolete at
all, they will probably stay as radio stays for now. So we need to plan
our future development. I've created a new wiki page with some thoughts
on future development of v4l kernel API.


Here are a few thoughts about development on the next generation API:
1. We should not split control over video and radio on /dev/video
and /dev/radio. The main problem with it is in simultaneous work of
# We should not split control over video and radio on /dev/video and /dev/radio. The main problem with it is in simultaneous work of multiple video/radio programs - actually we have single device and control over it should be collected in one place.
⚫
# Userspace program should be able to select cards and tuners and so on, no need to keep cards database in kernel.
multiple video/radio programs - actually we have single device and
# We probably need to provide some official user-space library with more intellectual and more natural programming interface (probably with the ability to support several operation systems)....a present discussion of such can be found [[V4L2UserspaceLibrary|here]].
control over it should be collected in one place.

⚫
2. Userspace program should be able to select cards and tuners and so
on, no need to keep cards database in kernel.

3. Probably we need to provide some offical user-space library with
more intellectual and more natural programming interface (probably
with the ability to support several operation systems).


Everyone is welcome to add comments and extend this list.
Everyone is welcome to add comments and extend this list.
[[Category:Development]]

Latest revision as of 00:16, 3 May 2009

Although probably some day analog television will became completely obsolete, the need for an analog video capture API (such as the Video4Linux API) will live on, as there will still be several practical needs for such. Consequently, we need still plan for the development of future v4l APIs.

Here are a few thoughts about development on the next generation API:

  1. We should not split control over video and radio on /dev/video and /dev/radio. The main problem with it is in simultaneous work of multiple video/radio programs - actually we have single device and control over it should be collected in one place.
  2. Userspace program should be able to select cards and tuners and so on, no need to keep cards database in kernel.
  3. We probably need to provide some official user-space library with more intellectual and more natural programming interface (probably with the ability to support several operation systems)....a present discussion of such can be found here.

Everyone is welcome to add comments and extend this list.

Retrieved from "https://www.linuxtv.org/wiki/index.php?title=Development:_Discussion_of_Video4Linux_API_Version_3&oldid=21981"