madVR - high quality video renderer (GPU assisted)

[el Filou]

If is has a good internal pathway that preserves madVR's dithering in 10 bit until the panel, and its FRC algorithm is good, it can be better to send it 10 bit.Wait, do you mean FRC can look better or even as good than madVR's dithering? I thought FRC always showed artifacts in some situations and it was best avoided if you could (of course in 6-bit TN panels you can't).

[Oguignant]

Wait, do you mean FRC can look better or even as good than madVR's dithering? I thought FRC always showed artifacts in some situations and it was best avoided if you could (of course in 6-bit TN panels you can't).

forgive my ignorance. what it mean FRC?

[MatLz]

http://bfy.tw/I09E

[Warner306]

http://bfy.tw/I09E

Love it.

You'd be be surprised how many questions I answer by Googling it myself. I sometimes have no idea what they are talking about, but in five minutes, I have an answer.

Will save that link...

[Warner306]

Yes, I'm applying customized 23hz refresh rate while in 60hz mode.

There is no secret for success with custom resolutions. You are at the mercy of the driver and the compatibility of your equipment. I was able to fix my issue by running DDU and reinstalling the drivers. But others haven't been so fortunate.

[Oguignant]

http://bfy.tw/I09E

hahahahahah i love it!

[Kamikaze Ice]

What about the LG OLED TV's ? B6 , C6

for HDR you need to choose Game Console/HDMI instead PC Input , And choose HDR Standard Picture mode

what is GL ?

I have an E6. With the latest firmware HDR with the PC Icon mode is restricted to a rec709 gamut (reports as bt.2020). I had to downgrade back to 04.30.95 to get back to full bt.2020 (or as full as this OLED can go).
Also in the latest firmware for PC Icon mode, the CMS controls were disabled, couldn't change color gamut between normal/extended/wide, and a few other things that I don't remember.
And I did want HLG and the new tone mapping (no clipping) for HDR game mode, but I'm not going to sacrifice PC input latency and calibration controls for them (and just thinking about having to change icon modes annoys me).


You can use HDR in PC mode but, on the C7 at least, the gamut coverage is much worse. Home theater or similar offers better HDR rendering but also uses 4:2:2 color subsampling. :(

Have you tried earlier firmware? I know this gamut restriction was added in one of the last firmware updates for the 2016 models, so you might have the option of downgrading to get the full gamut back with PC Icon mode in HDR.

[el Filou]

forgive my ignorance. what it mean FRC?Sorry, I now realise there are multiple things called FRC. In the context of LCD panels I meant this: https://en.wikipedia.org/wiki/Frame_rate_control

[wolfman2791]

It was the stupidest thing lol. I forgot that windows overlay does not work with AMD cards. That was causing the strange noises from my R9 390. Since i have a 10 bit display, i need to use windows exclusive instead.

[JarrettH]

Ever thought though that someone wants FRC explained - in your own words - and not from Google search? It's like selling out your own expertise.

[Chouonsoku]

I'm not sure when this issue was introduced or if it's just on my end (or if it was previously mentioned), but the film deinterlacing mode seems to not be accessible in the current build. Playing back 29.970 fps content that should be progressive is stuck in the video deinterlacing mode. I've tried setting "force film" in the settings and also cycling between deinterlacing modes with Ctrl+Alt+Shift+T and all the shows on the OSD is "auto detect: video" and "video". Can anyone confirm this is happening on their setup?

Edit: And of course as soon as I finally post here to ask, it's suddenly working as intended. No idea what the problem was. -_-

[FDisk80]

There is no secret for success with custom resolutions. You are at the mercy of the driver and the compatibility of your equipment. I was able to fix my issue by running DDU and reinstalling the drivers. But others haven't been so fortunate.

That's just it, I could apply the same timings I'm trying to apply with earlier nvidia drivers. But with all latest ones it is not possible anymore.

There is obviously some driver limitation. Even the error that pops out says exactly this.

https://i.imgur.com/SjACY99.png

The question is maybe it's possible to override those limitations with madVR or with some registry tweaks.

[Clammerz]

The question is maybe it's possible to override those limitations with madVR
If it were possible, madshi would have implemented those overrides already.

As for other workarounds and "tweaks", you are at the mercy of the drivers as Warner states.
People have had success using DDU and re-installing. Others have had to use other versions, and some simply cannot get it to work at all.
One thing that you have probably already done: make sure to switch to a mode that you are not trying to modify/add. Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

[FDisk80]

If it were possible, madshi would have implemented those overrides already.

As for other workarounds and "tweaks", you are at the mercy of the drivers as Warner states.
People have had success using DDU and re-installing. Others have had to use other versions, and some simply cannot get it to work at all.
One thing that you have probably already done: make sure to switch to a mode that you are not trying to modify/add. Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

Yes, tried DDU, clean installs... That didn't work.
Switch to a completely different resolution before applying the custom timings for 1080p. I did not try that. I only tried from a different refresh rate. That is a good idea. Will try that.

[ashlar42]

I think the suggestion was based on the fact that the 1050ti has an on-board hi-res decoder, while the 1060 does not.This is not true.
Harware video decoding is exactly the same in 1060 and 1050Ti (VP8 generation).

Thanks to everybody chiming in in the 3GB vs. 6GB matter.

[huhn]

they have a relative small difference.

the 1030, 1050, 1050 ti and 1080 ti have a "better" decoder that can decode VP9 profile 2.

[Ver Greeneyes]

I've worked around the Windows 10 April 2018 Update problem (with the queues not filling up) by making some dummy profiles that use the inexpensive default scaling algorithms, and activating them "if (1 == 1)" (which is obviously always true). Hopefully madshi will be able to work around Microsoft's latest buffoonery.

[mrmojo666]

I've worked around the Windows 10 April 2018 Update problem (with the queues not filling up) by making some dummy profiles that use the inexpensive default scaling algorithms, and activating them "if (1 == 1)" (which is obviously always true). Hopefully madshi will be able to work around Microsoft's latest buffoonery.

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

[Ver Greeneyes]

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

Interesting. Unfortunately I have an Nvidia card (GeForce GTX 1080) and I see the problems both with pre-update drivers (391.35) and post-update drivers (397.55).

[Betroz]

Interesting. Unfortunately I have an Nvidia card (GeForce GTX 1080) and I see the problems both with pre-update drivers (391.35) and post-update drivers (397.55).

My solution has been to use an older MadVr build and use NNEDI3 128 settings. I hope Madshi have the time to look into this when I comes back.

[mclingo]

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

Ive had issues with everything 18.3x onwards, 18.2.2 is my current stable.

I tried 18.4.1 thought, its shafted FSE for me, black screens and loss of HDMI all over the place.

With not being a gamer though its fine to just sit on an old driver and just enjoy my HTPC.

[mrmojo666]

Ive had issues with everything 18.3x onwards, 18.2.2 is my current stable.

I tried 18.4.1 thought, its shafted FSE for me, black screens and loss of HDMI all over the place.

With not being a gamer though its fine to just sit on an old driver and just enjoy my HTPC.

yes i remember our discussions.
the 18.4.x are not only for games , they should support 1803 win10 and should activate DRM for 4k netflix. But they mess all things with 1803 plus netflix still 1080 :) lol

[FDisk80]

Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

Tried it now, no go. Still same error. "Rejected by driver."
Oh well, it was a long shot.

[jkauff]

Tried it now, no go. Still same error. "Rejected by driver."
Oh well, it was a long shot.
I also have a GTX 1080. I get around this problem using the utility CRU (which stands for "Custom Resolution Utility"). I use it to create a 23.976 custom resolution (and others as well), which madVR can then use and optimize. It works at the OS level, not the GPU driver level, and so bypasses the Nvidia quirk.

[har3inger]

Guys, I found out the solution for the FSE flicker/freeze on 1803.

It's Focus Assist bugging out. Even if it's off, you need to make sure all the options underneath it are disabled. You can find the relevant page by typing focus assist into the start menu.

[FDisk80]

I also have a GTX 1080. I get around this problem using the utility CRU (which stands for "Custom Resolution Utility"). I use it to create a 23.976 custom resolution (and others as well), which madVR can then use and optimize. It works at the OS level, not the GPU driver level, and so bypasses the Nvidia quirk.

Hmm, I tried it before but I was getting the same error with madVR.
Can you share please what you did in CRU to override this issue?

Maybe I did something wrong in CRU. :confused:

[jkauff]

Hmm, I tried it before but I was getting the same error with madVR.
Can you share please what you did in CRU to override this issue?

Maybe I did something wrong in CRU. :confused:
I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

[FDisk80]

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

What do you mean by HDMI block?

[LigH]

Probably a display control data block...

[Siso]

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

In my case using displayport, I have to always add extension block, new CRU versions don't add it automaticly.

[Clown shoes]

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

Where does one check to see if the HDMI block is included?

[jkauff]

Where does one check to see if the HDMI block is included?
There's an Extension Block area below the list of standard resolutions. Click "Add" and then Add again in the lower box of the dialog. It'll pop up a list of extension blocks that includes HDMI and HDMI 2.0. Choose whichever version you're using.

That's if it's not already showing on the main screen, which it should be.

[Sunset1982]

I just build my new htpc with an amd rx480 on win10 (1709) with adrenalin 18.2.2 and latest madvr.

Works fine, except for the automatic hdr switching. it doesn't switch into hdr mode when a hdr file is played. Is there not automatic hdr mode on amd or ist something wrong with my setup?

[huhn]

the mad api needs 10 bit or it will not work.
but it is fine to send 8 bit over the cable. just take it as it is.

[sam0t]

I recently updated my HTPC (Win10) to the new April 1803 build and now when I put my videos in full screen exclusive mode, I get around 4 seconds of black screen, then when the video appears there are a few hundred dropped frames within a few seconds, and then the video finally plays smooth as normal. While this is all happening, the audio is still playing back at normal speed without interruption. So basically when I enter FSE, it takes like ~8 seconds to finally start playing back normal with zero dropped frames.
...
edit: Apparently it's Win10's new 'focus assist' feature which mutes notifications when doing select activities. When I enter FSE it thinks I'm playing a game and turns focus assist on. I turned focus assist off when playing games and it's fine now.

I'll leave this post up in case someone else has this issue.

Thx rahzel for sharing, I too was experiencing this very same issue with full screen exclusive (FSE) mode after W10 April 1803 update, and after I disabled the new Windows 10 focus assist feature, FSE mode works again normally without few seconds of black screen in the beginning of playback. :thanks:

[mclingo]

I just build my new htpc with an amd rx480 on win10 (1709) with adrenalin 18.2.2 and latest madvr.

Works fine, except for the automatic hdr switching. it doesn't switch into hdr mode when a hdr file is played. Is there not automatic hdr mode on amd or ist something wrong with my setup?

The only Prerequisites for HDR on and RX card I know are:

Set MADVR to 10 bit or higher
tick use DIRECT3D11 in general settings
set MADVR HDR to passthrough

[Clown shoes]

I also have a GTX 1080. I get around this problem using the utility CRU (which stands for "Custom Resolution Utility"). I use it to create a 23.976 custom resolution (and others as well), which madVR can then use and optimize. It works at the OS level, not the GPU driver level, and so bypasses the Nvidia quirk.

Dude, thank you so much for this. I set up my custom resolutions in CRU and was immediately able to optimise my 23.976 refresh, going straight from four and a half minutes to four and a half hours!

I've been trying to get custom resolutions working for ages and had all but given up :D

[FDisk80]

Dude, thank you so much for this. I set up my custom resolutions in CRU and was immediately able to optimise my 23.976 refresh, going straight from four and a half minutes to four and a half hours!

I've been trying to get custom resolutions working for ages and had all but given up :D

Sounds promising, will try playing around with it more today.

[Sunset1982]

the mad api needs 10 bit or it will not work.


ok, thx. That did the trick.


The only Prerequisites for HDR on and RX card I know are:

Set MADVR to 10 bit or higher
tick use DIRECT3D11 in general settings
set MADVR HDR to passthrough

Thank you!

[Dorohedoro]

Ok, I was able to find a custom resolution long time ago that is working flawlessly, but now I have a question because I'm doing playlists on potplayer (all of the files are exactly 23.976) and the stats for the frame repeats/drops are showing different values when the new video start, is that normal?

I'm going to explain myself a little better with an example:

With the first file (a trailer, 23.976) madvr shows that I'm going to get 1 frame repeat every 10 hours or so.. but when the playlist jumps to the actual movie (23.976 also) I get 1 frame repeat every 1.23 minutes, but it will improve slowly during the movie because at the end of the movie the stats show something like 1 frame repeat every two hours, and if the movie were longer the stats will also have better numbers, like 1 frame repeat every 3 hours or so...

So, my question is: this is just a stats "glitch" or I'm in danger to get repeated or dropped frames if I keep making playlists with potplayer? just for letting you guys know the display don't even blink when the playlist change files, so, I'm guessing that madvr is not changing the refresh rate (obviously, because every file is 23.976)... my wild assumption is that I'm still getting on the second file (the movie) the same frame repeat every 10 hours, but madvr for some reason is too slow calculating the number and is slowly improving during the movie.

Thanks!

[nevcairiel]

The drop stats are basically an average over time. You need to keep it running for a while to get accurate values. As long as you don't actually get a drop, its fine.

[Dorohedoro]

Yeah, that's my guess, because the stat will improve over the duration of the movie. If I play that movie alone (without a playlist) the stat will show "1 frame repeat every 10 hours" right from the first few seconds, so, that's why I think is just a stat issue.

Thank you so much!

[oldpainlesskodi]

windows 10 cumulative update windows-10-kb4103721 is out, and seems to have fixed some long standing issues of what the OS feeds the graphics driver (grey scale etc).

[FDisk80]

windows 10 cumulative update windows-10-kb4103721 is out, and seems to have fixed some long standing issues of what the OS feeds the graphics driver (grey scale etc).

Grey scale?

[mrmojo666]

windows 10 cumulative update windows-10-kb4103721 is out, and seems to have fixed some long standing issues of what the OS feeds the graphics driver (grey scale etc).

where is this statment ?

https://support.microsoft.com/it-it/help/4103721/windows-10-update-kb4103721

[oldpainlesskodi]

Grey scale?

Incorrect limited and full range.

As an example (using the same gfx driver), in the Nvidia control panel, if I choose "use default colour settings", it always changed to limited, regardless if I was using manual on full or limited. Now, after the cumulative update, it defaults to full.

Previously, using full, I had to set the brightness down so low, or I would have grayed cropped bars, as the full range was incorrect etc.

Of course, there is always a chance that the issue has only affected a small number of users.

[oldpainlesskodi]

where is this statment ?

https://support.microsoft.com/it-it/help/4103721/windows-10-update-kb4103721

I picked it up on one of the nvidia forums - all I can say, is give it a try.

[FDisk80]

Something new to try for nvidia users:
397.64

http://www.nvidia.fr/download/driverResults.aspx/134121/fr

http://us.download.nvidia.com/Windows/397.64/397.64-win10-win8-win7-desktop-release-notes.pdf

Found something interesting in the PDF though:
Issues Not Caused by NVIDIA Drivers

-When switching the refresh rate from 59 Hz to 60Hz, the refresh rate remains at 59 Hz.
See the Microsoft KB article KB2006076 at http://support.microsoft.com/kb/2006076.

- [Windows 10 Fall Creators Update][HDTV]: 12 bpc is automatically applied even on
HDTVs that support only 8 bpc, resulting in a scrambled display. [2007663]
To work around, open the NVIDIA Control Panel->Change Resolution page, select “Use
NVIDIA color settings”, then set the Output color depth to 8 bpc.

[Clown shoes]

Something new to try for nvidia users:
397.64

http://www.nvidia.fr/download/driverResults.aspx/134121/fr

http://us.download.nvidia.com/Windows/397.64/397.64-win10-win8-win7-desktop-release-notes.pdf

Found something interesting in the PDF though:

Ha ha, literally just read that in the PDF you posted and was about to comment on it.

[brazen1]

Could someone please confirm or deny an nVidia problem I've been having for months of updates?

385.28 remains the last working driver for me. Every driver release after this has some sort of problem including todays 397.64 upgrade I just installed.

With your AVR on, right click the volume icon in the notification area of the taskbar.
'Speaker Setup' should show what you setup in your audio properties and produce audio from your system. (7.1 or 5.1 for example will display)

Now turn your AVR off and it should show 'Stereo' because your display has two built in speakers and it is now producing audio.

The old driver correctly switches from 7.1 to stereo depending if the AVR is on or off. Anything newer fails. This matters because when it remains in stereo with the AVR on, you will not achieve proper surround sound until you manually switch it to multichannel. If it remains in 7.1 with the AVR off, you will not be able to play anything web based like youtube until you manually switch it back to stereo.

I can't believe this is only inherent to my system or a non-issue because no one else toggles their AVR on/off and I've brought this up a couple times starting last year but fell on deaf ears. Please will someone check?

Edit. Actually, I just checked an Atmos title and even though Windows reports it's outputting stereo, my AVR shows Atmos so maybe this a non-issue now? I'm going to use this driver for a bit and see if anything truly detrimental appears vs 385.28. Fingers crossed.