- Potplayer download 4gb patch mod#
- Potplayer download 4gb patch driver#
- Potplayer download 4gb patch upgrade#
- Potplayer download 4gb patch code#
Just tried it, one time with NV12 and one with YUY2. I'd also like to know what the the X8R8G8B8 and Y'CbCr mixer surface formats do with the rendering color accuracy on different setups. I'm quite interested if this solves the problems with black screens on the beginning of rendering, and the bit-ordering problem (red/black screen) of the A8R8G8B8 surface. Keep in mind that there's no chroma up-sampling and no limited ranges for Y'CbCr if the mixer is forced to render in RGB mode. It's only enabled when (the always-been-fake) "Force 10-bit RGB Input" is selected. The following test builds are not very optimized (I compiled them), but have a broader range of acceptable mixer formats, except for the RGB types: only X8R8G8B8 (RGB32) is allowed. We have some priority in choosing the compiler, so any input for that item is very much appreciated. What you are talking about is issue 3 in my quote, i cannot find the post you are referring to, but i understand you are saying that for some people the problem occurs even with 10.12. So basically NV12 input to the renderer is broken with certain configurations of the EVR CP renderer and newer radeon cards.
Potplayer download 4gb patch mod#
Video Codec = ALL WITH NV12 OUTPUT (tested internal DXVA H264, internal software H264, ffdshow software H264, ffdshow divx, dscaler itcv mod mp2)ĭriver = Cat 10.9 (others have tried 10.10 and 10.12)Īnd now the kicker: changing output format of the decoder from NV12 to YUY2 brings back the picture. Renderer = EVR CP with vsync, accurate vsync and alternate vsync ON (all other off) Here is the information you requested about the problem:įiles = ALL (tested with mkv, avi, m2ts, ts -> black screen)
Potplayer download 4gb patch driver#
Judging from the other posts the black screen issue seems to affect only newer cards in the 5xxx and 6xxx series to different degrees but independent of driver version (tested 10.9, 10.10 and Peekstra tested 10.12a and also has problems). It wont fix the driver bugs but hopefully prevent triggering them. There are several ways to work around this problem, the devs are testing several solutions to find the best one. There is a limitation or bug in the mixer that prevents certain surface types to be mixed, resulting in just black for the blocked ones.
Potplayer download 4gb patch code#
Exact renderer related settings (CTRL+J might still work)ĮDIT: breaking news: After days of research we think we have found the trigger in the code for the black screen problems. This is a bug and not a problem of the cat driver!What you are talking about is issue 3 in my quote, i cannot find the post you are referring to, but i understand you are saying that for some people the problem occurs even with 10.12. It also did not work with other renderer settings enabled. He tried cat 10.12a (not even "official") and that did not work with DXVA enabled.
Potplayer download 4gb patch upgrade#
A revert or bugfix is needed - also i know of no case where the upgrade to cat 10.12 fixed this. It affects both normal modes and D3D Fullscreen mode of MPC HCs custom presenter. The black screen issue has nothing to do with D3D Fullscreen mode. We would not release a stable build in this state. We need to add code to refresh the display on exit to D3D fullscreen mode.īased on the above its easy to see that we are again running into driver bugs with ATI, and a revert is not required.įinally, nightly/unstable builds are exactly that, not meant for daily use. Ati has to fix its drivers, users need to have at least 10.12(which fixes many other bugs as well like SD dxva) (intel and nvidia seem completely unaffected). Issue three: Black screen during playback with D3D and 10bit modes disabled, as far as i can see this is another driver bug, fixed in cat 10.12. Issue two: Crushed image (like the screenshot shown above), this has to do with the fact that some driver and codec combinations do not like "forced 10bit", again this is not a regression and will probably have to be fixed in the driver. Issue one: Black screen on Exit when D3D fullscreen is used: This is not a regression, the renderer does not refresh the display on exit, it never has. This is a bug and not a problem of the cat driver!