> On 1/17/07, Robin Gilks <[EMAIL PROTECTED]> wrote: >> >> > Going back to 0.6.3 and even upgrading to 0.6.6 on the 2.6.16 kernel >> is >> > fine. >> > >> > What extra information is required to assist in tracking this one >> down? >> >> Further info... >> >> Same problem on both an SP13000 (Via C2) and a ASUS (Athlon XP2700+) >> with >> the same hardware/drivers. 0.6.x is fine, 0.8.x has problems on svideo >> input. Tuner input on both systems and both driver series seem OK (but >> 0.8.x takes 2-3 seconds to settle down). >> >> Its not something stupid like svideo 1 & 2 getting swapped is it? > > It sound a lot like the problem with vbi and scaling. See [1] for more > info. > > Greets > Sander > > PS: The user list is a better place to ask for help ;-) > [1] > http://ivtvdriver.org/index.php/Troubleshooting#Closed_caption_.28vbi.29_with_non_default_reolutions > >
So what is the backward step from 0.6.x to 0.8.x that I undo in order to make it work then - I'm not using VBI on s-video inputs (at least I've never seen Teletext or CC on anything other than an RF signal) so just why has this been implemented/broken? -- Robin Gilks _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
