Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th July 2015, 16:40 | #32261 | Link | ||
Registered User
Join Date: Oct 2012
Posts: 7,923
|
Quote:
Quote:
and about DX11. a wise men once said: "..., but D3D11 decoding API is complicated and annoying." doesn't this count for rendering too? |
||
30th July 2015, 16:52 | #32263 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
It just doesn't make any sense to assume the worst intentions from everyone, what would they have to gain by removing this deliberately, and not for technical reasons?
It's far more likely that "not supported" means it just didn't work properly, and was therefore disabled. Which could simply mean it can get fixed later if they care enough. It's weird how on the internet everyone assumes a company is doing the worst they usually can and every statement is either a lie or legally binding, depending on what it says TL;DR: don't jump to conclusions without any facts. PS: updating a PC you rely on everydat to Win10 right away is kinda silly anyway. Everyone should expect hiccups in driver and software support for the first month or two.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 30th July 2015 at 16:54. |
30th July 2015, 16:53 | #32264 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
They make it sound as if Windows 10 by design cannot do D3D9 interop, which is AFAIK untrue. D3D9 interop still works with AMD and Intel, no? It seems that NVidia is not aware of that pretty much every HTPC playback software (except maybe PowerDVD, I don't know) out there is still using D3D9 DXVA. Nobody I know of uses D3D11 DXVA. Of course nobody besides madVR uses OpenCL for real time video playback (except MPDN), either, so NVidia removing D3D9 interop support basically means it's only madVR which is screwed.
I'm almost tempted to "stick it to them" and refuse to do anything about it. But then, that would probably hurt users much more than NVidia. Anyway, I will still not change my time schedule. So for now NNEDI3 won't work with NVidia, when using newer drivers. I guess that means I'll be recommending AMD GPUs from now on. I hope AMD releases next generation GPUs with HEVC DXVA, HDMI 2.0 and HDCP 2.2 soon. P.S: Of course nevcairiel is right and I might be jumping the gun here. But my experience with GPU companies is not exactly promising... |
30th July 2015, 17:04 | #32265 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
I don't think this would be a good idea, or has anyone proven that PCIe 3.0 is fast enough for 1080p60 NNEDI3 doubling?
This is not an uncommon task, since many YT videos now have 60fps and 4k displays are becoming popular. And with PCIe 2.0, OpenCL NNEDI3 is totally useless either on AMD. And there's probably a bug in the drivers regarding PowerPlay which makes the interop performance even randomly worse for some users. Bigger AMD GPUs (Hawaii, Fiji) are probably very fast with NNEDI3 SM5.0, I suppose Fiji might even could do already 1080p60 64 neurons. Sorry, but that OpenCL implementation has become very useless now that NV is going nuts. |
30th July 2015, 18:03 | #32269 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
Yes, it should work, since PCIe can transfer ~190fps 1080p.
But it's still vulnerable to driver quirks, here someone only has 115fps: http://www.forum-3dcenter.org/vbulle...8&postcount=62 And crazy AMD drivers can interfere even worse, only 36fps with PCIe 2.0: http://www.forum-3dcenter.org/vbulle...3&postcount=12 Some weird PowerPlay behavior: http://www.forum-3dcenter.org/vbulle...4&postcount=63 I don't think a copyback solution would ever be "clean" and thus stable for everybody. AMD still doesn't seem to have fully fixed flawed performance after 13.12 driver or it was never really stable. With SM5.0, results would be totally reliable. Either GPU ist fast enough or it's not and the driver hardly has any opportunity to interfere. Maybe peformance can be further improved for SM5.0? e.g. Prefer Vector is much faster on Maxwell than other options. |
30th July 2015, 18:19 | #32271 | Link | |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
I'm not sure I'm getting what you mean.
Copyback performance can even be worse with smaller Radeons? This would be bad. Then probably NNEDI3 could be used on more cards in general if done via SM5.0. Btw: 300 Radeon series refresh introduced much improved cooling systems like already known from Maxwell cards. Very good for "highend" HTPCs with enough compute power for NNEDI3. Quote:
You may already guessed it, but I'm extremely sad that I can't use NNEDI3 anymore, since I watch videos on my gaming system which profits by new drivers. I'm really missing madshi's deband filter in MPDN... |
|
30th July 2015, 18:40 | #32272 | Link | |
Registered User
Join Date: May 2008
Posts: 211
|
Quote:
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM |
|
30th July 2015, 19:11 | #32274 | Link |
Registered User
Join Date: May 2008
Posts: 211
|
No sir/mama. I either get a brownish image or no image at all. Also it takes about 2 to 5 seconds for the image to initialize in windowed mode, even without Nnedi3. I'm not using delay playback either.
Update: I used Nnedi3 32 neurons luma and chroma doubling and if I wait about 20 to 30 seconds I get a brownish tinted image. When I try to take a .jpg screenshot with MPC-HC's F5 the screenshot appears normal. I guess I wasn't waiting long enough. But 20 to 30 seconds seems like an inordinately long time, doesn't it? Further update: It seems the long wait time happens with super-xbr as well. The image is okay but its a long wait for the screen to show an image. I actually drop over 500 frames before I get an image on screen. Although the wait time for an image is almost instantaneous with EVR Custom. Edit: The excessive wait times were all in FS or FSE.
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM Last edited by XRyche; 30th July 2015 at 21:35. |
30th July 2015, 20:08 | #32277 | Link |
Registered User
Join Date: Jun 2005
Posts: 70
|
For me, madVR works just fine in MPC-BE on Windows 10, upgraded in-place from Windows 8.1 Pro 54. Well, partially. As soon as I switch to full screen, the player starts to react slowly. When I resize the window of the player, it is really really slow and stuttery. I updated madVR to the latest version 0.88.21 and still no luck, but the video is played back smooth now and there is no video stutter anymore, but the UI of the player is still acting very very slow... Also moving random windows of random applications around is stuttery and has micro glitches...
I may try the exclusive full screen mode instead and see if that makes any difference. Edit: Exclusive mode does not make ANY difference. Edit2: As long as I don't go into fullscreen mode, everything is like it was on Windows 8.1 Pro 64. After closing MPC-BE when I was in fullscreen mode, it goes back to normal. Edit3: The same phenomena CAN occur when opening another video while MPC-BE is still open. Edit4: It's ShadowPlay! When active, it screws up madVR! When I disable it, then it's not a problem anymore. Everything is then solved... But it would be nice if this problem would be investigated and fixed if possible and if it is a problem on madVR side. Edit5: Oddly enough: Problem is gone. When I activate ShadowPlay again, the problems does not occur anymore. Seems that there was something hanging from the upgrade procedure to Windows 10. Edit6: Sorry it came back. Disabling ShadowPlay solved the problem again. Machine: ASUS X99-E WS GeForce GTX Titan X 12 GByte with NEC MultiSync EA244WMi over DisplayPort 32 GByte Kingston ValueRAM reg ECC DDR-2133 (Micron Chips) Intel Xeon E5-2637v3 Intel 750 Series PCIe NVMe SSD 400 GByte Hitachi DeskStar 4TB 7200 RPM HDD Windows 10 Pro 64 Bit MPC-BE x64 1.4.5 beta (build 501) with madVR 0.88.21 x64 renderer. Last edited by BloodySword; 30th July 2015 at 22:03. |
30th July 2015, 21:33 | #32278 | Link |
Registered User
Join Date: May 2008
Posts: 211
|
No, a clean install using Display Driver Uninstaller (in Safe Mode) didn't change a thing.
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM Last edited by XRyche; 30th July 2015 at 21:37. |
30th July 2015, 22:06 | #32280 | Link | |
Registered User
Join Date: May 2008
Posts: 211
|
Quote:
__________________
Intel i5 3470, EVGA GTX 1050Ti SC ACX 2.0, Windows 10 Pro 64 bit, 16 GB 1600 mhz DDR3 RAM |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
Thread Tools | Search this Thread |
Display Modes | |
|
|