Thanks for the notes and tips, Doug. I'll be trying the debug version and checking that link tomorrow and will report results etc then.
Cheers, Todd Douglas Kosovic wrote: > Hi Todd, > > Sorry, I was looking at an older bttv driver source code, there is an > Impact VCB 64900 card listed in the new code, but suspect it isn't the > model you are using. The bttv devices link on the following page has > more useful info about adding support for new bt878 cards: > http://linuxtv.org/v4lwiki/index.php > > But I suspect if you set the bttv driver's card module parameter to 0x8f > (which corresponds to the existing Impact VCB 64900), the driver will > work correctly with your Impact VCB. > > I also forgot to get back to you about adding the sliders to the > VideoProducer/Video service config dialog box. The problem I had was > that after adding the 6 sliders, the okay and cancel dialog buttons > disappear off a 1024x768 screen (which is still common for projectors), > so didn't added them. I also wanted to add a few UVC V4L2 controls, like > autofocus, zoom, power line filter and back-lighting > > > Cheers, > Doug > > Douglas Kosovic wrote: >> Hi Todd, >> >>> This problem still exists on Fedora for me (AG3.1b2). It exists on >>> multiple computers; however.... >>> Am I the only person experiencing this? >>> >>> Symptoms are: >>> >>> Multiple video producers on Fedora and/or Redhat. >>> When I join a room, the proper device and port are selected; however on >>> some of the producers (not consistent... sometimes one, sometimes two >>> etc) it is just blue output. >>> When I hit 'Menu' and reselect the port (not even deselect - just >>> reselct) the camera source properly shows up. >> >> Install the vic-debug-enabled RPM from: >> http://www.vislab.uq.edu.au/accessgrid3/fedora/development/RPMS/ >> >> e.g: >> rpm -e --nodeps vic >> rpm -ivh vic-debug-enabled-2.8ucl1.3.1-0.1.20071017svn.fc7.i386.rpm >> >> it should hopefully output debugging info on what is going wrong. >> >>> Further, on many of these capture cards (bttv based Impact VCB) I have >>> to select the Television input when in fact I'm using one of the >>> Composite inputs.... >> >> The Impact VCB isn't listed in bttv-cards.c source file of the bttv >> driver, the known cards have their input port details and other stuff >> recorded in that file (like the GPIO bus wiring), if the card isn't >> known the bttv driver fallbacks to a generic bt878 card (which might >> only partly work). You might be able to configure /etc/modprobe.conf >> to tell the bttv driver what is what by using module arguments or >> submit a bug report to the bttv driver maintainer to have your card's >> details added. >> >> The Windows application btspy (in combination with the original >> Windows driver for the card) is often used to get the specific details >> of the Bt878 based card. >> >> Cheers, >> Doug >> >
