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 29th March 2019, 16:51   #55581  |  Link
onekmilesbehind
Registered User
 
Join Date: Mar 2019
Posts: 4
Quote:
Originally Posted by SirMaster View Post
I'm pretty sure there is no stuttering in any driver versions with vsync forced ON.
On the RTX line at least, Vsync "On" does not seem to have an effect in MadVR in the latest driver release.

I run a 2070 and, like others, found the cure to the stutter issue via forcing Vsync to "On"; when I updated to 419.67, the issue appeared again. Seeing Vsync was still on in the NCP, I assumed the issue lay elsewhere. After hours of troubleshooting, I went back down to 418.81 and that fixed it.

FWIW I do clean installs with every driver release and just flip the settings back the way they were. Vsync is always set back to "On".

I'm curious if it works in 419.17. If it does, then it appears the 419.67 release botched Vsync. If it doesn't, the fact that it goes from working-->broken-->working-->broken...doesn't indicate this is something NVIDIA cares too much about. Man I wish they had a dedicated testing group for HTPCs. Something like a Theater Ready Driver with a much larger release window (2-3 releases a year). They clearly don't hone the releases around the needs of the HTPC market. I'm sure it's a smaller segment of the userbase, but jeez, these releases are just sloppy and reflect poorly on them.
onekmilesbehind is offline   Reply With Quote
Old 29th March 2019, 17:02   #55582  |  Link
Nicog
Registered User
 
Join Date: Jan 2019
Posts: 17
Quote:
Originally Posted by onekmilesbehind View Post
On the RTX line at least, Vsync "On" does not seem to have an effect in MadVR in the latest driver release.

I run a 2070 and, like others, found the cure to the stutter issue via forcing Vsync to "On"; when I updated to 419.67, the issue appeared again. Seeing Vsync was still on in the NCP, I assumed the issue lay elsewhere. After hours of troubleshooting, I went back down to 418.81 and that fixed it.

FWIW I do clean installs with every driver release and just flip the settings back the way they were. Vsync is always set back to "On".

I'm curious if it works in 419.17. If it does, then it appears the 419.67 release botched Vsync. If it doesn't, the fact that it goes from working-->broken-->working-->broken...doesn't indicate this is something NVIDIA cares too much about. Man I wish they had a dedicated testing group for HTPCs. Something like a Theater Ready Driver with a much larger release window (2-3 releases a year). They clearly don't hone the releases around the needs of the HTPC market. I'm sure it's a smaller segment of the userbase, but jeez, these releases are just sloppy and reflect poorly on them.
For me :
419.17 NOK (neither FSE nor Windowed) with Vsync ON
418.81 is OK with Vsync ON
__________________
JRiver 25 in a Custom PC with i7 7700, Nvidia RTX 2070 (Zotac mini), Windows 10 1809, JVC X7900 in a dedicated black room :-)
Nicog is offline   Reply With Quote
Old 29th March 2019, 17:26   #55583  |  Link
onekmilesbehind
Registered User
 
Join Date: Mar 2019
Posts: 4
Quote:
Originally Posted by Nicog View Post
For me :
419.17 NOK (neither FSE nor Windowed) with Vsync ON
418.81 is OK with Vsync ON
Thanks and sorry if you had already posted the 419.17 status. So it appears NVIDIA is cycling between working-->broken then.

I'll jump on the next release when it's out to see if anything has changed. Hopefully this isn't another bug that's going to require a wait for the next major branch release (though I think that's due in April?). MadVR is absolutely amazing when the drivers don't muck things up.
onekmilesbehind is offline   Reply With Quote
Old 29th March 2019, 18:09   #55584  |  Link
Klaus1189
Registered User
 
Join Date: Feb 2015
Location: Bavaria
Posts: 671
Thank you for the info. These are 2019 drivers:
419.67 GRD 2019-03-25
419.67 CRD 2019-03-20
419.35 GRD 2019-03-05
419.17 GRD 2019-02-22
418.91 GRD 2019-02-14
418.81 GRD 2019-02-04
417.71 GRD 2019-01-15

Can you RTX users copy the version (one line) he/she used and know that there is an issue with stuttering or maybe not?
So I can be sure if there is stutter or not.
I copy then the info to the dedicated thread AMD, Intel and Nvidia driver issues and last recommended version
Klaus1189 is offline   Reply With Quote
Old 29th March 2019, 20:35   #55585  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,203
Nicog, you didn't need to quote the post directly above yours.
ryrynz is offline   Reply With Quote
Old 29th March 2019, 21:23   #55586  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 3,662
One day everyone will be trained.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 30th March 2019, 09:52   #55587  |  Link
jkauff
Registered User
 
Join Date: Oct 2012
Location: Akron, OH
Posts: 433
Quote:
Originally Posted by Asmodian View Post
One day everyone will be trained.
Except for the rebels, of course, who just enjoy annoying ryrynz.
jkauff is offline   Reply With Quote
Old 30th March 2019, 10:58   #55588  |  Link
Jinkai
Registered User
 
Join Date: Feb 2019
Posts: 2
Quote:
Originally Posted by huhn View Post
devices -> right click on "your device name" ->create profile group -> check color & gamma -> right click profile group -> add profile.

add a shortcut and gamma to the profiles done.
Thank you, sir!
Jinkai is offline   Reply With Quote
Old 30th March 2019, 17:59   #55589  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 527
Just noticed some new strange behaviour with NVIDIA driver 419.67 (Windows 1803).
When I start playback everything is normal but if I pause playback, after I un-pause the GPU clock goes down and render times shoot up until the average stats are consistently above the frame time but with madVR still not dropping frames. The downside is the render queue doesn't fill up anymore and I don't like this very much.
If I never pause playback, render times and GPU clocks stay the same as at playback start.
I never saw that behaviour before. Anyone else notice this on their NVIDIA?
See screenshot: https://drive.google.com/open?id=1_b...telXfj9JIHsGdj (normally when playing 50i my rendering time is max. 7-8 ms and DXVA is 4-5 ms)
Power management in NVIDIA control panel is on Adaptive.
__________________
HTPC: Windows 10 1809, MediaPortal 1, LAV Filters, ReClock, madVR. DVB-C TV, Panasonic GT60, 6.0 speakers Denon 2310, Core 2 Duo E7400, GeForce 1050 Ti
el Filou is offline   Reply With Quote
Old 30th March 2019, 20:34   #55590  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,203
Not seeing this on my 1060 with 419.67, any particular reason why you bumped your values up to 32 and 16? It's probably not required for smooth playback and you're just creating additional workload.
I changed my setting to match, recon soft 1080 playback -> 1080 screen D3D11 fullscreen windowed on Adaptive, I just am not playing back 25fps on 50hz.
Are you sure it's the latest driver is doing this? Revert and check?

Quote:
Originally Posted by jkauff View Post
Originally Posted by Asmodian One day everyone will be trained.
I see what you did there jkauff.

Last edited by ryrynz; 30th March 2019 at 20:39.
ryrynz is offline   Reply With Quote
Old 30th March 2019, 23:54   #55591  |  Link
el Filou
Registered User
 
el Filou's Avatar
 
Join Date: Oct 2016
Posts: 527
Thanks for the check.
Update: After more tests I noticed it was somehow only happening in MediaPortal and not in MPC-HC, which is weird because there isn't even an NVIDIA app profile for it
Rolled back to 419.35 and it went away.
(Edit: I suspect it had something to do with the way madVR calculates the rendering times, as there is no way I could have 0 frame drops with the render time being constantly above frame time. Maybe a way the GPU flushes are handled by the application? (MediaPortal's GUI runs in Direct3D). Anyway, it is strange)

I use 32/16 for various reasons:
- my HTPC is old and I find having a longer render queue is more drop-proof if Windows/another app decides to hog resources in the background
- I watch DVB TV and sometimes there are signal breaks, and I have less stutter when that happens if I use longer queues.
- I still watch (PAL) DVDs from time to time and there is a bug that 'halves' the decode queue: https://forum.doom9.org/showthread.p...13#post1832113
- I have the (V)RAM and I don't see how it would create an additional workload except when the queues are filling up obviously. More frames are just decoded/rendered ahead of time, but there isn't more total work?
__________________
HTPC: Windows 10 1809, MediaPortal 1, LAV Filters, ReClock, madVR. DVB-C TV, Panasonic GT60, 6.0 speakers Denon 2310, Core 2 Duo E7400, GeForce 1050 Ti

Last edited by el Filou; 31st March 2019 at 00:33.
el Filou is offline   Reply With Quote
Old 31st March 2019, 10:36   #55592  |  Link
whitestar999
Registered User
 
Join Date: Sep 2011
Posts: 36
Planning on installing a new os on ryzen 1200+1050Ti+1080p TV system.Should I go with win 8.1,ltsb 2016 or ltsc 2019? I will upgrade to 4k tv/better nvidia card in future & would like to keep the current os for as long as possible.
whitestar999 is offline   Reply With Quote
Old 31st March 2019, 11:19   #55593  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,203
I'll put my vote in for lTSC 2019.

Quote:
Originally Posted by el Filou View Post
I have the (V)RAM and I don't see how it would create an additional workload except when the queues are filling up obviously. More frames are just decoded/rendered ahead of time, but there isn't more total work?
Performance wise It doesn't appear to be quite as simple as only having higher usage when the queue needs to be fully sated and at all other times things being equal, test it for yourself.

If I lower queues to standard 16/8 my fan speed drops to nothing, my clocks lower, GPU usage is higher as a result and predicted wattage is around 10% with my setup as it is on Full HD content.
If I increase this to 32/16 my fan speed is now 20% my clocks are higher, GPU usage is lower but predicted watts are almost twice that of the standard queues.

Last edited by ryrynz; 31st March 2019 at 11:36.
ryrynz is offline   Reply With Quote
Old 31st March 2019, 12:33   #55594  |  Link
whitestar999
Registered User
 
Join Date: Sep 2011
Posts: 36
Quote:
Originally Posted by ryrynz View Post
I'll put my vote in for lTSC 2019.
Thanks! Any specific things I need to keep in mind like which driver version,any windows display settings & any win 10 specific madvr optimization. My tv is 1080p60Hz non-hdr & I currently use smooth motion option & most of my media is 720p/1080p SDR 23.76fps.
whitestar999 is offline   Reply With Quote
Old 31st March 2019, 12:45   #55595  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 1,460
Quote:
Originally Posted by whitestar999 View Post
Should I go with win 8.1,ltsb 2016 or ltsc 2019?
I vote for ltsb 2016, that's what I use and I don't upgrade it until LAV or madVR requires it.
The reason behind this is MS breaks stuff with every new version, so your older utils that you may use and haven't been updated for a while may break too. (E.g. Winaero Theme Switcher)

Quote:
Originally Posted by whitestar999 View Post
which driver version
Since you (will) have a Pascal card just use the old 385.28 driver.
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v385.28),Win10 LTSB 1607,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED65B8(2160p@23/24/25/29/30/50/59/60Hz)

Last edited by chros; 31st March 2019 at 18:36.
chros is offline   Reply With Quote
Old 31st March 2019, 12:55   #55596  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,203
Wait to see what others recommend, for drivers see if the latest works for you without issues, and stick with it until such time you feel it's worthwhile to upgrade and are prepared to take time to test it. The latest 419.67 apparently seems to be fine for the 10 series but 385.28 is the least problematic at time of writing.
Display settings, just what others have said.. Adaptive power mode and disable Focus Assist, pretty much everything else I can think of is fine with defaults. A 1050 is likely to have less issues with drivers (like the stuttering of recent drivers on some the newer cards)
If you can do 24Hz on your TV and create a display custom mode for it in madVR you may find that delivers the best experience, assess it vs your current setup with Smooth Motion enabled and decide for yourself.

Last edited by ryrynz; 31st March 2019 at 21:31.
ryrynz is offline   Reply With Quote
Old 31st March 2019, 13:57   #55597  |  Link
anta777
Rx470 50VT50
 
Join Date: Jun 2012
Location: Ukraine
Posts: 19
how can you compare speed
rx590 vs rtx2060 vs gtx1080ti
FullHD in 4K
anta777 is offline   Reply With Quote
Old 31st March 2019, 16:26   #55598  |  Link
Siso
Registered User
 
Siso's Avatar
 
Join Date: Sep 2013
Location: Bulgaria
Posts: 396
Quote:
Originally Posted by chros View Post
Since you (will) have a Pascal card just use the old 385.23 driver.
Is the driver 385.28 the same like 385.23?
Siso is offline   Reply With Quote
Old 31st March 2019, 18:37   #55599  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 1,460
Quote:
Originally Posted by Siso View Post
Is the driver 385.28 the same like 385.23?
385.28, I managed to screw it up, sorry.
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v385.28),Win10 LTSB 1607,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED65B8(2160p@23/24/25/29/30/50/59/60Hz)
chros is offline   Reply With Quote
Old 31st March 2019, 19:33   #55600  |  Link
katodevin
Registered User
 
Join Date: Sep 2007
Posts: 27
Quote:
Originally Posted by ryrynz View Post
The latest 419.67 apparently seems to be fine for the 10 series but 385.23 is the least problematic at time of writing.
That's what I'm seeing as well. My 1060 worked fine with new drivers, but my 1660 is stuttering like crazy unless I do fullscreen exclusive (even then I'm getting stutters every 45 seconds or so).

I tried downgrading drivers, but older drivers simply won't detect the 1660 as a compatible card. I'm totally pulling my hair out as my HTPC is pretty much garbage with UHD 4k content at this point.

Last edited by katodevin; 31st March 2019 at 20:42.
katodevin 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 11:18.


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