People incorrectly assume that AMD drivers suck. They don't.

[elanthis]

That's... just awful. How the fuck do they both with their huge driver teams and decades of writing drivers never test two apps running at once?

Partly because of the 98% of people who run their drivers, none of them use OpenGL. Even on Windows, the OpenGL stability of both AMD and NVIDIA is _terrible_. We shipped a game 4 months ago using OpenGL that literally crashed on every single NVIDIA driver except the very very latest, and we had to spend tons of time ripping out and rearranging bits of the graphics architecture until we found out what was causing the crash and how to get things rendering without triggering it. (Hence the interest of Valve and others in FOSS drivers.)

The D3D drivers are far more stable. In this case, the stability has a bit less to do with D3D being a better API and much more to do with D3D actually being used. Recall that Linux users still frequently run non-GL-accelerated desktops, use DDX drivers and EXA/RENDER to get their basic apps on screen. OS X uses an entirely Apple-written driver architecture. Very few Windows apps use OpenGL, and even most of the ones people think use OpenGL actually use D3D: all Windows implementations of WebGL run over ANGLE, many of the "big 3D content apps" have switched over to D3D on Windows, and the games that use OpenGL are almost entirely just simple little 2D indie games that don't do anything even remotely interesting with the GPU.

Granted, Microsoft also has tests for D3D and properly designed the driver model such that every vendor didn't have to reimplement all of D3D internally, while Khronos still doesn't even offer a test suite, much less a core OpenGL framework for the ISVs to build (and even if they did, at this point the ISVs have too much invested in their internal implementations, so a switch is unlikely to happen without some strong-arming).

[RussianNeuroMancer]

I have tested this right now running Gnome Player with VDPAU accelerated "Solaris (1975)" under XFCE/Compiz. Its tear free.

Try this samples: http://rghost.ru/37220226 http://rghost.ru/37220233 http://rghost.ru/37220247 .

[Gusar]

Even nVidia employees confirm that can not be TearFree

False.

Quoting ftp://download.nvidia.com/XFree86/Li...ausupport.html:

The overlay path is guaranteed never to tear, whereas the blit method is classed as "best effort".

[RussianNeuroMancer]

I'll fix quote of my message for you:

Even TearFree video playback under compositing environment with nVidia proprietary drivers? Not likely. Even nVidia employees confirm that can not be TearFree

False.

You are fail:

The overlay path is guaranteed never to tear, whereas the blit method is classed as "best effort".
...
The following conditions or system configurations will prevent usage of the overlay path:

• Overlay hardware already in use, e.g. by another VDPAU, GL, or X11 application, or by SDI output.
• Desktop rotation enabled on the given X screen.
• The presentation target window is redirected, due to a compositing manager actively running.
• The environment variable VDPAU_NVIDIA_NO_OVERLAY is set to a string representation of a non-zero integer.
• The driver determines that the performance requirements of overlay usage cannot be met by the current hardware configuration.

Now confirmed not by nVidia employees, but by nVidia properietary driver documentation. Thank you for this link.

[Gusar]

Err, dude... You said tear-free can not be. But the documentation says "best effort". That doesn't mean it can't be, it just means there's no guarantee. No guarantee != can not be. No guarantee = you might be tear-free, but you might not.

So the fail is 100% you.

[RussianNeuroMancer]

Err, dude... You said tear-free can not be. But the documentation says "best effort". That doesn't mean it can't be, it just means there's no guarantee. No guarantee != can not be. No guarantee = you might be tear-free, but you might not.

I have enough GeForce's and I done enough testing to say "it can not be" (under compositing environment).

[Gusar]

I have enough GeForce's and I done enough testing to say "it can not be" (under compositing environment).

You also say hardware video decoding doesn't work on Ironlake, but I have no problem whatsoever with that. So what you say does not have much (if any) merit.

Besides, the discussion was that the Nvidia devs supposedly said tear-free video in a composited environment can not be. Which is false.

[RussianNeuroMancer]

You also say hardware video decoding doesn't work on Ironlake, but I have no problem whatsoever with that.

You never test it with BD-Remux as I remember.

Besides, the discussion was that the Nvidia devs supposedly said tear-free video in a composited environment can not be. Which is false.

Sure, they never say "our drivers in fact sucks here", instead they said "our driver maybe suck here".

[Gusar]

You never test it with BD-Remux as I remember.

I tested 1080p, I mentioned that on some other thread some time later. It wasn't from a Blu-ray though. So if you're still not satisfied, link to a sample. I'm not going to download 40GB of stuff, but if you provide a smaller sample of a Blu-ray video, I'll run it.

Sure, they never say "our drivers in fact sucks here", instead they said "our driver maybe suck here".

Dude, why can't you just accept that your initial statement was false, and that someone in fact doesn't have tearing, instead of writing this nonsense? It doesn't help your credibility, it's nothing more than trolling.

[RussianNeuroMancer]

I'm not going to download 40GB of stuff, but if you provide a smaller sample of a Blu-ray video, I'll run it.

I doesn't check this one, but you may try to google for "Pole to Pole mkv".

Dude, why can't you just accept that your initial statement was false, and that someone in fact doesn't have tearing

Because different people may notice tearing, or may doesn't notice it. If someone doesn't see tearing (and need special samples that expose issue) that doesn't mean there is no tearing.

You know, it's like high-frequency squeak (I hope it's right English term) defect in audio stream, or incorrect color space conversion in video - most of people doesn't notice such problems, but it doesn't make such problems doesn't exist.