U and V chrominance components are swapped which basically looks the same as swapped R and B (we are in YUV color space).
Pierre-Loup Griffais (aka Plagman) from Nvidia has already created the patch for libvdpau – http://www.nvnews.net/vbulletin/showthread.php?p=2518770#post2518770 – which is intended as hack. If it really was Nvidia's problem we'd have seen the fix already, the bug is known since FP 11.2 beta.
As Plagman explains: "The problem only happens when Flash uses software decoding but VDPAU for presentation; it swaps two arguments of the call to upload the video data into VDPAU in that case." (http://bit.ly/HVK747)
Avidemux bug is unrelated, it affects only VP8 videos and VDPAU is not involved – I can reproduce the same problem on any hardware.
The newer thread on Nvidia forums – http://www.nvnews.net/vbulletin/showthread.php?t=177380 – points to VDPAU_NVIDIA_NO_OVERLAY environment variable which seems as even better workaround than disabling hardware acceleration in Flash Player.
U and V chrominance components are swapped which basically looks the same as swapped R and B (we are in YUV color space). www.nvnews. net/vbulletin/ showthread. php?p=2518770# post2518770 – which is intended as hack. If it really was Nvidia's problem we'd have seen the fix already, the bug is known since FP 11.2 beta. bit.ly/ HVK747)
Pierre-Loup Griffais (aka Plagman) from Nvidia has already created the patch for libvdpau – http://
As Plagman explains: "The problem only happens when Flash uses software decoding but VDPAU for presentation; it swaps two arguments of the call to upload the video data into VDPAU in that case." (http://
Avidemux bug is unrelated, it affects only VP8 videos and VDPAU is not involved – I can reproduce the same problem on any hardware.
The newer thread on Nvidia forums – http:// www.nvnews. net/vbulletin/ showthread. php?t=177380 – points to VDPAU_NVIDIA_ NO_OVERLAY environment variable which seems as even better workaround than disabling hardware acceleration in Flash Player.