This is something wrong with the firmware I believe, when we go into ff/rw
mode seems to re-init the VBI decoder, so we probably need to re-setup
that when coming out of ff/rw. I hopefully can get around to that here
sooner or later and put some code in to fix that, have been thinking about
that as being a problem but haven't had time to focus on it.
i did a little debugging myself on trying to get the CC turning back on
after
skipping ahead. i managed to get the CC turned back on. Well it said it did
in the dmesg that the CC turned back on at the after skipping ahead, but i
did not get any CC output to the tv. i looked into it a little more, and i
found
that something was spitting out "Unknown vbi data."
apparently ivtv vbi infromation is supposed to have "IVT0" or "ivt0" in
front of
the data, but i found that after skipping ahead it looked like this "ivAA"
and the
"AA" part are the funny ascii A characters.
this was as far as i could reach without actually understanding all the VBI
stuff.
hopefully it gives a hint to other people whats wrong.
stephen
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
