Open mzihlmann opened 1 year ago
However, now i run into a new issue i have not yet seen before. I have not yet tested/analyzed it further. But if you would like to i could help you in binary-search the culprit.
that would be fantastic.
[08:59:42] ../gst/imagefreeze/gstimagefreeze.c(1158): gst_image_freeze_src_loop (): /GstPipeline:pipeline0/GstImageFreeze:imagefreeze0:
is that by any chance trying to set a timeout image?
We have an android emulator that uses the loopback device as a camera-input. pytest+gstreamer+selenium are used to run end-to-end tests against the android app. To my understanding only static images are fed into the loopback device. The command that is used for generating the feed should be this one here:
gst-launch-1.0 uridecodebin uri="file://{image_path}" ! videoconvert ! videoscale ! imagefreeze ! v4l2sink show-preroll-frame=false device=/dev/video{self.dev_id}
Note that this setup is now running inside a kubernetes pod and uses generic-device-plugin to expose the loopback device to the pod.
i'm not exactly sure why, but inserting a tee
element just before the v4l2sink
seems to fix that issue (at least for me):
gst-launch-1.0 uridecodebin uri="file://{image_path}" ! videoconvert ! videoscale ! imagefreeze ! tee ! v4l2sink show-preroll-frame=false device=/dev/video{self.dev_id}
interesting. single frame output is fixed by this commit https://github.com/umlaeute/v4l2loopback/commit/b92e9ce7cccd30cd28743a3fe57eb7827909aeab
single frame output is fixed by this commit https://github.com/umlaeute/v4l2loopback/commit/b92e9ce7cccd30cd28743a3fe57eb7827909aeab
yes, that's expected. see #535
issue first appears here https://github.com/umlaeute/v4l2loopback/commit/d78f95bb2915ddedaccc87aa2e2fbdd1e0f502d9
adding a tee
fixes the issue
ping @umlaeute
given that there's an easy fix (adding tee
), this currently has no high priority for me.
is that ok?
Hey there, I'm very happy to see that there was a lot of traffic here in the last week. I'm now testing whether the newest master fixes the two issues we had so far.
However, now i run into a new issue i have not yet seen before. I have not yet tested/analyzed it further. But if you would like to i could help you in binary-search the culprit. our current "good version" that we run in production is here. its based on the last release (to avoid the single frame issue) and patched to avoid the kernel issue mentioned above.
Environment
v4l2loopback
version:0.12.7-357-g845cea0
(current HEAD)Linux ci4 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
Debian GNU/Linux 11 (bullseye)
Step 3: Describe the problem:
Observed Results:
Expected Results: