madVR - high quality video renderer (GPU assisted)

[Warner306]

Originally Posted by FDisk80

Nope, still busted with 397.55.
madVR gives this error when trying to apply custom timings.

I'm assuming you did, but did you make sure you selected a different refresh rate than the one you are trying to customize (e.g. anything besides 23hz?).

[brazen1]

I added Windows Media Center SE as a device to my HTPC activity. I changed Ctrl + J to Ctrl + Z in madVR. I added a soft button to my Harmony 900 mapping the Windows Media Center SE/Ctrl + Z command and pressing it toggles stats off and on.

[tyrindor]

I reported this when Windows 10 1803 was still an insider build but it seems it's still an issue.

I have upgraded two computers to Windows 10 1803 and both of them now have an issue where the video freezes for about 2-5 seconds whenever entering exclusive fullscreen mode. Downgrading back to the previous version of Windows 10 fixes it on both computers.

Titan XP, latest NVIDIA drivers/MadVR/MPC-BE. Default settings everywhere for testing.

[Clown shoes]

Originally Posted by Warner306

If you can map keyboard commands to your Harmony remote, it should be easy. You can change the shortcut in madVR to anything you want. You may even be able to push a button on your remote if madVR recognizes it, but I think it has to be a keyboard combination of some sort.

I use MCE Keyboard as the profile and Windows Media Center SE. Bluetooth keyboard would also work.

Originally Posted by brazen1

I added Windows Media Center SE as a device to my HTPC activity. I changed Ctrl + J to Ctrl + Z in madVR. I added a soft button to my Harmony 900 mapping the Windows Media Center SE/Ctrl + Z command and pressing it toggles stats off and on.

Cheers fellas,

Strangely I just can't get it working!

I have the Harmony 950 and I have Media Center SE added as a device. I've tried Ctrl + J and like brazen1 I have tried changing that to Ctrl + Z, adding either to one of the hard buttons on my remote.

I can't think what might be preventing it from working.

[brazen1]

What happens if you press that key combo on your keyboard? The Harmony should mimic it exactly. Try adding as a soft button.

[Clown shoes]

Originally Posted by brazen1

What happens if you press that key combo on your keyboard? The Harmony should mimic it exactly. Try adding as a soft button.

Well that's the weird bit; the keyboard combo works as expected.

I've tried as software buttons as well but same result. It's all very odd!

[brazen1]

You may have added Media Center SE as a device incorrect or something? If you call up the device 'Media Center SE', do any of the softkey functions for it work? Alt + F4 for example on a desktop window or mouse curser movement. Just seeing if it has any function. Beyond this, I've no idea?

[tzr916]

Is there any problem in running different installs of madVR on one machine?

I noticed that Zoom Player downloads/installs it's own madVR, then Jriver MC does the same (Jriver actually discourages trying to use the latest available in MC). Each install does have their own directory and settings.bin. So are there registry settings or other conflicts?

What about LAV? Similar situation....

[zaemon]

Originally Posted by tzr916

Is there any problem in running different installs of madVR on one machine?

I noticed that Zoom Player downloads/installs it's own madVR, then Jriver MC does the same (Jriver actually discourages trying to use the latest available in MC). Each install does have their own directory and settings.bin. So are there registry settings or other conflicts?

What about LAV? Similar situation....

I think you cannot have two instances of madVR.

[tzr916]

Originally Posted by zaemon

I think you cannot have two instances of madVR.

But I do.

Zoom Player installs (the latest) madVR in Program Files(x86).
Jriver installs (an approved version of) madVR in User/AppData/Roaming/Jriver/Plugins.

They both run fine, AFAIK.

[brazen1]

I'm pretty sure you can run two different instances of LAV also. Why not try your two different versions of madVR with your two different players and see what each shows as a version in the Windows notification area on your taskbar. Press Ctrl + S during playback from each player and see what version of madVR it displays.

[tzr916]

Yes, they both show different versions, when playing from each player. And they both have their own settings.bin.

[brazen1]

Hmmmm? I usually dial back my madVR settings to accommodate all videos that fall within certain profiles. I don't want to tailor madVR or anything else based on the variances in titles other than what profiles already offer. For instance, one 1080p title can use some very high settings. Another 1080p needs the settings dialed back. There is nothing a profile would distinguish differently between the two titles. One is just more resource intensive than the other. Perhaps I could use one version of madVR with settings appropriate for one title using MPC-BE, and another version of madVR for the other more intensive titles using MPC-HC for example? I can call up as many different players in my front end (KODI) as I desire to add. Presently I'm using 5 different players default assigned where each shines best.

MPC players only allow to select which renderer, not versions of the same renderer. This could pose a problem. madVR versions would need to be added in front end software unless someone knows how to associate madVR versions with players. This could be a wild goose chase. Only want to use one front end.

One example that would work appears to use ZoomPlayer with one madVR version and MPC with another. I may give this a try....

[stefanelli73]

After installing a NVIDIA GTX 1080 and tired of the constant bugs of the various drivers, I reassembled my "old" AMD RX480 and the first thing I noticed that even with version 92.14 I had 10bit and not 8bit, so the "problem" it exists only for NVIDIA.

[brazen1]

Yes, we know. Nvidia does not offer RGB 10bit. Never has. Only 8 and 12. Just use 8bit until maybe one day they decide to get around to it unless your display handles 12bit perfectly..... yawn.

[Asmodian]

Originally Posted by Manni

There was banding only in passthrough, only in fullscreen windowed mode, only in Windows 10, and it was very minor. So not that surprising.

People are noticing the number 8 because in most cases, there was NO banding in 10bits, but they now have (momentarily until it's restored) lost that feature, so it's very understandable they notice the unnecessary limitation and didn't notice anything before, when everything was working fine with no banding at all (or very minor one if win10 FSW passthrough).

I think you missed huhn's point.

People are not noticing a change in image quality, they only notice the change in the number in the OSD. If madVR lied and said it was outputting 10 bit when it was really dithered 8 bit no one who is noticing this change now would have noticed.

You have to do very specific tests with dithering disabled to even be able to tell if it is 8 or 10 bit. I really do not understand why so many people are so obsessed with 10 or 12 bit output. We have people using 4:2:2 chroma subsampling because they want 12 bit.

I see why madshi didn't worry about 10 bit for so long, bit depth is massively overrated by the casual HTPC user.

Then you have displays like mine, which offer better image quality using 8 bits, and people still want to send them 10 bit. Even I have to recheck this fact every once in a while.

10 bit just seems like it should be much better, but it really isn't.

[huhn]

it get's really interesting if you check part used in TVs and see that nearly every high end TV is 8 bit.

[Clown shoes]

Originally Posted by Asmodian

I think you missed huhn's point.

People are not noticing a change in image quality, they only notice the change in the number in the OSD. If madVR lied and said it was outputting 10 bit when it was really dithered 8 bit no one who is noticing this change now would have noticed.

You have to do very specific tests with dithering disabled to even be able to tell if it is 8 or 10 bit. I really do not understand why so many people are so obsessed with 10 or 12 bit output. We have people using 4:2:2 chroma subsampling because they want 12 bit.

I see why madshi didn't worry about 10 bit for so long, bit depth is massively overrated by the casual HTPC user.

Then you have displays like mine, which offer better image quality using 8 bits, and people still want to send them 10 bit. Even I have to recheck this fact every once in a while.

10 bit just seems like it should be much better, but it really isn't.

Originally Posted by huhn

it get's really interesting if you check part used in TVs and see that nearly every high end TV is 8 bit.

This is a very good point and shows that sometimes people become so obsessed with the numbers that they forget to just sit back and enjoy watching their content

It does make me wonder though about a lot of the current high end sets that say they are 10 bit, but are actually 8bit + FRC, which as I understand it is dithering at the TV end. In this scenario are we best off sending 8bit from MadVR or 10 bit and above?

[ntropy]

Originally Posted by Asmodian

If your brightness is at 30% then don't using the "500 nits" marketing as a data point, it is probably closer to 120-180 nits. It is 500 nits at 100% brightness (and nits is not linear with brightness).

I thought that "let madVR decide" would be the same as converting to SDR with your display, it converts to SDR with pixel shader math on SDR displays and does passthrough on HDR displays. That said maybe it does do something different, ignoring or overwriting bad metadata comes to mind from past discussion. We do know the paths are different, based on a recent bug that had an effect when set to convert to SDR with pixel shaders but not when using let madVR decide.

So I should turn the iMac display's brightness up to 100%? I tried it. It looked bright.

[Manni]

Originally Posted by Asmodian

I think you missed huhn's point.

People are not noticing a change in image quality, they only notice the change in the number in the OSD. If madVR lied and said it was outputting 10 bit when it was really dithered 8 bit no one who is noticing this change now would have noticed.

You have to do very specific tests with dithering disabled to even be able to tell if it is 8 or 10 bit. I really do not understand why so many people are so obsessed with 10 or 12 bit output. We have people using 4:2:2 chroma subsampling because they want 12 bit.

I see why madshi didn't worry about 10 bit for so long, bit depth is massively overrated by the casual HTPC user.

Then you have displays like mine, which offer better image quality using 8 bits, and people still want to send them 10 bit. Even I have to recheck this fact every once in a while.

10 bit just seems like it should be much better, but it really isn't.

I didn't miss anything at all. I'm only saying that it was only a very small minority of users that were affected by very minor banding (provided their displays were able to handle 10-12bits of course), but the latest version nukes this for ALL nVidia users, including those that had NO banding whatsoever because they were not using passthrough.

I'm aware that many people should be using 8bits for various reasons, and using 4:2:2 just to get 10bits is clearly a bad idea, but if you can get 10bits 4:4:4, that's a bit less noise than with 8bits 4:4:4, so I don't see why this should go.

Of course, most of you have displays that can't handle more than 8bits, or that could handle 10bits but not the 12bits that nVidia sends, so you keep harping about "no difference" between 8bits and 10bits, but that's simply not true if you have a 10bits or 12bits capable panel.

And by the way, I don't know any "casual" HTPC user that uses MadVR. I'm certainly not a "casual" HTPC user, and neither are you or most of those posting in this thread.

There is nothing better about 10bits regarding banding, MadVR's dithering is excellent, but there is simply a bit less noise than with 8bits.