[linux-dvb] USBVision device defaults

Thierry MERLE thierry.merle at free.fr
Mon Jun 29 21:47:47 CEST 2009

Hi Tim,

On Mon, 29 Jun 2009 11:34:50 +0100 (BST)
Tim Williams <tmw at autotrain.org> wrote:

> Hello,
> I'm trying use a WinTV USB adaptor which uses the usbvision driver to 
> capture the output of a video camera for streaming across the web, the 
> idea being that there is a reliable local recording, even in the event of 
> a computer crash, while allowing the remote viewers to see the proceedings 
> live without needing to have two separate cameras.
> Unfortunately there is a catch, i'm using flash to do the broadcast 
> and flash (in common with a lot of other software of this type) doesn't 
> have the ability to set the input type and picture format, so you are 
> stuck with the default, which is the rf-tuner. I have managed to make my 
> own bodged driver which disables the rf-input so that I can get a picture 
> via s-video, but it is stubbornly stuck in black and white, which i'm 
> assuming is some kind of colour format problem.
> If I use KDETV to look at the picture then everything comes through in 
> colour, so this would seem to be a problem with the defaults built into 
> the module being incorrect for my circumstances. Rather than carrying on 
> with my bodged driver (this is the first time I have ever attempted to 
> modify a C programme), what would be really great is away to achieve one 
> of the following :
> 1) Set the default input, tv standard and pixel format using module 
> parameters in modprobe.conf
> 2) Get the driver to 'remember' it's current settings when switching 
> between applications. The windows driver for these devices does this, so 
> all I have to do under windows is start up WinTV, make sure I have a good 
> picture, close it down again and then start up the video broadcast in 
> flash.
> 3) A way to change the device settings using a 3rd party app even when the 
> main video device is in use and can't be accessed. I've tried using v4lctl 
> to set the parameters before starting a capture, but if the flash capture 
> is active, then I (unsurprisingly) get device in use errors. If I use v4lctl 
> before starting flash, then the settings don't stick. The capture box becomes 
> active briefly (there is a red light on the box which indicates this), 
> presumably accepts the setting and is then powered down again, causing 
> the new setting to be immediately forgotten.
> Any thoughts or help would be much appreciated.
I remember a guy that did the trick with the vloopback device.
Searching a bit on the Internet, it seems that flashcam 
http://www.swift-tools.net/Flashcam/ can be convenient for your needs.

More information about the linux-dvb mailing list