Re: [Deinterlace-discuss] Another bug to fix

[Rob M. <rob...@gm...>]

At 18:35 01-03-07, Torsten Seeboth wrote:
>I have no issues with my cx card and as far I remember with an bt card some
>time ago too. I could be wrong but from feeling it does not depands on
>capture chip but on the machine you have. Mine is a bit outdated (1.8GHz,
>@512MB, GeForce2), maybe the reason why no overflow occurs in waiting loops.

Maybe it is also dependant on the motherboard?

>With current cvs no combobox is working.

Can you be more precise what is not working? I have tried several 
comboboxes and dialogs and they all seem to work fine.
If there is a problem I am afraid I created it by messing up 
resource.h when applying the scheduling code. I patched the file 
manually to prevent problems.

Could it be that you just need to recompile dscalerres.dll?

>  When using D3D output I have
>13DF/S. And so on. Very instabily atm.

I don't see any stability issues any more.
What video card do you have?

What is taking so much time? You can see this on the developers OSD 
screen, by default enabled with a debug build. (just press enter a 
couple of times with a debug build. press R to reset the statistics 
and wait 20 seconds to get stable readings.)

>That is true. Is there no other way for waiting?

I suspect that a simple Sleep(1) in the wait loop does wonders.

Unfortunately I have no real experience with Judderterminator. I have 
used a monitor at 60Hz (with 50Hz PAL) in the past and motion looked 
very bad with or without Judderterminator. Nowadays the NVIDIA 
drivers are finally capable of driving my LCD with 50Hz and movement 
is as smooth as it can be.

Rob