Re: [Deinterlace-discuss] Various reported overlay problems

[yvon q. <yvo...@nm...>]

Daniel Schmelzer wrote:

> Hi All--
>
> Yes, I agree with Tom--there have been sporadic but persistent overlay bug
> reports from those who didn't have any problems on earlier versions.  I have
> been collecting them on the following thread:
>
> http://www.avsforum.com/ubb/Forum12/HTML/010785.html
>

Hell, this "overlay update" error is in dTV/DScaler for ages now ! See http://deinterlace.sourceforge.net/FAQ.htm#OVERLAY

I've updated yesterday the FAQ and the statement "Seems to have disappeared since version ..." was still there, probably a sync issue. I should have
removed it since last january (see FAQlog.txt)

However, probably different issues here.

Some time ago, someone made me try to fiddle with the number of back buffers. We wanted to know how much buffers we could allocate because some
recent algoritm would work better with 3 or 4 buffers. I stopped at 25 without being able to show that I reached a limit. Probably putting 100 would
work also. This number, at least in the ini, doesn't seem to be used as we think it is.

Also what is quite new is what reports BGane on this topic ;

"I'm not sure that what I am seeing is the same problem.  It indicates in your FAQ that the problem likely occurs when resizing the screen on the
computer.  I am not touching my computer. I am merely changing chapters on my external DVD player.  And if the error is going to occur, it will
occur within seconds after having changed chapters.  Strangely - if I don't change channels and just let the movie play through - I haven't seen the
problem occur.

That is why I am led to believe that it might have something to do with the code related to the selection of deinterlace algorithm to use.  But I
will test that theory more fully by selecting a fixed deinterlace mode and see if I can get the problem to occur."

This is not limited to first time DScaler initialization. It occurs later, and without user interaction at the time it appears.

Back to the debug topic I wanted to start .. what debug options have we got to help trace such things ?

    Yvonus