Hans Verkuil wrote:
I've made a new release (available from www.xs4all.nl/~hverkuil until added
to the regular archive).
This one might be less stable than 0.3.7g since I've added sliced VBI for
the PVR150/500/PG600 cards, and it hasn't been tested very well. Especially
NTSC is basically untested.
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????
Thanks,
Chris
--
===
Chris Kennedy
[EMAIL PROTECTED]
-------------------------------------------------------
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
