I have implemented what will become the official v4l sliced VBI API. This is a
rather large change which also breaks VBI embedding in MythTV. This is
temporary, I'll have to think how to work around this.
From the ChangeLog:
- Replace the ivtv-specific sliced VBI API with the new video4linux
sliced VBI API. This will break any program that uses the following
ioctls: IVTV_IOC_S_VBI_MODE, IVTV_IOC_G_VBI_MODE,
IVTV_IOC_S_VBI_FMT,
IVTV_IOC_G_VBI_FMT, IVTV_IOC_TRY_VBI_FMT and IVTV_IOC_G_VBI_CAP.
This includes MythTV, so VBI embedding won't work for now. Before
the
release something should be done about that.
- Do not passthrough VBI data that is not in the expected line/field.
If someone can do a quick test and see how well CC data is handled: try to run
vbi /dev/vbi0 and see if VBI data is seen. Also run vbi-detect and do a test
with ivtvctl -w cc -b cc -x 1; cat /dev/video0 >/dev/video16 (PVR350 only).
It seems to work OK on PAL, except for the fact that WSS doesn't seem to be
either embedded or reported back through /dev/vbi4.
This is one of the two bigger changes that I want to do before starting a 0.4
series. The other is the format of the embedded VBI data: I want to see if
the DVB standard can be used.
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
