Cory, Bryan, Thanks for the info, I will experiment with other DisplaySize values in a 4:3 ratio until I find a text size that is comfortable.
Cory, the hardware I built is the same as yours, it uses a 3.579545MHz crystal adjusted with the trimmer (good enough for the application we're using it for). I don't have equipment to calibrate this either, but my tv seems to lock on over a wide range, so I found the extents on both sides where the picture lost sync and then centered the trimmer between them. I agree that the output is far superior to what I get from nvidia's tvout, and I never got their mythical scaler bypass mode to work either. I'll try emerging a few different versions of the nvidia driver and see if I can determine which ones have working interlace. Let me know if you find out the version you're using. Thanks again for the help. Ben On 7/28/05, Bryan Mayland <[EMAIL PROTECTED]> wrote: > Cory Papenfuss wrote: > > > Nicer than any tvout on any vid card I've ever seen... would you > > agree? Just a quick question... did you use a crystal for the 3.58MHz > > color subcarrier? Is that the trimmer cap you're talking about? I > > had a bugger of a time getting it calibrated, as I don't have a > > spectrum analyzer. I did have an RF generator, though. I ended up > > setting it by tuning up 3.58xxxMHz into the RF generator, using it for > > scope sync, and trying to "freeze" the output of my card. > > You all are making my head explode! > > > IIRC, the DisplaySize is supposed to be units, not pixels... like > > inches or cm. The ratio of them will set the aspect ratio > > mplayer/mythtv uses to play, but it's also used to calculate the dpi > > of the Xserver. Now that I RTFM, I see it's in mm. Try different > > values (in the same 4x3 ratio) and see if you can get the scaling > > right. I seem to remember I had to set Mythtv to use extra-large fonts. > > Yeah the units is in mm. What I like to do is figure out what DPI I > want (usually 75) then calculate DisplaySize depending on the resolution > I want to run. > mm = Pixels * 25.4 / DPI > For example, if I have a 1680x1050 display, and I want 75 DPI: > 1680 * 25.4 / 75 = 569mm > 1050 * 25.4 / 75 = 356mm > (of course this could be simplified to just pixels * 0.339) > > Use xdpyinfo to check you're getting the values you expect if the fonts > look wacky. > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
