Hi Chris, been testing #0.3.6e and #0.3.6f: both versions seem to break VBI for me (PVR350, PAL). When reading /dev/vbi0, the ID field of the ivtv_sliced_data structure returns consistently zero, meaning there's no VBI-data available.
However, "ivtvctl -B" returns: "vbi service set = 00000001", so there should be VBI-data available (my previous version, 0.2.0 rc3j, Gentoo, does give me VBI-data). capturing /dev/video0 works OK for #0.3.6e and #0.3.6f... Should I take extra actions to get VBI working properly again? I did return to #0.2.0 rc3j, VBI is OK again :-) Regards, Johan Duinkerken. Op Tuesday 7 June 2005 22:07, schreef ivtv: > This uses smaller buffers for encoding/vbi, interesting to see how well > this works and should be alot better about buffer allocation errors, > also minimize linked list mem size to minimal amount that will ever be > needed. > > #0.3.6e: http://www.ivtv.tv/releases/ivtv-0.3/ > > Thanks, > Chris ------------------------------------------------------- ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
