Sottek, Matthew J <[EMAIL PROTECTED]> wrote:
>
>[...]
>works most of the time. Allowing user defined modelines in XF86Config
>is bad enough, but having Apps insert modelines on the fly is really
>[...]
Yes but Xmame users need these user defined modelines and it wouldn't be worth us
running X if
Sottek, Matthew J ([EMAIL PROTECTED]):
> Let me summarize the options you've discussed and comment on each.
Matt! Great summary of the options.
> Assume 59.94 video.
Let's assume true 59.94 video, no 3:2 pulldown or other conversions,
and I want to display the full motion or better. Play
Let me summarize the options you've discussed and comment on each.
Assume 59.94 video.
Option 1: Run the display at 59.94. This is what you were attempting to do
by inserting modelines I presume? Using this method you don't
introduce any more judder than already existed in the video sequence.
T
Sottek, Matthew J ([EMAIL PROTECTED]):
> I understand why you are trying to generate the modelines on the fly,
> but I really think this is a bad idea. [...] I actually have a flat
> panel (Analog input) at home that is sooo finicky with timings that I
> have to have them exactly as expected or
Over the holidays I fixed XF86VidModeAddModeLine and
XF86VidModeSwitchToMode in my local copy of 4_1-branch. My patch though
is very strange and not entirely correct.
I don't believe the current CVS code ever worked for anyone: I felt I
was completing the code rather than bugfixing it. That
