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.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 9th September 2018, 12:36   #52301  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
the display framerate stays?

if that's the case your issue is windows.
windows 10 composition rate is all over the place.
try newer driver and newer OS version. make sure you only have one screen active and hope Microsoft fixes it.
it breaks for some user with newer WDDM version it is a total mess.

you may have luck with disabling game DVR or what that name is or xbox app thingy. FSE is currently fake on windows 10 there shouldn't be a composition rate.

they fixed it in windows 8 completely but i guess that was good enough...
huhn is offline   Reply With Quote
Old 9th September 2018, 13:34   #52302  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 577
Quote:
Originally Posted by huhn View Post
the display framerate stays?
Yes it does.

Thanks.
mparade is offline   Reply With Quote
Old 9th September 2018, 15:59   #52303  |  Link
Klaus1189
Registered User
 
Join Date: Feb 2015
Location: Bavaria
Posts: 1,666
Quote:
Originally Posted by mparade View Post
In FSE mode I cannot make a Prt Scr.
todays phones can also take pictures
I am also interested in in that issue.

Now to my question:
Having an older Nvidia card here but newest driver version from 2018-08-27, custom resolution doesn't work anymore. Strange thing is, I have the list to optimize the refresh rate and I select it, then I already tried to restart the comuter as madVR suggests, but I still have the same minutes when a frame drop or repeat occurs. When I open the optimized list again, it states the selected mode is enabled.

I used it already in the past and it worked well. But it was 1709 then.
This computer only has a 1080p screen, so it only has to deal with 1080p resolutions.
Is that a driver issue, or a Windows 10 18.03 issue? Hope you can help me, to avoid spending too much time on it without success.
Klaus1189 is offline   Reply With Quote
Old 9th September 2018, 17:19   #52304  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 577
1803 & 399.07 here as well.
mparade is offline   Reply With Quote
Old 9th September 2018, 17:37   #52305  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 577
Quote:
Originally Posted by Klaus1189 View Post
todays phones can also take pictures
http://mammutmail.com/hu/download/82...a6852e22130ff8

With similar quality like the one above.
mparade is offline   Reply With Quote
Old 9th September 2018, 18:54   #52306  |  Link
Warner306
Registered User
 
Join Date: Dec 2014
Posts: 1,127
Quote:
Originally Posted by Klaus1189 View Post
todays phones can also take pictures
I am also interested in in that issue.

Now to my question:
Having an older Nvidia card here but newest driver version from 2018-08-27, custom resolution doesn't work anymore. Strange thing is, I have the list to optimize the refresh rate and I select it, then I already tried to restart the comuter as madVR suggests, but I still have the same minutes when a frame drop or repeat occurs. When I open the optimized list again, it states the selected mode is enabled.

I used it already in the past and it worked well. But it was 1709 then.
This computer only has a 1080p screen, so it only has to deal with 1080p resolutions.
Is that a driver issue, or a Windows 10 18.03 issue? Hope you can help me, to avoid spending too much time on it without success.
Driver upgrades and Windows updates sometimes break the custom resolution. Although you have applied it, it is not acknowledged by the driver.

Try rolling back to an older driver before running DDU and doing a clean driver install. You should be able to apply a previous optimized resolution and get it working again.
Warner306 is offline   Reply With Quote
Old 9th September 2018, 19:06   #52307  |  Link
Klaus1189
Registered User
 
Join Date: Feb 2015
Location: Bavaria
Posts: 1,666
I ckecked in Nvidia driver installer to install it fresh, so the previous version should have been deinstalled. Anybody else having trouble with latest Nvidia driver 399.07 on 18.03?
Klaus1189 is offline   Reply With Quote
Old 9th September 2018, 20:23   #52308  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
No, I just recreated my custom resolution yesterday. I had also used the clean install option when installing the newest driver (399.07). Also running win10 1803.

I did not need to restart or anything, it all worked in a nearly ideal fashion and I got down to ~1day between drops or repeats.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 9th September 2018, 20:27   #52309  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 896
Quote:
Originally Posted by mparade View Post
Does that also happen with SDR video? That may be a problem with the NVIDIA HDR API interacting with the display definition change or something.
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40
el Filou is offline   Reply With Quote
Old 9th September 2018, 20:42   #52310  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 577
The same is with 2160p SDR content.
mparade is offline   Reply With Quote
Old 9th September 2018, 22:33   #52311  |  Link
thighhighs
Registered User
 
Join Date: Sep 2016
Posts: 70
mparade
I think this is just OSD bug
thighhighs is offline   Reply With Quote
Old 9th September 2018, 23:00   #52312  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
this is not an osd bug.

the desktop still runs at 60 Hz while the GPU runs at 24 hz.
huhn is offline   Reply With Quote
Old 9th September 2018, 23:10   #52313  |  Link
Damien147
Registered User
 
Join Date: Mar 2011
Posts: 380
Do I need to do anything else beyond setting madvr for HDR?I get the AMD HDR in stats but picture seems a bit dull in comparison with windowed vs fullscreen.
My TV has pseudo HDR(no wide color gamut and 8 bit).Am I wasting my time and convert to sdr setting is better for me?
(Windows 10,samsung ku6000,amd rx 470)
Damien147 is offline   Reply With Quote
Old 9th September 2018, 23:27   #52314  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
AMD can't do HDR in windowed mode.

use whatever you like more.

AFAIK all entry level samsung HDR TV with 60 Hz panels are native 10 bit what ever that is worth.
huhn is offline   Reply With Quote
Old 9th September 2018, 23:37   #52315  |  Link
thighhighs
Registered User
 
Join Date: Sep 2016
Posts: 70
Quote:
Originally Posted by huhn View Post
this is not an osd bug.

the desktop still runs at 60 Hz while the GPU runs at 24 hz.
TV switched to 60 too?
Otherwise the composition rate line can be ignored here. This not makes extra dropped frames, glitches or something else: i have same "60Hz composition rate" in FSE
thighhighs is offline   Reply With Quote
Old 9th September 2018, 23:43   #52316  |  Link
Damien147
Registered User
 
Join Date: Mar 2011
Posts: 380
Quote:
Originally Posted by huhn View Post
AMD can't do HDR in windowed mode.

use whatever you like more.

AFAIK all entry level samsung HDR TV with 60 Hz panels are native 10 bit what ever that is worth.


I suppose that in windowed I get the convert hdr to sdr setting.I guess it's the pseudo hdr and lack of WCG that makes the picture more dull.
Thank you.
Damien147 is offline   Reply With Quote
Old 10th September 2018, 00:11   #52317  |  Link
Manni
Registered User
 
Join Date: Jul 2014
Posts: 942
[EDIT: unfortunately scratch that, after further tests the custom res doesn't stick, so I'm back to 385.28]

Good news for JVC owners with nVidia, I think I might finally be able to upgrade from 385.28 to a more recent driver, specifically 399.07 (with Win 10 build 1803). The last driver I tested before that was 398.36, so some version(s) in between might work as well [EDIT: with Win10 1803, all the recent versions of nVidia drivers break compatibility with Asio4All, including those that fixed it such as 398.11 and 398.36. I had to go back al;l the way to 385.28 to get Asio4all to work. FlexAsio works fine with all versions].

Most of the bugs seem to be fixed (especially the borked levels in 12bits). I was able to keep my usual RGB Full GPU, limited MadVR, Limited JVC configuration. All at 12bits 4:4:4 at 23p, 8bits 4:4:4 at 50/60p. Levels were correct both in HDR and SDR.
Main benefit (apart from obvious gaming benefits): 13mn between frame drop/repeat in 3D (1080p23FP), vs 3mn between a frame drop/repeat pre 39x.xx.
Main drawback: they have managed to break Asio4All support again (it had been broken in 390.xx, and fixed in 398.xx), but the improvement in 3D is well worth the compromise, and FlexAsio seems to be working fine, at least with REW. Not sure which exact version broke it again, but it's after 398.36.
Main warning: in order to apply the usual custom mode created by MadVR using the EDID/CTA settings, I had to enable it manually in the nVidia CP afterwards, otherwise it doesn't show up in the list of available modes. Once enabled, it seems to stick and gives me the usual 50mn to 3 hours between a frame drop/repeat in 2D at 4K23, which I can live with. I haven’t tested 1080p.
Main annoyance: you still have to set the bit depth to 12bits BEFORE selecting the custom res. Once the custom res is selected, bit depth is locked to 8bits and displays as such, but 12bits is still applied internally, at least at 30p and below. Above 30p, the drivers switches to 8bits automatically.

I'll report back after a longer test, but having tested 3D (in FSE mode), HDR (pixel shader) and SDR briefly (in 10bits full screen windowed), all seemed fine (although significantly improved in 3D).

There might still be some issues with JVC passthrough, but as I don't use it anymore I haven't tested that.

Hopefully they'll fix Asio4All again soon, without breaking anything else. It would be nice to be able to keep a current driver. 385.28 started to feel a bit long in the tooth, but was still working perfectly, including with HDR, the main drawback being the worse 3D performance.

Detailed rig and settings in sig below.
__________________
Win11 Pro x64 b23H2
Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33
madVR/LAV/jRiver/MyMovies/CMC
Denon X8500HA>HD Fury VRRoom>TCL 55C805K

Last edited by Manni; 10th September 2018 at 19:42.
Manni is offline   Reply With Quote
Old 10th September 2018, 02:02   #52318  |  Link
jmone
Registered User
 
Join Date: Dec 2007
Posts: 652
Thanks Manni - I'll test as well
jmone is offline   Reply With Quote
Old 10th September 2018, 07:46   #52319  |  Link
Sunset1982
Registered User
 
Join Date: Sep 2014
Posts: 280
Quote:
Originally Posted by LigH View Post
you are right, missed a word...
__________________
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
Sunset1982 is offline   Reply With Quote
Old 10th September 2018, 10:23   #52320  |  Link
Manni
Registered User
 
Join Date: Jul 2014
Posts: 942
Slight OT but re my post above about 399.07 and Asio4All, it looks like the compatibility with Asio4All is broken with all recent nVidia drivers, including 398.11 and 398.36 which did fix the issue when I tested them at the time with a former build of Windows.
So this compatibility issue with Asio4all might not only be due to the driver, but also to a combination with the O.S. build. If I go back to my trusted 385,28, Asio4all works again fine, including on the latest 1803 build. Flexasio works with all drivers, all OS versions, at least with REW, so is a good workaround if you want to use a more recent version than 385.28 with the latest OS build.
__________________
Win11 Pro x64 b23H2
Ryzen 5950X@4.5Ghz 32Gb@3600 Zotac 3090 24Gb 551.33
madVR/LAV/jRiver/MyMovies/CMC
Denon X8500HA>HD Fury VRRoom>TCL 55C805K
Manni is offline   Reply With Quote
Reply

Tags
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 21:49.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.