#81 Flash Capture on Webpages does not list the virtual device

[Anonymous]

Originally created by: w...@mycertifiedgeek.com
Originally owned by: bharadwa...@gmail.com

I'm hoping this makes sense- I have...oh... 6 hours of knowledge of avconv, ffmpeg, video4linux, and well Java code.  That being said;

### What steps will reproduce the problem?
Open any webpage, skype, or other webcam previewing application and you will not get the option to select the virtual device or stream from Webcam Studio.

### What is the expected output? What do you see instead?
When visiting any website that has flash, I expect the flash applet to request my permission to access the video devices on my system.  I do get the request for permission, and grant them.  The problem is that I only see my integrated webcam device, and not the virtual one.  If I open Webcam Studio first and have it outputting, then flash will not detect the device at all (which is normal).

###  What version of the product are you using? On what operating system?
The 0.60 aplha 2 (416M) read-only source on Ubuntu 12.04 LTS.

###  Please provide any additional information below.
I understand that this is still in development, but I became very interested in how all of the different pieces of software tie in together after seeing some of your test videos on youtube.

I read on the web that the latest version of video4linux (I think) now allows you to have the same input/output device, rather than having to specify separate devices.  Which is how it appears to need to be for flash compatibility (I really don't know).  Anyway, in the code I see that avconv gets directed out to tcp 127.0.0.1 (I was wondering why?  Does FFMpeg grab the stream here for processing or something?) and also why can't it just be specified to be output on a /dev/videoX like the older version of Webcam Studio did (when I had it semi working)?  I'm just curious, I definitely appreciate where the program is going.  I was just hoping to get it to function for my needs right now so that Flash would recognize the virtual device.

Thanks for your time.  Let me know if you accept donations also, and what type of timeline you have set for milestones with the project.

[Anonymous]

Originally posted by: w...@mycertifiedgeek.com

In trying to continue to efforts ... I discovered this page, and have figured out that apparently it's the use of v2l2 that is incompatible with flash.  This "Flashcam" project aims to resolve this issue for projects such as this one.

http://www.swift-tools.net/Flashcam/

Please let me know your thoughts.

[Anonymous]

Originally posted by: bharadwa...@gmail.com

Guys I would like to have a look at this .. Please share your thoughts if anyone have insights on this..

Also let me if I can accept this ticket as its in new state.

[Anonymous]

Originally posted by: peter.u....@gmail.com

(No comment was entered for this change.)

Owner: bharadwa...@gmail.com
Status: Accepted

[Anonymous]

Originally posted by: peter.u....@gmail.com

Could you please check if the current version of WCS available in our LP PPA (daily builds) has the same behavior?

[Anonymous]

Originally posted by: bharadwa...@gmail.com

Hey
when I tried installing Daily build (0.6 beta) in 12.10  it installed but when start the WCS I got the following error.

None of the kernel modules webcamstudio/v4l2loopback are loaded...

Refer screenshot.. Hence I tried with 12.04 it worked fine with firefox...

Please suggest how to proceed in 12.10...

thanks

[Anonymous]

Originally posted by: peter.u....@gmail.com

The new debian packaging splits webcamstudio into two packages:
webcamstudio - containing the main app and the libwebcamstudio helper library
webcamstudio-dkms - the kernel module for the virtual webcam

Since the DKMS module is just recommended, and is not a dependency, you either need your apt to be configured to install all recommended as dependencies, or install the webcamstudio-dkms together with the main app... (btw v4l2loopback-dkms package works perfectly with WCS too)

There was a missing libwebcamstudio helper in latest daily PPA that I fixed, so update...

As for the reported problem... It is not a kernel module or a WCS problem, but it is a problem with handling v4l2 and v4l calls by the application affected....

This can be fixed using the v4l compat library as a preload. For more info see for example: http://community.linuxmint.com/tutorial/view/219

In a word:
- if you are on Ubuntu for example... install libv4l-0 and libv4l-0:i386. The i386 package is not available through the repo method, so you need to download it and install it from: http://packages.ubuntu.com/quantal/libv4l-0 together with: http://packages.ubuntu.com/quantal/libv4lconvert0 - both i386 deb files
- then you need to preload the v4l1compat.so library, depending on the binary that will be run. I.e. skype is 386 binary, so you need this as a starting command line:

LD_PRELOAD="/usr/lib/i386-linux-gnu/libv4l/v4l1compat.so" skype

If it is a x64 binary:
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so" THE_X64_BINARY

Same goes for flash depending on the main app that uses it...

Please test and provide feedback?

Labels: OpSys-Linux
Status: Feedback

[Anonymous]

Originally posted by: peter.u....@gmail.com

(No comment was entered for this change.)

Blocking: webcamstudio:20

[Anonymous]

Originally posted by: peter.u....@gmail.com

Issue 20 has been merged into this issue.

[Anonymous]

Originally posted by: peter.u....@gmail.com

(No comment was entered for this change.)

Blocking: -webcamstudio:20

[Anonymous]

Originally posted by: bharadwa...@gmail.com

Feedback: It worked .. If I start  the skype with the v4l1.so loaded then WCS opened properly.

Issue: But still the WCS is not listed in the Skype's Web cam options even after I started transmitting from WCS..

Refer the screen shot ..

[Anonymous]

Originally posted by: soylent...@gmail.com

Hi guys,
finally seems i find a way to put WS output in Skype.
You have to install the latest v4l2loopback from:
https://github.com/umlaeute/v4l2loopback/tree/v0.6.3
compile, install and modprobe it.
Then we have for example /dev/video0 as WebcamStudio Device and the new /dev/video1 as Dummy Video Device.
Start WS, enable the "WebcamStudio Device" only (Leaving the Dummy unchecked), enable audio, and start some example stream.
At this point open a terminal and type:

gst-launch-0.10 v4l2src device=/dev/video0 ! v4l2sink device=/dev/video1

if i lunch skype and i select my /dev/video0 i can see nothing as usual, but if i select the /dev/video1 now the WS video is fully functional but horizzontally mirrored. Going to WS and selecting the effect flipvertical (the name are switched one to each other and we'll fix this), i can correctly see my WS output in Skype.
I think we will add this implementation.
Have a nice day.

[Anonymous]

Originally posted by: peter.u....@gmail.com

Just a reminder that from [r467] webcamstudio and v4l2loopback modules are totally synced, so no need to use the v4l2loopback module

[Anonymous]

Originally posted by: willyayn...@gmail.com

Hi there,

I just wanted to say thanks to soylent...@gmail.com! #12 helped me very much. I was trying to get a WCS webcam to work with Google Chrome in a WebRTC application without any luck (the LD_PRELOAD method did not work). But the v4l2loopback device did the trick.

What I needed to do was basically the following (this should not be copy-pasted 1:1 as it may need personal adjustments and some required software may need to be installed first):

su
add-apt-repository ppa:webcamstudio/webcamstudio-dailybuilds
apt-get install webcamstudio
reboot

su
git clone https://github.com/umlaeute/v4l2loopback.git
cd v4l2loopback
make install
modeprobe v4l2loopback

webcamstudio
gst-launch v4l2src device=/dev/video0 ! v4l2sink device=/dev/video1
google-chrome

With this WCS can be used on Linux Mint 15 (64-bit) with the latest Chrome Browser.

[Anonymous]

Originally posted by: soylent...@gmail.com

Thanks willyaynard for useful feedback, you welcome.
Just to say that now WS flip-horizontal and flip-vertical effects are now right.
:)

[Anonymous]

Originally posted by: soylent...@gmail.com

Fixed with SkyCam implementation.

Status: Fixed