I was also seeing garbled VBI with 0.3.7k - osc showed garbage on all
lines, and the sliced decoder was giving me no data. It worked fine
with 0.3.7i. (this was on a PVR-350).
--bob
On Aug 29, 2005, at 12:00 PM, Hans Verkuil wrote:
On Monday 29 August 2005 15:34, Boleslaw Ciesielski wrote:
Hans Verkuil wrote:
I assume that you tested with 0.3.7k. Can you also test this with
0.3.7g?
Yes. I just tested 0.3.7g as well, but the results are the same. Both
vbi0 and vbi4 are garbled but the offsets seems to be OK (see
attached
log).
If vbi0 is already garbled then the problem is at the capture side.
Can you
test with the capture test tool of the zvbi library? (See doc/
README.vbi for
where to get it) That tool should show if the raw VBI is captured
correctly
and determine if it isn't perhaps a bad reception.
Hans
-------------------------------------------------------
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
-------------------------------------------------------
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
