Hi Dominik That's not answer for you (sorry). I think - rather to Gerd and bytesex team. Hello. I just suggested that a few weeks ago - more information. The new saa drivers have new futures, which are (I belive) fully usefull, but to set them, neccesairly is background knowledge about tv cards work rules and more details about specified (v4l2 faq gives some answers). For example - ts device - frankly, I do not now exactly what it does (shame - sure something simple). The most interesting would be insmod options list for saa7134 with some more description of them. "modinfo" gives only list, but description is unsufficient. I miss for some example parameters (tuner types configuration - first). My own: I hoped that final 0.1.6 release will work faster and will remove gray line at the bottom of screen, but something works different (api?) and: ioctl: mcapture (*,fmt=*,size=*x*): Invalid argument - for Arpad Gereofy's mencoder. questions: Where should I dig in, to correct this? Which parameter maniputate with? P.S. There is on bytesex page information, that v4l2/OSS driver is mandatory for saa7134. I tried to compile it (latest no cvs release videodevX-200112, but if I compiled it first I could not compile saa module (structure not member 'ts'), if first was saa, then it use anyway only videodev1.o.old (and work worse) so what do I need that driver for, when v4l2 in patched kernel-2.4.19-pre8 is newer? Regards Wieslaw
