madVR - high quality video renderer (GPU assisted)

[ikakun]

@madshi

same as tobindac on (un)install.bat. It does not work as intended without the manual "run as admin".
Win 8.1 with the latest updates.

EDIT: it shows that madvr was (un)registered but that doesn't seem to be the case when I look at the Output Renderer Settings on both mpc-hc & potplayer.

[James Freeman]

After some testing, all I can say is wow... just... wow.
Not only everything seems faster (loading and seeking but maybe it's just a placebo) but my refresh rate and rendering time are perfectly constant during playback.

No placebo, same here.
God bless you madshi and may you prosper doing the things you love.

[JonnyRedHed]

Does this x64 build have any benefits for us Zoomplayer MAX users. Is there a zoomplayer x64 yet, or planned. Does anyone know.

[huhn]

Does this x64 build have any benefits for us Zoomplayer MAX users. Is there a zoomplayer x64 yet, or planned. Does anyone know.

you may get the best informations about that here:
http://forum.doom9.org/showthread.php?t=171323

[JonnyRedHed]

you may get the best informations about that here:
http://forum.doom9.org/showthread.php?t=171323
Ok thank you.

[bejita7]

It still requires run as admin here. Win8.1.
Same here.

[Damien147]

Got a 1920x1200 monitor and when I put a 1080p movie it downscales.:confused:

[Soukyuu]

Getting a white/cyan checkerboard pattern now and then instead of the video in windowed fullscreen (no overlay) and the mpc-hc x64 test build.
Also a crash on exiting said fullscreen mode (sent a report).

edit: There is sometimes a "fade to grey" on first subtitle line using latest xySubFilter beta x64. The screen just fades to a dark grey color while sound continues.
Disabling overlay or going fullscreen exclusive crashes on first subtitle line seemingly randomly.
Found what caused it - it's the new "Lose BTB and WTW if it improves performance" option introduced with 0.87.15.
Voting to not have it enabled by default.

x64 playback chain seems to be stable now, many thanks!

[huhn]

List of display modes: 1080p23, 1080p24, 1080p50, 1080p59, 1080p60

There was issue in the 32 bit version, v0.86.10. Madshi then do workaround and issue was gone.

I noticed that when playing 1080p24 (mkv, m2ts, ts .. full screen exclusive mode, default settings) my screen goes to 23hz. Because of this, there is a drop frames every 30-40 sec.

If I uncheck 'Present Several frames in advance "(old path), my screen stays in 24hz.

so this issue right?
http://bugs.madshi.net/view.php?id=90

that's why i asked for the OS.

[huhn]

Got a 1920x1200 monitor and when I put a 1080p movie it downscales.:confused:

could you post a OSD sreen?


is the issue something like this?

http://forum.doom9.org/showpost.php?p=1717178&postcount=28783

if yes check here: http://forum.doom9.org/showpost.php?p=1717260&postcount=28810

[BetA13]

just a quick question....
madhcctrl.exe , is it normal it shows 32bit?? or is it supposed to be 64bit?
MPCHC is 64bit....
THX..

http://abload.de/thumb/fgfgfgh6u02.jpg (http://abload.de/image.php?img=fgfgfgh6u02.jpg)

[huhn]

just a quick question....
madhcctrl.exe , is it normal it shows 32bit?? or is it supposed to be 64bit?
MPCHC is 64bit....
THX..

http://abload.de/thumb/fgfgfgh6u02.jpg (http://abload.de/image.php?img=fgfgfgh6u02.jpg)

you can use the madhcctrl.exe without any player and there is only 1 version of it so it is 32 bit. in the end it change settings in the settings.bin or registry so a 64 bit version wouldn't do anything useful.

[BetA13]

@ huhn.. THX for the info..

.----------------------------


ok, just a heads up...
with the newest 347.52 Nvidia Driver, NNEDI3 gets artefacts when ENABLED (both in image douling and upscaling) with KEPLER GPU´s...

im not shure if only kepler GPU´s are affected..

hopefully nvidia fixes that..i really really really like NNEDI3....

greetz



Yay... i just tested needi3 with the new NV Drivers, and ITS FIXED :)

Finally i can use Needi3 without artefacts..

oh, and HUGE THX to madshi for teh 64bit version of MadVR. i can confirm from first testing that theres an performance increase :) my gpu now needs less power to do more work, awesome..

[huhn]

EDIT: driver is most likely still buggy.
the nvidia 349 branch added a serious issue with nnedi3. i'm going to test this later but i think is very unlikely that this issue is fix in this version. so it's maybe not a good idea to use this version with madVR.

i can't reproduce the nnedi3 issue introduced in 349.65 anymore.

good that my prediction for this driver are totally wrong. respect nvidia that was pretty fast.

i hope cyberbeing is going to see the same effect with that driver.

[XMonarchY]

Now that madVR supports 64bit, does it mean we can use MPC-HC 64bit with it? Are there any advantages over 32bit version?

The problem with 64bit is that ReClock won't work with it... Are there any alternatives to ReClock that work with 64bit MPC-HC? I know JRiver Media Center has its own "ReClock" feature and works in 64bit, but I dislike the actual player because its too cumbersome...

I also keeping having the same issue over and over and over again... FullScreen Exclusive Mode continues to cause me to drop frames. When I turn it off, no frames are dropped. Is it something with madVR or my setup?

[Anime Viewer]

As far as my testing has gone, x64 MPC-HC (1.7.8.156) with native lav filters works perfectly fine with x64 MadVR (0.87.21). Just the later nvidia display drivers (350.05 & 350.12) crash when going into windowed fullscreen. Also causing the video player to crash or report madvr direct x initialization failure. This behavior only occurs with windowed fullscreen, exclusive fullscreen seems to function just fine.

Downgrading nvidia driver to 347.88, both windowed and exclusive fullscreen function as intended with x64 versions.

I haven't had any crashes in windowed fullscreen with nvidia drivers 350.12, MPC-HC 64-bit version 1.7.8 (6fcba1b), madVR v0.87.20, LAV 0.64.0, and XySubFilter 3.1.0.705. I'll update madVR to the newest 87.x out at the moment and see if that crashes, but I'm guessing some other setting on your system/configuration is causing the crashing.
Edit: madVR v0.87.21 (like .20) works fine for me in fullscreen windowed mode.

Now that madVR supports 64bit, does it mean we can use MPC-HC 64bit with it? Are there any advantages over 32bit version?

I also keeping having the same issue over and over and over again... FullScreen Exclusive Mode continues to cause me to drop frames. When I turn it off, no frames are dropped. Is it something with madVR or my setup?
I've been using MPC-HC 64-bit with it without any problems. I can't speak to how 64-bit MPC-HC or 64-bit madVR do things differently than their 32-bit versions, but usually 64-bit OS/programs are able to access larger amounts of memory and/or more cores than their 32-bit counterparts, and depending on coding can sometimes transmit faster because they have a wider path/more routes to transmit along than 32-bit.

I tested with FullScreen Exclusive Mode just now (again with the all 64-bit configuration), and didn't get any dropped frames on my system. Are your fullscreen exclusive and windowed settings differing in present frames in advance settings or flush settings in madVR, or are they both set identical?

[huhn]

@XMonarchY

64 bit has better decoding performance. so it can matter a lot for software decoding.

in term of madVR performance there shouldn't be any real differences.

and about your issue we need way more information that just "if i got in FSE mode i get dropped frames"

resolution? what settings what are the renderer times, FPS, and way more questions.

[huhn]

can someone with a nvidia kampler GPU try to reproduce this issue: http://bugs.madshi.net/view.php?id=250

the openCL issue discussed later in this issue.

edit: not important anymore.

[seiyafan]

It's only day night difference if the scaling factor is high, which is not the case with 1080p -> 1440p.
Jinc3 AR chroma + luma:
http://abload.de/thumb/jinc38gbdx.png (http://abload.de/image.php?img=jinc38gbdx.png)

Jinc3 AR chroma + NNEDI3 64 image doubling (CR AR LL downscaling):
http://abload.de/thumb/nnedi364bxzsa.png (http://abload.de/image.php?img=nnedi364bxzsa.png)

Thanks a lot! I will stick with Jinc for luma then. My graphic card uses 70 Watts more power if I enable NNEDI3.

[SecurityBunny]

I haven't had any crashes in windowed fullscreen with nvidia drivers 350.12, MPC-HC 64-bit version 1.7.8 (6fcba1b), madVR v0.87.20, LAV 0.64.0, and XySubFilter 3.1.0.705. I'll update madVR to the newest 87.x out at the moment and see if that crashes, but I'm guessing some other setting on your system/configuration is causing the crashing.
Edit: madVR v0.87.21 (like .20) works fine for me in fullscreen windowed mode.


Perhaps it has something to do with my graphics card architecture? Using a kepler GTX 780 classified. Also on windows 10 technical preview build 10049. But as previously stated, nvidia driver 347.88 functions fine. Just the later ones crash in windowed fullscreen.

[Anakunda]

install.bat in both madVR 0.87.20 - 21 gives me install error (failed to load madVR.ax and madVR64.ax)
Is there additional system requirement?

[Damien147]

could you post a OSD sreen?


[/url]



http://i57.tinypic.com/2s9ejac.png

[Anime Viewer]

install.bat in both madVR 0.87.20 - 21 gives me install error (failed to load madVR.ax and madVR64.ax)
Is there additional system requirement?

Did you right-click on install.bat and choose "Run as Administrator" when you ran it?

[khanmein]

As far as my testing has gone, x64 MPC-HC (1.7.8.156) with native lav filters works perfectly fine with x64 MadVR (0.87.21). Just the later nvidia display drivers (350.05 & 350.12) crash when going into windowed fullscreen. Also causing the video player to crash or report madvr direct x initialization failure. This behavior only occurs with windowed fullscreen, exclusive fullscreen seems to function just fine.

Downgrading nvidia driver to 347.88, both windowed and exclusive fullscreen function as intended with x64 versions.

latest nightly should be 152 rite? https://nightly.mpc-hc.org/ where u get 156??

x64 mpc-hc v1.7.8.152 + LAVFilters v0.64.0-51 + madVR v0.87.21 + Nvidia 350.12 + win 8.1 pro + GTX 970 working with windowed fullscreen.

now reclock 1.8.8.4 not support x64. how to enable reclock on x64??

[ryrynz]

nightly should be 152 rite? https://nightly.mpc-hc.org/ where u get 156??


Few page back.

Seems to work fine. Test build for all folks before it gets to nightly https://www.dropbox.com/s/lrmrdd2e3sgoc46/MPC-HC.1.7.8.156.x64_madVR.7z?dl=1




now reclock 1.8.8.4 not support x64. how to enable reclock on x64??

You can't.

[Anakunda]

Did you right-click on install.bat and choose "Run as Administrator" when you ran it?

Strange I run it from console with admin rights and it gives this error. Run as admin from explorer succeed.

[khanmein]

@ryrynz thanks i stick with .152 cos my fifa 15 performed quite smooth on 350.12 compare with 347.88, 347.90 & 350.05

[Hprd]

Yay... i just tested needi3 with the new NV Drivers, and ITS FIXED :)

Finally i can use Needi3 without artefacts..

It's better than before, but there's still small artefacts once and a while. Problem isn't completely solved I think...

[huhn]

http://i57.tinypic.com/2s9ejac.png

the screen says this isn't fullscreen.

what player are you using?

[iSunrise]

http://i57.tinypic.com/2s9ejac.png
Your movie is reported as 1920x1040 and your target rectangle (that is the actual output resolution of the player window) is only 1902x1030, which is lower in both width and in height, so it's perfectly fine that madVR has to downscale.

The real question is, why do you mimic fullscreen playback by using windowed playback with borders? If you would either use real fullscreen or even fullscreen exclusive and your actual monitor has 1920x1080 resolution, then you wouldn't have to downscale.

Perhaps it has something to do with my graphics card architecture? Using a kepler GTX 780 classified. Also on windows 10 technical preview build 10049. But as previously stated, nvidia driver 347.88 functions fine. Just the later ones crash in windowed fullscreen.
Windows 10 is not even RTM, so bugs are expected. Not sure if madshi already cares enough to fix it, since it's not a finalized OS. I know I wouldn't.

[Shayne]

Is there any new guides for 64 bit setup? It is nice to see this come, thankz for all u do. I have been using MPC-HC, haali, MadVR, lav video and ac3 audio. Direction, link to a 64 bit setup guide would be appreciated.

Regards

[ryrynz]

Madshi, I'm seeing some dithering on pure blacks when the trade quality option 'use DXVA chroma upscaling' is enabled when doing native DXVA decoding on my HD4000
giving some pixels what would be with the other chroma upscalers, 0,0,0 a value of 0,0,1.

Might I suggest maybe that those use DXVA chroma options are not enabled by default? Because at least on Intel graphics the chroma upscaling is god awful nearest neighbor and the visual difference is night and day.

Any chance of putting (not recommended) beside the nearest neighbor GPU setting BTW? Just so people stay clear of it if they don't know what they're doing? I do wonder if really that's even useful aside from some sort of testing.

Also using nearest neighbor doesn't result in the black dithering color change even though it likely is the same sort of process.

Is there any new guides for 64 bit setup? It is nice to see this come, thankz for all u do. I have been using MPC-HC, haali, MadVR, lav video and ac3 audio. Direction, link to a 64 bit setup guide would be appreciated.


Well the 64 bit build only just came out, so not sure why you expect there to be a guide.. but here's one for ya.

Download MPC-HC x64, Download MadVR. Install both & enjoy. PS ditch Haali. :)

[Shayne]

Well the 64 bit build only just came out, so not sure why you expect there to be a guide.. but here's one for ya.

Download MPC-HC x64, Download MadVR. Install both & enjoy. PS ditch Haali. :)

Thankz for the second line.

Regards

[Vyral]

@Shayne

I've made a complete reinstall of MPC-HC, madVR and XYSubFilter in 64bit yesterday. Here some tips to help you :
- Before deleting the previous version of madVR, be sure to backup the settings.bin and restore it in the new version ;
- MPC-HC settings are stored in the registry and shared between the 32 and 64bit version, so no problem here. However, LAVFilters settings are not saved with MPC-HC. Make a backup of your LAVFilters settings.

[sneaker_ger]

madVR also saves settings in the registry (on top of saving them in the settings.bin file).

[Damien147]

the screen says this isn't fullscreen.

what player are you using?

mpc-hc(just turned 64bit)

Your movie is reported as 1920x1040 and your target rectangle (that is the actual output resolution of the player window) is only 1902x1030, which is lower in both width and in height, so it's perfectly fine that madVR has to downscale.

The real question is, why do you mimic fullscreen playback by using windowed playback with borders? If you would either use real fullscreen or even fullscreen exclusive and your actual monitor has 1920x1080 resolution, then you wouldn't have to downscale.


Oops!I took the pic like that because image> doesn't show up in fullscreen.So I guess it's only temporary because of what you've explained,my bad.

[Anatasia]

I figured this artifact appears with chroma upscaling set to NNEDI3.

Me too, W8.1, single R9 290X and latest stable driver. Also luma upscaling with NNEDI 3 seems to make the screen a little darker in exclusive mode. I'll try the 15.3 beta driver tomorrow to see whether it's gone or not

[obieobieobie]

Symantec has told me they have removed the false positive detection of mvrSettings32.dll

[JPulowski]

Currently using NVIDIA GTX690 with 350.12 WHQL driver. The NNEDI3 artifact issue seems to be fixed for 64-bit madVR. Did not test it yet with 32-bit.

Also I have some questions:

What is the optimal way of getting maximum performance for video playback from multi-gpu/SLI cards?
Are "Use a separate device for presentation" and "Use a separate device for DXVA processing" options related with multi-gpu somehow? If not what are they exactly?

Thanks. :)

[bejita7]

Oh, looks like this issue (http://bugs.madshi.net/view.php?id=250) is fixed in 350.12 WHQL. GTX 760, madVR x64.

[huhn]

Oh, looks like this issue (http://bugs.madshi.net/view.php?id=250) is fixed in 350.12 WHQL. GTX 760, madVR x64.

the main directsompute issue is fixed. the later talked openCL issue is kind of still there. 32 bit windows user with a kampler GPU get this issue for sure.

[Virtual_ManPL]

@ madshi - Thank you very much for 64-bit version of madVR :thanks:

[DigitalLF]

INFO. if WASAPI is of use for you in x64. Use MPC-BE or PotPlayer.

[Xaurus]

Thanks madshi for x64 version, I have just tested it and it works fine.
However, without being able to use ReClock I simply cannot use it even though I gained some % increase in performance.

So my question to you is: will there be some sort of MadAudio or something in the future as a replacement for ReClock? Seeing as ReClock seems dead and buried.

[raymondjpg]

madVR v0.87.21 released

http://madshi.net/madVR.zip

* fixed: (un)install.bat now works without having to manually "run as admin"
* fixed: active display wasn't properly set in the settings (x64)
* added workaround for window subclassing crash (x64)
Although the x64 crash seems to be gone now, I'd still like to encourage media player developers to implement "IMadVRSubclassReplacement", as MPC-HC has already done (thanks kasper93).

Running v20 and v21 (un)install.bat as administrator in 32 bit Win 7 Professional gives me error:

The module "madVR64.ax" may not be compatible with the version of Windows you are running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.

Anything I need to do or just ignore?

[bcec]

Folks is it me, or the latest nVidia drivers sped up madVR NNEDI3 processing quite a bit? I saw roughly a 5-6ms processing time reduction, and I can now do NNEDI3x64 (up from x32) image doubling with my 970 for 1080p->2160p while keeping everything else the same.

[Prolesious]

Folks is it me, or the latest nVidia drivers sped up madVR NNEDI3 processing quite a bit? I saw roughly a 5-6ms processing time reduction, and I can now do NNEDI3x64 (up from x32) image doubling with my 970 for 1080p->2160p while keeping everything else the same.

Not just you. I don't have 4k, but i was able go from 720p to 1080p with nedi3x32 to nedi3x128. I thought there was something wrong going on. Like Nedi wasn't being used, but as i upped it the usage was going up (via GPU-Z)

edit: forgot to mention, an nVidia 970 as well.

edit 2: i can also now quad nedi3, so i can use, nedi3x64 double to nedi3x32 for quad. for sd to 1080. that was no way possible for me before.

edit 3: Makes me wonder what a Titan X can do, if a 970 can do this now! I'm gonna start putting a little away each pay check now so i can get a Titan X!!!!

[Anime Viewer]

The module "madVR64.ax" may not be compatible with the version of Windows you are running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.

Anything I need to do or just ignore?

Are you sure you're running a 64-bit version of Windows? That error makes it sound like you're running a 32-bit OS.

[Prolesious]

Running v20 and v21 (un)install.bat as administrator in 32 bit Win 7 Professional gives me error:

The module "madVR64.ax" may not be compatible with the version of Windows you are running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.

Anything I need to do or just ignore?

Just ignore due to the fact you are using 32 bit Windows. madVR64.ax is 64 bit which will not operate with a 32 bit OS.

[Arm3nian]

Thanks madshi for x64 version, I have just tested it and it works fine.
However, without being able to use ReClock I simply cannot use it even though I gained some % increase in performance.

So my question to you is: will there be some sort of MadAudio or something in the future as a replacement for ReClock? Seeing as ReClock seems dead and buried.

Why do you need reclock? Just use smooth motion and the MPCBE audio renderer.