GNOME Bugzilla – Bug 614487
camerabin: Set v4l2 to NULL state before changing format
Last modified: 2010-11-24 19:52:10 UTC
For now, it is impossible set different values via set-video-resolution-fps signal if camerabin is in >=READY state: WARN v4l2 gstv4l2object.c:1920:gst_v4l2_object_set_format:<autovideosrc0-actual-src-v4l> error: Call to S_FMT failed for YUYV @ 640x480: Device or resource busy
Created attachment 157611 [details] [review] Set v4l2 to NULL state before changing format
Created attachment 157616 [details] [review] do nothing if format the same
Aleksey, there have been a lot of rewrites. The changes from bug #614958 are affecting this one. I guess your issue is still valid and this would need to be addresses in reset_video_capture_caps(). Patch even kind of applies still. Would be nice if you can confirm.
Why does v4l2src need to go to NULL for changing format? Why is it busy in READY?
Hmm, maybe what we see is a bug in v4l2src to now reset everything back when going down to READY?
Can you still reproduce this? If so, could you provide a sample application? I've tried to make one, but maybe you're doing it differently.
(In reply to comment #6) > Can you still reproduce this? > > If so, could you provide a sample application? I've tried to make one, but > maybe you're doing it differently. Sorry, I've postponed my camerabin based work and can't gather all pieces together. In my mind gst-camera demo application had the same functionality (though I didn't manage to try it, it was failing all time in my case :).
I just tried gst-camera and it switches the resolutions for me correctly. (Using git head of everything)
It works fine for me too. Shall we close this?
Just rechecked against recent git versions, works for as well. So, I'm closing the bug.