Comments

PLS wrote on 12/17/2011, 11:48 AM
OK, updated to the latest graphic drivers and the GPU option has returned. However.... now in a 3D track motion section of the project. half the background is black when rendered out. It is fine during timeline playback. Plus Windows Media Player is hosed. When I play video it is black!!!
PLS wrote on 12/17/2011, 12:16 PM
Rolling back the drivers cured the Windows Media Player and black background in the 3D track motion section problems... but I am stuck without GPU acceleration with build 511... fun and games!!!
PLS wrote on 12/17/2011, 12:43 PM
Loading the latest beta drivers 290.36 seems to have cleared up my problems... fingers crossed.

Paul
Steve Mann wrote on 12/17/2011, 1:39 PM
Do we guess that you have an nVidia graphics card?


TheHappyFriar wrote on 12/17/2011, 1:43 PM
Sounds like a driver problem. I'd say it a REALLY big problem when the beta drivers from a company always fix things but the "stable" drivers don't. ;)

In the release notes there was some mention about nvidia gpu's & drivers, give them a read.
MPM wrote on 12/17/2011, 2:26 PM
>"Sounds like a driver problem. I'd say it a REALLY big problem when the beta drivers from a company always fix things but the "stable" drivers don't. ;)
---

It's as they say: "Complicated. :-)

Assuming you've got a graphics card that's new enough & far enough up the food chain, Nvidia or ATI, checking out the relevant driver forums you'll find performance can often vary a lot driver version to driver version. That's a part of why beta drivers get leaked, & why people use them. Code for GPU accel works the same way, though both companies focus much more on gamers since that's where their hi dollar markets are.

I'd expect this sort of thing to be Much more a problem with ATI than Nvidia, considering Cuda's been in widespread use for so long now, but the video ecosystem in your Windows install can have a lot to do with it. Direct Show filters that seem to work fine with DXVA can [too easily] break when you introduce driver code for GPU video accel, & DS filters you'd think were irrelevant often do get called -- it can sometimes be instructive to check things out while opening/playing/rendering video with Process Explorer [sysinternals at Microsoft.com] . The OP for example talked about WMPlayer breaking -- I've had that happen, & I've also fixed it once or twice by turning off .wmv hardware accel, or DivX, or mpg2, even though I wasn't trying to play any of those 3 when I found WMPlayer inop.

FWIW I've got to back up & try adding the latest ATI drivers this weekend, & 1/2 expect the same sort of problems -- that's why the full backup, as ATI can be *difficult* to restore older versions. If this version works well, then I'll try to find a modded version for win8, where for me anyway renders happen just a bit faster. :-)