When I'm using MCE and a windowblinds skin with alpha blending and watching TV or video on the same monitor, computer slows down incredibly.

As soon as the MCE window is on the second monitor, it all runs smooth again.
If I then maximise a skinned window on the first monitor, it somehow must register as being on the second monitor too and the whole system once more slows down terribly.

I am 90% sure its the VMR video display mode being used by MCE conflicting or causing graphiccard/cpu heartache if it's being displayed on the same screen as a windowblinds alpha skin. Excluding MCE's program from windowblinds doesnt do anything (Didn't really expect it to)
and the issue does not occur with not alpha skins.

I would have no problem running the MCE on the second monitor and keeping all my other windows on the first monitor, but I can't maximise my windows cause it seems to render some part of the window on the extended desktop resulting in the slowdown. I can bypass the issue using windowfx maximization size limiter, but I would prefer to have an alternative solution, as even just moving a window partially off the first monitor edge (like i sometimes do just to look behind a window) causes the slow down also.

Also occurs with desktopx objects gadgets and widgets with alpha transparency in use. They just won't play nice on the same screen as the MCE video interface.

Please note, this is NOT the MCE interface, only the video rendering part, ie, the box where the video appears. The whole MCE menus etc all work fine. Just when video is playing, it hurts.

Comments
on Apr 22, 2006

Its a problem with the deinterlacing code in the ati drivers.  If it gets overlapped by semi transparency it starts using massive amounts of cpu.  It even happens if the semi transparency is under MCE.

I believe the simpler deinterlace options in the ATI drivers avoid this problem.  We will be speaking to ATI about this issue as its not just WB it impacts.

on Apr 24, 2006
Hi Neil, just wondering what you mean by 'simpler' deinterlace option so I can set it (if it's settable) and temporarily get rid of the problem.

Posted via WinCustomize Browser/Stardock Central