[Bug 2025204] Re: Wrong incoming frame length

[You-Sheng Yang]

Need sponsoring.

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ v4l2loopback may give wrong incoming frame length, and video capturing
+ client may freeze. Filed as
+ https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2532 and
+ https://github.com/umlaeute/v4l2loopback/issues/448.
+ 
+ [Fix]
+ 
+ Upstream v4l2loopback pull request
+ https://github.com/umlaeute/v4l2loopback/pull/543 and its merged git
+ commit
+ https://github.com/umlaeute/v4l2loopback/pull/543/commits/175adaf96d6d3784b922d3e0c77e9fd3e9ad8f53.
+ 
+ [Test Case]
+ 
+ # start gst in one terminal
+ $ gst-launch-1.0 videotestsrc ! video/"x-raw,width=320,height=240" ! videoconvert ! v4l2sink device=/dev/video0
+ 
+ # start ffplay in another
+ ffplay -hide_banner -i /dev/video0
+ 
+ [Where problems could occur]
+ 
+ When compiled against older (< v5.2) kernel this is ineffective.
+ 
+ [Other Info]
+ 
+ ========== original bug description ==========
+ 
  To backport upstream fix
  https://github.com/umlaeute/v4l2loopback/pull/543 for
  https://github.com/umlaeute/v4l2loopback/issues/448.
  
  "Gstreamer's v4l2sink is known to submit buffers with bytesused set to
  the length of the buffer instead of the size of the actual image-data
  within the buffer which is typically smaller due to buffer sizes being
  rounded op to a page-size: ..."

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2025204

Title:
  Wrong incoming frame length

Status in v4l2loopback package in Ubuntu:
  In Progress
Status in v4l2loopback source package in Jammy:
  In Progress
Status in v4l2loopback source package in Lunar:
  In Progress
Status in v4l2loopback source package in Mantic:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  v4l2loopback may give wrong incoming frame length, and video capturing
  client may freeze. Filed as
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2532 and
  https://github.com/umlaeute/v4l2loopback/issues/448.

  [Fix]

  Upstream v4l2loopback pull request
  https://github.com/umlaeute/v4l2loopback/pull/543 and its merged git
  commit
  https://github.com/umlaeute/v4l2loopback/pull/543/commits/175adaf96d6d3784b922d3e0c77e9fd3e9ad8f53.

  [Test Case]

  # start gst in one terminal
  $ gst-launch-1.0 videotestsrc ! video/"x-raw,width=320,height=240" ! videoconvert ! v4l2sink device=/dev/video0

  # start ffplay in another
  ffplay -hide_banner -i /dev/video0

  [Where problems could occur]

  When compiled against older (< v5.2) kernel this is ineffective.

  [Other Info]

  ========== original bug description ==========

  To backport upstream fix
  https://github.com/umlaeute/v4l2loopback/pull/543 for
  https://github.com/umlaeute/v4l2loopback/issues/448.

  "Gstreamer's v4l2sink is known to submit buffers with bytesused set to
  the length of the buffer instead of the size of the actual image-data
  within the buffer which is typically smaller due to buffer sizes being
  rounded op to a page-size: ..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/2025204/+subscriptions