dev-codec.xml 1.5 KB

123456789101112131415161718192021222324252627
  1. <title>Codec Interface</title>
  2. <para>A V4L2 codec can compress, decompress, transform, or otherwise
  3. convert video data from one format into another format, in memory. Typically
  4. such devices are memory-to-memory devices (i.e. devices with the
  5. <constant>V4L2_CAP_VIDEO_M2M</constant> or <constant>V4L2_CAP_VIDEO_M2M_MPLANE</constant>
  6. capability set).
  7. </para>
  8. <para>A memory-to-memory video node acts just like a normal video node, but it
  9. supports both output (sending frames from memory to the codec hardware) and
  10. capture (receiving the processed frames from the codec hardware into memory)
  11. stream I/O. An application will have to setup the stream
  12. I/O for both sides and finally call &VIDIOC-STREAMON; for both capture and output
  13. to start the codec.</para>
  14. <para>Video compression codecs use the MPEG controls to setup their codec parameters
  15. (note that the MPEG controls actually support many more codecs than just MPEG).
  16. See <xref linkend="mpeg-controls"></xref>.</para>
  17. <para>Memory-to-memory devices can often be used as a shared resource: you can
  18. open the video node multiple times, each application setting up their own codec properties
  19. that are local to the file handle, and each can use it independently from the others.
  20. The driver will arbitrate access to the codec and reprogram it whenever another file
  21. handler gets access. This is different from the usual video node behavior where the video properties
  22. are global to the device (i.e. changing something through one file handle is visible
  23. through another file handle).</para>