madVR - high quality video renderer (GPU assisted)

[jkauff]

Cool, that sounds fine to me. I will put it to Blight that the option be renamed to "Enable MadVR's smooth motion (always over-rides madVR option)".
Does the Zoom checkbox enable "Use always" or "Use only when needed"? Will that be clear to the user?

[jmonier]

Does the Zoom checkbox enable "Use always" or "Use only when needed"? Will that be clear to the user?

It does whatever is checked in madVR. It controls the overall use of Smooth Motion but not the way in which it is applied.

[romulous]

Yes, as jmonier has stated, the option in Zoom only controls the state of this option here:
http://i.imgur.com/s9cDfmR.png (the one inside the red rectangle)

Everything else outside that is controlled by madVR, specifically by what the user has set inside madVR's options dialog - so while Zoom can switch Smooth Motion on and off, madVR itself decides if Smooth Motion will be used (and if so, how) when it is enabled. There isn't enough room in the Zoom options dialog to put a whole paragraph on it, but as well as renaming the option in that dialog, I will ask Blight to make it clear in the Zoom help file that this option only changes the enable/disable state of Smooth Motion, and nothing else (the help file for Zoom is only updated for each stable release, so the help file does not yet list the "enable madVR's smooth motion" option - but it will).

[pankov]

I think that it will be better if there is a third state (cbGrayed) for this option in Zoom Player with the meaning of "don't change anything - respect madVR's settings" and this should be the default state. Otherwise madshi will get a lot of complaints from ZP users that madVR's options don't work.

[romulous]

@pankov: I've added that idea to the tracker report.

[jmonier]

I think that it will be better if there is a third state (cbGrayed) for this option in Zoom Player with the meaning of "don't change anything - respect madVR's settings" and this should be the default state. Otherwise madshi will get a lot of complaints from ZP users that madVR's options don't work.

Once the changed wording is put in, there will be a lot less chance of these complaints, but I agree that it could still be a problem.

If this third choice is put in it would have to disable the fnMadVRSmoothMo ZP Function, thus breaking any skinning, keyboard shortcut or script that uses this Function. So, there is a possibility of confusion, no matter what, unless the feature and the ZP Function is removed completely. Since I feel that the feature has value, I think that it should be retained as is (but with the changed wording and with a clear description in the documentation).

[burfadel]

Would Directx 11.2 provide any benefits for MadVR? If so, any plans to implement them for Windows 8.1 when it comes out?

[dbcooper]

Hi All, is it confirmed that MadVR can disable the default windows LUT when it plays video and uses a 3DLUT?

[dansrfe]

Hi All, is it confirmed that MadVR can disable the default windows LUT when it plays video and uses a 3DLUT?

devices -> [your_device] -> calibration -> disable GPU gamma ramps

[dbcooper]

Cheers. That's what I've been doing. I assume that Fullscreen Exclusive mode must be used?

[dansrfe]

Cheers. That's what I've been doing. I assume that Fullscreen Exclusive mode must be used?

Nope, it applies in all modes.

[dbcooper]

Thanks again. One last question:

I have created a 3DLut for Rec709 (using the following: collink.exe -v -3m -qh -et -Et -IB2.2 -G -iaw Rec709.icm MadVR.icm 3DLUT.icm), and have specified it in the Rec709 dialogue box under devices > calibration. Do I need to add it for the other gamuts, or will MadVR use it automatically and do appropriate transforms?

[Nui]

AFAIK, you must not add this LUT for other gamuts. Each gamut needs its own LUT if you want to add them. Or you use only the one for Rec709 and madvr will do its magic for the rest :)

[cyberbeing]

You can specify the REC709 3DLUT manually for all gamuts if you desire, it works the same either way.

Edit: In case that was too ambiguous, it means that madVR determines gamut from the primaries written plain-text in the 3DLUT header, not the slot you place it in. If the 3DLUT primaries do not match the gamut of the video, shader adaption to the native gamut of the 3DLUT will occur.

[flashmozzg]

Reporting here: weird graycolor issue I had with all madVR versions higher than 0.84.7 is no longer present after I did new windows clean install, so whatever caused it now gone.

[Trib]

Done more calibrating of my Panasonic p42st32y plasma and still being confused. So I tried with -dmadvr -a and using just madvr to control black level (nvidia madvrlevelstweaker also forced 0-255). Now I was using argyll with the scenarios.html workflow.

-If i used 0-255 I get around 6500 contrast ratio but I can only see black bars flashing 20 and up not 17. Whites clip around 245. Also gamma shows a huge drop to 1.9 at 90% brightness!

-If I used 16-235 I get around half the contrast ratio around 3500 and see bar 16 and up flashing. Whites dont clip. Gamma curve appears normal bt 1886.

I tried using different collink settings -iaw and -IB or -ir and -Ib but no difference.

For both tests I used default True Cinema preset but I got 17 and up flashing adjusting brightness a lil up with 0-255 after calibration.

Im wondering whichone is the more "correct" behaviour and should be used. Or if anyone got any alternatives or ideas?

[pie1394]

Would Directx 11.2 provide any benefits for MadVR? If so, any plans to implement them for Windows 8.1 when it comes out?

The new OS changes on some behaviors often have created a lot of headaches... They are always the first priority jobs to be dealt with. :devil:

Even if this OS has some "unique" new features unavailable on Win7, is it worthy to support that in short term --- when the Win8.x market share % is so low at this moment? :D

[ney2x]

My TV supports 23.976 Hz screen refresh rate and madVR perfectly fine with it (0 drop frames, no glitches), but, not with my PC monitor which natively supports 50, 59 and 60 Hz, and 72 Hz if I add custom resolution in Nvidia Control Panel.

My questions are, Is it safe for my monitor to used 72 Hz all the time? I mean, it doesn't destroy my monitor?

My configs are:
i7 2600k Sandy Bridge
GTX 560 Ti
LAV Filters - all default except LAV Video (CUVID)
Reclock - not bitstreaming because I used SPDIF

Sorry for my english :)

[lemo]

madVR v0.86.*
* fixed: #30: ZoomPlayer got stuck in 'on top' mode after leaving FSE

Hi. I think the above fix has broken the 'stay on top' feature in zoom player for me.

When zoom player goes from windowed to full screen exclusive and back to windowed again, 'stay on top' is still ticked but does not function. If I untick and retick the box 'stay on top' works as it should.

I like to have zoom player in the top corner of my screen so I can keep watching while browsing the web etc.

I have downgraded to madVR0865 which has fixed the problem.

Reporting bug, not complaining :)

[romulous]

@lemo: It's not madVR specific - same happens with all the other renderers. It's something that is a regression in the latest Zoom Player beta's (it was first reported with 8.70 Beta 11). There is a bug report in the Zoom bug tracker for Blight to look at:
http://forum.inmatrix.com/index.php?showtopic=14073#entry54462

I don't know why downgrading madVR fixes it for you when all the other renderers are affected as well though.

[dansrfe]

Is it just me or does smoothmotion use a substantial amount of VRAM?

[ryrynz]

Is it just me or does smoothmotion use a substantial amount of VRAM?

What's substantial? Specifics my boy!

For me my Intel HD 4000 GPU system memory grows from 239MB with it disabled to 303MB with it enabled, so it could be just you or to put it more accurately.. your graphics system.

A comparison between Intel, AMD and Nvidia results in this area would be interesting to see, perhaps something can be optimized here.

[dansrfe]

Well, when upscaling 1080p to 1440p at max settings in madVR with smoothmotion on an additional 300MB - 400MB of VRAM is taken up on my GTX 670 2GB. Not too sure I can attribute it directly to smoothmotion though. Need to do some testing to make sure exactly.

[dansrfe]

Ok, I now have a real (and tested) 120Hz monitor and a 60Hz monitor. I ran the SmoothMotion 24p test pattern on both monitors simultaneously and I cannot tell them apart in terms of smoothness with smoothmotion ON on the 60Hz monitor and smoothmotion OFF on the 120Hz monitor.

Now, other than the fact the 120Hz is good for games and even normal desktop usage, why is it still considered that a monitor @120Hz is better than a monitor @60Hz using smoothmotion? I would really like to know that technical reasons. Does interpolation cause microscopic artifacting? Is there some other drawback to using smoothmotion interpolation that cannot be easily seen?

[webs0r]

I thought smoothmotion only created frames when absolutely required. This is my understanding:

No frames would be created in the 24fps / 120Hz situation as madVR would show each frame 5 times within each second.
With 24 fps/60 hz situation madVR would show each frame twice, and interpolate 12 frames within each second via frame blending the adjacent frames.

If that's right, then 120 Hz is superior in that you are seeing only the intended frames present in the video stream. I think there is pretty low chance of artifacting with normal content but with 120 Hz you avoid any chance of it.

[madshi]

madshi: could you please add a link to the xy-subfilter thread in the first post so people know about it?
Done.

Is there any trick I can do to get madVR to display at 60 fps without dropping massive amounts of frames?
GPU usage is at 3%. I have basically everything disabled, but madVR still can't hold a steady 60 fps. It plays fine for a moment (the buffers even seem to hold steady) but then it suddenly starts dropping frames like mad. I'll add that the file is VFR and alternates between 24p and 60p.
The OSD shows that rendering/upload queue drops instantly on switchover to 60p segment. The stranger part is that the rendering frametime indicator holds at a steady 8 ms but jumps to 20 ms instantaneously on switch. Perhaps on a longer sequence the rendering time would return to a steady value, but the 60p segments are only a few seconds in length.

Edit:
On 60p CFR, I see madVR running fine for a brief period, up to a minute, with all buffers at max. Then they suddenly all drop, with the rendering time indicator reading 30-40 ms, causing massive frame dropping that madVR never recovers from. On 24p/60p VFR, I see all the buffers dropping instantaneously on switching from 24p to 60p.
Not sure what's going on there. Which is the queue which gets empty first, from top to bottom? Make sure you have no other software running at the same time which might also access the GPU. E.g. some browsers do. Also make sure your GPU doesn't clock down dynamically.

Some issues in v0.86.10:
when I use hotkey assigned for "image upscaling anti-ringing filter toggle on/off", it only displays *current* state of the filter in OSD but doesn't toggle it.
instead of two separate hotkeys to enable and disable FRC, it would only be natural to have one to toggle FRC on and off.
AR hotkey: If you press once, it shows the current state. If you press twice, it should change the state. At least that's how it works on my PC, just tested again, to be safe. Not all algorithms support AR, though, maybe that's the problem you ran into?

FRC hotkey logic might change in the future, but not now.

madshi, I wonder if it's possible to have madVR to run a quick query for other discrete GPUs and possibly parallelize usage of multiple GPUs for processing? Software SLI essentially.
Many things are "possible". I don't accept feature requests at the moment.

It seems that smooth playback isn't working anymore with 0.86.10 as video stutters sometimes (23.976 FPS with 24 Hz).
You mean smooth motion FRC? Seems to work fine for everyone else. Maybe something else is going on on your PC? Maybe a screenshot of your OSD would help, in the moment when playback stutters?

I know that madVR doesn't support portrait mode however, out of curiosity, why is that madVR has to "support" portrait mode?
Don't ask me. The Direct3D documentation says that portrait mode should work automatically, without me having to do anything about it. But it doesn't. I don't know why...

Hi ... Regarding madTPG, should I select 'disable VideoLUTs' throughout this workflow?
ArgyllCMS automatically disables everything that needs to be disabled.

the reason for my question is that with "-a TV.cal" achieves a strange result ... white is yellowish
Did you install this TV.cal into the GPU, when getting that yellowish? Did you tell madVR to disable the GPU gamma ramps during playback? When using "-a", the GPU gamma ramps are supposed to be empty/linear.

Would Directx 11.2 provide any benefits for MadVR? If so, any plans to implement them for Windows 8.1 when it comes out?
There are some things which might be beneficial, but I'm not sure if I will support them, because I don't think it makes sense spending a lot of time on something which only works on Windows 8.

Done more calibrating of my Panasonic p42st32y plasma and still being confused. So I tried with -dmadvr -a and using just madvr to control black level (nvidia madvrlevelstweaker also forced 0-255). Now I was using argyll with the scenarios.html workflow.

-If i used 0-255 I get around 6500 contrast ratio but I can only see black bars flashing 20 and up not 17. Whites clip around 245. Also gamma shows a huge drop to 1.9 at 90% brightness!

-If I used 16-235 I get around half the contrast ratio around 3500 and see bar 16 and up flashing. Whites dont clip. Gamma curve appears normal bt 1886.

I tried using different collink settings -iaw and -IB or -ir and -Ib but no difference.

For both tests I used default True Cinema preset but I got 17 and up flashing adjusting brightness a lil up with 0-255 after calibration.

Im wondering whichone is the more "correct" behaviour and should be used. Or if anyone got any alternatives or ideas?
It's hard to say for sure what's going wrong, without seeing the exact ArgyllCMS command lines you were using. In any case, this is a topic more suited to the ArgyllCMS+madVR thread. So you might want to ask there, with a list of the exact command lines you were using:

http://www.avsforum.com/t/1471169/madvr-argyllcms

My questions are, Is it safe for my monitor to used 72 Hz all the time? I mean, it doesn't destroy my monitor?
How are we supposed to know that? If a google search doesn't answer this question for you, you could call your monitor support hotline. Generally, I guess if your monitor accepts the signal and displays it, it's *probably* safe to use. But I can't really say for sure, or give you some guarantee or something...

Is it just me or does smoothmotion use a substantial amount of VRAM?
It does consume a bit more GPU RAM, yes. "Substantial"? I don't know...

Ok, I now have a real (and tested) 120Hz monitor and a 60Hz monitor. I ran the SmoothMotion 24p test pattern on both monitors simultaneously and I cannot tell them apart in terms of smoothness with smoothmotion ON on the 60Hz monitor and smoothmotion OFF on the 120Hz monitor.

Now, other than the fact the 120Hz is good for games and even normal desktop usage, why is it still considered that a monitor @120Hz is better than a monitor @60Hz using smoothmotion? I would really like to know that technical reasons. Does interpolation cause microscopic artifacting? Is there some other drawback to using smoothmotion interpolation that cannot be easily seen?
Basically if you don't see a difference that means that Smooth Motion FRC is doing a very good job.

Look for the "white line, black line, white line, black line" section in the test pattern bar which moves the slowest. That section should look slightly better with 120Hz and smooth motion FRC turned off.

Some people claim to see some ghosting artifacts when smooth motion FRC is turned on. Personally, I don't see that (with 24fps @ 60Hz). I do wonder if this artifact is really caused by smooth motion FRC itself or whether the display of the users which have this problem is not working as expected (e.g. running at a different internal refresh rate).

120Hz has some other advantages. E.g. it might allow the use of DFI (dark frame insertion) to make motion more sharp. You can't really do that with 60Hz, without getting strong flicking artifacts. But madVR currently does not do/support DFI. Maybe some far away day in the future...

One advantage of 120Hz is that you could do 50fps @ 120Hz with smooth motion turned on. Doing 50fps @ 60Hz currently doesn't work very well with smooth motion FRC.

[leeperry]

How are we supposed to know that? If a google search doesn't answer this question for you, you could call your monitor support hotline. Generally, I guess if your monitor accepts the signal and displays it, it's *probably* safe to use. But I can't really say for sure, or give you some guarantee or something...
nVidia recently came up with some new sales pitch implying that you could "overclock" your LCD monitor from the regular 60Hz to as much as 80Hz: http://translate.google.com/translate?hl=en&sl=fr&tl=en&u=http%3A%2F%2Fwww.lesnumeriques.com%2Fcarte-graphique%2Fnvidia-geforce-gtx-titan-p15386%2Fnvidia-overclocke-ecrans-60-a-80-hz-n28366.html

When lesnumeriques.com asked Samsung, they replied that this would void the warranty.....of course, they would have no way of finding out.

This said, CRT's do age faster when you go >100Hz. I was given a lot of technical reasons to that a few months ago, basically it really boils down to hardware "overclocking".....and my last 19" CRT did die very shortly after I had the genius idea of increasing its 720p refresh rate from 96 to 140Hz :o

Some people claim to see some ghosting artifacts when smooth motion FRC is turned on. Personally, I don't see that (with 24fps @ 60Hz). I do wonder if this artifact is really caused by smooth motion FRC itself or whether the display of the users which have this problem is not working as expected (e.g. running at a different internal refresh rate).
I did experience a lot of ghosting due to my GPU not being beefy enough....I then lowered my scaling settings in mVR and all went well.

I do see faint ghosting but I'm still utterly impressed by how FRC in mVR in suppresses 24p judder, to my eyes the pop effect is drastically increased and instead of judder I see barely noticeable ghosting.....which is nothing more than frames blending really. Also, my brain got used to it and as far as I can tell it quickly ignores them, so all I really see is dead smooth 24p without FI artifacts :cool:

FRC in mVR is really a God send because I finally found a LCD screen I like but the darn thing judders like hell in 24p and doesn't support 48Hz, the closest it'll do is 49Hz....not as evil as the 4% pitchshifted 50Hz but 2% is still (very) hard to bear, so FRC in 60Hz and that's it :devil:

I was also able to overclock this TV up to 72Hz using minimal blanking timings(within the 165Mhz pixel clock limit), but then the TV is forced to bypass most of its post-processing and I can kiss its Rec-709 gamut bye bye so that's a no-go.

120Hz has some other advantages. E.g. it might allow the use of DFI (dark frame insertion) to make motion more sharp. You can't really do that with 60Hz, without getting strong flicking artifacts. But madVR currently does not do/support DFI. Maybe some far away day in the future...

One advantage of 120Hz is that you could do 50fps @ 120Hz with smooth motion turned on. Doing 50fps @ 60Hz currently doesn't work very well with smooth motion FRC.
That TV I just mentioned also offers BFI, but it really dims the picture.....to the point that whatever I do, gamma gets utterly dark >90 IRE, that's just painful and unacceptable.

So indeed BFI in mVR could be useful but it would require a display with a lot of extra brightness available, and of course clouding/light bleeding would become more visible. This might very well not be worth the hassle as the best way is to turn off the backlight really: Display motion blur (http://en.wikipedia.org/wiki/Display_motion_blur)
Sharp Corporation use a "scanning backlight" which rapidly flashes the backlight in a sequence from the top to the bottom of the screen, during every frame.

[JohnLai]

Been a while since I posted here.

I noticed that Madvr + LAV filters + xyvsfilter beta = DXVA can be used without issue.

Can anyone verify this? I wonder if the 'dxva' indicator I saw at madvr statistics is just a bug.

[madshi]

No bug, DXVA decoding has been working fine for a while now. Not that I recommend using it. I prefer software decoding...

[JohnLai]

No bug, DXVA decoding has been working fine for a while now. Not that I recommend using it. I prefer software decoding...

I see. Good thing DXVA finally works with xyvsfilter + madvr scaling. :thanks:

[sneaker_ger]

To be more precise: the new XySubFilter does not interfere with DXVA decoding, because it does not sit between the video decoder and madVR in the DirectShow chain. The traditional xy-vsfilter still does not allow DXVA decoding and that will not change because of the design.

[dansrfe]

Ok, with the 50fps test pattern there are noticeable differences between the 100Hz monitor with smooth motion OFF and 60Hz monitor with smooth motion on. I can change the refresh rate on the other monitor that I have and it's been tested to be real.

I just wish I watched more 50fps material then... Wait, does deinterlacing video content from a pal dvd give 50fps back or does madVR throw away the other frames to maintain 25fps?

[DragonQ]

I just wish I watched more 50fps material then... Wait, does deinterlacing video content from a pal dvd give 50fps back or does madVR throw away the other frames to maintain 25fps?
Depends.

If it's 576i/25 then it should be deinterlaced to 576p/50, if deinterlacing is set up correctly. If it's 576p/25 then it should be either weaved to 576p/25 or deinterlaced to 576p/50. If the latter is done properly, every other frame will be identical to the preceding one.

[TheElix]

Regarding automatic display mode matching. I think it's bugged or I just use it incorrectly. "1080p23, 1080p25, 1080p29, 1080p50, 1080p59" is what I have there but it switches to 1080p23 on every video, even 25p or 30p. So even though source filter says the video is 29.970 or 59.940 it still switches to 23.976.

[dansrfe]

Depends.

If it's 576i/25 then it should be deinterlaced to 576p/50, if deinterlacing is set up correctly. If it's 576p/25 then it should be either weaved to 576p/25 or deinterlaced to 576p/50. If the latter is done properly, every other frame will be identical to the preceding one.

By weaving are you referring to setting the deinterlacement mode to "film" and having a 2:2 cadence with 25fps film material?

[6233638]

madVR v0.86.11 released
* added import functionality for eeColor 3dlut filesDoes this mean that I can use CalMAN to create LUTs for madVR now? (I have no idea if it needs to be connected to an eeColor LUT box to create LUTs for it, or if it can just use the PC generator)

[dansrfe]

Also madshi, not sure if this is an actual bug but having more than one madVR instance running in overlay mode causes subsequent instances to now show anything other than a black screen.

[Thunderbolt8]

No bug, DXVA decoding has been working fine for a while now. Not that I recommend using it. I prefer software decoding...why is that?

[madshi]

Regarding automatic display mode matching. I think it's bugged or I just use it incorrectly. "1080p23, 1080p25, 1080p29, 1080p50, 1080p59" is what I have there but it switches to 1080p23 on every video, even 25p or 30p. So even though source filter says the video is 29.970 or 59.940 it still switches to 23.976.
Make sure you only enter modes which really exist. 1080p29 is not a mode commonly used, I rather doubt your GPU actually supports it (without a custom resolution). If you still think there's a problem, upload a debug log and I can tell you why madVR did what it did.

Does this mean that I can use CalMAN to create LUTs for madVR now?
Yes. At least in theory. I don't have a Calman license, so I can't test it. I tested it with eeColor LUTs created by ArgyllCMS and cross checked that LightSpace eeColor LUTs have the same format. So I suppose it should also work for Calman.

However, Calman does not support the madVR test pattern generator yet, so you'll need to use a different way to do the measurements. Obviously, it would be nice if Calman supported the madVR test pattern generator. They did express interest in maybe adding support for it. But I guess only if licensed Calman customers are actually asking for it, they will actually do something...

So, all Calman customers who're interested in having Calman support the madVR test pattern generator, now would be a good time to ask them about it.

Also madshi, not sure if this is an actual bug but having more than one madVR instance running in overlay mode causes subsequent instances to now show anything other than a black screen.
Known problem.

why is that?
Because software decoding is faster (if you have a decent CPU) and more reliable. No stupid limits like max number of reference frames, no hardware decoding bugs, no bluescreens or crashes etc...

[DragonQ]

By weaving are you referring to setting the deinterlacement mode to "film" and having a 2:2 cadence with 25fps film material?

Yes, that is "weave" deinterlacing.

My nVidia GPUs do this automatically so I can leave MadVR (or CUVID) deinterlacing all the time and 25p material doesn't lose any resolution when output as 50p. Apparently some GPUs don't handle 2:2 cadence properly though - for these cards, MadVR must be set to "film mode" to avoid resolution loss.

[makakam]

I have my panny vt30 calibrated with i1d, calman and calman pc pattern generator. Do I enable "disable gpu gamma ramps" option or leave it disabled?

[Acetyl]

Not sure if this is a bug report, an intended behavior, or neither. But I thought I'd report it nonetheless.

MadVR's smooth motion seems to produce a constant blurring when video fps is extremely close to (or slightly above) the refresh rate. (eg 59.94 on an ~59hz monitor). The video plays smoothly with no visible hitching without it however. (In the case of credits or the like, it makes them less clear to read, as an example)

[dansrfe]

Not sure if this is a bug report, an intended behavior, or neither. But I thought I'd report it nonetheless.

MadVR's smooth motion seems to produce a constant blurring when video fps is extremely close to (or slightly above) the refresh rate. (eg 59.94 on an ~59hz monitor). The video plays smoothly with no visible hitching without it however.

madshi has mentioned that smoothmotion doesn't work well when the source fps is close to the output refresh rate. That's may be why.

[madshi]

I have my panny vt30 calibrated with i1d, calman and calman pc pattern generator. Do I enable "disable gpu gamma ramps" option or leave it disabled?
How exactly did you do the calibration? Did you create an eeColor box 3dlut and loaded that into madVR? Or what did you do exactly? I can't answer your question without knowing what you did exactly...

MadVR's smooth motion seems to produce a constant blurring when video fps is extremely close to (or slightly above) the refresh rate. (eg 59.94 on an ~59hz monitor). The video plays smoothly with no visible hitching without it however. (In the case of credits or the like, it makes them less clear to read, as an example)
I don't really recommend activating smooth motion FRC when your refresh rate is near to the movie framerate. Although it does make everything smooth and gets rid of any stutter, it does come at a certain price (loss of sharpness) in that situation. The higher your refresh rate and the lower your movie framerate, the less sharpness you will lose.

[Acetyl]

I don't really recommend activating smooth motion FRC when your refresh rate is near to the movie framerate. Although it does make everything smooth and gets rid of any stutter, it does come at a certain price (loss of sharpness) in that situation. The higher your refresh rate and the lower your movie framerate, the less sharpness you will lose.
I see. The issue is this file is VFR, so it switches from 23.976 to 59.94 midway.

I doubt it'd be this simple of a matter, but out of curiosity, would it be possible to add a side option for, or a conditional check in the "only if there would be judder without it" setting?

[makakam]

How exactly did you do the calibration? Did you create an eeColor box 3dlut and loaded that into madVR? Or what did you do exactly? I can't answer your question without knowing what you did exactly...


I just used calman pattern generator installed on my htpc along with calman v4 on my laptop. Only tv's setting were altered, I didn't create luts and in madVR I have "this display is already calibrated" option enabled and now that gamma ramp option is what makes me wonder.

[Mikey2]

Hi all, and thanks again for still supporting/enhancing this awesome renderer.

I have a couple quick questions concerning xy-SubFilter.

1) Someone mentioned another thread on this topic. I could not find it. Can someone please send a link of the thread so I do not further cross-post. :eek:

2) I can render embedded subs, but not external ones. Previously I played external .srt files by putting the srt file in the same folder as the mkv and renaming so both files match. This is not working with xy-SubFilter. Am I missing anything? (I suppose I can mux them back into the same mkv, but I don't think I should have to do that.)

3) Previously, I mapped MPC-HC keyboard shortcuts to easily toggle subs on/off, switch between subs, etc. Naturally this no longer, works, but is there even rudimentary hotkey support for this in xy-SubFilter (or even madVR if it has access?)

Thanks in advance for your help!
Mike

[sneaker_ger]

1) Someone mentioned another thread on this topic. I could not find it. Can someone please send a link of the thread so I do not further cross-post. :eek:

http://forum.doom9.org/showthread.php?t=168282

[cyberbeing]

2) I can render embedded subs, but not external ones. Previously I played external .srt files by putting the srt file in the same folder as the mkv and renaming so both files match. This is not working with xy-SubFilter. Am I missing anything? (I suppose I can mux them back into the same mkv, but I don't think I should have to do that.)
Did you remember to install it via the installer or regsvr32? madVR is in charge of loading XySubFilter Beta for external subtitles, but the registry key madVR requires isn't written unless you install. Otherwise, if you are using Windows 8 or have renamed mpc-hc.exe, you may need to update your MPC-HC build (http://nightly.mpc-hc.org/).

3) Previously, I mapped MPC-HC keyboard shortcuts to easily toggle subs on/off, switch between subs, etc. Naturally this no longer, works, but is there even rudimentary hotkey support for this in xy-SubFilter (or even madVR if it has access?)

MPC-HC for some reason has never supported those hotkeys with VSFilter, and XySubFilter uses the same API. The only hotkey which functions is "S" for Next Subtitle, with the rest only functioning with the MPC-HC ISR.

I'd recommend grabbing a MPC-BE nightly build (http://sourceforge.net/projects/mpcbe/files/MPC-BE/Nightly%20Builds%20%28from%20svn%20trunk%29/), if you want more functional media player support for xy-VSFilter and XySubFilter.

[moshmothma]

But I guess only if licensed Calman customers are actually asking for it, they will actually do something...

So, all Calman customers who're interested in having Calman support the madVR test pattern generator, now would be a good time to ask them about it.


.
This is the response I got when asking about Calman support for madvr...

We will it's just a matter of priorities at the moment. We are working on getting CalMAN 5.2 ready for IBC and CEDIA. The new features and hardware updates are already slated for CalMAN 5.2