madVR - high quality video renderer (GPU assisted)

[ileile]

Sometimes stereo 3d playback is not smooth, and the "dropped frames" or "presentation glitches" keep increasing. My CPU is not good enough (i3 2100), but I think it is not the reason. Because I tried some times with same movie clip, but the problem is not easy to reproduce.

another problem is that: if I connect two displays and play something using mpc-hc, when I drag the mpc-hc from one display to another, the system often crash. Not BSOD, but something like black screen, system can not respond(ctrl+alt+del usually can't work too, but I can move mouse pointer for a period). this problem may occur with only one display, when switching between window mode and exclusive mode. My GPU is AMD R7 200.

system is windows 10.

[chros]

Originally Posted by tp4tissue

what.. what............................ wait, is it the same download in the OP ?

yep, yep, I haven't realized it for a long time either, just kept extracting the zip file

[James Freeman]

madshi can you please add a ST.2084 EOTF transfer function under calibration tab?

[aufkrawall]

Sometimes my GTX 980 gets stuck in the wrong powerstate when opening videos, it doesn't run with full clock then and drops lots of frames. I suspect this is a randomly triggered bug by NNEDI3 in the OpenCL driver, a bit annoying.
Has someone else observed anything similar? Happens with the current driver (364.51) and some previous ones as well. Win 10 x64.

[fedpul]

Originally Posted by ryrynz

Only 2ms difference between 1D and 2D? I think something's broken, you should maybe look into resetting your settings as my GTX 960 has about 8ms render times when downscaling 4K content and 16-18ms when using 2D (with AR and LL)

Hi, I can confirm that supersampling 720, the difference between SSIM 1D and SSIM 2D is between 2-3 ms. I have a GTX 970 but I can also see that when supersampling 1080 the change in rendering times are kind of abnormal, it is a jump of 30-40 ms between 1D and 2D the same haapens with Jinc. I'm not sure if this is normal or not.

I'm also trying to detect what is causing black screens in 90.15. I'm almost sure that is NNEDI in Chroma Upscaling but I need to do some more testing.

[fedpul]

Originally Posted by aufkrawall

Sometimes my GTX 980 gets stuck in the wrong powerstate when opening videos, it doesn't run with full clock then and drops lots of frames. I suspect this is a randomly triggered bug by NNEDI3 in the OpenCL driver, a bit annoying.
Has someone else observed anything similar? Happens with the current driver (364.51) and some previous ones as well. Win 10 x64.

It happens to me when I update madvr and try to open a movie without restarting the PC.

[bcec]

is superxbr + sr4 preferable over nnedi3@64 + sr3 when doing 1080p->2160p upscaling?

I seem to have slight preference to the latter, but I am not sure if it is placebo, or if there are indeed noticeable difference making the latter a better option?

[ryrynz]

Originally Posted by bcec

is superxbr + sr4 preferable over nnedi3@64 + sr3 when doing 1080p->2160p upscaling?

I seem to have slight preference to the latter, but I am not sure if it is placebo, or if there are indeed noticeable difference making the latter a better option?

Does it really matter what the other users think? It's your opinion that matters more. Screenshot and compare to see if there's a noticeable difference. Everyone has their own preferences.

[Ver Greeneyes]

Originally Posted by bcec

is superxbr + sr4 preferable over nnedi3@64 + sr3 when doing 1080p->2160p upscaling?

I actually tend to stick to sr2 - I find anything higher to be too harsh. But that's pretty much personal preference.

[QBhd]

madshi, has the logic behind when doubling occurs changed? I can no longer use NNEDI3 to double the luma y when I play back 1280x720 ==> 1024x768. I was really happy with the results when I was able to do this:



With 90.15 this is what is happening:



This time I have included my settings.bin which you asked for the last time.

settings.bin

[fedpul]

Originally Posted by QBhd

madshi, has the logic behind when doubling occurs changed? I can no longer use NNEDI3 to double the luma y when I play back 1280x720 ==> 1024x768. I was really happy with the results when I was able to do this:



With 90.15 this is what is happening:



This time I have included my settings.bin which you asked for the last time.

settings.bin

That is beacuse in the first picture you are doubling just luma y (vertical resolución if I am not wrong) and in the second you must be using supersampling so both x and y are doubled. But indeed those settings seems overkill. You should be fine with using nnedi 32 for chroma and 64 for doubling luma. Hope this helps.

[QBhd]

It's the exact same settings... just different versions of madVR. I'm not worried about overkill (noise and heat are non-existant and I don't pay for electricity)... The problem is with the new logic, I can't use anything that doubles the image, it's far too demanding. I don't need to double the x. 1280>2560<1024 is not something I want or need. Doubling the y is rather nice 720>1440<768 is a thing of beauty (to me at least)

QB

[fedpul]

Your point is good, maybe in the future could be an option for selecting to double just y, x or both.

Enviado desde mi MI 4LTE mediante Tapatalk

[bcec]

Originally Posted by ryrynz

Does it really matter what the other users think? It's your opinion that matters more. Screenshot and compare to see if there's a noticeable difference. Everyone has their own preferences.

Great suggestion! what's the right way to take a screen shot in madvr. I see that printscreen gives me a black screen

[Asmodian]

You have to turn off "Windowed overlay" to take screenshots.

[bcec]

Originally Posted by Asmodian

You have to turn off "Windowed overlay" to take screenshots.

Thank you!

[bcec]

Originally Posted by ryrynz

Does it really matter what the other users think? It's your opinion that matters more. Screenshot and compare to see if there's a noticeable difference. Everyone has their own preferences.

Thanks for the recommendation!

Originally Posted by Ver Greeneyes

I actually tend to stick to sr2 - I find anything higher to be too harsh. But that's pretty much personal preference.

After comparing screenshots, you are absolutely right, 4 is quite harsh. I like 2 as well.

[edited]: Also, super-xbr seem to resolve more aliasing than nnedi3@64. Look at the left round frame of his eyeglasses, super-xbr is doing a much better job:

Nnedi3@64:


Super-xbr:

Originally Posted by madshi

It could be a problem with the video decoder, but it's hard to say for sure. Which video decoder are you using? LAV? Which decoding mode (software, DXVA native, DXVA copyback, CUVID, ...)?

The software i am using to play video:
MPC-HC + LAV filters + AC3 filter + madvr.
And the decoding mode is CUVID, using a gtx 660ti.

[ryrynz]

Originally Posted by bcec

Also, superxbr seem to resolve less aliasing than nnedi3@64. Look at the left round frame of his eyeglasses:

I think what you meant to say was that suber-xbr resolves more aliasing than NNEDI3 64 neurons. Super-xbr is looking good there, although the sizes of the images aren't the same.
The top of the ear is another noteworthy mention for suber-xbr here also, NNEDI3 dominates for lower resolution animated content without question though.

[bcec]

Originally Posted by ryrynz

I think what you meant to say was that suber-xbr resolves more aliasing than NNEDI3 64 neurons. Super-xbr is looking good there, although the sizes of the images aren't the same.

yup, that's what I meant (edited the post)

btw, the size of the original images are the same. they are just not cropped equally (i did a quick crop of the face before posting)