View Full Version : madVR - high quality video renderer (GPU assisted)
oldpainlesskodi
16th November 2017, 22:29
what exact version of the 385 drivers are you guys using ?
I am tired of manualy switching back HDR off in windows everytime I watch a movie.
I was about to re-install 378.46 as I know for a fact that these work quite well. But since I plan to play a recent game(ELEX) I will prefer to have more recent drivers.
385.28 is a good choice, failing that 385.41
K (win10 fall update)
mclingo
17th November 2017, 01:13
hi, i've had to sack off my ATI RX 550 card as I just cant get it stable with anything these days, KODI DS crashing randomly caused by graphic driver crashes, tried all version of drivers MADVR and LAV no joy. I've switch to an NVIDIA 1050, no crashes but I cant get rid of frame drops every 3-4 mins whatever I do. I tried creating custom resolution for 23,976 @1080p but makes no difference. I've also tried reclock, nothing changes it at all. At my whits end here guys, hoping someone can help.
el Filou
17th November 2017, 01:16
Can anyone point me in the direction of a guide/some settings for madVR/LAV for passing through 2160p/HDR content with as little GPU-taxing enhanchments and features as possible? The GT 1030 is *barely* able to play the content without dropping frames, but is VERY sensitive to any background activity on the PC. 60fps content especially will drop frames now and then.If you pass HDR through to the display, when playing 2160p on 2160 screen the GPU just needs to do chroma upscaling which should be fine.
I bet it's the 2 GB of VRAM causing issues. MediaPortal already uses a few 100s MB for its GUI, so when playing 2160p the VRAM usage should be pretty high.
Try lowering the queue sizes (start with the decode one).
RenderGuy2
17th November 2017, 02:21
Regarding Dolby Vision, I'm certainly not an expert on these things, but it seems like the enhancement layer might be a form of ratio image. Basically the 12 bit Dolby Vision source divided by the HDR10 version equals the ratio image which has been down scaled to 1920x1080 (probably among other things). It's sort of a clever way of storing higher bit depth information in two lower bit depth images. In order for MadVR to access the 12 bit Dolbly Vision version, the decoder would need to simultaneously decode both layers (HDR10+enhancement) making both available to MadVR, which would need to scale the enhancement later back up to 3840x2160 and multiply it with the HDR10 pixels. Probably other operations would need to be performed on the enhancement layer, bit shifting or something as in float it would have values greater than one which would need to preserved/recovered. Or all this could be completely wrong :o
jmonier
17th November 2017, 02:21
Even if you reduce the CPU/GPU queue sizes ? It always a little more than 3gb or just in cases ? And with a 1060 3gb, does it hurt the performance (dropped frames) heavily or force you on setting compromises ?
I'm using default queue sizes and I haven't done any testing of the sort you're asking about. In my limited testing, it always seems to use 3-3.5 gb. My feeling is that it would be silly to try to use the 3gb version for 4k and be always worrying whether it works for any given situation.
nsnhd
17th November 2017, 04:32
I'm using default queue sizes and I haven't done any testing of the sort you're asking about. In my limited testing, it always seems to use 3-3.5 gb. My feeling is that it would be silly to try to use the 3gb version for 4k and be always worrying whether it works for any given situation.
I'd appreciate if you could do the testing with reduced queue sizes. You're right that the 3gb is a silly version but the cost of the 6gb version is too much and not justifiable for non-gamer like me.
Thanks.
huhn
17th November 2017, 04:38
then 1050 will not assoluamente good, for my future 4k, but only for the fullhd?
a 1050 ti is absolutely fine.
it can easily do 1080p23 -> with NGU high.
a 960 can do this easily so a 1050 ti can do this too. the 4 GB make it absolutely save.
obviously you can't use every feature with a 1050 ti but that counts for a 1080 ti too.
a 1060 is about 60 % faster and gives you more options but that's it.
RCA is just so slow that NGU high is kind of free in comparison.
so yeah that's not going to work with a 1080p source or high FPS source need some tweaking like NGU mid.
but it's the new feature on the block so every one things you have to use it or something i don't know...
Note that for 4k a 1060 6gb is needed. Memory usage on 4k seems to be just a little more than 3gb.
well it is even possible with 2Gb but just get 4 GB a lot of features will not work with a 2 GB card and the only limiting factor is the 2 GB nothing else.
a 1060 3Gb may work totally fine but just get the 6 GB is generally faster and the 6 GB will be enough for sure well at least for now.
nsnhd
17th November 2017, 05:06
If there were a 1060 4gb version then no one would buy a 6gb version unless gamers, I guess.
huhn
17th November 2017, 05:43
we will never know until someone tries it out.
a program is usual using more memory than it actually needs.
so seeing 3.5 GB or more is not unusual.
but well i got this working with 2GB and 3Gb is quite a lot more way more than 1 GB for madVR because madVr doesn't get all of the 2Gb.
https://abload.de/img/2gbcanworkr5uxx.png
it's just i can easily say 4GB is save because i know it is save i was using a 4GB RX 480 for 3Gb well... i saw more than 3 Gb Vram usages but i can make it work with 2 gb too well kind of...
Razoola
17th November 2017, 10:01
I must say that I have really lost all faith with Nvidia in the last month. I have reported the HDR issue (not switching off) a month ago to their support and I have heard nothing since, even after three followups through their live support chat and being told I would be contacted within 24 hours. Looking at the driver threads in their forums it seems they currently have huge issues with their drivers, not just with HDR but also GSYNC and stuff in relation to the latest win10 updates. I am at a loss to understand why they have not simply scrapped the current 388.xx tree, gone back to 385.xx and started over.
Has anyone else contacted nvidia support directly over HDR issues or am I the only one? I'm just thinking the more people that complain the more chance they will do something to fix that mess.
d3rd3vil
17th November 2017, 12:04
Regarding Dolby Vision, I'm certainly not an expert on these things, but it seems like the enhancement layer might be a form of ratio image. Basically the 12 bit Dolby Vision source divided by the HDR10 version equals the ratio image which has been down scaled to 1920x1080 (probably among other things). It's sort of a clever way of storing higher bit depth information in two lower bit depth images. In order for MadVR to access the 12 bit Dolbly Vision version, the decoder would need to simultaneously decode both layers (HDR10+enhancement) making both available to MadVR, which would need to scale the enhancement later back up to 3840x2160 and multiply it with the HDR10 pixels. Probably other operations would need to be performed on the enhancement layer, bit shifting or something as in float it would have values greater than one which would need to preserved/recovered. Or all this could be completely wrong :o
Sounds good, lets do it
Razoola
17th November 2017, 13:32
I have just been reading this new info from nvidia in relation to HDR and netflix (http://nvidia.custhelp.com/app/answers/detail/a_id/4583/) and its got me beginning to think that HDR has been purposely crippled in newer drivers when third party players are used.
el Filou
17th November 2017, 13:37
That page you linked does not mention HDR.
Razoola
17th November 2017, 13:41
That page you linked does not mention HDR.
Yea sorry, I ment UHD for the first part.
el Filou
17th November 2017, 13:55
What do you mean by "purposely crippled" exactly ?
I think the issues are discrepancies in behaviour between Windows' internal configuration and NVIDIA's own APIs. That does not necessarily means they intentionally crippled functionality, Microsoft is just careless. Nobody wants to run Insider Preview releases on their production systems as they can break many things and Microsoft sometimes won't provide the fixes for months, so Win10 versions are always released in a beta state and then you have to wait for several weeks (if not months for the next feature update) for the things that broke to get fixed.
Razoola
17th November 2017, 14:19
What do you mean by "purposely crippled" exactly ?
I think the issues are discrepancies in behaviour between Windows' internal configuration and NVIDIA's own APIs. That does not necessarily means they intentionally crippled functionality, Microsoft is just careless. Nobody wants to run Insider Preview releases on their production systems as they can break many things and Microsoft sometimes won't provide the fixes for months, so Win10 versions are always released in a beta state and then you have to wait for several weeks (if not months for the next feature update) for the things that broke to get fixed.
I'm talking about nvidia here more than microsoft. HDR playback has many issues for many people since the 387.xx driver releases. By crippled I simply mean not workings correctly compared to earlier driver revisions intentionally.
jmonier
17th November 2017, 14:23
I'd appreciate if you could do the testing with reduced queue sizes. You're right that the 3gb is a silly version but the cost of the 6gb version is too much and not justifiable for non-gamer like me.
Thanks.
You're asking a lot! Why should I spend my time doing testing so you have the POSSIBILITY of saving $60? If you want to do 4k, you need the 6gb version, period! I'm done with this stupid discussion.
mclingo
17th November 2017, 14:32
hi, i've had to sack off my ATI RX 550 card as I just cant get it stable with anything these days, KODI DS crashing randomly caused by graphic driver crashes, tried all version of drivers MADVR and LAV no joy. I've switch to an NVIDIA 1050, no crashes but I cant get rid of frame drops every 3-4 mins whatever I do. I tried creating custom resolution for 23,976 @1080p but makes no difference. I've also tried reclock, nothing changes it at all. At my whits end here guys, hoping someone can help.
Hi, can anyone help with this, how do I get rid of the frame drops with NVIDA cards, getting them every 4 mins on the mark regardless of whatever I do.
Now cant seem to create a customer 1080p 23.976 resolution either, its imediately overwritten with 24p.
Razoola
17th November 2017, 14:40
Hi, can anyone help with this, how do I get rid of the frame drops with NVIDA cards, getting them every 4 mins on the mark regardless of whatever I do.
Now cant seem to create a customer 1080p 23.976 resolution either, its imediately overwritten with 24p.
Reclock is the answer if you cannot set a custom resolution. If that does not help (you mentioned you tried it before) then either you have not set reclock up correctly or there is some other task on your PC that is causing the stutter every few minutes.
nevcairiel
17th November 2017, 15:52
I'm talking about nvidia here more than microsoft. HDR playback has many issues for many people since the 387.xx driver releases. By crippled I simply mean not workings correctly compared to earlier driver revisions intentionally.
And you think thats unrelated to Microsoft? Those drivers that broke it are those that started to integrated with Windows 10 HDR functions, which are still a bit of a work in progress. Hence there is a direct correlation to Microsofts HDR efforts (or lack thereof).
If you were to use Windows 8.1, even the latest drivers would work absolutely perfectly fine, since there is no Windows HDR functions it has to co-exist with. Hence why madshi keeps recommending 8.1 for a media PC (among other reasons).
At this point its quite a bit unclear of Microsoft has to fix stuff, or NVIDIA. Likely both have some work to do. People that care about HDR today however need to realize that they are early adopters at best, so its somewhat expected for stuff to be a bit unstable.
Razoola
17th November 2017, 16:43
And you think thats unrelated to Microsoft?
In my case yes given I'm on win7 and not using nvidia win10 drivers. I also get to skip the microsoft win10 fall creators update mess. My problem btw is not HDR enabling or looking bad, but HDR not turning off once playback has ended.
dvd1
17th November 2017, 17:21
a 1050 ti is absolutely fine.
it can easily do 1080p23 -> with NGU high.
a 960 can do this easily so a 1050 ti can do this too. the 4 GB make it absolutely save.
obviously you can't use every feature with a 1050 ti but that counts for a 1080 ti too.
a 1060 is about 60 % faster and gives you more options but that's it.
RCA is just so slow that NGU high is kind of free in comparison.
so yeah that's not going to work with a 1080p source or high FPS source need some tweaking like NGU mid.
but it's the new feature on the block so every one things you have to use it or something i don't know...
to what extent the 150 TI can use DVD to 4K?
khanmein
17th November 2017, 17:52
Adjust the brightness of SDR content on your HDR display: Starting with Build 17040, Windows now lets you adjust how bright SDR content appears when running in HDR mode on the desktop. On an HDR capable system, you will see a slider in the “HDR and advanced color settings” page under Settings > System > Display. This is one of the improvements to HDR image quality that we have planned based on feedback from Insiders.
https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/
ashlar42
17th November 2017, 18:03
Thats mostly Windows fault, stick to 8.1 and everything works perfectly, even with brand new drivers. :)Note: I don't currently own an HDR TV.
But still, nevcariel, what you write can't be considered a good long term strategy. The free upgrade policy to Win 10 represented a potential money saver for lots of people. To stay with Win 8.1 (which I used and was satisfied with) meant being forced in the future to spend $199 in the future. That's the money you spend for a decent GPU. You can't be too hard with people that did not want to stick with 8.1, in my opinion. :)
I agree that HDR, on HTPC and not just on HTPC, is early adopters territory, though.
cork_OS
17th November 2017, 18:28
Quick test with my GTX 1060 3GB (2560x1440@60Hz 8-bit display, decoder is NVIDIA CUVID, chroma upscaler is sxbr125, ordered dithering, smooth motion on, FSE off):
NTSC DVD quadrupling with NGU High > Bicubic150 AR: 10-11ms
NTSC DVD quadrupling with NGU High > Bicubic150 AR + RCA: 12-12.5ms
720p24 doubling with NGU High: 8-9ms
720p24 doubling with NGU High + RCA: 12-12.5ms
1080p24 doubling with NGU Medium > Bicubic150 AR: 12-12.5ms
4k@24p HDR downscaling with SSIM2D100 AR: 35-37ms (maybe limited by VRAM amount)
Fabulist
17th November 2017, 18:30
Hello people. Is there a consensus regarding the anti-bloating filters on image enhancements/sharpeners - for example does 100% anti-bloating mean 100% elimination of any possible bloating, 150% means it could over anti-bloat, and 50% is half the anti-bloating required? Is there a safe value?
Is that how it works or what is the logic behind it? I am asking this because I am noticing an inconsistency between sharpeners, especially with Sharpen edges, it seems the filter does not bloat at all at even at 4.0 on HD and above sources, thus activating anti-bloating simply kills quality without any apparent bloating repair.
e-t172
17th November 2017, 19:29
But still, nevcariel, what you write can't be considered a good long term strategy. The free upgrade policy to Win 10 represented a potential money saver for lots of people. To stay with Win 8.1 (which I used and was satisfied with) meant being forced in the future to spend $199 in the future. That's the money you spend for a decent GPU. You can't be too hard with people that did not want to stick with 8.1, in my opinion. :)
Even though the free update offer "officially" ended, it is still technically possible to upgrade for free using the standard procedures. I would expect this state of affairs to go on pretty much forever - Microsoft cares more about people converging on the latest version than extracting scraps of money from late adopters. It is quite likely that they never intended for the free update to ever stop working and that the "deadline" was just a marketing trick to induce a sense of urgency in the userbase.
mark0077
17th November 2017, 20:54
Hi guys,
I just dug back up some old music DVDs I had and have been trying to play them but have been noticing menu navigation is causing mpc to crash, even just when doing previous / next chapter (currently testing with Queen Greatest Hits I DVD). When I switch to another video renderer like vmr9 its fine and I can't reproduce the crashes. I'm using mpc-hc BE, LAV Filters, ffdshow video + avisynth + svp. When I turn on madVR as the video renderer I'm getting the crashes where mpc will crash and windows will start reporting the issue to microsoft.
Just wondering is this something thats common / known about with madVR or is anyone still playing DVDS :)
In the filter chain, this is the DVD Renderer thats in action "Module : C:\Windows\SysWOW64\qdvd.dll"
Regards,
Mark
sat4all
17th November 2017, 21:23
Hi guys,
well i ditched my haswell i5 intel nuc in favor of a zotac en1060k, so this is my first nvidia card for years. i've been werstling with 2160p@23.976 using madvr's custom modes and after couple of optimization i was able to achieve no frame drops/repeats expected but ctrl+j display showing 23.97556.
the strange thing here is that the optimization before the last one showed me 23.97590 which is more close but still expecting 1 repeated frame every 1.xx hours.
should i just stick with 23.97556 afs it claims no drops or repeats? and ignore the claimed ctrl+j display value?
with my nuc it was dead 23.976 with no drops/repeats without engaging any kind of custom resolutions.
cheers
huhn
17th November 2017, 21:29
to what extent the 150 TI can use DVD to 4K?
i don't see a problem in that.
Hi guys,
well i ditched my haswell i5 intel nuc in favor of a zotac en1060k, so this is my first nvidia card for years. i've been werstling with 2160p@23.976 using madvr's custom modes and after couple of optimization i was able to achieve no frame drops/repeats expected but ctrl+j display showing 23.97556.
the strange thing here is that the optimization before the last one showed me 23.97590 which is more close but still expecting 1 repeated frame every 1.xx hours.
should i just stick with 23.97556 afs it claims no drops or repeats? and ignore the claimed ctrl+j display value?
with my nuc it was dead 23.976 with no drops/repeats without engaging any kind of custom resolutions.
cheers
the only number that matter is the dropped repeated frame number. it doesn't matter if the refreshrate is far or closer to 24000/1001 it's pointless.
Epedemic
17th November 2017, 21:32
If you pass HDR through to the display, when playing 2160p on 2160 screen the GPU just needs to do chroma upscaling which should be fine.
I bet it's the 2 GB of VRAM causing issues. MediaPortal already uses a few 100s MB for its GUI, so when playing 2160p the VRAM usage should be pretty high.
Try lowering the queue sizes (start with the decode one).
Thanks! Makes sense, as the new task manager in win10 FCU shows GPU ram usage in the roof... I already had the GPU queue sizes set to minimum, but i'll try to fiddle a bit with the CPU sizes as well, and try to find the lightest possible skin for MP (if it makes a difference). Regarding Chroma Upscaling, i left that at the default (Cubic), is that hte least taxing setting or does it make sense to switch to bilinear (or something 3rd)?
Epedemic
17th November 2017, 21:35
Adjust the brightness of SDR content on your HDR display: Starting with Build 17040, Windows now lets you adjust how bright SDR content appears when running in HDR mode on the desktop. On an HDR capable system, you will see a slider in the “HDR and advanced color settings” page under Settings > System > Display. This is one of the improvements to HDR image quality that we have planned based on feedback from Insiders.
https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/
Interesting. I'm running preview builds on my laptop, but it seems a bit risky to run them on my HTPC, which is supposed to "just work", as the preview builds (obviously) are a bit hit and miss... But great to know they are evolving the HDR capabilities :D
Manni
17th November 2017, 21:51
But still, nevcariel, what you write can't be considered a good long term strategy. The free upgrade policy to Win 10 represented a potential money saver for lots of people. To stay with Win 8.1 (which I used and was satisfied with) meant being forced in the future to spend $199 in the future. That's the money you spend for a decent GPU. You can't be too hard with people that did not want to stick with 8.1, in my opinion. :)
Once you have upgraded to Window 10 on a computer, the license will ALWAYS work on that machine, even if you do a clean reinstall. You simply have to install Windows 10 saying that you don't have a serial number, and once it's installed to activate it. Windows will recognize your PC and will fully activate it.
So once you've done the free upgrade, nothing prevents from your wiping out your Windows 10 install, install Windows 8.1 for now, and re-install Windows 10 at a later stage (for free) whenever HDR support is more stable.
I'm seriously considering doing this on my HTPC. I'm not installing to Fall Creators update, but if Windows forces it on me and HDR doesn't work even with older drivers, I'll definitely go back to win 8.1 (even if on a second SSD with a dual boot).
The main drawback of 8.1 in a mixed gaming/HTPC machine is the loss of DirectX 12, but the main advantage is to get native MCE back.
As video playback is a lot more important to me than gaming, I'll go back to 8.1 is MS forces me to. I've done the free upgrade to Windows 10 on all my PCs knowing that I could go back and forth if needed, provided the hardware doesn't change too significantly (for example a change of two of mainboard/GPU/system drive would probably require a manual activation that might be refused). That's why I upgraded my GPU before reverting to 8.1 if needed, makes it possible to change the hard drive without activation issues).
QBhd
18th November 2017, 00:20
https://image.prntscr.com/image/nksl03BTTvePsd8xtpdVow.png
Activation is also now tied to your MS account. If you sign in to your Windows 10 PC, your activation can be used even after a motherboard change. GPU's or system drives have never been tied to MS activation, just the motherboard.
QB
Manni
18th November 2017, 03:07
Activation is also now tied to your MS account. If you sign in to your Windows 10 PC, your activation can be used even after a motherboard change. GPU's or system drives have never been tied to MS activation, just the motherboard.
QB
GPUs and System drives (and even CPU) have ALWAYS been tied to activation, along with MB. You could change any of these (except MB), but if you change any two you have to reactivate (on the phone or automatically if you MS account is linked), and on OEM versions (tied to the MB) reactivation could be denied.
http://www.thewindowsclub.com/windows-10-license-hardware-configuration
So depends on whether you have an OEM (tied to one motherboard) or a full version of the OS (you can install it on any PC you want but it will only be activated on one at a time). For a full version, unless it has changed in Windows 10, the GPU and system drive are also taken into account.
You don't have to link an MS account by the way. It's only an option since the Anniversary update, but it's not necessary. I use a standard login and the activation still works.
I kept it simple because all this this is fairly off topic. The point is if you have upgraded to Windows 10 you can downgrade to Windows 8.1 and upgrade back to 10 later. That's the only on-topic part.
Razoola
18th November 2017, 10:57
The main drawback of 8.1 in a mixed gaming/HTPC machine is the loss of DirectX 12, but the main advantage is to get native MCE back.
From how I have been reading things in the last few weeks in relation to nvidia, even DX11 is playing games better than DX12 on win10 machines.
ryrynz
18th November 2017, 11:56
Regarding Chroma Upscaling, i left that at the default (Cubic), is that hte least taxing setting or does it make sense to switch to bilinear (or something 3rd)?
Not sure why you asked, when you can do it in less time than it took you to type that and find out yourself..
Make sure the trade quality for performance options are all ticked and then you can see if unticking any from the bottom is feasible.
ashlar42
18th November 2017, 12:11
Even though the free update offer "officially" ended, it is still technically possible to upgrade for free using the standard procedures. I would expect this state of affairs to go on pretty much forever - Microsoft cares more about people converging on the latest version than extracting scraps of money from late adopters. It is quite likely that they never intended for the free update to ever stop working and that the "deadline" was just a marketing trick to induce a sense of urgency in the userbase.I suppose you're referring to the assistive tech upgrade path. That's gonna close at the end of this year: https://www.cnet.com/how-to/microsoft-windows-10-free-upgrade-offer-assistive-features/
nevcairiel
18th November 2017, 12:37
From how I have been reading things in the last few weeks in relation to nvidia, even DX11 is playing games better than DX12 on win10 machines.
That mostly depends on the game, but its generally not wrong. NVIDIAs DX11 driver is quite optimized, so the benefit from DX12 is usually small - especially since DX12 optimizations in the games are often not the absolute best yet.
This may change over time however as the big rendering engines get better dealing with DX12.
aufkrawall
18th November 2017, 13:06
Yep, absolutely true. It depends a lot on the game.
I found a solution for myself how to stick to the Anniversary Update, this was/is really a stable version of Windows 10.
Funny that I'm having a much more hassle free experience on Arch Linux with all the latest stuff than with recent Windows 10 builds. Microsoft just have proven themselves incompetent for "Windows as a service". :rolleyes:
ashlar42
18th November 2017, 13:07
I'll post just this last time on the subject , because, yes, it's off-topic. Advocating for 8.1 usage after more than two years since Windows 10 release is, in my so very humble opinion, kind of backward looking. As time goes by, the stuff that won't work correctly on 8.1 will only grow but, more importantly, there's a clock ticking for when security updates won't be coming anymore.
As such, I feel that all efforts should be directed toward having stuff work correctly on 10. From a user's point of view this includes bugging companies in order for them to fix existing bugs, and so on and so forth.
Suggesting people keep using 8.1, instead, actually slows down the process.
It would be different if madVR was multiplatform. Windows 10 sucks? Go and install Linux (in whatever distro). That would be ok, because it won't be a suggestion with a date of expiration built in.
Cheers and, it goes without saying, only respect and thanks for madshi and nevcariel, who remain free to suggest whatever the hell they prefer, disregarding completely my personal opinion, which ain't worth nothing (and I'm not being ironic).
aufkrawall
18th November 2017, 13:09
Linux does not even support HDR at all. ;)
It will happen though.
Manni
18th November 2017, 13:16
From how I have been reading things in the last few weeks in relation to nvidia, even DX11 is playing games better than DX12 on win10 machines.
I have no interest re performance, but some games are DirectX 12 exclusive: https://en.wikipedia.org/wiki/List_of_games_with_DirectX_12_support. Not that I care that much personally.
I'll post just this last time on the subject , because, yes, it's off-topic. Advocating for 8.1 usage after more than two years since Windows 10 release is, in my so very humble opinion, kind of backward looking. As time goes by, the stuff that won't work correctly on 8.1 will only grow but, more importantly, there's a clock ticking for when security updates won't be coming anymore.
As such, I feel that all efforts should be directed toward having stuff work correctly on 10. From a user's point of view this includes bugging companies in order for them to fix existing bugs, and so on and so forth.
Suggesting people keep using 8.1, instead, actually slows down the process.
It would be different if madVR was multiplatform. Windows 10 sucks? Go and install Linux (in whatever distro). That would be ok, because it won't be a suggestion with a date of expiration built in.
Cheers and, it goes without saying, only respect and thanks for madshi and nevcariel, who remain free to suggest whatever the hell they prefer, disregarding completely my personal opinion, which ain't worth nothing (and I'm not being ironic).
You are barking at the wrong tree. Madshi and Nev do all they can to make it work as best as possible on all recent/supported OSes and drivers, within reason.
HDR still works fine with Windows 10 pre Fall Creators Update with nVidia 385.28. That's why I stayed with these personally.
The problem is that MS keeps changing things (because they keep getting their HDR support wrong), and just by the time nVidia catches up they break it again.
When MS and nVidia stop this dance, then we'll get stable support (hopefully). This is why, until they get their HDR support in order, it is an option to go back temporarily to 8.1 if your priority is HTPC use.
Otherwise, use older OS/drivers versions, or complain to MS/nVidia instead of complaining here and taking valuable time from the devs who already do all they can to deal with what MS and GPU manufacturers throw our way.
e-t172
18th November 2017, 13:45
I suppose you're referring to the assistive tech upgrade path. That's gonna close at the end of this year: https://www.cnet.com/how-to/microsoft-windows-10-free-upgrade-offer-assistive-features/
No, I'm not referring to that. Even if you don't use assistive tech, you can still install and activate Windows 10, today, with a Windows 7 or 8 key. Nothing changed. And I don't expect it will.
Patrik G
18th November 2017, 14:36
Does Madvr downconvert HDR to 8bit and also srgb colorspace when you select "Convert HDR content to SDR"?
when i compare the same hdr content with madvr to my K8500 UHD player i can see that colors are more saturated with madvr but i can also see that the content has the usual 8bit bandings in skies and such.
my tv has 89% of dci p3 colorspace
isnt it possible to set custom colorpoints X and Y for HDR that madvr can convert to instead of the lower srgb colorspace?
that way i can use the full color performance from the tv with HDR.
also leave the 10bit precision alone from the content would be a great idea :)
ipanema
18th November 2017, 18:06
This is probably a stupid question. I know that MadVR isn't so difficult to install, but is there a particular reason why it doesn't have a installer (such as NSIS) that might make it even easier for novices to install/uninstall ?
jkauff
18th November 2017, 18:38
This is probably a stupid question. I know that MadVR isn't so difficult to install, but is there a particular reason why it doesn't have a installer (such as NSIS) that might make it even easier for novices to install/uninstall ?
I expect version 1.0 will include standard Windows install/uninstall .exe files. I agree that many younger users don't even know what a .bat file does.
oldpainlesskodi
18th November 2017, 18:56
Installed the latest win 10 insider build (17040-171110) and the latest nvida driver 388.31,
My observations so far - yep, HDR borked, but, and this is a big but, the PQ has been given a big bump up (such an improved depth, clarity and colour reproduction - far more movie like). I can only assume the dev work that has gone into this build is to squeeze every ounce of PQ for the new Xbox (basically a Win10 box).
Sure, its a trade off for HDR (i've settled on letting MadVR convert, given the sheer volume of non-hdr movies in my collection vs hdr movies), but, from what I've seen, it's a price I'm personally willing to pay (until if and when they fix hdr).
Just my 2 cents.
K
el Filou
18th November 2017, 19:55
What do you mean by "depth, clarity and colour reproduction"? Please use more precise terms.
Do you mean MS have improved the HDR conversion to SDR? Or the SDR playback in HDR mode?
RenderGuy2
19th November 2017, 04:59
Regarding Dolby Vision, I'm certainly not an expert on these things, but it seems like the enhancement layer might be a form of ratio image. Basically the 12 bit Dolby Vision source divided by the HDR10 version equals the ratio image which has been down scaled to 1920x1080 (probably among other things). It's sort of a clever way of storing higher bit depth information in two lower bit depth images. In order for MadVR to access the 12 bit Dolbly Vision version, the decoder would need to simultaneously decode both layers (HDR10+enhancement) making both available to MadVR, which would need to scale the enhancement later back up to 3840x2160 and multiply it with the HDR10 pixels. Probably other operations would need to be performed on the enhancement layer, bit shifting or something as in float it would have values greater than one which would need to preserved/recovered. Or all this could be completely wrong :o
I did some research and it looks like I am wrong. It seems that the enhancement layer is not derived through division, but through subtraction. It contains the residuals from subtracting the HDR10 stream from the Dolby Vision signal. The tricky part is that the residuals are processed with a non-linear quantizer. The parameters of the non-linear quantizer are conveyed via metadata, so to reconstruct the Dolby Vision signal, first you need to read a bunch of metadata to derive the inverse quantizer so that you can access the residuals and add them to the HDR10 baselayer :scared:
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.