Time to say goodbye.

[knirfie]

Originally posted by defaultuser

But I can wait. I have a feeling your NDA is non-binding should the company fail, so perhaps in a few months you can tell all.

little optimistic aren't we? like matrox will really fall in a few months just because the same happened to your favorite graphics company. GET A LIFE, and a matrox card

[Maggi]

Originally posted by VigilAnt

The "banding" problems are soley a 3D issue. Not 2D.

VigilAnt

This is not true, VigilAnt !!!

Unless you call video overlay "3D" as well ...



Seriously, I cannot believe you missed my posts about PowerDVDs internal system test that benchmarks various video overlay modes and causes the exact same banding problems that occur when running 3D apps ...

Cheers,
Maggi

[VigilAnt]

Originally posted by Maggi


This is not true, VigilAnt !!!

Unless you call video overlay "3D" as well ...



Seriously, I cannot believe you missed my posts about PowerDVDs internal system test that benchmarks various video overlay modes and causes the exact same banding problems that occur when running 3D apps ...

Cheers,
Maggi

Thank you for taking the time to respond, it brings up a very valid point and one that I think I can address.

I did not miss your posts regarding the benchmarks, and I have no doubts that it does it during those benchmarks. However this problem does not expose itself when running real applications where video is actually overlayed on the fly in the real app. Am I missing something or do you agree?

VigilAnt

[DGhost]

could be something dealing with the high level of traffic being handled by the overlay in benchmark mode... several people reported that the banding issue got significantly less noticable by enabling VSync on 3d....

[TdB]

well, if a framerate-cap would solve the problem, then I think they should enable it as an option in the drivers.
it would be acceptable as a temporary solution IMO.

[Wombat]

A framerate cap? Doubtful. I see the problem quite strongly even if the game is pushed down to 20fps.

[Maggi]

Originally posted by VigilAnt

Thank you for taking the time to respond, it brings up a very valid point and one that I think I can address.

I did not miss your posts regarding the benchmarks, and I have no doubts that it does it during those benchmarks. However this problem does not expose itself when running real applications where video is actually overlayed on the fly in the real app. Am I missing something or do you agree?

VigilAnt

Thanx for coming back to me ...

I partly agree that it is usually not noticable, when just playing back in video overlay.

Knowing that the problem exists and becomes evident at high framerates, made me have another really close look and it also occurs in normal playback, but it is just so subtle, that you usually won't see it.

In other words, the problem is there all the time, but under normal circumstances not really visible when using video overlay.

Sad, but true !



Cheers and keep up the good work !
Maggi