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. |
4th March 2016, 08:43 | #36641 | Link |
Registered User
Join Date: Dec 2014
Posts: 1,127
|
Really, at 58 Hz? I would have thought that would make it worse.
__________________
HOW TO - Set up madVR for Kodi DSPlayer & External Media Players |
4th March 2016, 09:18 | #36642 | Link |
Registered User
Join Date: Dec 2007
Posts: 18
|
Me too Warner, but no, everything is perfect now, maybe it compensate with the clock deviation or something like that, because right now the clock deviation is like 0.000x% and before was much higher. Im really happy now, Ive been testing for like two hours with movies with a lot of panning (like the martian) and every was really smooth, with no visible dropped frames or choppy movement, and the best, no flicker!! (I hate flicker). Ive been testing on three different setups (a tv, a projector and a pc screen) and Ive got the same result on all of them.
Thank you so much! Last edited by kabal223; 4th March 2016 at 09:25. |
4th March 2016, 11:08 | #36643 | Link |
Registered User
Join Date: Sep 2014
Posts: 280
|
I've had some problems starting movies the last two days. When I first start a file the screen gets black and my tv shows no connection. When I press ctrl +alt + del desktop comes back and mpc-hc and madvr is closed. When I try to start the file again, it works flawless.
Someone had same problems? Don't know if it is madvr90.13 which I installed these days or the windows 10 Update which was installed 3 days ago... I'll test with older madvr today. Next thing I've seen these days with madvr 90.13 and the new glitch handling method activated was that during playback my screen gets dark and back again, showing "exclusive mode failed" message and then movie goes on playing fine. Don't know if its the new madvr option, but after disabling this option everything worked fine except for the other problem above.
__________________
Intel i5 6600, 16 GB DDR4, AMD Vega RX56 8 GB, Windows 10 x64, Kodi DS Player 17.6, MadVR (x64), LAV Filters (x64), XySubfilter .746 (x64) LG 4K OLED (65C8D), Denon X-4200 AVR, Dali Zensor 5.1 Set |
4th March 2016, 11:46 | #36645 | Link | |
Registered User
Join Date: May 2011
Posts: 164
|
Quote:
Took me a while to notice but sigmoidal looks a bit "cleaner" to me now. Very interesting as 1080p>1440p with Jinc AR is 99% of the upscaling I do so this sounds like something worth checking out when I get back home. Need to test this with other samples. |
|
4th March 2016, 12:00 | #36646 | Link | |
Registered User
Join Date: Sep 2014
Posts: 280
|
Quote:
__________________
Intel i5 6600, 16 GB DDR4, AMD Vega RX56 8 GB, Windows 10 x64, Kodi DS Player 17.6, MadVR (x64), LAV Filters (x64), XySubfilter .746 (x64) LG 4K OLED (65C8D), Denon X-4200 AVR, Dali Zensor 5.1 Set |
|
4th March 2016, 12:09 | #36647 | Link | ||||||||||||||||||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Do you have the "render frames in advance" (or however it was named) NVidia GPU control panel option set to "application controlled"? Quote:
Quote:
Quote:
The only spec difference Dolby Vision brings is 12bit instead of 10bit. Dolby Vision doesn't have different gamut or peak luminance values. Quote:
Quote:
Quote:
Quote:
madVR's pulldown playback (23fps at 60Hz) isn't really very optimized atm, it's not as smooth as it could be. 23fps at 60Hz is really what smooth motion FRC was mode for. If you hate the smooth motion FRC look, then your best bet is to try to set your TV to a simple multiply of the video framerate, which would be 47.952Hz or 71.928Hz. Quote:
In some scenes it does. But if there's a lot of visible ringing artifacts, it sometimes makes things worse. Which is why I'm not sure I should recommend it. Quote:
Quote:
|
||||||||||||||||||
4th March 2016, 15:27 | #36648 | Link | |
Registered User
Join Date: Dec 2007
Posts: 18
|
Quote:
No, sorry, its a projector and the top is 60hz. For now it seems that 58hz is doing the trick for me, everything is working fine with that refresh rate, I dont know how, but it works. Thank you so much Madshi. |
|
4th March 2016, 17:49 | #36650 | Link | |
Registered User
Join Date: Feb 2014
Posts: 139
|
Quote:
I'm on ATI. The Crimson driver control panel doesn't allow manual tweaking of flip queue size. I have no idea what it is at default. My MPC-HC is renamed, so it shouldn't be triggering any per-app settings in the driver. When I have a moment I'll troubleshoot this a bit more and let you know what happens. I've been perfectly happy with 2-3 frames for the present queue with "present a new frame per vsync" unchecked (and 24 GPU 128 cpu) for quite some time now. FRC seems to work just fine even with a small present queue. The stats show it's constantly between 1-3 and I never get presentation glitches or dropped frames (though this could be misreporting). I've kept it this low because the GPU queue drops to a max of 2/24 when I increase present queue to 4 or above, and the present queue fails to fill higher than 4 regardless of how high I set it. |
|
4th March 2016, 18:05 | #36651 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
|
|
4th March 2016, 20:52 | #36652 | Link |
Registered User
Join Date: Feb 2014
Posts: 139
|
I've gone ahead and done that. I tested:
D3D11 old, 3 present queue: Everything's fine. D3D9, 3 present queue: Everything's fine. D3D 11 new, 3 present queue: Everything's fine. Here's where it's interesting: D3D9, 16 present queue: a/v desync. Video is noticeably earlier than audio, but you'd have to be looking for it to see it. Didn't bother checking if it gets better/worse over time. I feel like it's a constant displacement. D3D11 New, 15 present queue (setting it to 16 makes it 15): a/v desync. Exact same amount of perceived desync as D3D9, with video noticeably earlier than audio. D3D11 Old, 15 present queue: Never fills the present queue above 4-5/15, never fills GPU queue above 3-4/24. Oddly enough, starts with mad stuttering and tons of dropped frames, but after queues stabilize, it settles down and stops dropping frames, with no A/V desync. All of these above tests are using FSE mode, and I quit the program and reload after each setting just to be sure they're getting applied properly. The OSD reports that the present queues and D3D mode are set as I wanted. Oh yeah, D3D9 isn't throwing tons of glitches anymore. Everything is 0 glitches, 0 dropped frames after queues fill. Now, in windowed, playing with backbuffer sizes: D3D9: backbuffer 16, present queue 16: A/V desync in FSE, back out into windowed mode, desync is gone. D3D11 new: present queue (windowed) 15, present queue FSE 15: A/V desync in FSE, gone in windowed. It's definitely a problem with the present queues in FSE, and isn't a result of whether I use D3D11 or D3D9, since it affects both. The problem exists in FSE, but disappears in windowed mode with the same number of backbuffer/present frames. I suspect there's desync as well with smaller present queues, but it's been unnoticeable since I set it to max of 3. Last edited by har3inger; 4th March 2016 at 21:01. |
4th March 2016, 21:28 | #36653 | Link |
Registered User
Join Date: Feb 2013
Posts: 137
|
Here is a screenshot that shows clearly the difference between Linear Light on and off for Crispen Edges.
http://screenshotcomparison.com/comparison/164352 The value I used was 1.0 in upscaling refinement but the issue is also present in image enhancements. I guess it's ringing after all but it's pretty bad...
__________________
Windows 8.1 and 10 x64 - Intel Core i5-4670K (4.2 GHz) - 8 GB DDR3 - MSI Geforce GTX 1080 8 GB - Sony KD-55A1 - Denon AVR-X3600H |
4th March 2016, 22:33 | #36656 | Link | ||
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Can you roughly quantify the desync amount? In any case, it kinda looks like a driver issue. My impression is that for some reason your driver doesn't allow a higher than 4 frame queue. The "old" D3D11 mode just had different problems with that than the "new" mode. I assume you have tried different drivers already, and also a "clean" driver install with default settings etc? Found this: http://forums.guru3d.com/showthread.php?t=403389 So it seems there is a registry setting for the flip queue size for AMD drivers. Maybe it's set to a non-standard value for your GPU for some reason? Try setting it to 16 as a test. Quote:
Can you please make the original unsharpened frame available (PNG should suffice), so that I can test with that? |
||
4th March 2016, 22:37 | #36657 | Link |
Registered User
Join Date: Dec 2010
Posts: 255
|
If your queue isn't filling up, you're probably overtaxing the GPU. Test and see what happens when you set all the scaling to bilinear for example and don't use doubling. Does it still not fill up? Then...as madshi said, it's a driver issue.
|
4th March 2016, 23:08 | #36658 | Link | |
Registered User
Join Date: May 2015
Posts: 7
|
Quote:
Sorry though. Greetz, Unr3aL |
|
4th March 2016, 23:13 | #36659 | Link | |
Registered User
Join Date: Feb 2013
Posts: 137
|
Quote:
Original
__________________
Windows 8.1 and 10 x64 - Intel Core i5-4670K (4.2 GHz) - 8 GB DDR3 - MSI Geforce GTX 1080 8 GB - Sony KD-55A1 - Denon AVR-X3600H |
|
4th March 2016, 23:18 | #36660 | Link | |
Registered User
Join Date: Feb 2014
Posts: 139
|
Quote:
The A/V delay is probably on the order of 25-75 ms. It's slight, but it's there. Has anyone else noticed this problem? Only exists when you use very high present queues in FSE. I've tried only 16.2 crimson for testing the A/V delay. The driver is kinda cruddy and has lots of broken UI/settings functions on laptop, but otherwise runs applications well. Things are all set at default. I don't really want to revert to 15.12 crimson because the new driver is needed for a couple games I have. Radeonpro doesn't actually work on my computer. It can't find the ATI card. Regedit search shows that the reg key doesn't exist by default. I'll go add it in manually at some point later once I find where my GPU reg settings are. For now, I might just go back to using a 3 frame queue for present queue. Honestly, I don't really see any difference between 3 and something huge like 12, and FRC behavior doesn't seem to change based on the queue size. I've read before that you need more frames in present queue for FRC, but haven't actually found this to be the case. What would I be looking for, if it's not working properly at low queue sizes? Last edited by har3inger; 4th March 2016 at 23:22. |
|
Tags |
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling |
|
|