-
Notifications
You must be signed in to change notification settings - Fork 530
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
buildin and installing on opensuse 12.2 (64 bit) #27
Comments
ad device creation: v4l2loopback is supposed to use the first available devices. it's working here, so i wonder which version of v4l2loopback (and which kernel) you are using. |
ad cheese: this might well be a bug in cheese, rather than in v4l2loopback (well, cheese should never crash, even if it encounters an invalid device, so there is a bug) maybe cheese likes it better if you fill the device with some stream (so the format is settled and cheese can grab some images) |
any news on that? have you ever managed to use v4l2loopback corrently? e.g. with some known-to-work application like |
no sorry ... i need it to work with linux webcam studio. That project was discarded :-( On Tue, Feb 5, 2013 at 9:29 AM, umlaeute notifications@github.com wrote:
Messagenet VOIP: 5338759 My blogs: http://altri-media.blogspot.com/ YouTube Channel: AllegFede VIMEO HD videos: http://www.vimeo.com/user1912745/videos |
after make and make install, no way to get another /dev/video# device (already have /video0 and /video1 as webcam ...) with modprobe v4l2loopback
I succesfully got another /dev/video# device (/dev/video2) with modprove v4l2loopback video_nr=2
but now webcam application (Cheese) crash on load .....
modprobe -r v4l2loopback (removes the /dev/video2) and chees turns on perfectly ...
The text was updated successfully, but these errors were encountered: