Re: Captions/BTTV

[Cyrus Adkisson <lists@xxxxxxxxxxxxxxxxxx>]

So, I think this closed captioning thing is different from case to case. 
Right now I'm having a situation where I get the garbled output (see 
below), but ONLY when using video capture cards at the same time. When 
they operate independently, they seem fine. Right now it's happening 
with two K-World BT878RF cards, but was also happening with two Winfast 
2000 Deluxe cards. What in the heck does this? The picture and reception 
are fine. I don't get it.

Cyrus

Garbled output:

LIKE HE DID NOT WANT THAT TO BE
IY
s Asd N O4USILL ,VER
BE AE TO UNDERSTAND WHAT YOU
WENT THROUGH, BUT CAN YOU JUST
TELL US HOW IT FELT TO BE IN
THE ROOM I YOUR HOME WITH THI
O4TW
THINGS WERE GOING TO HAPPEN
EIER I WAS GOING TO WALK OUT
OF THERE ALIVE OR I WAS GOING
TO BE DEAD, ANI JUST REALY
SAID OK, IM GOING TO SHOW HIM
I9I



Cyrus Adkisson wrote:

> Cyrus Adkisson wrote:
>
> > David Liontooth wrote:
> >
> > > Michael Jackson wrote:
> > >
> > > > My apologies on the HTML formatted post earlier.  Here's a readable 
> > > > one.
> > > >
> > > > ________________________________
> > > >
> > > >     From: video4linux-list-bounces@xxxxxxxxxx
> > > > [mailto:video4linux-list-bounces@xxxxxxxxxx] On Behalf Of Michael 
> > > > Jackson
> > > >     Sent: Monday, January 31, 2005 6:24 PM
> > > >     To: 'Linux and Kernel Video'
> > > >     Subject: Captions/BTTV
> > > >             Hello, all.  I'm back.  :)
> > > >          Here's an interesting issue.
> > > >            My newest pet project is dealing with closed caption data.
> > > >          I'm playing around with a bunch of avermedia PCI 350's 
> > > > that seem to
> > > > work well for our purposes.
> > > >          I'm messing with ntsc-cc to pull captions right now, 
> > > > called as
> > > > "ntsc-cc -c"
> > > >          What's interesting is that ntsc-cc will pull captions 
> > > > perfectly as
> > > > long as XawTV is running.  As soon as I quit, the captions become 
> > > > "mangled,"
> > > > for lack of a better word - They become very nonsensical.
> > > >          Example output:
> > > >          BUILERE FAST.
> > > >     UI
> > > >     LA ARLYCENY
> > > >         ONERLI
> > > >         NTEQTY
> > > >         ADT         TR99
> > > >     'SCE
> > > >     HENT
> > > >         This is on kernel 2.6.10...  Using bttv, autodetecting the 
> > > > card.
> > > > Again, video and sound work beautifully (as long as I go from the 
> > > > audio out
> > > > to the line in)
> > > >          I'm just wondering what sort of 
> > > > initialization/uninitialization is
> > > > happening here that makes the captions switch from "working" to 
> > > > "garbled."
> > > >  
> > > I'm also surprised by the garbled stuff --  I thought closed captioning
> > > was located in the 'virtual blanking interval', so why is anything 
> > > available
> > > at all if the picture isn't being received?
> > >
> > > BTW I'm doing robust and reliable ntsc-cc -cp >> $DIR/$FIL.txt &
> > > capturing while mencoder is running to a cron job -- works great.
> > >
> > > Dave
> > >
> > >
> > >
> > > --
> > >
> > > Unsubscribe 
> > > mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> > > https://www.redhat.com/mailman/listinfo/video4linux-list
> > I'm getting the same error described above. Perfect captioning while 
> > xawtv is on but as soon as it goes away, there is severe garble. And 
> > it doesn't matter if xawtv is never actually turned on... if I reboot 
> > and try ffmpeg without even touching xawtv, I still get the garble 
> > out of ntsc-cc.
> >
> > I've had this problem before and somehow got around it. I think maybe 
> > just kernel upgrades fixed the issue. The error is occurring with a 
> > few leadtek winfast 2000 cards in a fedora core 3 i386 machine. The 
> > weird thing is I have another computer with the same devices, os, and 
> > architecture working perfectly well. I don't know what the difference 
> > is. If anyone has any further suggestions, they would be greatly 
> > appreciated.
> >
> > Cyrus
> >
> > --
> >
> > Unsubscribe 
> > mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/video4linux-list
> I think I figured it out (again). Whatever program you're running 
> while trying to capture closed captions has to be set to the correct 
> frame rate for your capture device. I was using ffmpeg, which sets it 
> automatically to 25 fps. All I had to do was put "-r ntsc" or "-r 
> 29.97" in the command and it started causing ntsc-cc to behave correctly.
>
> Hope that helps.
>
> Cyrus
>
> --
>
> Unsubscribe 
> mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list

--

Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list