madVR - high quality video renderer (GPU assisted)

[Manni]

Originally Posted by Asmodian

Ah, OK, I probably mis-remembered. That seems really odd though. How does the driver know if madVR processed the HDR video first or not?

Because in one case MadvR uses the nVidia API to switch the display to HDR, and in the other it doesn’t, so the video path (and possibly the driver code used) isn’t the same, because in passthrough the driver outputs HDR (with associated metadata) and in pixel shader it outputs SDR, without any metadata. At least that’s my assumption, I’m sure Madshi will correct me if I’m wrong.

[stefanelli73]

However, going to 92.14 at 92.12 the "problem" of the 8bit is no longer in passthrough hdr comes out to 10bit again

[Manni]

Originally Posted by stefanelli73

However, going to 92.14 at 92.12 the "problem" of the 8bit is no longer in passthrough hdr comes out to 10bit again

Yes, Madshi has only started to force 8bits in passthrough (and in pixel shader possibly due to a bug) in the latest public release. You do get 10bits in previous versions in passthrough (up to and including test build 5), but there is minor banding in passthrough (not in pixel shader), which is why Madshi decided to force 8bits.

If you can use FSE in any version, there is no banding so 10bits should be enabled.

[x7007]

Originally Posted by Manni

Yes, Madshi has only started to force 8bits in passthrough (and in pixel shader possibly due to a bug) in the latest public release. You do get 10bits in previous versions in passthrough (up to and including test build 5), but there is minor banding in passthrough (not in pixel shader), which is why Madshi decided to force 8bits.

If you can use FSE in any version, there is no banding so 10bits should be enabled.

So is there a difference between FSE 10 bit and Full Windowed mode 10 bit ? or using Windowed mode and not Full Windowed is the issue ? Is it ok to use HDR ( OS MODE ) Full-Windowed mode 10 bit ?

[Manni]

Originally Posted by x7007

So is there a difference between FSE 10 bit and Full Windowed mode 10 bit ? or using Windowed mode and not Full Windowed is the issue ? Is it ok to use HDR ( OS MODE ) Full-Windowed mode 10 bit ?

Yes there is a difference.

FSE = no banding in 10bits.
Full windowed mode on win 10 with nVidia and passthrough = minor banding in 10bits until 94.12.

In 94.14, all modes are forced to 8bits, except if FSE is used,

Hopefully in the next build, only passthrough will be forced to 8bits, except if FSE is used.

Don’t know about OS HDR mode, I never use it as the nVidia API works great and is much preferable.

Just use whichever mode you normally use and live with 8bits dithering until a fix is available. This doesn’t make much difference visually, as MadVR’s dithering is excellent. This is a very small amout of noise, but hardly perceptible. Or revert to 94.12 if you really want 10bit dithering and can’t use FSE,

[Asmodian]

Originally Posted by Manni

Because in one case MadvR uses the nVidia API to switch the display to HDR, and in the other it doesn’t, so the video path (and possibly the driver code used) isn’t the same, because in passthrough the driver outputs HDR (with associated metadata) and in pixel shader it outputs SDR, without any metadata. At least that’s my assumption, I’m sure Madshi will correct me if I’m wrong.

You mean pixel shader to SDR? That puts madVR into an SDR mode, I was talking about modes that output HDR. There are more than just passthrough.

"passthrough HDR content to the display"
"process HDR content by using pixel shader math"
"process HDR content by using an external 3DLUT"

[Manni]

Originally Posted by Asmodian

You mean pixel shader to SDR? That puts madVR into an SDR mode, I was talking about modes that output HDR. There are more than just passthrough.

"passthrough HDR content to the display"
"process HDR content by using pixel shader math"
"process HDR content by using an external 3DLUT"

Process HDR doesn't work on any display I know. It creates metadata that no display can understand and process. Are you using any of these with success? I don't know of anyone who does.

As far as HDR is concerned in MadVR, there is passthrough and pixel shader. Process is a dead end, except maybe process with a 3D LUT.

Still, there is only one pass-through mode.

[nussman]

Come on ... this is way too much off topic here ...

[NoTechi]

Originally Posted by nussman

Come on ... this is way too much off topic here ...

Sorry. Could you point me to a better place where I should ask? I will delete my post then (if thats possible)

NoTechi

[nussman]

Maybe start your own thread here @doom9 (software players section should be fine).

[NoTechi]

Originally Posted by nussman

Maybe start your own thread here @doom9 (software players section should be fine).

Done and posted here as you sugested
https://forum.doom9.org/showthread.p...75#post1840475

Sorry again

NoTechi

[brazen1]

#1 Use KODI 17.6 because Alpha v.18 is not even close to usable yet.
#2 Windows HDR and color settings switch is NEVER enabled and will significantly hamper madVR if it is.
#5 Don't covert HDR to SDR unless your display is not HDR compatible. Use passthrough.
#6 Driver v.385.28 is the last driver that half way works. Anything newer presents even more problems.

The guide in my signature will offer more details for your general questions than this specific madVR forum.

[NoTechi]

Originally Posted by brazen1

#1 Use KODI 17.6 because Alpha v.18 is not even close to usable yet.
#2 Windows HDR and color settings switch is NEVER enabled and will significantly hamper madVR if it is.
#5 Don't covert HDR to SDR unless your display is not HDR compatible. Use passthrough.
#6 Driver v.385.28 is the last driver that half way works. Anything newer presents even more problems.

The guide in my signature will offer more details for your general questions than this specific madVR forum.

Thanks Brazen and sorry again for capturing this thread

[Warner306]

Originally Posted by NoTechi

Hi everyone,

hopefully my madvr questions are not too newb for this thread ...

Really looking forward to "play" with madvr and other settings on upcoming months and hope you could let me know your opinion if the software setup I described above sounds like a good way to go and again sorry if it is too newbish

NoTechi

1. Kodi DSPlayer is a valid alternative for the next couple of years. I used Jarvis 16.1 for two years and the only thing it lacked was support for three add ons out of the 88 installed on my system. I did miss a couple of those addons, however.

Future releases are in doubt but it can work for a couple of years and updates have always been provided by the original developer in the past despite ceasing active development. The benefit of DSPlayer is that content from video addons can be played through the player, which has madVR support. This includes YouTube, various public broadcasters, online sites, magazines, etc. There are also piracy add ons, if that's your thing. There is even such as thing as madVR-enhanced porn (not that I'm an expert on that subject, but it's out there in large quantities). Be careful when installing any third-party add ons, as this can corrupt your Kodi install with badly-written scripts that constantly run in the background.

Regular Kodi with MPC will offer the best add on support and some of those add ons (but not all) can be played with MPC. This varies based on the type of links in the add on. DSPlayer is more reliable than MPC with video add ons.

I don't know if external players work well for live TV. DSPlayer has native support for some backends, but I don't know if it still works with new versions.

2. There is a Netflix add on in Kodi, but it is limited. Something has been planned for v18, but I don't know how complete it will be. If you use the official Windows Netflix app, you will have to toggle the HDR switch and then turn it off again before using Kodi.

3. Use the official YouTube app in Kodi.

4. I don't think you can play a game in Steam and render it with madVR.

5. For projector owners, HDR -> SDR conversion is the same thing as HDR mode in most respects due to the limited lumens of projectors in all modes. HDR -> SDR conversion still uses PQ gamma and similar tone mapping techniques, so it is no different than your projector's HDR mode, just with different algorithms. It could be better; it could be worse. This technology is still being improved for future releases and hasn't finished the testing stages yet.

6. Driver 385.28 seems to have the least issues of all recent drivers, but newer drivers are working for many users. There are still some quirks and bugs with HTPC use, but there is no need to upgrade the driver as no new features have been added to enhance video playback. All features in newer drivers deal with video games alone.

[NoTechi]

Many Thanks Warner and others this really helps me to get started!

Please if there is more assistance on my questions please use the other thread I started to not get even more offtopic for this thread ...
https://forum.doom9.org/showthread.php?t=175414

I know those who replied here just have been super fast answering and I would like to thank for that

NoTechi

[Darkmatterx76]

Hi, starting last night I started hearing a quiet chirping sound that sounds not unlike a cricket. I've tracked the problem back to MadVR by uninstalling everything installed for playing videos, MPC-HC, MadVR, Re-Clock, and SVP 4 Pro.

I reinstalled everything 1 at a time and tested a video that starts out quiet so it is easier to hear it. It came back near the end of my trial after installing MadVR. I tried resetting MPC-HC and played the video. No chirp. I set MadVR as the preferred rederer and the chirp comes back. It does this in MPC-HC and BE, but not VLC which doesn't have MadVR. I tried applying each component 1 by 1 and still only got the problem once MadVR was activated as a preferred external filter.

Here is a link to an MP3 I recorded of the sound. The sound seems to be constant but is often drowned out by louder sounds. I'm sure it still has an effect on quality though.

http://s000.tinyupload.com/index.php...76119381288677

I'm using the latest ver of all software and have updated my audio and video drivers.

My system is Windows 10 Pro 64
MB: Asus Z97M-Plus (Latest Firmware)
CPU: i5 4690K
Video Card: Asus ROG GTX 1070
Audio Card: Asus Strix SOAR
Audio Listening Hardware Used: Sennheiser HD558 Open Back Headphones
Memory: DDR3 Corsair PC3-10700 (XMP-1600) 800MHz (Dual) 9.0, 9, 9, 24, 41, 2T, 1.5V


Thanks.

DM

[lvqcl]

Sounds a bit like www.youtube.com/watch?v=HP73edpQwgc

[Asmodian]

I am almost positive that is coil whine, a manufacturing defect that specific loads can cause to manafest. Try different madVR settings, more or less load can change or eliminate the sound.

[Darkmatterx76]

I only JUST bought this Asus SOAR a couple weeks ago. If this is in fact a defect I should be returning it. It has a shield over it to prevent this sort of thing. (I thought)

Will Asus see this as a defect, or a "feature?"

Thanks.

[el Filou]

Originally Posted by ashlar42

The problem with Kodi has to do, unfortunately, with too few Windows developers on board. Being open source, I hoped for quite a long while that somebody would fork it to something Windows only and be done with it.

That already happened 14 years ago when Kodi was called XBMC, and the result was MediaPortal 1. It supports madVR too, by the way.