Video Capture box stability probs

[Robert Olson]

The one you want is 0.01. It's actually bttv-0.6.4h, not sure why it comes 
up as the other version.

--bob

At 02:05 PM 6/9/2000 -0500, Jeff Long wrote:
>Bob,
>         So on our machines are we supposed to be using the 0.01 or the 1.00
>drivers?  It was unclear from your message which we were supposed to
>have (I'm guessing 1.00 but figured I'd verify).
>
>Jeff Long
>KU
>
>Robert Olson wrote:
> >
> > Try running dmesg and look for a verison message from bttv. It should look
> > something like this:
> >
> > Linux video capture interface: v0.01 ALPHA
> > i2c: initialized
> > bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 120, irq: 15, memory: 
> 0xfd5fe000.
> > bttv1: Brooktree Bt878 (rev 2) bus: 0, devfn: 128, irq: 11, memory: 
> 0xfd5fc000.
> > bttv: 2 Bt8xx card(s) found.
> > bttv0: model: BT878(Hauppauge new (bt878))
> > i2c: bus registered: bt848-0
> > bttv1: Hauppauge eeprom: tuner=Philips FM1236 (2)
> > bttv1: model: BT878(Hauppauge new (bt878))
> > i2c: bus registered: bt848-1
> >
> > The v0.01 ALPHA is a signal that it isn't the RedHat default kernel
> > drivers. THey show up as something like:
> >
> > Linux video capture interface: v1.00
> > bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 136, irq: 9, memory: 
> 0xf4001000.
> > PCI: Enabling bus mastering for device 00:88
> > bttv: 1 Bt8xx card(s) found.
> > bttv0: NO fader chip: TEA6300
> > bttv0: model: BT878(Hauppauge new)
> >
> > --bob
> >
> > At 10:16 AM 6/9/2000 -0500, Allan Bautista wrote:
> > >Im having some problems with my video capture box.
> > >
> > >Spec:
> > >dual p3 600's w 256mb PC100 mem
> > >4 Hauppage wintv cards
> > >3com 10/100 nic
> > >
> > >Running RedHat 6.1, configured with Bob's script
> > >
> > >Problem:
> > >Im constantly dropping transmissions from this box, all 4 feeds work fine
> > >for about 3-4 min after theyve been started.  From there they will start
> > >to drop out one by one till they are all gone.
> > >
> > >Ive tried running 3, 2 then one feed to see how long they will last.
> > >the longest transmission Ive had sofar is about 1 hour with one feed.
> > >
> > >Now, during the Globus tutorials I was having the same problem, so I
> > >manually started up vic sessions in the proper rooms and had better
> > >stability with that.  Differences were quality settings, fps settings, and
> > >rate settings.  I usually had an fps of 30, q of 10, and set the threshold
> > >rate at 500k.
> > >
> > >Ive already reinstalled all the software so my vid machine is clean, but
> > >exhibiting the same behavior as before.  Prior to installing the VV stuff,
> > >"when all the feeds were manually typed in", the machine was stable, it
> > >would transmit for days/weeks with no problems.  So Im not sure where to
> > >point, hardware or software.  I think the hardware is fine, and since Ive
> > >reinstalled clean I "think" the software setup is ok.
> > >
> > >The only thing close to an error message I get comes from the window I
> > >spawned vrm-viewer from
> > >
> > >         subprocess died: ag.VicVideo at 80de1a8
> > >         delete returns false
> > >
> > >Now Im just plain stumped.
> > >
> > >
> > >any suggestions?
> > >
> > >
> > >Al @ ACCESS
> > >
> > >abautist at ncsa.uiuc.edu