[AG-DEV] Vic Video Device Conflicts

[Douglas Kosovic]

Hi Todd,

>> Thanks for the screenshot attachment, it made it clear.
>>
>> Looks like one of the VICs fails during the webcam driver 
>> detection/interrogation for some reason, in which case VIC will 
>> default to the device at the top of the device list.
>>
>> VIC only creates the device list with the device names, anywhere else 
>> that the device name appears in VIC is a string passed from the AGTk. 
>> Any issues with the other VIC are most likely side-effects due to the 
>> webcam VIC.
> 
> Ah.. understood.
> 
> 
>> With the recent VIC RPMs they now output the V4L & V4L2 debugging 
>> output, could you send that?
> 
> I've attached the venueclient debug (that seems to have the vic debug 
> also) if that is what you mean.  If you want any other debug files, send 
> me a note.
> 
> This log shows VC launch, configuration selected, venue entered with 
> resulting failed video - then vc kill.

The PWC webcam driver (which is what the Logitech QuickCam Pro 4000 
uses) is busy, extract from log :
   V4L2: trying /dev/video0... Error opening: /dev/video0 :
   Device or resource busy

With the majority of V4L2 drivers this situation doesn't happen as they 
are happy with two applications accessing the device at the same time to 
interrogate them. Anyway, I've got to think about it.

The other issue I notice is that your bttv driver is capturing at 
704x480, I think I'm going to apply Claus's patch exactly like his 
original and not my variation, so that it will force it to use 640x480.


Cheers,
Doug