Chris Kennedy wrote:
This seems to look good on raw VBI output from what I can tell so
far. The sliced VBI on the pvr150 for CC NTSC doesn't seem to work
though, and the pvr350/250 seem to show a bunch of junk characters
randomly (strings of dtdtdtdtdtdtd over and over, or spaces oddly set,
was always clean in the past). The pass through VBI to the TV and
maybe either that or the VBI CC embedding it not working, nothing is
output and seems not to activate it in the logs. I get nothing on the
vbi scanner utilities output for line 21, or anyother line. So that's
my report, seems to have killed most NTSC VBI besides raw here, should
have time to do any tests, wondering if it's just me, are others in
NTSC CC areas seeing similar results????
vbi-detect shows CC data on line 21 for me, but I don't get any CC on
Live TV. I do get CC on programs that were recorded with an earlier
version of the driver, however.
Watching Live TV via MythTV I also get the following errors (which I've
never seen before):
ivtv: ivtv ioctl: Buggy application set embed mode to 4 which is way
out of range
ivtv warning: IRQ: IVTV_IRQ_DEC_DMA_ERR
Then MythTV crashed.
Daniel
Daniel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
