madVR - high quality video renderer (GPU assisted)

[DragonQ]

Originally Posted by huhn

if you want to scale to UHD you will need to buy a 1050 ti i don't see a problem with the 1050 for FHD.

you need more than 2 Gb of Vram for UHD.

I see. I'm not sure whether to just get a 1050 for HEVC HD stuff now and upgrade again when I eventually upgrade my TV, or to just plump for the 1050 Ti and maybe have forward compatibility.

[huhn]

do you really think you will need the HEVC decoder?

i would get the 1050 ti or nothing at all.

i have a UHD TV for over a year and a GPU that can decode HEVC too and i never needed it.

[Asmodian]

Originally Posted by CruNcher

The thing is as nice as it sounds to put the PC to the TV it is blasting inefficient on every side just for that small gain especialy with NGU wasting so much energy that is sorry crazy.

All TVs currently are Highly Efficient ARM Platforms Partly with their own Processing SOCs and you Put a PC to that todo Chroma upscaling with a Discrete GPU ?

If you use that TV as a PC Monitor you should take advantage of this and not use the PC at all anymore for Media Playback only for those that ARM System is to weak for or doesn't support, and merge both in a efficient way.

These were questions about madVR... I am not sure what you are arguing; HTPCs aren't worth it in general?

The little ARM computers in TVs are ok but I much prefer Zoom Player wth madVR, NGU, 3DLUT (i1 Pro2), and ED dithering. It takes more power then using the TV's soc but it is higher quality and much easier to control. My Titan X (Pascal) keeps my room nice and warm.

If small gains aren't important then 10-bit isn't important.

[Dogway]

Adding to my question on profiles (I like NGU for SD real life content, but not on anime), I wanted to address a few points.

Overall I like the new GUI, yes some setting freedom is lost but the layout makes more sense. To note a few things, next to NNEDI3 and NGU (only doubling, quadrupling) or something similar should be remarked, so the following settings makes more sense. For instance NNED3 is capable of quadrupling but the setting still says (algorithm to use after "doubling"), it confused me at first and I am a long time madVR user that came back after a few months off.
Also the setting "200% super sampling" looks out of place, I personally don't find how super sampling a 1080 source can be improved for viewing on a 1080 display, all while we already have 200% (doubling) HQ upscalers for sub-1080 sources.

Another point, many graphs don't update accordingly (reconstruction upscaler on the various variations; soft, sharp...)

And a question, what is bicubic50, 60, 75? How does that translate to Catmull-Rom (0.0,0.5), Robidoux (0.3782, 0.3109), Mitchell-Netravali (0.33,0.33)...

[Asmodian]

Originally Posted by Dogway

And a question, what is bicubic50, 60, 75? How does that translate to Catmull-Rom (0.0,0.5), Robidoux (0.3782, 0.3109), Mitchell-Netravali (0.33,0.33)...

Check the second post in my options explained thread.

[Dogway]

@Asmodian, thank you! you quite keep things up to date. I guess arbitrary settings are not possible like Robidoux or that negative "b" Didée suggested back then.

I did some comparisons with my old default (NNEDI3 based), and my (now decided) new default using NGU, they are all transcodes but improvement is superb, even when I'm never for ultra sharp plastic-like results, but NGU does things in a very subtle and smart way, only on very SD content (mostly sub 480p) a softener must be applied, or something like NGU-low (softer) while we wait on what NGU quadruple can deliver. I'm not too fond on relying in post-processing (soften edges, etc) to fix things that can be handled before hand. btw I also second the option for calling madVR settings on a hotkey.

[CruNcher]

Originally Posted by Asmodian

These were questions about madVR... I am not sure what you are arguing; HTPCs aren't worth it in general?

The little ARM computers in TVs are ok but I much prefer Zoom Player wth madVR, NGU, 3DLUT (i1 Pro2), and ED dithering. It takes more power then using the TV's soc but it is higher quality and much easier to control. My Titan X (Pascal) keeps my room nice and warm.

If small gains aren't important then 10-bit isn't important.

You misunderstand me for old TV Platforms MadVR is a good solution but im not sure if it still will stand up vs 2016/2017 Platforms.
We might getting into equal quality results this year on the Processing side for a much bigger userbase.

Especially the "It is higher quality" is questionable if that will still hold up.

And yes a HTPC depending on the Format needed for consumption only is becoming more and more useless and inefficient for the AVG mass market.

And 10 bit is super important and surely no small step finally leaving Hollywood to end users.

MadVR is super useful i agree on the control side of things for Windows PCs and Madshi did a awesome job here, combining things and now presenting his own approach with NGU.

[oddball]

Any chance of adding a new option to allow different profiles for different resolutions? So for something intensive like 4K/UHD playback it allows you to choose a simpler scaling method (or no scaling at all) and will auto switch to that profile upon detection of that resolution? I have found at least one 4K video I cannot play using the settings I usually use for 1080P material without tons of dropped frames even on my overclocked RX 480 and I7 4770K (LG Chess UHD HDR demo). I have to back off to really simple scaling for that clip to play smoothly.

[CruNcher]

Originally Posted by oddball

Any chance of adding a new option to allow different profiles for different resolutions? So for something intensive like 4K/UHD playback it allows you to choose a simpler scaling method (or no scaling at all) and will auto switch to that profile upon detection of that resolution? I have found at least one 4K video I cannot play using the settings I usually use for 1080P material without tons of dropped frames even on my overclocked RX 480 and I7 4770K (LG Chess UHD HDR demo). I have to back off to really simple scaling for that clip to play smoothly.

Huh is it losing Hardware acceleration does it accelerate it at all ?

Is it only this 4K HEVC Demo that collapses with your scaling chain in MadVR on your RX480 ?

But yeah it's the most complex one currently out of Atemes Titan



I actually wonder how Samsungs Hardware Decoder handles it

Would be nice if you could push your RX480 Decoding result of it (without MadVR overhead) in the HEVC Decoder thread we have no information on that one yet.

[QBhd]

Originally Posted by oddball

Any chance of adding a new option to allow different profiles for different resolutions? ......

It's called profiles... and they have been a part of madVR for quite some time.

For example this is what I use:

if     (srcHeight <  641) and (deintFps < 25) "univisium24"
elseif (srcHeight <  721) and (deintFps < 25) "720p24"
elseif (srcHeight <  801) and (deintFps < 25) "1080p24 cropped"
elseif (srcHeight < 1081) and (deintFps < 25) "1080p24"
elseif (srcHeight <  721) and (deintFps < 26) "720p25"
elseif (srcHeight < 1081) and (deintFps < 26) "1080p25"
elseif (srcHeight <  353) and (deintFps < 31) "352p30"
elseif (srcHeight <  405) and (deintFps < 31) "404p30"
elseif (srcHeight <  541) and (deintFps < 31) "540p30"
elseif (srcHeight <  717) and (deintFps < 31) "716p30"
elseif (srcHeight <  721) and (deintFps < 31) "720p30"
elseif (srcHeight < 1081) and (deintFps < 31) "1080p30"
elseif (srcHeight <  721) and (deintFps < 61) "720p60"

QB

[Warner306]

Originally Posted by QBhd

It's called profiles... and they have been a part of madVR for quite some time.

For example this is what I use:

if     (srcHeight <  641) and (deintFps < 25) "univisium24"
elseif (srcHeight <  721) and (deintFps < 25) "720p24"
elseif (srcHeight <  801) and (deintFps < 25) "1080p24 cropped"
elseif (srcHeight < 1081) and (deintFps < 25) "1080p24"
elseif (srcHeight <  721) and (deintFps < 26) "720p25"
elseif (srcHeight < 1081) and (deintFps < 26) "1080p25"
elseif (srcHeight <  353) and (deintFps < 31) "352p30"
elseif (srcHeight <  405) and (deintFps < 31) "404p30"
elseif (srcHeight <  541) and (deintFps < 31) "540p30"
elseif (srcHeight <  717) and (deintFps < 31) "716p30"
elseif (srcHeight <  721) and (deintFps < 31) "720p30"
elseif (srcHeight < 1081) and (deintFps < 31) "1080p30"
elseif (srcHeight <  721) and (deintFps < 61) "720p60"

QB

OR

if (deintFps <= 25) and (srcWidth > 1920) "2160p25"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "2160p25"

else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "2160p60"

else if (deintFps <= 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p25"
else if (deintFps <= 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p25"

else if (deintFps > 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p60"
else if (deintFps > 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p60"

else if (deintFps <= 25) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p25"
else if (deintFps <= 25) and ((srcWidth <= 960) and (srcHeight > 540) and (srcHeight <= 720)) "720p25"

else if (deintFps > 25) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p60"
else if (deintFps > 25) and ((srcWidth <= 960) and (srcHeight > 540) and (srcHeight <= 720)) "720p60"

else if (deintFps <= 25) and ((srcWidth <= 960) and (srcHeight <= 540)) "540p25"

else if (deintFps > 25) and ((srcWidth <= 960) and (srcHeight <= 540)) "540p60"

[Neo-XP]

Originally Posted by Dogway

Also the setting "200% super sampling" looks out of place, I personally don't find how super sampling a 1080 source can be improved for viewing on a 1080 display, all while we already have 200% (doubling) HQ upscalers for sub-1080 sources.

I find it fantastic to reduce aliasing while retaining all the details, and to also reduce dark halos. The result is sharper too so it is a must have for me.
I use it with Bicubic150 AR for downscaling after doubling with NGU for luma, and Lanczos3 AR for chroma doubling (impossible to do that in new versions unfortunately).

PS : One month without a message from madshi in this thread, I hope he is doing a lot of changes to madVR (and for advanced users too)

[kevbo]

One more post on DLP Checkerboard...I've found that the other program that I was using is really kind of unreliable: we attempted to watch a 3D movie with it, and it had several issues, including complete crashing. I loaded the same file up in MPC-HC using madVR showing side-by-side, and it works like a charm. Not that I can _see_ it in 3D like that, but I was testing to see if there was another issue causing the crashes. madVR really seems to do a much better job with MVC.

I suspect this is way low on the priority list these days, with HDR and 4K being more interesting...I just thought I'd ask.

Thanks.

[Telion]

Originally Posted by Neo-XP

PS : One month without a message from madshi in this thread, I hope he is doing a lot of changes to madVR (and for advanced users too)

Yeah, a new Opti-Tune™ Settings Manager which renders all manual settings obsolete.

[arrgh]

Originally Posted by arrgh

MPC-BE; LAV-Filters; xySubFilter; madVR;

give Problems with Subtitles (idx/sub) and cropped h264 Video packed in a MKV:

I have chosen in madVR (under "zoom control") to move the subtitles to the bottom of the screen/window;
but in the case of the cropped Video the Subs remain always within the activ/Video area (I'm in full Screen, not windowed);
also in xysubfilter the "override Placement" Option does not allow to leave the active Video area;

is that a bug, or am I missing something?

Thanks

meanwhile it is clear that the MPC-BE internal subtitle filter can move PGS outside the Video area of cropped Videos (probably also text based ones) but not idx/sub...

LAV/xysubfilter/madVR can neither PGS nor idx/sub...

sorry, if I sound rude; I know everybody is doing this in his spare time, for free... but on the other hand...
I think, with all the discussions about fancy scaling options for equipment where there is no realy matching content available yet (from my Point of view : "early adopter" problems), the basics are losing focus:
things like normal subtitles and 3D-subtitles should work first before one moves on to the next Level...

[e-t172]

So, apparently, AMD is developing a framework called Freesync 2 which doesn't seem to have much to do with variable refresh rate and has more to do with allowing PC applications to get information about the capabilities of HDR displays and then use this information to directly drive the display with HDR content. That sounds extremely relevant to madVR, though just like G-Sync and Freesync, the biggest problem is getting displays other than gaming-focused PC monitors to pick up the standard.

[Asmodian]

I am not sure it is too relevant, low latency tone mapping doesn't help with video playback because latency isn't an issue and we already have fast HDR tone mapping with madVR anyway.

Being able to query the monitor for its tone mapping information might be nice, if it was in a form madVR could use, but it would not be as accurate as using a 3DLUT for HDR tone mapping. Also madshi doesn't seem to like implementing proprietary APIs and Freesync 2 capable displays will always be rare.

Edit: If this does become a good standard for an application to be able to get the display's HDR metadata it would be very good, automatically rendering into the display's native color space sounds very nice. There isn't anything else like this anywhere as far as I know.

[QBhd]

Originally Posted by Warner306

OR

if (deintFps <= 25) and (srcWidth > 1920) "2160p25"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "2160p25"

else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "2160p60"

else if (deintFps <= 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p25"
else if (deintFps <= 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p25"

else if (deintFps > 25) and ((srcWidth > 1280) and (srcWidth <= 1920)) "1080p60"
else if (deintFps > 25) and ((srcWidth <= 1280) and (srcHeight > 720) and (srcHeight <= 1080)) "1080p60"

else if (deintFps <= 25) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p25"
else if (deintFps <= 25) and ((srcWidth <= 960) and (srcHeight > 540) and (srcHeight <= 720)) "720p25"

else if (deintFps > 25) and ((srcWidth > 960) and (srcWidth <= 1280)) "720p60"
else if (deintFps > 25) and ((srcWidth <= 960) and (srcHeight > 540) and (srcHeight <= 720)) "720p60"

else if (deintFps <= 25) and ((srcWidth <= 960) and (srcHeight <= 540)) "540p25"

else if (deintFps > 25) and ((srcWidth <= 960) and (srcHeight <= 540)) "540p60"

This makes no sense... why is everything doubled up? I think it's time to clean up your profile script

QB

Edit: I cleaned it up for you:

if      (deintFps < 26) and (srcHeight < 541)  "540p25"
else if (deintFps < 26) and (srcHeight < 721)  "720p25"
else if (deintFps < 26) and (srcHeight < 1081) "1080p25"
else if (deintFps < 26) and (srcHeight < 2161) "2160p25"
else if (deintFps < 61) and (srcHeight < 541)  "540p60" 
else if (deintFps < 61) and (srcHeight < 721)  "720p60"
else if (deintFps < 61) and (srcHeight < 1081) "1080p60"
else if (deintFps < 61) and (srcHeight < 2161) "2160p60"

BTW.... the easiest and simplest way of doing scripts is to start low and go high with the "less than" operator. And it is best to start with frame rate. As you can see from my scripts it all goes up up and it is easy to insert new profiles if they are needed. It's all about understanding how logic works

[Asmodian]

While it makes no real difference I like:

if      (deintFps < 26) and (srcWidth <= 960) and (srcHeight <= 540)  "540p25"
else if (deintFps < 61) and (srcWidth <= 960) and (srcHeight <= 540)  "540p60" 
else if (deintFps < 26) and (srcWidth <= 1280) and (srcHeight <= 720)  "720p25"
else if (deintFps < 61) and (srcWidth <= 1280) and (srcHeight <= 720)  "720p60"
else if (deintFps < 26) and (srcWidth <= 1920) and (srcHeight <= 1088) "1080p25"
else if (deintFps < 61) and (srcWidth <= 1920) and (srcHeight <= 1088) "1080p60"
else if (deintFps < 26) and (srcWidth <= 4096) and (srcHeight <= 2160) "2160p25"
else if (deintFps < 61) and (srcWidth <= 4096) and (srcHeight <= 2160) "2160p60"

Sometimes things I watch are very cropped so I want to use both dimensions when picking a profile. Resolutions fit together more then frame rates for me... not sure why.

I also tend to add an else "fast" at the end. If madVR hits the end of a profile script without picking a profile it uses the first profile in the settings menu, which is sometimes not what you want with a video that deinterlaces to 120 fps.

[Oguignant]

A little help here. What is the best frequency to watch 23,976 fps movies? I have these options on my TV + NV: 23, 24, 25, 29, 30, 59 and 60 mhz. (And how should I setup reclock?)

Gracias!!!