-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
video stream freezes #33
Comments
thanks for the bugreport. therefore it would be interesting, to know what you mean by those errors "that I don't get from 0.4.1". |
Thank you for your response. I just submitted a second bug report for the problems running 0.5.0, 0.6.1, and 0.6.2 since that appears to be a separate issue from what I'm encountering here. |
thanks for the additional bugreport. |
I'm using an 8-channel video capture card that doesn't support multiple sinks and I'm trying to use v4l2loopback so that gstreamer can display multiple copies of the video source. I'm also using Ubuntu 12.04 LTS on a quad-core i7.
Release 0.4.1 installs and I'm able to generate the desired multiple video streams. Unfortunately, when I start the second sink from one of the v4l2loopback devices the first video stream freezes. Sometimes it will recover after many seconds (measured 23 and 32 seconds). Sometimes the second video stream starts in a frozen state and neither recovers (stopped after 1 minute, although it restarted immediately when the second stream was killed)
I've tried using 0.5.0, 0.6.1, and 0.6.2, but I'm getting errors from them that I don't get from 0.4.1.
I'm doing the following to configure 0.4.1:
sudo modprobe v4l2loopback devices=8 max_buffers=8
I'm starting the v4l2loopback device using:
gst-launch-0.10 v4l2src device=/dev/video7 ! deinterlace method=linear ! v4l2sink device=/dev/video15
Note: This will not work without the "deinterlace" element.
I'm starting the displays using:
gst-launch-0.10 v4l2src device=/dev/video15 ! xvimagesink display=:0.0
The text was updated successfully, but these errors were encountered: