madVR - high quality video renderer (GPU assisted)

[chros]

Hi. I'm looking to madvr profiling. Does exist a switch that allow to enable a profile if the laptop is running with ac plugged or battery? I'd like to set a lighter profile when I'm running on battery only.
Not in an automated way, as far as I know, but you can switch between them manually.

[Akeno]

Hi, :helpful:
I tried this method, but it didn't work. Nothing like "Geforce GTX 960M" showed up. How do I make madvr use the 960M instead of HD4600?
(W10 64, newest driver for both GPU, Jinc3 & xbr).
Thanks in advance!

Two ways of doing this:

Use the Nvidia inspector and change the MPC-HC profile settings to utilize the GPU
or make a copy of the MPC-HC exe and rename it to something like MPC-HC graphics card and set that to use the GPU and as your default player.

[x7007]

Following this guide
http://forum.doom9.org/showpost.php?p=1730855&postcount=31986

Does it mean I need to select


Chroma Upscaling : super-xbr - Sharpness 100 - AR - SuperRes Filter / Default
image downscaling : Lanczos 3 Taps - AR
image doubling : not sure what to choose here
image upscaling : Jinc - AR
upscaling refinement : SuperRes / Default - 1 , 0.66 Rfine the image after every ~2x upscaling step

Is that correct / same as what madvr selected , is that how you enable SuperRes or there is other way ? Do I need to select upscaling refinement after selecting it in chroma upscaling ?

[huhn]

superres should be used only once so select "refine the image only once after upscaling is complete"

[x7007]

superres should be used only once so select "refine the image only once after upscaling is complete"

So I only select SuperRes from Chroma Upscaling and not touching the upscaling refinement ? what it is for ?

[huhn]

chroma is for chroma and image is for image so you can use both if you see the difference.

but upscale refinement and superres shouldn't be used with every 2x.

[Akeno]

You can also use this chart as a sort of guide. As for what you need to select, that depends on both your hardware's abilities and your eyes. Image doubling doubles the image size using whatever algorithm you select there. As a rule of thumb, people are much more sensitive to the luma channel than the chroma channel so the majority of madVR users put their processing power into image scaling.
http://haruhichan.com/img/KCP/mvrchart.png

[nghiabeo20]

Two ways of doing this:

Use the Nvidia inspector and change the MPC-HC profile settings to utilize the GPU
or make a copy of the MPC-HC exe and rename it to something like MPC-HC graphics card and set that to use the GPU and as your default player.


does it force 960M to decode and render the film? or just decode? thanks!

[Akeno]

Decoding is done by whatever you have designated. MPC-HC will automatically use its internal LAV Filters if you haven't specified another one. madVR has no decoding capabilities as it is purely a video renderer.

[x7007]

chroma is for chroma and image is for image so you can use both if you see the difference.

but upscale refinement and superres shouldn't be used with every 2x.


So selecting Refine the image only once after upscaling is complete would be preferred ?

The question is can I select Chroma Upscaling SuperRes and Select Upscaling refinement SuperRes .

from the post I read super-xbr + SuperRes has better quality than Jinc tap 3. that what Madshi said at least

[Akeno]

You can select both if you prefer and if your GPU can handle running both. Development of SuperRes is being concentrated on upscaling refinement at the moment as that produces the most visible differences. This means that the SuperRes filter in Chroma and Upscaling Refinement are similar but not the same due to more tweaks made towards the latter.

[chros]

does it force 960M to decode and render the film? or just decode? thanks!

Decoding is done by whatever you have designated. MPC-HC will automatically use its internal LAV Filters if you haven't specified another one. madVR has no decoding capabilities as it is purely a video renderer.
As Akeno said, for me both decoding and rendering is done by nvidia in this way.

[amayra]

did i missed the reason you can't use 353.49 needi3 work with these driver under win10
upgrade to windows 10 worst decision ever

[huhn]

upgrade to windows 10 worst decision ever

this is an nvidia issue not windows 10. keep on track plz not everyone is ignoring new features.

[XMonarchY]

Is madshi resting/on vacation with red pandas or coding for new madVR? I don't have a problem with either!

BTW, NVidia stated that it was simply the first company to remove D3D9 - OpenCL support from their drivers due to its age and rare cases when it is used, especially in Windows 10. Supposedly both AMD and Intel will drop support for this interop sooner or later. Then again, NVidia hasn't made the best decision in recent past - lack of Async shader support in DirectX 12, overall poor/glitchy drivers (aside from D3D9 - OpenCL interop), and of course lack of the needed OpenCL interop is drivers past 353.49 Hotfix release... AMD may become the next Home Theater and gaming ruler!

[Akeno]

People need to stop assuming that Nvidia is purposely gimping their drivers. They're doing what's best for business and what's best is reflected in what the market needs or wants. D3D9 <-> OpenCL interop fits neither of those criteria outside of specific cases like with madVR. If you want to complain about Windows 10 and Nvidia, do so in a different thread instead of clogging up a madVR discussion and testing thread.

[Kranium]

I was playing around with my MadVR settings last night and a few questions have popped up.

When I play any 29-30fps video in FSE I get something like 10+ repeated frames per second. I lowered upscaling settings a lot with these files and it didn't change anything. I just realized I didn't play with Smooth Motion settings though. Any other ideas why this would be? When I run the same files windowed at the desktop's 60Hz setting I do not get these repeated frames.

Second question. I reached a "desired" upscaling setting that has 39-41ms rendering times on fairly high bitrate 720p -> 1080p conversions. I had read that you want to keep these a bit lower, but if I'm not getting any reports of dropped or repeated frames should it be ok? Or is there another downside I am not thinking of.

Thanks for the help in advance :o

*Edit: This is Win10 with 353.49 drivers.

[zvans18]

When I close Precision X everything works fine. Other overclocking programs like MSI Afterburner or Asus GPU Tweak do not have this issue.

FWIW precision made a bunch of games stop working correctly for me, something is definitely wrong with some part of it

[huhn]

When I play any 29-30fps video in FSE I get something like 10+ repeated frames per second. I lowered upscaling settings a lot with these files and it didn't change anything. I just realized I didn't play with Smooth Motion settings though. Any other ideas why this would be? When I run the same files windowed at the desktop's 60Hz setting I do not get these repeated frames.
a screen from the OSD could help.
Second question. I reached a "desired" upscaling setting that has 39-41ms rendering times on fairly high bitrate 720p -> 1080p conversions. I had read that you want to keep these a bit lower, but if I'm not getting any reports of dropped or repeated frames should it be ok? Or is there another downside I am not thinking of.
that fine as it is.

[ryrynz]

People need to stop assuming that Nvidia is purposely gimping their drivers. They're doing what's best for business and what's best is reflected in what the market needs or wants. D3D9 <-> OpenCL interop fits neither of those criteria outside of specific cases like with madVR. If you want to complain about Windows 10 and Nvidia, do so in a different thread instead of clogging up a madVR discussion and testing thread.

I share the same sentiment. Like I've said before, downgrade your driver and wait for madshi to fix it.

[Akeno]

Second question. I reached a "desired" upscaling setting that has 39-41ms rendering times on fairly high bitrate 720p -> 1080p conversions. I had read that you want to keep these a bit lower, but if I'm not getting any reports of dropped or repeated frames should it be ok? Or is there another downside I am not thinking of.

I would prefer render times to be no higher than 25 or 26ms simply because I want the option to watch 30hz video as well. The frame interval on that is about 33ms but I also like to keep a buffer room in case something pushes my GPU a bit harder than normal so that it won't jump over the frame interval. What you have is fine, however.

[Kranium]

a screen from the OSD could help.

that fine as it is.

I don't think I can screen shot FSE can I? It does it in windowed overlay too anyway so I took a shot of that. This is after only like 2-3 minutes of running. Maybe the few 30hz videos I have are encoded poorly. I have tried turning smooth motion off, lower upscaling settings, and since I was in there I unchecked present a frame for every vsync. Nothing changed this behavior so far.

http://oi59.tinypic.com/34pmgao.jpg

I would prefer render times to be no higher than 25 or 26ms simply because I want the option to watch 30hz video as well. The frame interval on that is about 33ms but I also like to keep a buffer room in case something pushes my GPU a bit harder than normal so that it won't jump over the frame interval. What you have is fine, however.

Thank you for the input. Maybe it's time I create some profiles for those cases you mention.

[bcec]

Apart from NNEDI3 not working with current nVidia drivers, are people happy with MadVR performance in Windows10 (or with Windows10 overall)? I am debating whether I should upgrade or not from Win7. I was a firm believer of NNEDI3, but after I recently switching to super-xbr & SuperRes, I am not looking back, so I am not worried about NNEDI3 issue.

[optimist]

Apart from NNEDI3 not working with current nVidia drivers, are people happy with MadVR performance in Windows10 (or with Windows10 overall)? I am debating whether I should upgrade or not from Win7. I was a firm believer of NNEDI3, but after I recently switched to super-xbr & SuperRes I am not looking back, so I am not worried about NNEDI3 issue.

I have upgraded from Win 8.1 to Win 10 on the release day and it feels as if nothing has changed for me except the GUI. I am running AMD R9 290x so NNEDI3 is running fine. Only 'bug' I have is some of right click - context menu item on desktop does not work after switching to Microsoft account from previous local account I used to use in 8.1. MadVR and MPC-HC 1.7.9 32bit is running as usual without need to change any settings.

[aufkrawall]

I recently had some weird flickering in D3D11 windowed mode after opening a file. It did open it a second time and flickering was gone.
GTX 980@355.82 on Windows 10.
May be better to stick with D3D9 path.

[leeperry]

Madshi, please keep super-xbr-25 option, which could be useful for some not well coded videos. super-xbr-25 would be sharp enough but not overly sharped.

For Chroma upscaling, shouldn't we use a less sharper algorithm? In this case, super-xbr-25 can also be useful.

Anyone ever tried with super-xbr-25 for chroma upscaling?
Yes, fully agreed. After a truckload of testing I've settled down to sxbr25+SR for both luma and chroma because SR is very sharp to begin with and as much I'd prolly use sxbr 30-35 for luma if it was possible, I still prefer a slightly too soft picture over slightly too sharp.

[BetA13]

ok guys, im totally confused now about the nnedi3 NV drivers?!?!?!

"Whats the last/latest driver for NVida-WINDOWS 7 that has the opencl dll stuff, so that nnedi3 works correctly.."
or is this just a windows 10 problem?

im reading this thread here over and over and cant seem to find an clear statement :(

THX in advance ;) greetz

[aufkrawall]

Just Windows 10 problem. Latest driver there with that extension (not dll) is 353.49.

[BetA13]

Thanks a lot for the quick response...
So, i can upgrade without any hassle or downgrades..

*nice*

[Ver Greeneyes]

Well, that depends really. 353.49 was one of the first drivers for Windows 10, so it's entirely possible that there are problems with it in other areas. But if you want NNEDI3 in Windows 10 on an Nvidia card, it's the best we've got.

[aufkrawall]

353.49 is very stable for most users and e.g. doesn't have custom resolutions in Nvidia control panel broken, unlike every driver after it so far.
You may want to use 355.60 or newer if you suffer crashes in Witcher 3, but apart from this, there shouldn't be any problem with this particular "old" driver.

Well, of course it would be better if madshi implemented new interop that works with newest Nvidia drivers on Windows 10 and doesn't have copyback problem for AMD users.

[huhn]

there is no known error with 23p on nvidia or did i missed something huge?
i'm pretty sure my 760 was fine but my 960 is something else...

http://abload.de/img/23pdx97qkb1.png

with 10 bit it's 23.97818...
no one else have this problem right? i mean i just said some days ago that nvidia has proper 23p clocks.

maybe madVr has a proper to proper read this under windows 10?

[nevcairiel]

"Proper" 23p is not really a thing. It needs to match the audio clock to avoid any drift, so even if its perfect 23.976023976.. it could lead to drops because the audio clock is slightly different.
Watch a movie for an hour, look at drops, make your own decisions based on that.

[huhn]

i know that but 23.972 is a really big gap between the normal 23.97602 and having two different locks is totally new to me.

[Asmodian]

I get different clocks on different screens plugged into the same GPU, not much difference betwen the two I am using now, but I am used to seeing much larger changes than that even when not changing generations.

I am sure I have seen a similar 0.004Hz difference between GPUS of the same make. Also between different screens/DVI ports on my old Titans.

[Dlget]

MadVR crashing on video.
Here is crash report.
As i can remember,this video was working fine last time i checked.

[Dlget]

i tried cutting that part of video where i got crash using this (http://forum.doom9.org/showthread.php?p=1737138#post1737138) with video copy,audio copy,subtitle copy & same chapter for sharing in the forum.
Strangely no problem with that video.I copied everything.But video seems fine where as i got crash with original video.can't share original video since it's 524MB & my upload speed is not that great.

Only that part crash occur randomly.1 time it don't crash & 1 time it crash.But i noticed at that part where crash occurs strangely render queue & subtitle queue fails to fill every time.

[Serhiyko]

Starting with madVR v0.88.17, subtitles are not hidden/shown in paused mode when I disable/enable them. I have to start playing the video for subtitles to actually hide/show. In madVR v0.88.16 and before, when I set subtitles to off/on in paused mode, they were hidden/shown immediately without me having to do anything else
I use the last version of MPC-HC, if that matters

[huhn]

I get different clocks on different screens plugged into the same GPU, not much difference betwen the two I am using now, but I am used to seeing much larger changes than that even when not changing generations.

I am sure I have seen a similar 0.004Hz difference between GPUS of the same make. Also between different screens/DVI ports on my old Titans.

so this is "normal" for nvidia? never saw something extrem like this with an AMD card.

[Asmodian]

It is normal as far as I know, it is why I stopped worrying about exact refresh rates and simply use smooth motion all the time.

As you know that is madVR's detected refresh rate, setting up a custom resolution (the drivers has a section for this) allows you to tune it to whatever you want. I used to tune to eliminate any drops after two hours but I haven't bothered now that all my displays accept 120+ Hz as smooth motion is so good.

[digitech]

It is normal as far as I know, it is why I stopped worrying about exact refresh rates and simply use smooth motion all the time.

As you know that is madVR's detected refresh rate, setting up a custom resolution (the drivers has a section for this) allows you to tune it to whatever you want. I used to tune to eliminate any drops after two hours but I haven't bothered now that all my displays accept 120+ Hz as smooth motion is so good.

i have an optoma hd180 24hz compatible proyector with my nvidia 760, is madvd smooth motion still needed? does reclock have to do something with these scenario?

[Asmodian]

i have an optoma hd180 24hz compatible proyector with my nvidia 760, is madvd smooth motion still needed? does reclock have to do something with these scenario?

Do not use smooth motion if you are sending your projector a 24 Hz signal. Smooth motion doesn't work well unless your refresh rate is over double the frame rate. edit: At low refresh rates smooth motion is blurry because too many of the frames are blended frames.

Reclock allows you to avoid tuning the refresh rate to match the audio clock because it re-samples the audio to match the difference in the video's refresh rate as long as it is close. Without reclock you would want to tune your refresh rate to as close to 23.976024 Hz as possible, or if your audio clock isn't exact (it probably isn't), you want to tune it so there are no frame drops/repeats for at least two to three hours (experimental).

[James Freeman]

madshi is taking a long vacation from us ingrates...
Hope he has the motivation to continue developing this renderer, at least till it would bring some profit to him.

[apgood]

I suspect he's either too busy with paid work or a new feature to knock your socks off, because he definitely has something coming.

[Sunset1982]

so this is "normal" for nvidia? never saw something extrem like this with an AMD card.


I had an AMD R9 280 which did proper 23,976 Hz. Then I testet with same Hardware and my NVidia GTX970. NV is not as accurate as the AMD card. Same with my GTX 750

You must create a customised resolution to get it as near as possible to 23,976 Hz. With good settings you can get it near perfect, so you get a dropped frame every 3-4 hours. Let me know if you need support to create a custom resolution.

[ashlar42]

I found this useful when trying to get as close as possible to 24/1.001 refresh rate: http://www.hometheatershack.com/forums/computers-htpc-media-servers/62832-cant-hit-23-976-hz-nvidia-gts-450-panasonic-ae4000u-projector.html#post560082 not copying the values (they depend on slight clocks differences on the card) but the principles illustrated.

[madshi]

I'll reply to all "old" posts later. For now:

[madshi]

madVR v0.89.0 released

http://madshi.net/madVR.zip

* added new device "screen config" settings page
* added screen masking feature
* added support for anamorphic stretch
* added new processing "zoom control" settings page
* added automatic detection of black bars with lots of sub options
* fixed: DXVA deinterlacing sometimes produced "DXVA processing failed"
* fixed: profiles: scaling factor wasn't properly reported
* increased seek "black screen protection" to 2 seconds (formerly 1)
This is just the first version with the new "black bar detection" and "screen config" features. Still lots of related things to do, like implementing the new options which are already in the settings dialog but still grayed out, or moving OSD and subtitles into the non-masked region of the display, making device settings profileable etc etc. But I've thought I'd release a new version for you to play with, so you don't get too frustrated with the long wait for a new build... :D

The new features are not complete yet, but they should already be quite useful. Mostly for front projection users, but also for all users of screens which don't happen to be exactly 16:9. Front projection users with CIH, CIW and CIA setups should love the new features.

Feedback about the new features welcome!

(The black bar detection algorithms are much improved over the last test build, btw.)

For the next weekend I plan to look into the NNEDI3 Windows 10 problem.

[huhn]

is it still possible to get the green lines to check what it detected so i can still watch out for mis detections?

[madshi]

No, sorry, I've disabled that... :( I suppose I can add in a hack for the next build to reenable it somehow.