[MPlayer-users] first frame green with directx vo using slave mode

[Reimar Döffinger]

On 15.11.2013, at 14:26, mo <mo at avpresentations.com> wrote:
> On 11/15/2013 01:59 AM, Reimar Döffinger wrote:
>> 
>>>  I can provide benchmarks I did with directx, direct3d and gl if that would help.  I couldn't really understand what they showed.
>> In particular if they contain performance traces or CPU usage numbers that might indeed help.
> 
> [swscaler @ 023c6f00]BICUBIC scaler, from yuv420p to yuyv422 using MMXEXT
> VO: [directx] 1280x720 => 1280x720 Packed YUY2
> BENCHMARKs: VC:   2.863s VO:  11.166s A:   0.000s Sys:   0.586s =   14.615s
> BENCHMARK%: VC: 19.5895% VO: 76.4010% A:  0.0000% Sys:  4.0096% = 100.0000%
> 
> 
> 
> VO: [direct3d] 1280x720 => 1280x720 Planar YV12
> BENCHMARKs: VC:   4.341s VO:  31.850s A:   0.000s Sys:   0.180s =   36.371s
> BENCHMARK%: VC: 11.9354% VO: 87.5696% A:  0.0000% Sys:  0.4950% = 100.0000%
> 
> 
> 
> VO: [gl] 1280x720 => 1280x720 Planar YV12
> BENCHMARKs: VC:   3.043s VO:  33.065s A:   0.000s Sys:   0.221s =   36.329s
> BENCHMARK%: VC:  8.3762% VO: 91.0154% A:  0.0000% Sys:  0.6083% = 100.0000%

I was thinking of real CPU usage numbers like from e.g. task manager or similar tools.
MPlayer only shows time used, that can be far of from CPU used.
Either way this looks fairly consistent with vsync issues.
Also your issue is almost certainly the colorkey. Keep in mind that colorkey is a per-file option, so make sure to specify it before the filenames.

> However, I'dreally like to better understand the issues with 60 fps, which is indeed the refresh rate I use.  I had intentionally asked for videos to be created at 30 or 60 fps because I thought this would match up better to the 60 hz refresh.  What would you suggest for a better playback at 60 hz?  Would 59.94 fps work better, or is that still too close to the refresh rate?

That would probably be worse. Using Aero/a compositing window manager and disabling vsync in MPlayer itself should be the easiest solution.