settable devicename

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install several capture devices (each opening a different /dev/video*), or 
no capture device at all
2. make sure that the v4l2loopback driver creates a loopback device different 
from /dev/video1
3. try using v4lsink

What is the expected output? What do you see instead?

/dev/video1 is hardcoded, so v4lsink will fail to run if this file is not 
present or not a v4l2loopback device.

i would like to be able to tell v4lsink which device to use. so i can adjust it 
to my system without having to recompile (think usb-cameras...)

What version of the product are you using? On what operating system?

mercurial checkout on debian squeeze/sid

Please provide any additional information below.

attached is a patch that adds a "device" property to the V4l2SinkLoopback 
element.
it defaults to /dev/video1 

example usage:
$ v4lsink 'videotestsrc ! ffmpegcolorspace ! V4l2SinkLoopback 
device=/dev/video0' 

note that this is the first time that i have written any vala code.
so please check the code for any problems :-)

Original issue reported on code.google.com by umlae...@gmail.com on 25 Aug 2010 at 4:40

Attachments:

• devicename.diff

[GoogleCodeExporter]

Thanks for the patch.

Can you please make a clone of a project with patch applied, it will be much 
easier for people to get you improvement, chances it will go unnoticed in the 
bug tracker.

Eventually I'll reintegrate your changes here.

Original comment by gorinich...@gmail.com on 25 Aug 2010 at 4:52

[GoogleCodeExporter]

ok, i have cloned the repository onto github.

http://github.com/umlaeute/gst-v4l2loopback/tree/vala

Original comment by umlae...@gmail.com on 26 Aug 2010 at 9:18

[GoogleCodeExporter]

Actually I meant code.google.com, for it to be available at source/clones page.
Is there any automated way of merging git branches into mercurial?

Original comment by vas...@gmail.com on 26 Aug 2010 at 9:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i understand, but i prefer to not use code.google (it took me a lot of 
consideration whether i actually can file this issue, as it requires me to 
login).

there is a mercurial-git (a git extension to hg) which allows to convert 
between the two (lossless, they claim). it's what i used for pushing to github

i don't know about automation though.

Original comment by umlae...@gmail.com on 26 Aug 2010 at 9:40

[GoogleCodeExporter]

That's understandable, anyway having a clone that can be checked out is better 
than patch in bug tracker.

Original comment by vas...@gmail.com on 26 Aug 2010 at 9:48