On Sat, May 9, 2009 at 10:39 AM, Andy Walls <[email protected]> wrote: > On Sat, 2009-05-09 at 08:54 -0700, Jim Stichnoth wrote: >> Thanks Andy, that is very helpful. >> >> Here is what dmesg says about my card: >> ivtv: Start initialization, version 1.1.0 >> ivtv0: Initializing card #0 >> ivtv0: Autodetected Hauppauge card (cx23416 based) > > Do you know what A/V decoder your board has: CX25843, MSPnnn, SAAnnnn, > etc.?
I would guess CS25843, based on /var/log/messages: May 9 10:19:55 mythmaster kernel: tveeprom 1-0050: audio processor is CX25843 (idx 37) May 9 10:19:55 mythmaster kernel: tveeprom 1-0050: decoder processor is CX25843 (idx 30) May 9 10:19:55 mythmaster kernel: cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0) >> I ran osc, and it looks like the DISH VIP211 is inserting 2 very clean >> lines in the VBI with the rest blank. >> >> When I try to examine the raw VBI data (zvbi-ntsc-cc --cc -d >> /dev/vbi0), I get good caption text. This is consistent with what >> shows up on a direct TV connection. > > That's consistent with STB's. OK, so raw VBI capture and software > decoding of CC works. > > What lines did osc say the CC waveforms were on? "Row 11 Line 21" and "Row 23 Line 284". All others are blank. >> When I try to examine sliced VBI data (v4l2-ctl -d /dev/video0 >> --set-fmt-sliced-vbi=cc ; zvbi-ntsc-cc -S --cc -d /dev/vbi0), I get >> nothing at all. No errors, no warnings, no cc text printed. Just no >> activity/output until I kill it. >> >> If I try either of these zbi-ntsc-cc commands while a MythTV capture >> is going on, I get a series of messages "VBI read timeout (ignored)". >> In addition, running with the -S option gives an initial error >> message: "VIDIOC_S_FMT failed: Device or resource busy." I suppose >> that confirms that MythTV is actively looking at the vbi device. >> >> So it looks to me like the driver is having troubles with the sliced >> VBI. Any suggestions on diagnosing this? > > Nope. I'll have to test with my PVR-150MCE. If I can't reproduce the > problem, I'll come up with suggestions. > > It looks like the VBI slicer in the CX25843 (if that's what you have) is > not being set up properly, or the lines aren't being captured and > decoded properly. Not that I know anything, but I would guess the latter since the VBI slicer seemed to work perfectly with the old STB on the same S-video input. > I just fixed this for the cx18 driver for NTSC and am going to fix it > for PAL this weekend (hopefully). > > > Once I fix that, I'll try to look at the cx25840 module and ivtv module > next weekend. The cx18's integrated A/V decoder is very much like a > CX25843. What I would do will fix cx25840 and ivtv, but it might break > sliced VBI in ivtv for other digitizers, or break sliced VBI for chips > that do sliced VBI with a CX2584x. Out of curiosity, is there a discussion thread about the fix you're talking about? Jim _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
