madVR - high quality video renderer (GPU assisted)

[aufkrawall]

I think that shouldn't be the case.
You can go to device manager and disable and restart the driver manually there, I haven't encountered any problems with this yet.
Also, in order to get WHQL signature, driver installers must be able to stop, replace and restart a driver without having to restart Windows.
At least that's what I heard about video drivers.

[JarrettH]

Does NVIDIA list everything that has been fixed in the release notes? Seems like there are always many issues addressed not in the release notes

[madshi]

Well, FWIW, disabling and reenabling the GPU driver does make that NVidia registry tweak work without needing a reboot.

[aufkrawall]

Ok, that's an argument. :D
I couldn't try it since I just use DVI.

[Xaurus]

Oh my god this new WHQL driver is awesome, no presentation glitches with 24.94 material @ 59.97 and this with all tweak options disabled, no DX11 and without use a separate device for presentation.

edit: No glitches at all for 23.976 material nor for 25.00 @ 50.00 either.

Just awesome.

[SamuriHL]

Yup. I'm noticing the same thing on my 680. Very impressive. I'll set it up on my 450 soon.

[aufkrawall]

Yup. I'm noticing the same thing on my 680. Very impressive.
Uhm, I don't find it impressive, just the way it should be.
With a Radeon 7970 I didn't encounter this issue either.

[nevcairiel]

With a Radeon 7970 I didn't encounter this issue either.

Not this issue, but a looong list of others.
I'm still fighting with the weirdest audio dropouts right now..

Driver wise, with this issue out of the way, i would favor nvidia over amd any day (probably even before)

[madshi]

Uhm, I don't find it impressive, just the way it should be.
With a Radeon 7970 I didn't encounter this issue either.
I agree that it's now finally the way it should have been right from the start. In any case, it's a very big step forward for NVidia/madVR users. When I originally developed the "new" fullscreen exclusive mode many many months ago, I had expected (and announced) it to be the most reliable playback mode, with no frame drops, no presentation glitches, no smoothness problems whatsoever. I had even hoped to get along without any configuration options etc. But in reality, with NVidia drivers, it was less stable than the other playback modes, and required more configuration and tweaks than the other modes. Now *finally* the new fullscreen exclusive mode may finally live up to its original promise for NVidia users. I'll probably ditch all those ugly tweak options in the next madVR build. Which also means that configuration for new madVR/NVidia users will be much less painful than before. Default settings should work just fine now.

[madshi]

Here's a little tweak utility which should be able to tweak NVidia cards to output fullrange RGB without needing to create custom resolutions:

http://madshi.net/madNvLevelsTweaker.zip

When using a multi-monitor setup, just move the tweaker window to the target monitor (the tweak is per monitor) before applying the tweak. This utility is also able to undo the tweak. Furthermore it should work without needing a reboot. It does that by restarting the GPU driver. Doing that might eventually make your computer explode, or result in your socks catching fire. So USE AT YOUR OWN RISK. Of course it works fine on my PC. But then, my socks are fire-proof...

[SamuriHL]

I'm getting a 404.

[madshi]

Oopsi, please try again now.

[SamuriHL]

Excellent, thanks!

[aufkrawall]

Not this issue, but a looong list of others.

That's why I don't have the 7970 anymore (I even had three different ones and all were more or less defect by hardware too *wtf*. :angry: )

Default settings should work just fine now.
Yup, madVR definitely gives rock solid playback performance now in FSE.
With highered presented frames in advance, I can watch any kind of video without any dropped or delayed frame nor presentation glitch.

[jmone]

.... looks for a good passive (or very silent) 650. :)

What make/models look good?.... I'm no GPU expert but these seems to be similar in processing to a 550ti but with way less power consumption/heat output. I'd prefer those silent(ish) fan designs that dumps the heat out the back of the card.

[Boltron]

Guys, I was just following your comments regarding Nvidia vs. ATI. I have always used ATI and currently I run a 7770. Playback has always been pretty solid I usually get about 15 drops frames when I start a movie but then I can watch the entire movie without any noticeable glitches. The only issue I have from time to time is with music playback, I get small drop outs (some time). I use MC17, LAV and madVR in FSE. I watch 1080p/720p exclusively and mostly rip Blurays 1:1 (no compression).

So, I was just wondering why many of you favour Nvidia over ATI? I don't think PQ will be different, is there something I am missing?

[Mikey2]

EDIT: I apologize, I did not read far enough back, it looks like you definitely do know about this.

Has anyone else noticed that the new NVidia driver 306.23 contains the following? :

"Media Player Classic Home Cinema displays a black screen during playback when using the MadVR video renderer. [960463]"

Does anyone know what this means? (I obviously have not seen any issue so serious.)

LOL and congrats on Madvr being under the radar of NVidia itself. ;)

EDIT: If the issue is involved with 0-255 colorspace/BTB/WTW issues, I have been pushing 0-255 to my Pioneer Kuro without any registry fixes with my NVidia graphics card. I thought I had the issues resolved a couple years ago or so and I was displaying the correct colorspace without any "black crush." Am I incorrect? For instance, do I need to run the new "tweaker" Madshi posted a few posts back?

[Mikey2]

Does NVIDIA list everything that has been fixed in the release notes? Seems like there are always many issues addressed not in the release notes

I believe that almost everything is posted in their detailed release notes:

http://us.download.nvidia.com/Windows/306.23/306.23-win8-win7-winvista-desktop-release-notes.pdf

[agustin9]

All my problems with Amd were fixed lowering the gpu queues, I'm using 6 frames for that and for the presented frames in advance

[Pat357]

All my problems with Amd were fixed lowering the gpu queues, I'm using 6 frames for that and for the presented frames in advance

This suggests that Mad might consider leaving size of the queues as a setting for users to change in the upcoming MadVR version.

[Budtz]

Here's a little tweak utility which should be able to tweak NVidia cards to output fullrange RGB without needing to create custom resolutions:

http://madshi.net/madNvLevelsTweaker.zip

When using a multi-monitor setup, just move the tweaker window to the target monitor (the tweak is per monitor) before applying the tweak. This utility is also able to undo the tweak. Furthermore it should work without needing a reboot. It does that by restarting the GPU driver. Doing that might eventually make your computer explode, or result in your socks catching fire. So USE AT YOUR OWN RISK. Of course it works fine on my PC. But then, my socks are fire-proof...

I tried this but it seemed to make my image to dark. I have tried to tjek the image using the same place in same movie madvr vs blurayplayer. the two images seem identical and correct without this tweak? i have set madvr to pc levels and i have a samsung tv from 2011 (d6530 i think)

can madvr compensate for nvidas defualt tv-leveles setting?

[nevcairiel]

If your TV expects the video in limited range, then you obviously don't need this tweak.
You can however still use it, and afterwards set madVR to TV levels.

GPU in Limited Range/TV Mode:
- Desktop still renders at full range, GPU compresses to limited range on output
- madVR set for PC levels outputs 0-255 -> GPU compresses to 16-235 on output.

GPU in Full Range/PC Mode:
- Desktop renders at full range, GPU outputs as-is
- madVR set to PC levels leaves the GPU as PC levels
- madVR set to TV Levels, leaves the GPU as TV levels (the signal is 0-255, but madVR makes all video only use 16-235)

In case your TV needs Limited Range/TV Levels, the second option may have slightly better accuracy in the colors, at the expense of your desktop being black and white crushed.

[Budtz]

If your TV expects the video in limited range, then you obviously don't need this tweak.
You can however still use it, and afterwards set madVR to TV levels.

GPU in Limited Range/TV Mode:
- Desktop still renders at full range, GPU compresses to limited range on output
- madVR set for PC levels outputs 0-255 -> GPU compresses to 16-235 on output.

GPU in Full Range/PC Mode:
- Desktop renders at full range, GPU outputs as-is
- madVR set to PC levels leaves the GPU as PC levels
- madVR set to TV Levels, leaves the GPU as TV levels (the signal is 0-255, but madVR makes all video only use 16-235)

In case your TV needs Limited Range/TV Levels, the second option may have slightly better accuracy in the colors, at the expense of your desktop being black and white crushed.

thx for the awnser.

i think i figured out my tv has a hdmi black levels setting. so i can adjust what my tv epectrs i think. the question then is whats best? set gpu fullrange with the tweak and tv to exspecy that or go with limited?

[madshi]

Go fullrange if your TV supports it. It results in less conversions being performed, so better image quality for all desktop, games and videos. Of course if your TVs HDMI black level setting is not implemented well, things could get screwed up again. So in the end you'll have to try both solutions and trust your eyes which looks better. Try the madTestPatternSource test patterns to check if you can see a difference.

[Budtz]

kk thx.

yes the tv's blacklevel for fullrange is called normal. I guess sugetsting that the "lov" setting does some converting. anyway with the tweak enabled and black level set to normal the image looks the about the same as with no tweak and a setting of "low". the image was pretty darn good before but i guess i cant see much of a difference.

it so annoying that tv manufatcures insist on using settings names like "contrast+", "motion plus" and "black level" with a normal and low settings. such names say nothing of what the settings actually do. dint know i had the abillity to choose full or limeted untill just now becouse of this. ah well.

[Mikey2]

I just tried running the "Tweak" utility. I was on my 0-255 plasma and it went entirely blank. I had to do a hard-reset of my computer. It now displays properly; however, I notice no difference than before. (I have madVR set to 0-255 and my TV set to the same. Blacks are grey when madVR is set to 16-235.) Furthermore, when opening up the Tweaker, the "force PC levels" is still not checked.

Does this mean that the "tweak" did not take? As I mentioned before, I am not sure I needed it in the first place, but I guess it was a dumb question since no one responded. Well, I'll try again: am I ok as it stands right now?

Boy I hate colorspace issues; they have been dogging me since I first built my HTPC!

Thanks in advance for any help,
MikeY

EDIT: In conjunction with some research on this thread, is the "tweak" simply adding/setting the " SetDefaultFullRGBRangeOnHDMI " key (in My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B0823740-41FA-45D1-8D11-E547D5CED249}\0001 ) to 1? If so, mine is there and set to 1.

EDIT2: My Mistake, that value is missing for my Plasma. (I know you said the Tweaker was based on the current monitor; I have three monitors and it was sensing the wrong set of registry keys. I do NOT have this value on my plasma, which is the only one I care about. Should I add it?

Once I had this pointing to the correct key, the tweak did in fact work and the checkbox is now on (i.e. I can undo it.) I am still curious on its necessity though...

Oh and I found this link: http://forums.guru3d.com/showthread.php?p=4278943#post4278943
I assume that the first post is the custom resolution that should not be necessary with this tweak? (And the linked post is what your tweaker tool does?

I apologize that this post is pretty scattered; it is getting late and I keep finding out more as I go along.

[THX-UltraII]

Why not just change the .inf file (adding lines HKR,,SetDefaultFullRGBRangeOnHDMI,%REG_DWORD%,1?).
This is a one time procedure and no worries after that anymore.

@Madshi: can we expect a totally new madVR version soon now that NVIDIA fixed the most important thing?
Zou wel zwaar relaxt zijn! :)

[andybkma]

I can confirm that on my HTPC (NVidia 9400 mainboard) the glitches seem to be gone with all tweak options disabled, without DX11 presentation, and even without "use a separate device for presentation". So this looks reaaaaally promising!

madshi, tested "Use a seperate device for presentation" CHECKED on my Optimus Ivy Bridge/Nvidia 640M-LE video card laptop with the new Nvidia 306.23 drivers and I still have the same problem as before I upgraded the video card drivers in that the playing video will pause by itself in FSE and then try to catch up when I go back to Window mode. This problem occurs when I use Zoom Player and/or Pot Player with my Nvidia card (Run with graphics processor ---> High performance Nvidia processor) instead of the default on-board Intel 4000 Graphics. (Note: that "Use a seperate device... " option checked works fine when I use Zoom Player/Pot Player with the default on-board Intel Graphics so it's definitely an Nvidia problem because it only happens when I use the media player with Nvidia graphics)

So before you decide to remove that option please don't as us Optimus users seem still need that "Use a seperate device for presentation" option....

Cheers

[madshi]

Ok, 6 months worth of replies, part I:

Well the problem is not as bad as I initially thought. The only difference is that when I seek or fast-forward there is a small pause before movie playback resumes. I am using LAV software decoding on a 4,5ghz quad core processor. Before 0.82.5 seeking was instantaneous.
Have you tried disabling the "delay playback start until queues are full" (or whatever the exact name was) option? Does that "fix" the problem?

Hey madshi, do you think the "queue output samples" in ffdshow would have an impact on madvr's performance? I remember the feature has been in there for a long time. I disabled it recently just in case.
I've no idea.

Is there a preferred tool to cut samples from h264 interlaced? I tried DGAVCIndex but after demuxing I get an unplayable .264 file
You could mux to TS and then use TsSplitter. Or you could mux to MKV and then use mkvtoolnix. Not sure, maybe there are better alternatives than these...

Is it possible to make a madvr where you leave the whole scaling part on the shaders away and leave that to the hardware but keep the rest ;) ?
For Intel user that would be much much more efficient i guess having not the massive GPU overhead from the Shader Scaling part Especially on the less powerful Intel HD Graphics GT1 and leaving the scaling to the Driver and Egurs Hardware Asic Lanczos4 (Luma/Chroma) implementation :)
It's on my to do list.

No, not really :D
Right after boot-up I launched MPC/MadVR : this way the dbghelp from the Madvr dir became loaded.
If I launch Process explorer then, I think that Windows will not load the dbghelp from the OS but rather use the one that's already in memory.
I don't think that's how things work. The processes are supposed to be totally separate from each other. If madVR is loading the dbghelp from directory A, ProcessExplorer can still load it from any other directory without any problems. Anyway, it should be no problem if you replace madVR's dbghelp.dll file with a newer one. Just make sure you really use a *newer* one.

madshi, here is the sample from the silent film blu-ray: http://www.mediafire.com/?tsydibjadsd8zs8

I'm willing to guess that the end framerate after IVTC is still >24fps, hence the framedrops in 24Hz mode. The combing without IVTC isn't as pronounced as interlaced DVDs, I actually didn't notice it as first... but madvr seems to get rid of it completely
Unfortunately the file got deleted in the meanwhile. I'm sorry, it's my fault for being absent for so long. If you still have the sample, could you re-upload?

Hello everybody,

I am used to change the framerate of my 25fps movie to 23.976 with eac3to and mkvmerge but the "ctrl+j" menu of madvr still says they are 25fps movie.

I checked with mediainfo that tells me they are, as expected, 23.976fps movies.

Do you know what I could change to make madvr understand it is now a 23.976fps movie ? because when it misunderstands framerate, the info about "one frame drop every x minutes" is false, etc.

Do I need to retag my movies ? how ? Why media info tells me the good framerate and madvr is not ?

Thank you so much ;)
That could have different causes. madVR shows what the decoder is reporting. So it could be a bug in the splitter or in the decoder. Which splitter/decoder are you using?

madshi,
I'd like to report a few problems with madVR I had since yesterday when I installed my new projector (EPSON TW9000 / 6010 in the US) which supports 3D.
First let me say that I'm truly amazed by the looks of bright 3D. I hate my local cinemas which don't want to invest in new projectors/lamps and simply ruin the pleasure with such dim presentation. I also hate the "authorities" (SMPTE) that agreed that the minimum standard for 3D in theaters should be 4.5 ft-lamberts, while the minimum for 2D is 12 ft-lamberts (recommended 16 ft-lamberts). That's enough hate for the moment - I will simply enjoy my bright 3D home cinema from now on ;)
Now let me share my problems.
Everything started with the stupid limitation of NVidia that I can't have 3D (frame packing) on my secondary monitor - it only works on the primary. I lost a few hours searching the internet why I can't make my new projector run in 3D mode until a friend of mine told me that for him it only works when the 3D HDMI 1.4 display is the primary monitor. Does anybody know if ATI/AMD has the same limitation? Since my PC serves me both as HTPC and a workstation I'd like to continue using my LCD monitor as primary device and have the projector as secondary. This lead to problem 1:
After I watched a 3D movie with TMT I decided to switch back to my default profile (the PJ as secondary) and watch a 2D movie. I did so using UltraMon (if I remember correctly - it was last night and I had guests so I left the report for today - only managed to make a log file) and fired up Zoom Player on the secondary monitor and started the playback. Strangely all I got was audio and a black screen. At the same time the primary monitor was blinking like crazy. I did restart the player but it didn't help. I also tried changing the refresh rate / mode of the secondary display but it didn't help. I then changed the renderer to EVR and it worked just fine, so I was pretty sure it was a problem in madVR. I made a log ("madVR - log - blinking primary and black secondary.txt" - in the archive bellow) and I hope you'll be able to see problem. The only think that helped was a full restart of the PC. :(

Today I watched more 3D and out of curiosity I decided to test how will madVR behave in this "HD 3D" mode as NVidia call it. So here comes problem 2:
madVR shows a black screen and hangs the player when I try to seek. I've made both a debug log ("madVR - log - black screen + freeze on seek.txt") and freeze report which are also in the archive below.
In this "HD3D" mode EVR is showing images only for the right eye, with the left I see only a black screen.
I've tested the playback both in Zoom Player and MPC-HC and they behave exactly the same.
The Windows' desktop and player UI are OK ... except the right click popup menu in Firefox which behaves the same as the video window - black with the left eye and OK with the right ... also the UI of the ArcSoft's TMT 5 is visible only with the right eye ... but only until I start the movie.
To avoid "problem 1" I decided to change the display mode manually using NVIDIA Control Panel but left the projector as primary - didn't want to go to the PC at that moment. I did change it to a normal 1080p50 mode and the projector changed to 2D mode accordingly. I confirmed the changed and closed the control panel. So far so good. I started Zoom Player again and selected a recording of the today's F1 Australian Grand Prix and all of sudden both the NVIDIA and the projector were back to 3D HD mode !?!?!? How is this possible? What did madVR do to trigger it ?!?!? I'm not sure it's madVR's fault but let's call this "problem 3" for now.
This behavior made me remember something that I read in the notes when I finished the 3D Stereoscopic setup I did yesterday in the NVIDIA Control Panel. I think I saw something similar saying that the next time a player requests 3D mode it will lauch automatically and I don't have to switch manually from the NVidia Control Panel. This sounded nice but the question is "how is madVR requesting this special 3D mode".

Does anybody else have similar issues/experience with NVIDIA, a 3D HDMI 1.4 display/projector and madVR?

Here is the link for the log/freeze report files
http://www.mediafire.com/download.php?2u2niae9xzqgdub
The key problem is the reading VSync scanline information doesn't work properly, anymore. This is clearly a bug in the NVidia drivers. Nothing I can do about it.

What is wrong with the "BT.709/601 curve" for gamma processing?
Nothing. If it looks better to you, you can use it. If your display is not perfectly calibrated, trying different gamma curves/values could help improving the image. If your display is perfectly calibrated, then using the power curves might be the more mathematically correct option. But it's still a matter of taste. The BT.709/601 curve simply has a different look to it.

Hi, I got a hang just now seeking in a bdmv. mpc-hc was still responsive, audio continued for a few minutes in the background, just the image froze. Also double clicking on the mpc-hc window to resize to fullscreen, I can see the image doesn't fill the screen so madVR isn't completing the resize to the full width of the screen while in this state.

http://pastebin.com/GTyQ9sAg

I'm using mpc-hc 4164, madVR v0.82.5, LAV from here http://files.1f0.de/lavf/LAVFilters-0.49-41-gd935c59.zip

Apologies if it has nothing to with madVR.
From a quick check I can see nothing wrong. It doesn't seem like a typical freeze, more like a state of not-working. In such cases a debug log helps more than a freeze report. I'm aware of that it's difficult to know for you which is needed in which situation. So if you have the chance, having both is always a good idea, just to be safe. Of course with non-reproduceable freeze, there's no chance for you to provide a debug log. In that case creating a freeze report can still be very helpful. Just not in this case, unfortunately.

madshi, would it be possible to separate start of file delay and seek delay option?
I'm not sure. I always have to consider whether adding a new option is worth it. I understand why you want to have that option. But on the negative side, every new option makes the settings dialog more complicated and more difficult to understand for new users. So I'm not really sure I should add this option or not. I think I'll not add it for now. Maybe later. When madVR has reached v1.0, I might have to reorganize all the settings to make everything nicely sorted etc. Maybe then I'll find a way to add options like this without confusing new users...

But now I was given information that it seems means I am not really using Madvr at all.

"the dxva native option wont work with madvr"
dxva is the only option that runs smoothly with my hd2600 pro.

So is that true? Am I not really getting any benefits?
Thanks
madVR currently does not support DXVA decoding. However, using the latest LAV Video Decoder version, you can still use DXVA decoding with madVR, because LAV finds a way around the madVR limitation. It comes at a certain performance cost, though. So you'll have to try if it runs fast enough on your PC or not.

Feature request: an option to disable the global hotkeys.

I know you have them enabled because there are situations in which the player is not the active window for some kind of reason. I've also read that you have vague plans to make the hotkeys configurable sometime. I'd ask you to add an option to at least disable them completely. I don't use them -- at all! Don't have to, maybe never will.However, I'm programming in Emacs at the same time, and Ctrl-R and Ctrl-J are both often used keys that I simply cannot use while madVR is running.
The problem is I don't have any place in the settings dialog where I could place such an option. I'd have to create a new section. And once I do that I can also go ahead and implement the customized keyboard shortcuts. So let me just up the priority on customizing keyboard shortcuts. Shouldn't take too long now...

Is there a difference in using madvr built in h.264 decoder or using lav decoder or ffdshow performance wise and IQ?
Nev is regularly updating to the latest ffmpeg/libav version. I'm slower with that. So there's a chance LAV might be slightly faster than the madVR built in decoders. I don't expect there to be a big difference, though. And if there is, it should go away once I update to the latest ffmpeg/libav version myself.

IQ should be the same.

I am using mpchc x86 + hali media splitter + lav video x86 + madvr. Should I set LAV video configuration to use hardware decoder NVIDIA CUVID? It's set to NONE at the moment. Everything works fine.
Using NVIDIA CUVID or DXVA moves decoding from CPU to GPU. Whether that makes sense depends on which of those 2 is the bottleneck on your PC. Personally, I prefer software decoding, because it's been more stable and reliable in my experience. But then, if your CPU is a bit slow, or if you want to do e.g. AviSynth processing, moving the decoding to the GPU might make sense. I'd say just try both and use what works better for you. If both your CPU and GPU are equally fast, you'll probably not notice a difference either way.

[madshi]

Pardon me if this has been asked before, but is there any difference, all other things being equal, between madvr and evr custom pres when playing 1080p on a 1080p display? I take it madvr has better scaling etc but is any scaling actually done in this case? What about a resolution such as 1920x800? Does that need to be scaled?
Chroma always needs to be upscaled, and there madVR should have an advantage. Also, madVR's color conversion (YCbCr -> RGB) should be more exact than what EVR is doing. Furthermore, madVR also applies dithering, not sure if EVR is doing that. Finally, madVR also has a different presentation logic compared to EVR, resulting in smoother motion in certain situations. I'd say, just try them out yourself and check if you can see a difference. Don't just compare screenshots, though, also check for motion smoothness (over the runtime of a full movie) and check for seeking behaviour etc.

I often watch videos when my monitor is in a vertical orientation (1200x1600) out of laziness, but I noticed that under these circumstances together with the LAV filters, madVR dies horribly.
Yes, madVR currently does not support vertical orientation. I'll put this on my to do list, but it doesn't have the highest priority right now.

So I finally decided to try a GTS 450 to use Cuvid instead of my HD2600 Pro with DXVA Native.
Well, first impression yesterday was not very good. It was smooth (which it was already with my previous one) but like it lacked a lot of punch to the image. I thought it was a matter of PC vs tv settings but did not look like it.
Then I started to think the problem was my contrast and brightness settings were somehow incorrect for this card...no idea why.
So I tweaked those and it started to look better..and details looks more refined (maybe I am using the sharpening in the nvidia settings)
Although in reality, changed to video playback section did nothing only the ones for desktop (the color vibration thing) worked.
So any settings I might be missing? I tried the ones in madvr changing from 0-255 to 16-235 and I can see the change there.
NVidia drivers default to outputting 16-235 when outputting via HDMI. You can fix that by either creating custom resolutions or by using the madNvNVidiaLevelsTweaker (link see a couple posts above).

Here is a sample TS file (http://www.mediafire.com/?cd8jxvr8m66ta15) that contains a mixture of progressive (1080p/25) and interlaced (1080i/25) video. EVR correctly shows the progressive parts (00:00 - 00:16) as 1080p/25 and deinterlaces the interlaced parts (00:17 - 00:44) to 1080p/50. However, MadVR just treats the whole file as progressive and plays it all at 1080p/25, therefore the interlaced parts show combing.
Thanks, I'll have a look at this.

Has anyone been playing around with this option? I had it enabled until last night when I kept getting stuttering on certain scenes from a progressive PAL DVD. Turns out disabling it actually fixed the problem. The sequences it happened on seemed rather normal, with IVTC off there seemed to be no problem, but with IVTC on it would detect 'unknown cadence' and stutter. Is there any reason why it would behave this way if it were only looking at the center of the frame? Also, for those of you who use madvr to watch DVDs as well, do you have IVTC forced on even when the DVD is progressive? Would there theoretically be any adverse affects doing so?
Can I have a sample, please?

The problem can occur if there's a cadence break and there's not enough motion in the middle of the screen for madVR to find the new cadence. When watching the full screen, of course there's more information to look at.

So here's a possibly one of a kind feature I'm trying to cook up. not really sure if this is the part of the path to put it though. Here's the deal:

Texas Instruments DLP sets use a wobulation mirror to turn their half-res DLP chip's image into a full 1920x1080 image. This, in effect, is sort of a modified interlacing, where every other pixel (in a checkerboard pattern) is displayed every 120th of a second. What I'm thinking, is that this would allow for perfectly smooth 24Hz playback, without changing video mode from 1920x1080p60, if properly rendered into this checkerboard pattern. It would make sense to be done at the GPU level (simple for a pixel shader to handle). Expand the video up to 120Hz, then merge every frame pair down with a checkerboard mask (top left pixel is displayed first).
Interesting idea. But since I don't have such a DLP, I have no way to test if it would actually work ok. Developing such a solution without being able to test it doesn't sound very attractive to me, and since those DLPs are really very much outdated today, I don't think it's worth the time for me, I'm sorry. There are so many important things I still need to do for displays/projectors which are up-to-date.

I have a LG LCD (LED Full Array) set which I have calibrated for both color (has yCMS adjustments) and grey scale with a colorimeter and ColorHCFR software. I am not an expert at this but I have done it a few times following a good guide and I am quite happy with the results.
You say you have calibrated it. How? Did you use the display controls to do the calibration? Or did you use yCMS? If you calibrated the display by using the display controls then in the madVR settings you should set it to "this display is already calibrated".

3) Devices > Color & Gamma
Do I enable Gamma Processing?
Depends on whether you watch in the same lighting conditions all the time or not. If you watch in sunlight or with room lights on, using e.g. a pure power curve of 2.20 might make sense. And that's probably what you calibrated your display to? However, if you watch at night with all lights turned off, going to a gamma curve of maybe 2.35 might make sense. So if you want to switch between different gamma values to adjust for different lighting situations, turn gamma processing on. Otherwise turn it off.

mpc-hc 1.6.2.4902, lav .50.5, madvr 82.5. Win7(64) GT450, amd athlon II x2 250, 3G. 8G memory

I can start to play a dvd, vob folder but if I try to seek or pause, mpc-hc hangs and becomes unresponsive. The seek or pause never happens. This is only using madvr. If I switch to evr it's good. 720x480 movies.
Not sure what's happening there. DVD playback is not officially supported by madVR yet. Could be caused by the splitter or decoder or by bad "team-work" between all filters. Or it could very well be a madVR bug. Maybe I can see more if you create a madVR debug log. Alternatively you could also try different splitters and/or decoders. Also make sure you update to the latest LAV version, just to be safe.

I did that. It was on PC levels as it should. Switching to the other just makes all files wrong, and makes the test file worse.
Since then I've been tinkering with settings but nothing seems to work. Switched between driver versions also. (for gts450 BTW) Its the same with both PotPlayer and MPC-HC.
I tried resetting the settings with botha "restore default settings.bat" and manually by searching for madvr in the registry but even that didn't work. The settings didn't get reset to default.
Do you still have these problems? If so, can you sum them up again for me? Your reports are so spread over this thread that I lost overview.

means that decoder performs vertical chroma upsampling probably using NN (nearest neighbor) algorithm. Than EVR makes the same in horizontal direction, using the same algorithm, than shader fixes (smooths) the result.
MadVR does the same (chroma upsampling in horizontal direction), but using better (selected) algorithm, but it can't fix what decoder have done.

So, you just need to make decoder to output video without chroma upsampling (in YV12/NV12 format).
Very good analyzation of the problem!

Is there a way to disable the "Windowed" and "Exclusive" OSD message when switching from them?
Not at the moment. It's on my to do list.

For those looking for a sharpener you might want to try FineSharp (http://forum.doom9.org/showthread.php?p=1569035#post1569035) It's the best I've used but ffdshow is required.
Looks really good!

Madshi, is there any chance of adding negative 'b' values for bicubicresize?
Oh well, I'm afraid of making things too complicated. Yeah, it would be nice if the cubic parameters could be manually edited. But already right now this thread is flooded with questions like "which scaling algorithm should I use"? Can you imagine the questions if I allow to separate numeric options which cover everything from SoftCubic to Mitchell to Catmull to Bicubic etc? I'm open to the general idea, but I'm not sure how to do it in the best way for all users (noobs and experts).

Madshi, I know you weren't particularly interested in cosmetics at this stage, but the "minimized" window from MPC that occasionally springs up before playing the next file is the only thing that's affecting otherwise perfect playback.
I hope you can patch that up in your next cycle.
Please let's look at this later.

Is there any plan to make translations of the Madvr release?
Probably at some time in the future, but not soon.

what would you say about forcing the tightest NT timer resolution using NtSetTimerResolution()?
Good idea, will look into it. Thanks!

Is there a *quick* way to enable/disable fullscreen exclusive mode?
Not at the moment.

When using the main monitor, I don't need FSE mode, when using the TV, I do.
Makes sense. Maybe I should use the setting to the devices section, so you can set it per monitor? But then, probably nobody is going to look for that setting there! Hmmmm... Difficult...

[madshi]

However, I dont't want to set my TV to 0-255 as I have both a BD player and Cable box going through my AVR in addition to my HTPC and they want 16-235. There's no easy way to switch the TV to 0-255 just for my HTPC.
Ouch, that's painful.

So assuming that my TV is 16-235 here's what I've found using LAV, madVR, ATI 5570.

The Dynamic Range setting in ATI's CCC does nothing. No matter the setting there is no difference. Is this a bug or expected?
That's as expected.

However, ATI's Pixel Format does make a difference.

If madVR is set to 0-255:
-Pixel Format to RGB Studio I get good levels both black and white.
-Pixel Format to RGB Full I get good white levels but bluck crush which is no good.

If madVR is set to 16-235:
-Pixel Format to RGB Studio I get WTW and BTB which is no good.
-Pixel Format to RGB Full I get WTW but black levels are good.

So, my primary question is which is better:

1. madVR 0-255 with RGB Studio or
2. madVR 16-235 with RGB Full and WTW showing.
If you only care about videos looking correct, and if it doesn't matter to you whether the desktop or games look correct, then I'd recommend to set the Pixel Format to RGB Full and to set madVR to 16-235. This should produce correct results. You should *not* see WTW. Not sure why you do. Maybe your TV's brightness/contrast setting is not set correctly? But that should also affect your hardware Blu-Ray player and your Cable Box then.

After messing around with madVR for a while, I realized that it ruined the colors!

I have a Philips TV that causes many issues but one that I recently noticed was that once madVR goes into exclusive mode, the resolution turns to an HDTV resolution instead of a PC resolution and as a result, the colors get washed out.
This is not really madVR's fault, but the only big NVidia driver problem left for HTPC users. You can work around it by applying the PC levels tweak (see a few posts above).

Speaking of avisynth, is there any chance madvr supporting pre and post resize avisynth scripts?
No, because avisynth scripts run on the CPU and madVR does most of its processing on the GPU. However, I do plan to allow custom pixel shader scripts sooner or later, and it might be possible to achieve similar things to those avisynth scripts that way.

Those months go by quickly Madshi :)
Yes, they do, especially if I take half a year madVR development pause... :o

madshi, could you please add an option to set more specific anti-ringing conditions? For example, the resolution of my display is 1366x768, and the anti-ringing algorithm works perfect when I watch SD videos with Lanczos upscaling. But when I watch a 1280x720 video, the ringing produced by lanczos3/4 is too few to be noticeable, so I prefer not applying anti-ringing in this case to save my GPU resources(on my iGPU, when anti-ringing is enabled, the rendering time increases significantly when input resolution increases, about ~34ms for 1280x720, so frame drops for 30fps videos). This can be done by adding an option to set the resolution enlargement factor for anti-ringing condition, say, enable anti-ringing when rendering_resolution / input_resolution >= 1.5, and disable it when rendering_resolution / input_resolution < 1.5.
I have on my to do list to allow things like that, but in a more global way, for all settings. E.g. to allow you to choose totally different scaling settings for SD and HD videos etc. But I can't say right now when I'll find time to implement that...

BTW I always wanted to ask but forgetting every time. If I encode 720x480 h264 video with 32:27 SAR and will play it (LAV splitter used and it is set to take SAR from stream, not DAR from container). Why madVR scales this video to 1919x1080? Looks like rounding issue somewhere...
Can I have a sample, please?

According to madvr status the queues are constantly full except for render queue which goes down 1 for a second about every 20 seconds.
And the decoder queue is full at the same time? If so, that suggests that your GPU is not fast enough to render the frames. Try setting your GPU clocks to a fixed clock. It was reported before that dynamic GPU clocking can sometimes result in problems like this. E.g. imagine the GPU driver thinks the clock doesn't need to be that high. So it clocks the GPU down. Then the render queue gets empty, and the GPU driver clocks up again. Ouch.

I am having problem deinterlacing MBAFF with LAV Filter (w/o software deinterlacing) and madVR, both latest problem. Is there anything I should set?
What problems do you have exactly? In the madVR debug OSD (Ctrl+J), is deinterlacing reported on or off? If it's off, try forcing it on by pressing Ctrl+Shift+Alt+D multiple times. Does that fix the problem?

1- I watch a lot of Vob of music videos and often old videos are 4/3 and boxed, before with ffdshow I use to use a script called LameAutoCrop which automatically crop the black border so that I can watch the clip in full screen and don't have to zoom each time. Is there anyway you can add this option ? or a way to adopt it ?
I think you should still be able to use ffdshow in the same way you used it before.

2- problem is that I can not take screenshot in MPC-HC when I use madvr :( i have to switch to other output option in MPC to do so. are you planning to add this option in future ?
It's on my to do list.

I have a question with regards to the color correction built into madVR. My monitor is calibrated using an X-Rite ColorMunki Photo, using a LUT together with a v4 ICC profile. If I setup my monitor in madVR so that it's set to "this display is already calibrated", will it use the ICC profile assigned to my monitor? Or do I somehow need to convert my ICC profile to a 3DLUT file? The LUT itself should already be loaded into my GPU.
To be honest, I don't know how ICC profiles and LUTs loaded in the GPU behave with madVR. Does anybody else know?

Oh, and should I "enable gamma processing" on the color & gamma tab? Would it do anything if it's set to the same gamma as my ICC profile (2.20)?
Enabling should do nothing if the chosen curve type and gamma value matches the values in the "calibration" tab. You can enable it to modify the gamma curve or values, if that's what you want.

wouldn't it be much faster to preserve the source pixels?
No, it would actually be slower, due to the way pixel shaders work.

Now 692x448 with 103:86 SAR results 1920x1058 resolution, while it should be 1920x1038 (20px error seriously? Oo)
Sample, please?

My HTPC (Radeon 6570) is connected to onkyo avr with hdmi and then to tv(panasonic vt30) with hdmi as well. I have been using full rgb pixel format and mpc-hc with madvr set to 16-235
Sounds correct to me.

I have calibrated my tv using htpc pattern generator and greyscale ramp in it looks like the one from avs hd calibration disc when I play it in mpc-hc which is not perfectly smooth. I have noticed that when I change pixel format to ycbcr 4 2 2 the ramp in htpc pattern generator becomes smooth but thin vertical lines are still there in mpc-hc. Am I doing sth wrong or is it just impossible to have it completely smooth in mpc-hc? Thanks in advance.
Can you make screenshots? The ramps in calibration discs are often made so that there are many pixels with the same color. Such a pattern can't be perfectly smooth. Please try the madTestPatternSource "smallramp.ytp" test pattern and scale it up to fullscreen. If you get that perfectly smooth, you should be safe.

YCbCr 422 is not the ideal solution. However, there are certain receivers and certain displays which behave better with some color spaces than with others. So it's possible that your receiver or your display can't handle RGB input so well. In that case doing YCbCr 422 might be better. But I'd first try really hard to get RGB working cause it should be the best solution (except if your receiver or display is buggy).

I have a question about yCMS in madVR:
How can we move to a target SMPTE-C while the concervant yCMS, the two can not be checked ??
I'm not sure what you mean. Can you clarify?

Under scaling algorithms, spline 4 taps is the best for image quality?
There is no "best". It depends on test and also on the source material. Just try which looks best to your eyes.

I've read that panasonic vt30 doesn't have full 4 4 4 reproduction but it subsamples it, so the question is should I still use 4 4 4 pixel format or ycbcr 4 2 2 with madvr?
I can't really say. You'll have to try and trust your eyes.

I don't know if Madshi is still working on MadVR (been a while since any updates?). But was wondering what he and others thought of this.

http://darbeevision.com/
http://www.avsforum.com/t/1410383/darbee-darblet
http://darbeevision.com/assets/documents/DarbeeVision%20Whitepaper%20with%20Tech%20Details%2020120415.pdf
From the screenshots I have to say I don't like the look too much. It has the typical "sharpened" look. I prefer Didée's new "FineSharpen" avisynth script. Looks better to my eyes.

I just noticed I have a madVR - crash report.txt (http://www.mediafire.com/?x7d12g24a0vgik6) file on my desktop, so I thought I should send it to the developer. :rolleyes:
Thanks, will have a look.

[madshi]

Ive been trying out the display changer on my new laptop and new tv and it has worked pretty well so far. Im using 1080p23, 1080p25, 1080p50, 1080p59.
1080p23 and 1080p59 run a bit smoother than p24 and p60 respectively. and also the automatic detection of 25 and 50 fps seems to work flawlessly, in case of some sources which are identified with a movie fps of 25.000 by madvr, the TV refresh rate is automatically set to 50fps, because they stutter all the time at 25fps while running completely smoothly at 50. others are kept at 25fps, all smooth as well.

there has only been one exception so far. had a BD movie with a movie fps of 29.97 which also needs a bit of deinterlacing which madvr doesnt recognize correcly by its automatic settings.
when I then add 1080p29, 1080p30 (or other way round) to the display changer line, then it wont run smooth in both cases. when I remember correctly, playback stutters even more with p29 even though its a tiny bit closer to 29.97fps than setting p30. p30 plays somewhat okish, but beings to drop A LOT OF frames when I activate madvr deinterlacing. but when I (let madvr) set the refresh rate to 59p or 60p instead and then activate deinterlacing, its running perfectly fine without dropping and stuttering.

so Im basically wondering why playback stutters with p29/p30, either by default or by activating deinterlacing. and why madvr unfortunately in this case seems to be unable to figure out the preferred refresh rate of p59/p60 so that I have to delete p29/p30 from the list of resolutions because otherwise I'd have to change it to p59/p60 manually for that movie.
There is very very *VERY* few content which is truely 29p/30p. Most content is really 59i/60i, which after proper deinterlacing either becomes 23p/24p (native movie content) or 59p/60p (native video content). I would suggest to remove 1080p29 and 1080p30 from the list of modes.

It seems you are working on scaling algorithms these days. The anti-ringing filter option is really impressive (especially for Lanczos). I think this is the right time to make a suggestion for an optional method of chroma upscaling/ resampling. Although I don’t have a technical background in this area and my understanding of image scaling is also limited, yet I think I can suggest you a way of upscaling chroma in linear light. I am not sure if this is worth the effort, but I think I should express what I have in my mind.

If I understood correctly, the issue which prevents you from providing the option of chroma upscaling in linear light is that you need to convert Y’CbCr image to R’G’B’ before you can scale the image in linear light, and to do that conversion you need both chroma and luma information for the full resolution. That’s why you have to upscale chroma in the first step and you can’t do that in linear light. I think there is a way to deal with this issue.

I will take the example of a Blu ray content which has chroma information for 960x540 resolution and luma information for 1920x1080 resolution.

Step 1: Consider only the luma information from the content and use that to create a black-and-white image of resolution 1920x1080. Do the conversion to R’G’B’ and downscale this black-and-white image in linear light to 960x540 resolution (which is the resolution of the available chroma in the original content). Convert this downscaled image back to Y’CbCr (actually Y’ only).

Step 2: Combine the chroma information of the original content with the luma information of this downscaled (in linear light) black-and-white image to create a color image of resolution 960x540 in Y’CbCr.

Step 3: For the above color image of 960x540, do the conversion from Y’CbCr to R’G’B’ and upscale in linear light to 1920x1080 resolution. Convert this upscaled image to Y’CbCr.

Step 4: Consider only the chroma information from the above upscaled (in linear light) image and combine it with the luma information of the *original* content. In this way you will get a Y’CbCr image which has both chroma and luma information for the full resolution, and the chroma has been scaled in linear light.
Interesting idea. However, from my experiments with linear light luma upscaling I've found that for *up*scaling, using linear light doesn't seem to bring much - if any - benefit. I have some other ideas about chroma upsampling which I think would result in much more noticeable improvements, but that's will have to wait a while. Anyway, I don't think going to such lengths to upsample chroma in linear light is worth it. The possible benefit is just too low (if there at all).

By the way, there is one issue with madVR which you might be aware of. MPC-HC crashes when I open any still image using madVR as a renderer. I have attached a crash report here. It looks like madVR doesn’t support viewing of still images. I was wondering if that be ever supported.
It seems to working just fine here. Which splitter/"decoder" is used on your PC to display images?

Hi, new here. One question. Do i have to calibrate my display (using Windows 7 internal calibration) for my Samsung P2250 monitor in order to get better colours ? I tried it but it seemed to me the model pictures are the same as the ones after i shoul calibrate (no noticeable differences in colour/brightnes/gamma).
I don't know anything about what the win7 internal calibration does and whether it affects madVR playback.

Alright, I think I have an (odd?) bug report here (using 0.82.5). I'm not entirely sure it's a bug on madvr's end tbh, but oh well, here we go.
Basically, it seems that madvr will always read rgb32 from vsfilter and xyvsfilter as if it was tv range rgb32, whereas I'm quite positive it always overlays as 0-255 rgb.
As far as I know, madvr assumes pc range rgb if it isn't sure about the rgb range, which means that if it's reading it as tv range, there's something in vsfilter's output that makes madvr think it's tv range.
This is further confirmed, as if I try to send rgb32 directly from lav or ffdshow, it correctly reads it. I tried sending both 16-235 rgb and 0-255 rgb from lav, and it works correctly in both cases.
However, if there's vsfilter or xyvsfilter in between, it's going to always read it as 16-235.
As a further check I tried to have lav send 16-235 rgb data to vsfilter and then have madvr render. It turns out that the video itself is rendered correctly, but the overlayed subtitles are stretched in range and don't match the video's colours.
I have typeset the subtitles on 0-255 rgb32 in aegisub with colourpicking to make sure I got the right colours.
If I get lav to send 0-255 rgb to xyvsfilter, both video and subtitles get stretched from 16-235 to 0-255, but the colours do match.
Using evr cp or haali, I get the video displayed correctly (this is to be expected, as they always assume 0-255 rgb in input).

As I said, I doubt it's a bug with madvr, as I tested that, when reading rgb32 directly from lav, it gets it right in both tv and pc range cases. But as far as I know, if madvr isn't sure of the range, it's going to assume pc range rgb, which means it's sure vsfilter's output is 16-235, which I'd like it not to do, since I'm positive vsfilter will always overlay 0-255 even with 16-235 input (as the 16-235 rgb32 from lav -> vsfilter -> madvr test showed to me).
So we're talking about a native RGB video here? Can you send me a sample?

I havent followed all this stuff for a while, is it actually possible to watch a 3D blu-ray (iso, if needed) with madvr
Not in 3D, no.

Hello I have a .icm profile that came with my monitor and I have implemented the values according to the guide at: http://files.nyaa.eu/HOW_DID_I_PLAYED_BACK.txt

Basically it says

18. Color management using yCMS is always recommended, but it is only required if you use a wide gamut display.
This is done by selecting "calibrate this display by using yCMS" under "devices" -> [Display] -> "calibration" and
filling out at least the "primaries / gamut measurements" table on the "yCMS" tab.
If you do not have any suitable hardware, but you do have a proper ICC profile, you can acquire at least the XYZ values
for red, green, blue, and white point by using an application such as ICC Profile Inspector
- http://www.color.org/profileinspector.xalter - and double-clicking on rXYZ, gXYZ, bXYZ, and wtpt, respectively.
Change the format from Yxy to XYZ and fill out as appropriate. Click on "save".

Does this look correct?

Also since it is already set as the color profile in the color management does madvr still require this?
To be honest, I don't really know. I'm not sure if the color profile is still "active" if you play a video with madVR. You can probably double check that by creating a dummy color profile with grossly incorrect values. That way you should be easily able to see if the profile is still active or not.

Hello Guys, I have a problem and I would like to know if I am the only one or if you can help me.. I'm using the last build of MADVR but sometimes during a movie in HD (play via MPC-HC) i have a nasty sound (BZZZZ like on the old TV before they explode..) and right after the screen becomes black or/and the image is divided in 2, but the sound continues normally behind... Then the only solution is to reboot and everything works perfectly a certain time before it happen again. I have a ATI 6850 + phenom X4 925.... Any ideas?????? My config is not good enough to handle MADVR????
I'm not sure what this is. Maybe it's a hardware defect?

I am encountering problems when I use madVR... I have a Sapphire 4890 connected by HDMI to my Xonar HDAV 1.3, which is connected to my receiver (Onkyo TX-NR709). When I try to play 1080p/i movies (BD or mkv) with HD audio (DDTHD or DTS-HD MA/HR) in bitstream or in LPCM, the sound is cutted and cracks. If I choose EVR custom pres. as video renderer, everything works fine.
Not sure what that is, either. Have you tried different audio decoders and different audio renderers? madVR should have no direct impact on audio. madVR does not do *anything* audio related.

Switched my tv from iGPU Intel HD 3000 to my 6950 for more demanding scaling algorithms and was wondering when checking with the testpatterns and when using Pixel Format from Amd CCC, Full or Limited Range RGB, the colors.ytp testpattern showed a vertical line moving horizontally using 0-255 levels and any paned bit depth.

That got fixed with using either YCbCr 4:4:4 or 4:2:2 Pixel Format from CCC with 0-255 levels and 8-bit bit depth. But was wondering if it was ok to use YCbCr rather than RGB as madshi said in front page "Ok, e.g. in ATI's control panel with some graphics cards and driver versions you can activate YCbCr output, *but* it's rather obvious that internally the data is converted to RGB first and then later back to YCbCr, which is a usually not a good idea if you care about max image quality."

So was wondering should I rather use Full Range RGB with the line or YCbCr 4:4:4 or 4:2:2 with no problems in colors.ytp for playback.
If your eyes tell you that the image looks better with YCbCr 4:4:4 then by all means use that. In theory RGB should be better, though. Do you see any difference at all when switching between "Full" and "Limited" Range RGB in the AMD CCC? Does the black/white level change? Maybe the switch is broken and AMD always outputs limited? Also try disabling all funny stuff that might impact GPU output. E.g. try disabling any ICC profiles, win7 calibration and whatever else you can find.

I m using SVP frame interpolation. This is a heavy CPU usage real-time frame interpolation mode. In order to save more CPU i noticed that lowering the GPU and CPU queue saves quite some CPU power. Am I correct that I can lower them as much as possible without getting more dropped frames and pres. glitches?
EDIT: just put them on the minimum (both 4) and get not more dropped frames or pres. glitches then with the default settings (I think default was 12 and 8?)
If your playback is fine with lowered queues then that's just fine for you to use. However, higher queues should only result in higher CPU consumption while the queues are filling. As soon as all queues are full, CPU and GPU consumption should be identical to smaller queues. Maybe activating the madVR option "delay playback start until all queues are full" will make madVR work fine with higher queues, too?

I just tried running the "Tweak" utility. I was on my 0-255 plasma and it went entirely blank.
Ouch. I feared something like this might happen. I'll modify the tweak utility to simply change the registry and require a reboot, just to be safe.

You might have been able to repair the black screen by turning the plasma off/on, or by temporarily pulling the HDMI cable. But anyway, having to do any of these things is not good, obviously.

It now displays properly; however, I notice no difference than before. (I have madVR set to 0-255 and my TV set to the same. Blacks are grey when madVR is set to 16-235.)
The tweak is only necessary for the standard SD/HD resolutions. It's not needed if you are using custom resolutions.

EDIT2: My Mistake, that value is missing for my Plasma. (I know you said the Tweaker was based on the current monitor; I have three monitors and it was sensing the wrong set of registry keys. I do NOT have this value on my plasma, which is the only one I care about. Should I add it?
I would recommend it, at least it shouldn't hurt.

So before you decide to remove that option please don't as us Optimus users seem still need that "Use a seperate device for presentation" option....
I wasn't planning to drop *that* option.

[sneaker_ger]

Are the replies up-to-date or did you already write them during the time the questions were posed?

[madshi]

Of course they're up-to-date. Why would I write them and then not post them months ago?

[sneaker_ger]

Well, if you were to answer immediately you'd also get more follow up questions immediately...

[leeperry]

Good idea, will look into it.
Glad you like it! At my request, a friend of mine made a small app that forces the tightest NT resolution. It didn't change much on XPSP3 as I had already forced 0.97ms via its boot.ini but on Vista/W7/W8 you can force it down to 0.5ms instead of the default 1ms so it effectively provides a twice lower jitter :)

I can send you his small timerbooster app if you wanna try it, it hasn't gone public yet but it works wonderfully as far as I can tell.

Several ppl claim that W7 can reach less than 0.5ms when using HPET(even though it's undocumented), so it's good practice to force the value "1"(that's what fidelizer does) instead of "5000" just in case. Worst case scenario, it will be rounded to 9766 on XP and 5000 on the later OS.

Also, this value will only be forced for as long as the application requesting it will be running, so my friend had to provide a GUI-less mode so it would remain in memory as a process.

Strangely enough, Vista and W8 enable HPET by default but W7 does not(in most/all cases?) and uses an hybrid TSC+HPET mode that's utterly sloppy. I'm eagerly awaiting W7SP2 to make the big jump(there are several sub-SP1 audio related hotfixes) and I wanna do it in the most optimal conditions.

All this said, many ppl claim that fidelizer improves the SQ and everything USB related in general so forcing the same thing in madVR would only do good IMHO. m$ only force a low NT timer resolution when running multimedia apps in order to save power, which is mandatory on a laptop for instance...but they don't use the lowest one, they only go from 15.6ms to 0.9766 on XP/1ms on the later OS(when it can actually go as low as 0.5ms).

Going back to mVR, it works flawlessly on my system! The only thing I would love to see added is an "only when the movie starts" sub-option to "delay playback start until renderer queue is full" in order to allow ffdshow/avisynth/Reclock to all be synchronized and avoid the load induced judder I can see from time to time on WMV videos for instance(no GPU decoding so synchronizing everything can be a hit and miss). I believe other Reclock users would also welcome this feature.

:thanks:

[Keiyakusha]

madshi
Here is sample that appears as 1919x1080 resolution. This happens with any 720x480 file which have proper sar info in stream... http://www.mediafire.com/?ahmb8a2qvwa6ibx It doesn't matters what target resolution is, starting from 720p all affected (didn't tried less).

About second issue, this appears to be my mistake, I didn't noticed crop rectangle value, sorry.

[madshi]

madshi
Here is sample that appears as 1919x1080 resolution. This happens with any 720x480 file which have proper sar info in stream... http://www.mediafire.com/?ahmb8a2qvwa6ibx It doesn't matters what target resolution is, starting from 720p all affected (didn't tried less).
Ok, I've checked, it's not a bug in madVR. The problem is pretty simple: The renderer reports to the media player which resolution the video file has and which is the preferred aspect ratio resolution. So madVR reports a video size of 720x480 and a preferred aspect ratio resolution of 853x480. The correct AR resolution would be 853.333333x480, but madVR has no way to pass this information to the media player, so it rounds down to 853x480. Now if you configure the media player to e.g. "touch window from inside" (MPC-HC) then the media player has to figure out which zoom factor to use on the 853x480 video. It could either use zoom factor 1920/853 or 1080/480. When using 1920/853, we would end up with a resolution of 1920x1080.422. That does not fit to the "touch window from inside" option. So MPC-HC instead goes for a zoom factor of 1080/480, which results in 1919.25x1080. The cause of all the trouble is the rounded preferred aspect ratio resolution of 853x480. There isn't really much I can do about that, I think.

P.S: Of course scaling is only performed once!

[madshi]

For this sample (PAL DVD film in 50i container)
http://dl.dropbox.com/u/43376972/Pal%20film%20deinter%20OFF.mkv
Settings:
force film mode
if in doubt, activate deinterlacing,
but OSD says that deinter is off !

So deinterlacing is not on automatically?
madVR is not in doubt for this sample. The MPEG2 stream is set to "progressive_sequence = 1" and the MPEG2 spec says:

When set to '1' the coded video sequence contains only progressive frame-pictures. When progressive_sequence is set to '0' the coded video sequence may contain both frame-pictures and field-pictures, and frame-picture may be progressive or interlaced frames.

[Keiyakusha]

Ok, I've checked, it's not a bug in madVR. The problem is pretty simple: The renderer reports to the media player which resolution the video file has and which is the preferred aspect ratio resolution. So madVR reports a video size of 720x480 and a preferred aspect ratio resolution of 853x480. The correct AR resolution would be 853.333333x480, but madVR has no way to pass this information to the media player, so it rounds down to 853x480. Now if you configure the media player to e.g. "touch window from inside" (MPC-HC) then the media player has to figure out which zoom factor to use on the 853x480 video. It could either use zoom factor 1920/853 or 1080/480. When using 1920/853, we would end up with a resolution of 1920x1080.422. That does not fit to the "touch window from inside" option. So MPC-HC instead goes for a zoom factor of 1080/480, which results in 1919.25x1080. The cause of all the trouble is the rounded preferred aspect ratio resolution of 853x480. There isn't really much I can do about that, I think.

P.S: Of course scaling is only performed once!
I see, so madvr always scales to the values that player requests? But in exclusive fullscreen mode maybe you can use your own more precise info?
Or what if you will report to player that frame size is 720x480 but ar is not 853x480 but something higher that divides better

[nlnl]

madVR is not in doubt for this sample. The MPEG2 stream is set to "progressive_sequence = 1" and the MPEG2 spec says:

Thank you for the reply!
And please have a look at this
http://forum.doom9.org/showpost.php?p=1588430&postcount=13767

[madshi]

I see, so madvr always scales to the values that player requests? But in exclusive fullscreen mode maybe you can use your own more precise info?
Or what if you will report to player that frame size is 720x480 but ar is not 853x480 but something higher that divides better
If I report something other than 853x480 then the media player will also default (with "Normal Size" zoom setting) to something other than 853x480 which would not be good.

Currently madVR reports what it should report and strictly obeys whatever size/zoom/AR wish the media player has. Of course it would be possible to detect certain situations and override/correct them. E.g. I could always correct 1919x1080 to 1920x1080. But this is something I'm not ready for at this point in time. Maybe some time in the future.

And please have a look at this
You don't really need to remind me. That post of yours is already on my to do list, as are a few others I haven't replied to yet.

[madshi]

I just noticed I have a madVR - crash report.txt (http://www.mediafire.com/?x7d12g24a0vgik6) file on my desktop, so I thought I should send it to the developer. :rolleyes:

I noticed the MPC-HC hanged a bit during some file openings but I thought it's the Samba file sharing server to blame.
Weird. This only makes sense to me if 2 madVR instances were open at the same time, which shouldn't really be happening. I guess you can't reproduce this, can you?

[Nevilne]

Could resolution switching logic be improved? My monitor's refresh range is 50-60, and madvr doesn't switch to 50 with 24p content, but it will switch to 50 with 40p content. (madvr options 1080p50, 1080p60)

[madshi]

Could resolution switching logic be improved? My monitor's refresh range is 50-60, and madvr doesn't switch to 50 with 24p content, but it will switch to 50 with 40p content. (madvr options 1080p50, 1080p60)
60p seems more appropriate for 24p content. You'll get 3:2 pulldown judder, but other than that it should be perfect. With 50p you'll get much uglier motion judder. Unless you use Reclock, of course, to speed 24p up to 25p. 40p content? Never heard of that before...

[Nevilne]

Yeah, forgot to mention I use Reclock. 40p was some game movie content, just used it as example.

[madshi]

Well, I plan to modify the refresh rate changer in a future version. You'll have to wait for that. Can't give you an ETA right now.

[e-t172]

To be honest, I don't know how ICC profiles and LUTs loaded in the GPU behave with madVR. Does anybody else know?

Well, LUTs loaded with SetGammaRamp (http://msdn.microsoft.com/en-us/library/bb174434.aspx) (this includes ICC profile loaders) are still active when playing with madVR, including fullscreen exclusive mode. That's because, AFAIK, the translation is done at a very low hardware level just before the signal is sent to the monitor.

That's why I made a feature request ages ago to have madVR reset these tables (and restore them at the end of playback): to avoid the obvious double conversion issue when using madVR's 3DLUTs and the hardware LUTs simultaneously.

[madshi]

Ah, thanks, that makes sense. Is there something like SetGammaRamp for colors, too? Or does the GPU only support gamma manipulations via ICC profiles? How are colors managed then?

[madshi]

http://samples.mplayerhq.hu/V-codecs/CRAM/clock-cram16.avi
http://samples.mplayerhq.hu/V-codecs/CRAM/worm.avi
http://samples.mplayerhq.hu/V-codecs/CVID/1984.apple_ad.mov
http://samples.mplayerhq.hu/V-codecs/CVID/handss.avi
4 Day Weekend.mov (http://www.directmirror.com/files/BAWVF6FZhttp://)
AVI Decompressor (RGB24) + madVR = artifacts
ffdshow (RGB24) + madVR = normal
AVI Decompressor (RGB24) + Color Space Converter(ARGB32) + EVR = normal
I can reproduce the problem, but I don't know how to fix it. From what I can see, it seems to me that the AVI Decompressor is responsible for the artifacts. My best guess is that the AVI Decompressor can't handle the way madVR stores frames into a queue and reuses media sample buffers. If that's really the cause of the problem then it's clearly a bug in the AVI Decompressor. But I'm not 100% sure. Don't really know what to do here...

FWIW, adding the ffdshow raw filter in between AVI Decompressor and madVR fixes the problem.