[CraftyClown]

Add "ActivateWindow(123)" to your keymap and you can adjust many settings with your remote. These settings are saved in the madVR control panel.

And select "Load from madVR active profile" for the least hassle with madVR settings.

 Cheers Warner,

I am a little confused about what you meant by "Add "ActivateWindow(123)" to your keymap and you can adjust many settings with your remote"

I am almost ready to give up on the whole FSE issue, however if I'm not mistaken I currently need it to get the best out of my HDR material. Is that correct?

As I mentioned before, the curious thing about this issue is that FSE works everytime with MPC and maybe 1 in 10 times with DSPlayer, so I don't think there is any issue at the MadVR end, otherwise it would never work. I do feel like there must be a conflict going on here somewhere and I'm inclined to think it's at the Kodi/DSPlayer end.

If I'm loading from the MadVR active profile, do I need FSE selected in both MadVR and DSPlayer settings, or does one make the other redundant?

On a slightly different note, do you have your Kodi open at all times or do you open and force close it from your remote? I've struggled with reliable ways to close Kodi from the remote recently    

 You can change madVR processing settings from the video settings menu, which is accessible during playback. A shortcut to this menu is ActivateWindow(123).

So, you could add it to a keyboard.xml like this:

<keymap>
<FullScreenVideo>
<keyboard>
<home>ActivateWindow(123)</home>
</keyboard>
</FullScreenVideo>
</keymap>

The key "home" could be anything you want.

The only need for fullscreen exclusive mode is that it's the only way to currently get 12-bit output with HDR content with Nvidia graphics cards. This is simply due to a driver bug. So you might have to set your output to 8-bits in the GPU control panel, or allow the GPU to dither to 8-bits until this is fixed. Or launch these files with MPC. But I would just stick with 8-bits for the time being because no one's eyes are good enough to tell the difference between 8-bits with dithering and 10-bits, even with their face up to the screen. Many new UHD displays are still 8-bit, as well. This is really annoying, but it is a Nvidia driver bug, so you will have to work around it until it is fixed.

You do need to select fullscreen exclusive mode in DSPlayer. It wouldn't hurt to also select it in madVR. If you aren't doing this, it could be your problem.

I close Kodi by having my Harmony remote close Kodi with a key command when I push power. You would have to set this up in the Harmony remote software. The command is "ShutDown()" You assign this to a key command first in a keyboard.xml and then call that key command from the Harmony software. Of course, this assumes you have a Harmony remote. Occasionally, Kodi crashes. If it happens more than occasionally, you probably have a bad add-on that is not allowing Kodi to close properly.

If you put your PC to sleep, an easier way is to use Laucher4Kodi, which will close Kodi automatically on power off/sleep. It will also auto-open Kodi on resume. This is more reliable than sending a key command from a Harmony remote. 

 So I got FSE working again. I used CRU to reset all refresh rates and resolutions back to default and DDU to reinstall my drivers. I'm not exactly sure where the root of the issue was but it was clearly driver related and this immediately fixed things. I'm generally not that fussed about using FSE but it was more the annoyance of knowing there was something that was broken that I couldn't fix.

My issue with opening and closing Kodi is that I don't just use the PC as a HTPC. It's also my media server that I log into remotely to manage and I also very occasionally game as well, therefore I only want the Kodi interface available when I want to watch a movie or TV show, any other time it will get in the way. It wouldn't be an issue with a keyboard or mouse, but I want everything remote controlled and seamless, I'm annoying like that

So my method if anyone is remotely interested is to apply a keyboard short cut to the Kodi.exe which I map to a button on my remote allowing me to start it and then the slightly more complicated process of closing Kodi. To do this I use Launcher4Kodi with all the settings switched off, no focusing or anything. I take the force close kodi shortcut it provides of Ctrl + F4 and add it to a .vbs script as follows:

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.SendKeys "^{F4}"

I then make a shortcut to that script and pin it to my taskbar as the first three taskbar items can be mapped to my harmony which gives me a working shutdown Kodi button. I then automate all of this by creating grouped activities in Harmony like start Kodi which turns on my TV and AV amp and launches Kodi and then the same for turning everything off using the new close Kodi shortcut.

The icing on the cake was bringing Alexa into the mix, so now all I have to do is shout "Alexa turn on Kodi" and everything turns on and the lights dim