Closed GoogleCodeExporter closed 9 years ago
Hi joanguisado,
sorry but WS 0.5x is no longer maintained.
You can try the SkyCam feature in WebcaStudio 0.6x to have flash compatibility
or if you want to use WS 0.5x you can try the solution well explained by
willyaynard in this past issue:
http://code.google.com/p/webcamstudio/issues/detail?id=81&can=1
" 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):
<< Install v4l2loopback module >>
su
git clone https://github.com/umlaeute/v4l2loopback.git
cd v4l2loopback
make
sudo make install
sudo modeprobe v4l2loopback
<< Run WS 0.5x and start a source >>
webcamstudio
<< Open a Terminal and type the gst-launch command line >>
gst-launch-0.10 v4l2src device=/dev/video0 ! v4l2sink device=/dev/video1
<< Open Chrome and use the /dev/video1 device >>
google-chrome
With this WS can be used on Linux Mint 15 (64-bit) with the latest Chrome
Browser."
Basically you have to stream the Webcamstudio Module to another virtual webcam
instance (v4l2loopback) with gst-launch in a terminal and then use the last
device with Chrome.
Sometimes this re-streaming could flip horizontally your output, but you can
use WS 0.5x filters to adjust the image.
Hope this helps
karl
Original comment by soylent...@gmail.com
on 14 Jan 2014 at 5:45
Thank Karl for your answer. It was very quick and most important...It almost
worked. I'm having problems when executing this commnad:
$> gst-launch-0.10 v4l2src device=/dev/video0 ! v4l2sink device=/dev/video1
I got this error:
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Device
'/dev/video1' is not a output device.
I don't know if it's due to the difference in the distributions Ubuntu and Mint
but I don't think so since Mint is based on Ubuntu. Maybe you have some idea of
what's happening.
Thanks again.
joan
Original comment by joanguis...@gmail.com
on 14 Jan 2014 at 9:29
Are you sure to use the correct /dev/videoX as input and output?
Try this command to have infos about video device in your system and change the
command accordling to your configuration (v4l2-ctl have to be installed):
v4l2-ctl --list-devices
karl.
Original comment by soylent...@gmail.com
on 15 Jan 2014 at 9:15
For a better explanation, let me show you the outputs of the commands:
$>v4l2-ctl --list-devices
Dummy video device (0x0000) (v4l2loopback:0):
/dev/video1
WCStudio video device (0x0000) (webcamstudio:0):
/dev/video0
$> gst-launch-0.10 v4l2src device=/dev/video0 ! v4l2sink device=/dev/video1
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Device
'/dev/video1' is not a output device.
Additional debug info:
v4l2_calls.c(528): gst_v4l2_open ():
/GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0:
Capabilities: 0x5000001
Setting pipeline to NULL ...
Freeing pipeline ...
Thanks,
j
Original comment by joanguis...@gmail.com
on 15 Jan 2014 at 9:55
Ok,
seems you have to switch video0 with video1 like this:
gst-launch-0.10 v4l2src device=/dev/video1 ! v4l2sink device=/dev/video0
because we have to stream webcamstudio video device video0 (used as output) to
the new installed v4l2loopback (Dummy video device) video1 (input/output).
Once the gst-launch pipe is running try chrome.
karl
Original comment by soylent...@gmail.com
on 16 Jan 2014 at 5:30
I was able to make it work thanks to you help.
Thanks a lot.
Original comment by joanguis...@gmail.com
on 16 Jan 2014 at 5:54
I'll handle this one.
Original comment by soylent...@gmail.com
on 9 Mar 2014 at 7:59
WebcamStudio 0.5x no longer maintained.
Original comment by soylent...@gmail.com
on 9 Mar 2014 at 8:00
Hi, would you help me have flash to recognize the pseudo camera?
The source built WebcamStudio is of version 0.72, I followed the instruction
below to work it out:
https://plus.google.com/108633206357681875841/posts/WGx6syTrvvE
It seemed to work almost right, but I never see "WCStudio video device" button.
Here is my output of command 'v4l2-ctl --list-devices' for reference:
Dummy video device (0x0000) (platform:v4l2loopback-000):
/dev/video21
Dummy video device (0x0001) (platform:v4l2loopback-001):
/dev/video0
Obviously, "WCStudio video device" won't appear.
I tried any possible combinations of option and here I attatched the main
window of WCS.
Original comment by cohom...@gmail.com
on 6 Apr 2015 at 9:58
Attachments:
Hi, WSVideoDevice appears if you compile it.
http://sourceforge.net/projects/webcamstudio/files/Binaries/Beta/MultiDistro%20%
28Fedora-OpenSuse-Arch%29/dist_WebcamStudio072_r583_MultiDistro_150326.zip/downl
oad
I see you have dummy video device that is the one you get from original
v4l2loopback installation.
You can use that instead of WSVideoDevice (which is a fork) and it is the same.
If you have issues, please point to :
https://sourceforge.net/projects/webcamstudio/?source=directory
... because google-code hosting is going to close.
Thanks.
karl.
Original comment by soylent...@gmail.com
on 7 Apr 2015 at 6:10
Forgot to mention that is better to have only one v4l2loopback (virtual Webcam)
installed. So if you decide to install the "webcamstudio module"
(WSVideoDevice) fork, first uninstall v4l2loopback (Dummy device) module first.
Thanks.
karl.
Original comment by soylent...@gmail.com
on 7 Apr 2015 at 6:13
It worked!
Basically what I did was
1. uninstalled v4l2loopback (just removed v4l2loopback.ko)
2. download the kernel module(webcamstudio-module-112.tar.bz2)
3. compiled, and installed it.
4. after modprobe, there needed not to re-compile the webcamstudio itself. It
seemed to me that the WebCamstudio detected the loaded module on launch that it
determines how the interface should look.
From what I saw, two devices are seemingly worked differently at least in
respect that v4l2loopback (dummy video device) didn't let the flash player
detect the pseudo-camera but WSVideoDevice did.
Anyway it helped, thank you karl.
Original comment by cohom...@gmail.com
on 11 Apr 2015 at 9:57
Original issue reported on code.google.com by
joanguis...@gmail.com
on 13 Jan 2014 at 11:09