On Fri, Nov 28, 2003 at 08:30:27AM +0100, Denis Oliver Kropp wrote: > However, I'm facing a problem concerning it's TV encoder (VT1622), > or at least the register tables from viafb. Using 720x576 doesn't > produce a TV picture as expected. Even using overscan there's way too > much of it within the visible area of a standard TV set, i.e. the picture > is scaled down, producing interferential effects and blurry motions when > the framebuffer contains interlaced data. Also, the scaling results in a > pulpy picture in general.
Nasty! > I tried all supported modes with and without overscan. None of these > correctly passed through the interlaced information to the TV set. > > I wrote a small test program which fills even lines with black and odd > lines with white pixels. The TV set should turn into a stroboscope, but > instead it shows a steady gray picture. Using the different modes just > varies how homogenous this gray picture is, actually making the interference > more or less visible. > > I would appreciate any help or documentation about VT1622(M). Do you have the 1621(M) datasheet from http://sxpert.esitcom.org/EPIA/ ? I'm not sure how much of it applies to 1622(M) though. > Ville: How does dfbmga display interlaced videos on CRTC2 flawlessly > regardless of how much the video is stretched to fullscreen? I have no idea :) It seems to work in almost all cases but not every time as was indicated by the mail from Neil Radisch. The scaling is done on the TMU and the TV encoder doesn't touch the data. > Does it > stretch the fields seperately? No. But I've thought about adding such a thing. Currently it would require using DSCAPS_SEPARATED surfaces but I haven't added support for that in the CRTC2 driver. If we would add a new blitting flag we could do it on interleaved surfaces too. Maybe something like DSBLIT_FIELD? Apps would then need to do it twice to get both fields but I think it would be more flexible than always blitting both fields. SetField() could be used for this I think. And we'd need another way of marking layer surfaces as interlaced. > Log message: > Disabled dithering again... > > ... because: I fixed the triangle (rectangle) color bug! ;-] *jump* *jump* LOL. Absolutely hilarious stuff... :) -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
