Rene Schumann <[EMAIL PROTECTED]> writes: >> > Latest kwintv dosnt work too. It crashes after start. >> >> kwintv sucks. > > But it should work at least and not crash right? ;-)
one doesn't code right everytime. every soft has bugs. anyway, i'll give it a look to try to make it works. but don't hope too much since 8.2 release candidates'll come fast now. > With -noxv it works ok, without this option my picture ist still > yellowed. > It looks like the range for color,bright etc is with -noxv still 0 to > 65535 but without option -noxv -1000 to 1000. > My .xawtv have had this settings > > [defaults] > color = 32000 > bright = 32000 > contrast = 25000 > > And so with a range from -1000 to 1000 all setting are set at maximum. > My new settings are > > > color = 30% > bright = 50% > contrast = 50% > > And there are no more problems with the range. > > But i i look at man xawtvrc is see this info > > Valid range is 0-65535, default is 32768. Adding a > percent symbol changes the range to 0-100, i.e. > "50%" has the same effect like "32768". > > IMHO the valid range -1000 to 1000 without option -noxv is wrong and > does yellow the picture if my config used the range 0-65535. if you rename your config file, the first time you run XawTV (that is the wrapper script), is the config file ok ? what i want is that a newbie install mdk, get an icon on his desktop and a menu entry, select his frequency table and TV norm, and voila, all is ok. at first, i fear that i must add a black list table for tv cards/graphic card pairs that don't support the v4l module.
