On Monday 09 May 2005 02:36, Chris Kennedy wrote:
> Ah, it is working now, but seems it will output garbled CC, repeat
> letters alot, and not output all the CC, comes in spurts kinda, very
> odd, I'm looking closer, but sounds like still a possible parsing issue,
> seems like there's alot of stuff with the first 2 bytes 0x80...
>
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 8080e576
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 808079f2
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 8080f420
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 808070ef
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 80807020
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 808064e5
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 808067e9
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 8080e5f2
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 808020e5
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 80807562
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 8080ecec
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 80808073
> May  8 19:36:13 digit kernel: saa7127: CC data 3: 8080f294
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 8080a197
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 808061e3
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 80802094
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 8080d094
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 8080a297
> May  8 19:36:14 digit kernel: saa7127: CC data 3: 80806854

I believe that 8080 is the CC data of field 2 (XDS data). The actual closed 
captioning is in field 1 (that's the lower 16 bits). I think that a 
widescreen NTSC program will actually use the XDS data. Can you confirm that?

From what I remember all CC data is actually stored correctly in the stream, 
i.e. no CC data is dropped. So my suspicion is that it all boils down to 
timing problems with the output. First check that each VBI 'frame' is 
obtained on time from the stream. I.e. that you don't get multiple VBI frames 
in spurts instead of one frame per 1/30 second.

If that's OK, then it is a timing issue with programming the saa7127. Loop the 
output of the PVR 350 to the input of another PVR and check if the XDS data 
really ends up in field 2 and the CC data in field 1. I remember seeing 
problems with that.

Hope this helps,

                Hans


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to