madVR - high quality video renderer (GPU assisted)

[aufkrawall]

I'm hoping for a anti-ringing solution for SupeRes that works as good as the deringing filter, but without the bad effects combined with SuperRes. madshi said he didn't remove the anti-ringing checkbox for SR because he has plans to improve it. :devil:

[iSeries]

Hi Madshi,

Is it possible to add profiles for 3dluts? Or maybe a keyboard shortcut to switch them? My plasma calibrates completely differently at different refresh rates so this would be very useful.

[Asmodian]

Hi Madshi,

Is it possible to add profiles for 3dluts? Or maybe a keyboard shortcut to switch them? My plasma calibrates completely differently at different refresh rates so this would be very useful.

You can make profiles for devices now so you can make profiles for 3DLUTS now. :)

[JarrettH]

Make SuperRes faster, or deband, or Smooth Motion...:D...I don't know; however, I need a performance bump somewhere. :cool:

[pose]

the source is not using a standard timing but you are using smoothmotion so you can ignore this number the frame repeat is not going to happen.

Are you sure about that? Can you explain mechanic behind this please?

[Asmodian]

Are you sure about that? Can you explain mechanic behind this please?

Smooth motion perfectly displays the source frame rate at the display's true (measured) refresh rate, smooth motion never needs to drop or repeat frames to match audio sync.

madshi has told us that line in the OSD can be ignored if using smooth motion. :)

[robl45]

So I tried the 3d mvc again. It appears to work, but basically only if I skip a little bit in the movie, like move the movie back a little on the slider, than it seems to play correctly. Anyone know why this is? Otherwise I get the phenomenon where the eyes are slightly out of sync. Basically the 3d looks fine until there is any movement, then you can tell its a little blurry and the scene changes are obviously messed up.

[JarrettH]

Why isn't this activating for 60 fps?

if (srcWidth <= 800) "SD"
if (srcWidth >= 801) "HD"
if (fps = 60.000) "Live Stream"

Can someone simply fix this? Thanks

I've tried reordering it too (assuming it looks for 60 fps first)

if (srcWidth <= 800) "SD"
if (fps = 60.000) "Live Stream"
if (srcWidth >= 801) "HD"

Somehow it needs to not activate HD before looking at the fps

if (srcWidth <= 800) "SD"
else if (srcWidth >= 801) and (fps = 60.000) "Live Stream"
else "HD"

This doesn't work either. Is something bugged?

[leeperry]

I need a performance bump somewhere

werd :D

[hannes69]

if (fps = 60.000) "Live Stream"


Maybe it´s a bad idea to compare to exact numbers. Do you have 60fps movies or 59.94fps movies? And maybe a 60fps movie is measured as 59.999fps or 60.001fps, then your logic won´t work. Use something like fps>59.9

Originally Posted by ryrynz View Post
That leeperry will find some esoteric setting that he really can't live without, madshi will ask for opinions on it and end up deprecating it thus removing his preferred setting
forcing him to hold on to what he believes is the "perfect" madVR build.

This joke made my day :) Especially because it isn´t a joke but more a kind of reality :devil: Good job ryrynz, you could be a good clairvoyant:cool:

[JarrettH]

Maybe it´s a bad idea to compare to exact numbers. Do you have 60fps movies or 59.94fps movies? And maybe a 60fps movie is measured as 59.999fps or 60.001fps, then your logic won´t work. Use something like fps>59.9



This joke made my day :) Especially because it isn´t a joke but more a kind of reality :devil: Good job ryrynz, you could be a good clairvoyant:cool:

I'll try that too, but I just entered whatever madvr reported in the stats window. :devil:

[Myrsloik]

I believe Y416 input is broken. More specifically that the plane order is switched. I found this when adding Y416 output to VapourSynth and I'm very certain my own code is correct. I can't give you a good example script until I release the next VS version though.

[huhn]

forcing Y416 in lavfilter is working fine.

so it should work in general shouldn't it?

[nevcairiel]

I believe Y416 input is broken. More specifically that the plane order is switched. I found this when adding Y416 output to VapourSynth and I'm very certain my own code is correct. I can't give you a good example script until I release the next VS version though.

forcing Y416 in lavfilter is working fine.

so it should work in general shouldn't it?

Indeed, LAV Filter properly forms the format according to Microsofts documentation for it, and madVR can handle it fine.
I did just double-check the generated format from LAV Filters, and it seems fine to me.

Unless Microsofts documentation has confused myself and madshi in the same way and we implemented it both backwards.
That then begs the question, is there any independent software that could be used to verify?

A quick check seems to suggest that Microsofts Y416 and Apples y416 (note the lowercase) might use different plane order, but madVR being a DirectShow component, using Microsofts definition seems to be the one to go with.
(MS uses AVYU and Apple uses AYUV)

[Georgel]

We're supposed to never use G-sync with madVR, no?

How do we make sure it's disabled?

(Testing a G-sync based config and wanting to get best results with madVR)

(Using G-sync, or at least leaving it seemingly enabled doesn't seem to affect performance at all or do anything, so either it's not disabled or it's okay to leave them working together) (Still testing on this, sorry if I'm wrong)

BTW, first time without optimus in years, I love being without it. Finally the frames aren't jumping around anymore. It was so annoying. Quick advice: avoid optimus as much as possible. There are cheap solution without it, just go with them, it will make madVR run much better, and for me optimus meant a lot of unreported skipped frames (they were never repordet as dropped but the image was not fluid at all) ^_^

[Asmodian]

You can disable G-sync for your video player in the application specific 3D settings in Nvidia's drivers. That said madVR and G-sync seem fine together now, the only difference appears to be a slightly reduced measured refresh rate, e.g. 143.86Hz instead of 143.99Hz in my case. I still keep it disabled for my video player anyway.

[CarlosCaco]

We're supposed to never use G-sync with madVR, no?

How do we make sure it's disabled?

(Testing a G-sync based config and wanting to get best results with madVR)

(Using G-sync, or at least leaving it seemingly enabled doesn't seem to affect performance at all or do anything, so either it's not disabled or it's okay to leave them working together) (Still testing on this, sorry if I'm wrong)

BTW, first time without optimus in years, I love being without it. Finally the frames aren't jumping around anymore. It was so annoying. Quick advice: avoid optimus as much as possible. There are cheap solution without it, just go with them, it will make madVR run much better, and for me optimus meant a lot of unreported skipped frames (they were never repordet as dropped but the image was not fluid at all) ^_^

I've seen a lot of people with madvr problems on optimus, I never had really a problem... only that optimus its not optimal hehe... but now I having the first time experience without optimus too.. and its great hehe for me the best change its the possibility to use windows overlay mode.. it's great! I think optimus has some perfomance loss because have to pass information from one gpu to another gpu...

[Georgel]

I've seen a lot of people with madvr problems on optimus, I never had really a problem... only that optimus its not optimal hehe... but now I having the first time experience without optimus too.. and its great hehe for me the best change its the possibility to use windows overlay mode.. it's great! I think optimus has some perfomance loss because have to pass information from one gpu to another gpu...

Whoa!

You must be having a really good computer!

My Acer VN7-791G with optimus did not work as I wanted with madVR. There was a serious delay between render time and presenting time. and this kinda broken the entire video playback..

For example, a smooth panning scene would stop and jump around instead of being a smooth panning scene, while without Optimus (direct GPU to display), the scene pans smoothly.

While at first it doesn't seem much, it can get pretty distracting over time... Then you eventually get used to it.

Good part is that some devices using Optimus fare very well. this or it's my fault for not setting it up the right way.

What Optimus does is that it basically sends the data to the GPU, data goes through iGPU, data is processed in the dGPU, sent back to the CPU (iGPU) then sent to the display. This while road data has to travel creates heat, delay (lag) and the data bus can be a bottleneck for the data transfer rates in this case. Best way to explain what happens is that even though the computer processes the data in good time (under 16 ms for 60fps), the display doesn't receive each frame in time due to this road the data has to travel and this can cause a delayed, dropped or a wrong timed frame.

Worst part is that this is something not happening with most software (you can play games smoothly at 60fps as long as the GPU processess the image much faster), but to use madVR close to it's full potential, the smoothness of the video can take a hit.

[Georgel]

You can disable G-sync for your video player in the application specific 3D settings in Nvidia's drivers. That said madVR and G-sync seem fine together now, the only difference appears to be a slightly reduced measured refresh rate, e.g. 143.86Hz instead of 143.99Hz in my case. I still keep it disabled for my video player anyway.

Thanks!

I'm new to Gsync and such,... Seems like there is no difference in most case scenarios, but it's cool to have it around.

[ryrynz]

With the GTX 960 I get 24.97014Hz and get a frame drop every 4 minutes or so, is the Pascal range able to get any closer to 23.976?

[ren7o]

Anybody encounter fullscreen freeze on the Crimson 16.9.1
on 64bit Win 10?
Revert back to Crimson 16.8.3... :(

[Georgel]

With the GTX 960 I get 24.97014Hz and get a frame drop every 4 minutes or so, is the Pascal range able to get any closer to 23.976?

Depending on video, Pascal gets from 1 frame repeat every 2 minutes up to 1 frame repeat every 30 minutes... Can't say it's consistent enough to make an assertion if it's better or not.

Anybody encounter fullscreen freeze on the Crimson 16.9.1
on 64bit Win 10?
Revert back to Crimson 16.8.3... :(

Had an AMD driver just fail and freeze using windows 10, there could be something wrong with their last versions..

[CarlosCaco]

With the GTX 960 I get 24.97014Hz and get a frame drop every 4 minutes or so, is the Pascal range able to get any closer to 23.976?

Have you tried the guide in this forum? Me and my friends get perfect timings with different nvidia gpus...

My for ex is an GTX 570 and with cru I get 23.97627 and get one frame repet every 15 hours...
Why 960 can t do this?

[ryrynz]

Have you tried the guide in this forum? Me and my friends get perfect timings with different nvidia gpus.

I attempted using that guide but ended up having Windows boot into a black screen. That guide is not very clearly written BTW, for such a fairly simple process that guide makes it far harder to understand than it should.
I think I'll post in that (http://forum.doom9.org/showthread.php?t=173571) forum and perhaps we might figure out needs to be changed to get this working.

[QBhd]

Anybody encounter fullscreen freeze on the Crimson 16.9.1
on 64bit Win 10?
Revert back to Crimson 16.8.3... :(

I've had no issues what so ever with the latest Crimson... specs in my signature with the latest version of Windows 10

QB

[huhn]

I attempted using that guide but ended up having Windows boot into a black screen. That guide is not very clearly written BTW, for such a fairly simple process that guide makes it far harder to understand than it should.
I think I'll post in that (http://forum.doom9.org/showthread.php?t=173571) forum and perhaps we might figure out needs to be changed to get this working.

the black screen is one of the things that just happens.
you have to try a different approach to get the same timing.

maybe your screen doesn't like custom resolution less then other than there is little you can do.

i said before that this guide/custom resolution in general is nothing for an avg user.

[Sunset1982]

With the GTX 960 I get 24.97014Hz and get a frame drop every 4 minutes or so, is the Pascal range able to get any closer to 23.976?

Have you tried to create a custom resolution?

[ryrynz]

Have you tried to create a custom resolution?

Getting something working seems harder than I thought it would be, almost thinking it's not worth the hassle. Already wasted a hour on it so far with no success and am not even sure I'm doing it right, I'll leave it off this forum as it's not really the place for it.

[pose]

Have you tried the guide in this forum?

This guide is terrible honestly. The worst guide ive seen in a while. Ive spend a lot of time and still couldn't make it work.

[Sunset1982]

Getting something working seems harder than I thought it would be, almost thinking it's not worth the hassle. Already wasted a hour on it so far with no success and am not even sure I'm doing it right, I'll leave it off this forum as it's not really the place for it.

Try this: in nv control panel create a custom resolution. Then use this options:

http://fs5.directupload.net/images/160928/rfiaj3hh.jpg (http://www.directupload.net)

just lower the last vertical pixel counter 1. In this case it would be 1124. Save it and try running a 23,976 movie. It leads to 1 frame drop every 3-4 hours on my machine with my old 970, 960 and new 1060.

[ryrynz]

Try this

DUDE. *High five*
What exactly is this doing BTW?
MadVR is all over the place with estimation on this, from 1 frame drop every couple of hours to a couple of days.

[Sunset1982]

DUDE. *High five*
What exactly is this doing BTW?

i dont really know. :D

found it in a tutorial some time ago. Searched for months because I never got drop free 23,976 playback on nvidia. Since then, it worked like a charm on all tested nv cards. UHD resolution too.

with amd, there is no such issue. running good out of the box. This and the nv 3D setup mess (3D is not working if a custom resolution is set) is the reason I'm using a rx480 on my htpc now. my gtx 1060 is now in my gaming machine.

[Della]

Try this: in nv control panel create a custom resolution. Then use this options:

http://fs5.directupload.net/images/160928/rfiaj3hh.jpg (http://www.directupload.net)

just lower the last vertical pixel counter 1. In this case it would be 1124. Save it and try running a 23,976 movie. It leads to 1 frame drop every 3-4 hours on my machine with my old 970, 960 and new 1060.

Even without the -1, I've been getting 23.9763 on 960 and now 1070.

[huhn]

Anybody encounter fullscreen freeze on the Crimson 16.9.1
on 64bit Win 10?
Revert back to Crimson 16.8.3... :(

dxd9 new path is broken with this driver.

try the old path or d3d11 as a work around for now.

AMD released broken driver a lot in the past there are major OpenGL problems too.

so just hope that they will get there **** together soon.

[clsid]

Latest one is 16.9.2.
Dunno if it fixes anything.

[CarlosCaco]

This guide is terrible honestly. The worst guide ive seen in a while. Ive spend a lot of time and still couldn't make it work.

I waste some time with cru before reading the guide, in fact I read a lot about customs resolutions before... so when I read the guide the things became very clear to me... it was very easy but I see lots of people
Complaining... I not a native English speaker but I can try to explain better the guide...
I think worth waste sometime on this because really improves the smoothnes, I m very sensible to frame glitches drops and repeats só for me its very important the right timings
It's Good read the cru forum tô know the right configuration

[huhn]

Latest one is 16.9.2.
Dunno if it fixes anything.

just tried it. still broken.

it is known in the bug tracker for some time now: http://bugs.madshi.net/view.php?id=431

[Betroz]

Try this: in nv control panel create a custom resolution.

This doesn't work with my Panasonic VT30 plasma TV and GTX 1080 card for some reason. When the profile is saved, it says 24 Hz and not 23.976 Hz.

[Georgel]

Had a chance to play through with an 1080 card. Everything maxed out per my own usage (not using NNEDI 256 anywhere because I don't feel like it's actually needed though). I must say that besides some noise, an 1080 is enough to fully take advantage of madVR features at FHD up to 60fps, smooth play, and amazing image quality.

@madshi Thank you very much for this great software!

(Planning to test 4K on 4K display soon, downscaled 4K videos work well.)

[ryrynz]

This doesn't work with my Panasonic VT30 plasma TV and GTX 1080 card for some reason. When the profile is saved, it says 24 Hz and not 23.976 Hz.

The profile will say 24Hz. It's what madVR says for display and repeating/dropped frames that's key.
MadVR will change to this with 1080p23.

There will be a new madVR version in maybe 2-3 weeks or so (maybe longer), with a brand new algorithm that you guys will probably like a lot.

Fingers crossed another post processing filter, denoising or deblocking would be nice.

[Ver Greeneyes]

Fingers crossed another post processing filter, denoising or deblocking would be nice.
Deblocking would be great, yeah. I've noticed that chroma especially tends to be a mess of blocks for things like YouTube videos (though admittedly chroma artifacts are much less noticeable), which probably trips up the scaling algorithms quite a lot.

[ryrynz]

Deblocking would be great, yeah.

It's surprising how blocky some frames of video can be even at 720 or 1080 resolution.
It's the lower quality videos that require the most help from madVR. Still a lot of lower quality content being watched out there and onboard GPU's are really starting to stretch their legs now.

[CarlosCaco]

I have some internet rips that are taged as variable framerate... what the purpose of this? How media player and madvr handle this? Why the ripper want to make a rip with a variable framerate...
Should I expect to see judder, glitches, frame drops on this type of file?

[ryrynz]

Should I expect to see judder, glitches, frame drops on this type of file?

I'd guess that depends on what your refresh rate is. If you have Smooth Motion enabled it shouldn't be an issue.

[CarlosCaco]

I'd guess that depends on what your refresh rate is. If you have Smooth Motion enabled it shouldn't be an issue.

No... its on my 23.976 mode but the files have a minibus and a maximum framerate...
Why someone doe that?

[huhn]

because the source is VFR. that's the only correct treatment you can do to some sources.

there is a lot of content that has 23p scene and 29p scene put in 59i or 59p. the only solution is a VFR encode.

smoothmotion can handle VFR BTW.

[ShiftyFella]

Why isn't this activating for 60 fps?

if (srcWidth <= 800) "SD"
if (srcWidth >= 801) "HD"
if (fps = 60.000) "Live Stream"

Can someone simply fix this? Thanks

I've tried reordering it too (assuming it looks for 60 fps first)

if (srcWidth <= 800) "SD"
if (fps = 60.000) "Live Stream"
if (srcWidth >= 801) "HD"

Somehow it needs to not activate HD before looking at the fps

if (srcWidth <= 800) "SD"
else if (srcWidth >= 801) and (fps = 60.000) "Live Stream"
else "HD"

This doesn't work either. Is something bugged?
srcfps option never worked for me, try using deintFPS >=50 instead as 1st rule, this will obviously screw settings for files that do require deinterlacing and are not live sports but most of my files that require it are, so no issue for me. you can always try switching profiles manually tho

[Warner306]

deintFps works for me as a profile rule. The source doesn't need to be deinterlaced.

[Asmodian]

Why isn't this activating for 60 fps?

if (srcWidth <= 800) "SD"
else if (srcWidth >= 801) and (fps = 60.000) "Live Stream"
else "HD"

This doesn't work either. Is something bugged?

I would suggest:

if (srcWidth <= 800) "SD"
else if (deintFPS > 59) "Live Stream"
else "HD"

The "else if" will only be evaluated if the first statement is false so you don't need to check the resolution again. Never use an = sign for fps, the real value has higher precision than 60.000 and is usually something like 59.94005994005994, your 60.000 was probably something like 60.000001 fps. :p

[AngelGraves13]

Is there a way to tell madvr to use double expanded range for a specific file every time? I've heard you can add something into the filename, but what about a header in the mkv or a tag?