madVR - high quality video renderer (GPU assisted)

[madshi]

Exactly. See also first post of this thread, where rotated displays are listed as a known limitation of the current madVR build.

[psishock]

Rotated screens are not supported by madVR at this time.
Its on madshis list to support it, but not a high priority, iirc.

Oh... that's a big bummer then, i stopped filling the bug. I am usually moving my player between the screens, depending on my stuffs that im doing, so i would constantly use this feature.

Many times, i would just move my player to the other screen to play something not really important, that doesn't require full attention, while working on the primary monitor.

[psishock]

Exactly. See also first post of this thread, where rotated displays are listed as a known limitation of the current madVR build.

well, now im fully aware what is happening at least. I have a bad habit of not fully reading everything before i ask questions, this is a perfect example for the fact that i need to start getting rid of it.

Thanks anyway madshi, hope that you'll find some time in the future between the important fixes to solve this one too.

[pie1394]

Yes, I did.
Which GPU is needed to handle Jinc3 AR upscaling to 1080p60 was discussed in this thread multiple times and the general consensus was that a 660 is needed for that. Jinc is *really* demanding on the GPU. Well, maybe a 650 Ti would also do the job, I'm not sure if anybody tested that yet. But a 650 is definitely too slow. It should be able to handle 24p stuff, but not 60p. After all 60p requires 2.5x the power of 24p.


Just replace my 3.6 years-old MSI Lightning GTX260+ (680MHz, 216SP, 1792MB GDDR3-2100 448-bit) with Lantic HD7970 (925MHz, 2048 SP, 3GB GDDR5-5500 384-bit).

Gaming performance, 4K HDMI/DP single-display, Deep color support are major considerations to choose this HD7970 instead of GTX660Ti. (Both cards are the same price in my country now...)

Get it tested with the ISDB-T MPEG-2 program 1440x1080i60 --> 1920x1080p60, DXVA2 Vector-Adaptive Deinterlacing, Deblocking options, madVR Jinc3+AR.

I just can say that HD7970 should be capable of 120fps --- not just 60 fps in such case.

Too sad that my CPU is not powerful enough to play the H.264 95.4Mbps video stream 3840x2160i60 --> 1920x1080p60. I will try some other 4K samples with less bit rate that UVD3 supports to see if HD7970 is powerful enough with madVR Jinc3+AR in this case. Need nevcairiel to find out the solution to enable UHD decoding on AMD/ATi GPU again. :D

[wanezhiling]

Need nevcairiel to find out the solution to enable UHD decoding on AMD/ATi GPU again. :D
http://forum.doom9.org/showpost.php?p=1608909&postcount=1807

[renethx]

A IVB processor (Core i3 or higher) with LAV Video Decoder's Intel Quick Sync is good for 4K UHD H.264 decoding (works with AMD and NVIDIA, of course). Tested with RED-Multi(120mbs).mkv (http://e-nautia.com/vanden/disk?p=2148838) (24p) and [V6. 4K UHD p] Spring.mkv (http://www.4shared.com/folder/_WSZLJmV/) (60p).

Celeron G1610, the cheapest IVB processor, can decode every 4K UHD H.264 just fine, at least with DXVA2 (native) (that won't work with a discrete card, of course). Unfortunately, Intel QS requires more power than DXVA2 (native) and Celeron is not good enough. Pentium IVB? Maybe, but I didn't test. Core i3-3220/3225 is fast enough.

HD 7770 is good enough for downscaling 4K UHD 60p to FHD with Jinc3+AR/C-R+AR+LL (maybe with slight OC). HD 7970 is good enough to upscale SD/HD/0.75FHD/FHD 60i/p to 4K UHD with Jinc3+AR/Jinc3+AR. (0.75FHD = 1440x1080.)

[Plutotype]

LAV Video Decoder's Intel Quick Sync (e.g. Core i3-3225) is good for 4K UHD H.264 decoding (works with AMD and NVIDIA, of course). Tested with RED-Multi(120mbs).mkv (http://e-nautia.com/vanden/disk?p=2148838) (24p) and [V6. 4K UHD p] Spring.mkv (http://www.4shared.com/folder/_WSZLJmV/) (60p).

HD 7770 is good enough for downscaling 4K UHD 60p to FHD with Jinc3+AR/C-R+AR+LL. HD 7970 is good enough to upscale SD/HD/0.75FHD/FHD 60i/p to 4K UHD with Jinc3+AR/Jinc3+AR. (0.75FHD = 1440x1080.)

Thanks for this post.

[hulkss]

I posted some instructions that work for me over at the JRiver forum: How To Get Perfect Video Color (http://yabb.jriver.com/interact/index.php?topic=78302.0)

[dansrfe]

I posted some instructions that work for me over at the JRiver forum: How To Get Perfect Video Color (http://yabb.jriver.com/interact/index.php?topic=78302.0)

Thank you very much.

[cyberbeing]

Experienced a random freeze while seeking a WMV:

madVR 0.85.8
LAV Video 0.55.3 (Microsoft WMV DMO)
LAV Audio 0.55.3
WM ASF Reader

Freeze Report (http://www.mediafire.com/?g7bgup897vpa4pk)

Edit 2/19: Another freeze while seeking a WMV, but this time it hung MPC-HC entirely so a Freeze Report was unable to be generated. I'd suspect this is probably a LAV Video bug rather than a madVR bug, but the randomness of the freeze make it difficult to confirm.

[Nekomata]

Experienced a random freeze while seeking a WMV:

madVR 0.85.8
LAV Video 0.55.3 (Microsoft WMV DMO)
LAV Audio 0.55.3
WM ASF Reader

Freeze Report (http://www.mediafire.com/?g7bgup897vpa4pk)

Edit 2/19: Another freeze while seeking a WMV, but this time it hung MPC-HC entirely so a Freeze Report was unable to be generated. I'd suspect this is probably a LAV Video bug rather than a madVR bug, but the randomness of the freeze make it difficult to confirm.

I use the same configuration if i remember correctly WMV DMO is disabled by default in lav filter...

[nevcairiel]

I use the same configuration if i remember correctly WMV DMO is disabled by default in lav filter...

You remember wrong.

What i see in the freeze report is that madVR is doing a CFGManager.EnumFilters right now, and from what i know, thats a operation not really safe during graph building, because it can easily deadlock (because it'll hold a lock on the filter graph)
The freeze report indicates that you're in the process of opening a file, and not seeking...? Maybe the WM ASF reader just does odd things when seeking, who knows, at least it seems to re-open the codec.

[madshi]

The freeze report also mentions seeking. So I suppose the freeze comes from a combination of (1) seeking, (2) WM ASF reader doing funny things when seeking and (3) madVR doing EnumFilters once in a while. I guess I could limit the EnumFilters to only be done when DVD playback was detected when the pins were connected. The only reason I'm using EnumFilters is to get the state of DVD playback.

[nevcairiel]

Seems to at least not be something that needs doing on seeking.. :)

[madshi]

FWIW, it's not being done as a result of the seeking, it's being done in a timer event, which in the freeze situation just happens to be executed at the same time as seeking.

[madshi]

madVR v0.86.0 released

http://madshi.net/madVR.zip

* added smooth motion frame rate conversion algorithm
* added settings page for smooth motion frc configuration
* added "trade quality for performance" option for smooth motion frc
* added test patterns to madTestPatternSource to test smooth motion frc
* fixed: RGB input with odd width/height is now accepted untouched
* fixed: IVideoWindow::put_Owner() failed when pins were not connected yet
* fixed: madHcCtrl.exe autostart registry entry was incorrect / not working
* fixed: occasional crash when using DXVA scaling with high-bitdepth content
* fixed: green line at the left image border when using DXVA scaling
* file "settings.bin" is not written into win7/8 "VirtualStore", anymore
* slightly improved multi monitor behaviour (when using DXVA or MPC-BE)
* filter enumeration timer is now only active during DVD playback
* extended logging for fullscreen exclusive presentation queue
* internal software video decoders are now disabled by default (again)
Introducing the new "smooth motion" frame rate changer (FRC) with the following main features / benefits:

(1) Can convert any source frame rate to any display refresh rate, while maintaining smooth motion.
(2) Endless playback without frame drops/repeats (if your PC is fast enough) without needing Reclock.

There are disadvantages, too, of course:

(1) Slightly higher GPU usage (not too much) with default settings.
(2) Some sharpness loss (almost invisible with 23-25fps -> 60Hz conversion).

23-25fps -> 60Hz: minimal sharpness loss, nearly invisible
24fps -> 24Hz: visible sharpness loss
60fps -> 24Hz: very noticeable sharpness loss

Basically the higher the refresh rate, the better. And the lower the source framerate, the better.

There's a new version of the madTestPatternSource filter (http://madshi.net/madTestPatternSource.zip) available. It's now a separate download because it increased in file size quite a lot, due to the new test patterns for smooth motion.

Technically the FRC algorithm simulates a display with infinite refresh rate. Which means that every video frame is displayed exactly when the timestamps ask for it. Consequently the motion smoothness depends on proper timestamps. If the timestamps (or audio clock) contain jitter, the playback will contain jitter, too. So even if Reclock might not be needed to avoid frame drops/repeats, anymore, when using madVR's new FRC algorithm, you might still want to use Reclock, because it provides a stable and reliable audio clock with very low jitter, and it supports WSAPI exclusive mode, too. You can however slave Reclock to the audio hardware clock, if you want. Having Reclock fully enabled with audio resampling is still possible, though, it shouldn't harm madVR's FRC algorithm.

To my best knowledge madVR is now the only way to playback Blu-Ray/DVD movies without 3:2 pulldown judder on displays which don't support 23.976Hz playback properly. I don't think any hardware Blu-Ray player can do that, or even any of the expensive video processors. (Correct me if I'm wrong).

One last hint: There's a new "trade quality for performance" option in the madVR settings which affects the quality of the FRC frame blending. By default frame blending is done in gamma corrected light, which is fast, but not mathematically correct. If your GPU is fast enough, it's highly recommended that you disable the "trade quality" option for highest image quality. There are no negative side effects to blending frames in linear light - except for higher GPU usage, of course.

P.S: Just to avoid confusion: madVR's smooth motion FRC does *NOT* modify audio in any way. Playback speed is not affected at all. The only thing that changes is that motion looks much smoother, if the display refresh rate isn't an even multiple of the source framerate.

[nevcairiel]

Since you say accurate timestamps are important, how bad would the usual MKV timestamps be, which typically are just in ms precision? (for 24p, 41ms and 42ms alternating, giving a good average)

[madshi]

MKV timestamps shouldn't be a problem. I was thinking of much higher volume jitter. But in any case, I haven't done too much testing yet, so we'll have to wait and see how it works in real life.

[ryrynz]

24fps -> 24Hz: visible sharpness loss


Is this a typo? Why wouldn't MadVR just not do anything here?

[andyvt]

madVR v0.86.0 released

To my best knowledge madVR is now the only way to playback Blu-Ray/DVD movies without 3:2 pulldown judder on displays which don't support 23.976Hz playback properly. I don't think any hardware Blu-Ray player can do that, or even any of the expensive video processors. (Correct me if I'm wrong).


Impressive.

Any idea where the cut off is in GPUs levels for this feature (do you need a double PCIe dGPU to use it or is HD4000 good enough)?

[madshi]

Is this a typo? Why wouldn't MadVR just not do anything here?
No, it's not a typo. Of course that only applies if FRC is turned on, which is not the default setting for 24fps -> 24Hz. But you can turn it on, if you want. The benefit would be endless playback with no dropped/repeated frames, without needing Reclock audio resampling. You'd lose sharpness, though. Basically whenever you turn FRC on, madVR simulates a display with infinite refresh rate by using frame blending.

Any idea where the cut off is in GPUs levels for this feature (do you need a double PCIe dGPU to use it or is HD4000 good enough)?
The GPU cost is really small. My HD4000 can do it with ease even with linear light frame blending. Just give it a try...

[andyvt]

The GPU cost is really small. My HD4000 can do it with ease even with linear light frame blending. Just give it a try...

Of course! Just wanted to keep my expectations in check until I have time (unfortunately not until later tonight).

[pirlouy]

How do you blend images for 24->60 ? Is this a Madshi © ?
For 240 Hz, is this something like xxMyyxxMyy (with x, y frames from video, and M a madVR calculated image) ? Or is it smarter ? Does it break the movie theater effect (of 24 fps) ?

Sorry for all these questions, you're not obliged to answer. :)

[ryrynz]

Of course! Just wanted to keep my expectations in check until I have time (unfortunately not until later tonight).

Have been using the HD4000 with frame blending and it looks like you wouldn't want to have Jinc enabled with it, it's too demanding, GPU useage around 75% is introducing stuttering.

Using Lanczos 3 AR and Bicubic 75 AR, I unticked use linear light for frame blending and panning scenes are incredibly smooth, The HD4000 seems a bit problematic when GPU hits about 75% so using Lanczos instead brings it down to 55-70% depending on the content with zero issues so far.

It really is amazing. Video quality just went up another notch, cheers Madshi!

[leeperry]

w00t, more features! :thanks:

I just bought a 120Hz projector, hopefully I won't be needing a GTX670 should I like the 24p>120Hz blending in Jinc3AR :D

[DeadlyEmbrace]

Wow, Smooth Motion Frame rate is really impressive! :D
Gave it a try on some really juddery scenes and the results are perfect.
Thanks for all the hard work Madshi, really appreciate it! :D

[madshi]

For 240 Hz, is this something like xxMyyxxMyy (with x, y frames from video, and M a madVR calculated image) ? Or is it smarter ?
I'm showing the original frames untouched as often as possible, but I'm showing blended frames as often as necessary to achieve the visual effect of a display with infinite refresh rate. There's no fixed pattern for specific framerate -> refresh rate combinations. The exact blending factors (and whether blending is needed at all) are calculated for every vsync interval. The blending factors usually change all the time.

Does it break the movie theater effect (of 24 fps) ?
No. Basically if you let madVR FRC 24fps content to 60Hz, the end result should look almost identical to displaying 24fps on a properly implemented 24Hz display.

[JarrettH]

So would the best setup for this be to continue to use your monitor's supported display modes and the "only if there would be motion judder without it" option?

OR

Blank out those display modes and use 60hz for everything?

Thanks for your work with this nice new feature madshi :cool:

[madshi]

w00t, more features! :thanks:

I just bought a 120Hz projector, hopefully I won't be needing a GTX670 should I like the 24p>120Hz blending in Jinc3AR :D
Scaling is done *before* frame blending. So the cost of FRC is totally independent of the scaling algorithm. Meaning if you let madVR FRC a Blu-Ray movie to 120Hz, the cost of using Jinc3 AR is not higher than when using 24Hz. Of course there will be added cost for the frame blending and 120Hz presentation, but that's much lower compared to Jinc3 AR.

So would the best setup for this be to continue to use your monitor's supported display modes and the "only if there would be motion judder without it" option?

OR

Blank out those display modes and use 60hz for everything?
Some displays accept 24Hz but still show 3:2 judder due to internal conversion to 60Hz. You should test whether your display supports smooth 24Hz playback. You can use the new "madTestPatternSource" test patterns for that. If your display can do 24Hz just fine then you don't really need the new FRC algorithm. Of course you could also use 60Hz for everything. Some displays flicker with 24Hz, so for those maybe using 60Hz for everything could make sense. Only your eyes can be the final judge of what looks better in the end.

[Gelatinous]

off the bat i was fiddling with my settings and everything seems to have reset itself (i usually delete the contents of the madVR folder before installing a new version, since settings were stored elsewhere)

though i can't make the new settings save unless i run mpc as administrator (madvr 0.86, installed in MPC's folder which requires admin rights to edit files)

that aside, the smooth motion is working well for me too; thanks for the new release.

[nevcairiel]

I'll have to do some extensive testing on the weekend, maybe i can switch my TV into its 4:4:4 mode and run it at 60Hz if it looks close to what my TV does with 24Hz input... :) (24p in the 4:4:4 mode looks a bit odd because it disables its internal interpolation things)

[madshi]

off the bat i was fiddling with my settings and everything seems to have reset itself (i usually delete the contents of the madVR folder before installing a new version, since settings were stored elsewhere)

though i can't make the new settings save unless i run mpc as administrator (madvr 0.86, installed in MPC's folder which requires admin rights to edit files)
Settings are stored in the registry, too. Please check "HKEY_CURRENT_USER\Software\madshi\madVR\Settings". MPC-HC should have write access to that, so madVR should be able to store its settings there. Not sure why that doesn't work for you. It seems to work just fine here.

I'll have to do some extensive testing on the weekend, maybe i can switch my TV into its 4:4:4 mode and run it at 60Hz if it looks close to what my TV does with 24Hz input... :) (24p in the 4:4:4 mode looks a bit odd because it disables its internal interpolation things)
Let us know what you find! :)

[bugmen0t]

What happens if you slow down 25p to 24p using ReClock? Will madVR do 25p or 24p conversion to 60 Hz then?

[JarrettH]

oh I figured for 24hz that would be best, but this monitor only supports 50, 59, and 60. In that case should I just be using 60hz since you said the higher the refresh rate the better?

Edit: It might be a good idea to only use Smooth Motion in full screen. For some reason I get a heck of a lot of dropped frames if it's on when I initially open a video in windowed

[Nevilne]

Some initial thoughts: looks smooth, about the same for 24>60 frc and 24>25>50 reclocked, frame blends don't stand out. There are some bugs with seeking.

simple right to left pan 24>60:

frc linear light off: http://i7.minus.com/iWJbce3Hi8j7S.png
frc linear light on: http://i2.minus.com/ifQIl8vKfENOJ.png

but it's hard to catch exact frame (pause goes to "real" frames) so these might be quite different blend amounts.

What would be suggested settings if I want to keep reclock just as audio renderer?

[ryrynz]

Can get the odd bit of stuttering going between windowed into fullscreen with smooth motion enabled specifically with overlay on, would be nice to have a smoother transition into fullscreen at a later stage.

[madshi]

What happens if you slow down 25p to 24p using ReClock? Will madVR do 25p or 24p conversion to 60 Hz then?
Try it and report here! (I think it should work just fine.)

oh I figured for 24hz that would be best, but this monitor only supports 50, 59, and 60. In that case should I just be using 60hz since you said the higher the refresh rate the better?
Yes, if your monitor only supports those than for 23-25fps content I'd choose 59Hz or 60Hz (the difference between 59.940Hz and 60.000Hz is too small to make a meaningful difference in this case).

Some initial thoughts: looks smooth, about the same for 24>60 frc and 24>25>50 reclocked
That is high praise because "24>25>50 reclocked" like smoothness is the ultimate goal of the FRC algorithm.

There are some bugs with seeking.
Could you be any more unspecific? :p

simple right to left pan 24>60:

frc linear light off: http://i7.minus.com/iWJbce3Hi8j7S.png
frc linear light on: http://i2.minus.com/ifQIl8vKfENOJ.png

but it's hard to catch exact frame (pause goes to "real" frames) so these might be quite different blend amounts.
Yes, the blend factors will differ everytime you restart playback. You can still see some basic differences in blending behaviour between the two images you uploaded, though. If your GPU can handle it, definitely use linear light blending.

What would be suggested settings if I want to keep reclock just as audio renderer?
Probably the first FRC option, I would say.

Can get the odd bit of stuttering going between windowed into fullscreen with smooth motion enabled specifically with overlay on, would be nice to have a smoother transition into fullscreen at a later stage.
Hopefully that is only temporary? Meaning after a very short time playback goes back to totally smooth by itself?

-------

TIP: You can compare smooth motion on/off very nicely by assigning keyboard shortcuts for FRC on/off in the madVR settings dialog. I've added separate keyboard shortcut options exactly for this purpose.

[ryrynz]

Hopefully that is only temporary? Meaning after a very short time playback goes back to totally smooth by itself?


Yup it's only temporary.

[sidi0us]

I can't believe it works with an Intel HD 2500, this is just awesome, you just set madVR to a whole new level.

Regarding reclock, if I leave it to auto, 24 fps adaptation (60 Hz LCD), will it cause any problems to madVR, or should I disable media adaptation? Thanks.

[mark0077]

Thanks madshi, fantastic work on 0.86.0. Can I get you're opinion on something. I use SVP to interpolate to somewhere around 59.996fps as this is the highest rate I can use on my 60.00173hz display without seeing frame drops. The only "problem" with this is its very cpu / gpu intensive, especially when the target rate is not a nice multiple of the display rate, so for me going from 23.976... to 59.996 is much more intensive than 23.976... * (5 / 2) = 59.94

I'm wondering do you think its a good option for those of us that want the smoothness of something like SVP with these nice multiples (to reduce cpu / gpu usage, or to increase SVP's quality settings), but with the accuracy of having something that helps us get 0 drops / repeats, could use SVP with your smoothing set to "always" to achieve the best of both? Is madVR theoretically going to kick in at those times when ordinarily this exact multiple 59.94 output from SVP, might not be accurate enough, and cause a frame repeat / drop on my display at 60.001 (which needs 59.996 to not drop / repeat anything).

I hope this all makes sense, and thanks again.

[Nevilne]

Hmm, when playing back 30 fps on 60 it enables frc with first frc option, is that intended?


There are some bugs with seeking.

Could you be any more unspecific? :p

Sorry! If you seek during playback and if "delay playback start after seeking, too" is unchecked and "use a separate device for presentation" is checked, the previous frame will flicker for a few frames after seek.



What would be suggested settings if I want to keep reclock just as audio renderer?

Probably the first FRC option, I would say.

Hehe, I meant the reclock settings, i'm just worried that it might mess up playback speed somehow.

[cyberbeing]

In the next version could you add a setting to disable FRC for close matching refresh rates?

A) Disable FRC when refresh rate is within 0.001Hz of video frame rate multiple.

OR

B) Disable FRC when "dropped/repeat every..." calculation is greater than X hours?

OR

C) Disable FRC with video display frame rates greater than XXfps

OR

D) Disable FRC based on a complex refresh rate to frame rate exclusion list


My GT440 DDR5 (overclocked) needs to make too many quality compromises for 1440x1080->1920x1080 59.94fps deinterlacing, 1920x1080 59.94fps deinterlacing->1600x900 95.904Hz, and 1280x720->1920x1080 59.94fps @ 119.88Hz to be playable with FRC enabled. Horrible blurring artifacts occur whenever the render queue drops below half-full from my GPU being too slow. This is particularity a problem when entering fullscreen, since the queues empty and need to fill up again faster than realtime. Overall I don't seem to be seeing any smoothness benefit with FRC when using 23.976fps @ 95.904Hz & 23.976fps/29.97fps/59.94fps @ 119.88Hz, but as mentioned above the main problem is my GPU being too slow to do 1280x720/1440x1080 59.94fps/60fps -> 1920x1080 119.88Hz or 1920x1080 59.94fps/60fps -> 1600x900 with decent settings. In these specific cases my GPU was already being pushed very hard in previous madVR versions with minimalistic settings, so there isn't really any headroom for the extra GPU load from FRC.

Edit: The Keyboard shortcut for FRC may also be more useful as a Toggle rather than separate Enabled / Disable

[dansrfe]

This is my first time using the madTestPatternSource. I just looked at the SmoothMotion24.ytp file and madVR automatically switched the refresh rate to 48Hz, as I had specified in the refresh rate changer, but the lines at the bottom flicker quite a bit. Does this mean that the display is internally converting the 48Hz signal to 60Hz?

PS: I tested this with v0.85.8 (so no frp). Not sure if that makes a difference when using test patterns with madTestPatternSource though. Does it?

Also, what should I be looking for when viewing the colors.ytp and grayramp.ytp files?

Why is there an option in the smooth motion settings page for "... or if the display refresh rate is an exact multiple of the movie frame rate"? I thought that was a good thing... If 24 fps is being played back at 24Hz, 48Hz, 96Hz, or 120Hz then there shouldn't be any need for smooth motion frame rate conversion, right? I'm slightly confused.

Thanks madshi!

[trip_let]

Maybe this is the obvious and expected result, but I tested...

23.796 -> 59.94 playback
23.796 -> 59.94 playback with smooth motion FRC
23.796 -> 71.93 playback

on my nominal 60 Hz 1080p eIPS monitor. 71.93 is through custom timing in Intel control panel on HD 4000, which can't seem to do 71.928 exactly. FRC beats no FRC on 59.94 (blending looks pretty good overall, as in generally harder to notice and less offensive than juddering), but having an integer factor is better than that. I would say that in my limited impression so far, though there are different processes and things going on under the hood, subjectively I think the 59.94 FRC is closer to the 71.93 in "quality" than it is to the original raw 59.94.

Anyhow, very impressive work!

[Plutotype]

I'm showing the original frames untouched as often as possible, but I'm showing blended frames as often as necessary to achieve the visual effect of a display with infinite refresh rate. There's no fixed pattern for specific framerate -> refresh rate combinations. The exact blending factors (and whether blending is needed at all) are calculated for every vsync interval. The blending factors usually change all the time.


No. Basically if you let madVR FRC 24fps content to 60Hz, the end result should look almost identical to displaying 24fps on a properly implemented 24Hz display.

So are there any motion sharpness or less flickering benefits when playing back 24fps on 60Hz ( or even higher refresh rates ) with FRC on?
Thanks for the new version anyway, I like this new feature.

[robpdotcom]

Small request: Can you make the keyboard shortcut for frc into a toggle? One shortcut to turn off/on, instead of one to turn on and another to turn off?

[Qotscha]

I have similar problems when using dxva2 decoding. If I open a new file while playing a video in fullscreen exclusive mode on my secondary display, I often get a black screen or a MPC HC (or BE) crash. With software decoding everything works flawlessly.

0.86.0 fixed these problems :thanks:

[n3w813]

I was skeptical at first when I read the release notes for 0.86.0 on smooth motion...I had to leave work early just so I can try it out at home.....

After testing, WOW, no judder at all with 23.976 sources running at 60Hz :eek:. As good as 24p with manually adjusted custom resolution settings plus Reclock. (I think it might be even smoother)

One downside though, I definitely see some loss of sharpness/clarity. Not much, but noticeable.

:thanks: a bunch Madshi!!!

[pie1394]

No, it's not a typo. Of course that only applies if FRC is turned on, which is not the default setting for 24fps -> 24Hz. But you can turn it on, if you want. The benefit would be endless playback with no dropped/repeated frames, without needing Reclock audio resampling. You'd lose sharpness, though. Basically whenever you turn FRC on, madVR simulates a display with infinite refresh rate by using frame blending.


Does the FRC option handle the Variable Frame Rate contents (Ex: 24p + deinterlaced 60p OP/ED anime) like this?

23.976 / 24 fps --> 23.976 / 24Hz (direct, no blending)
59.94 / 60 fps --> 23.976 / 24 Hz (motion blur)


madVR causes heavy playback stutters at the specified refresh rate when it presents the non-24fps contents in the middle of video files.

i.e. Japanese ISDB-T 24fps animes contents with horizontal scrolling texts. It looks like the broadcaster's encoding equipments are always to merge the scrolling text's video at 60-field rate instead of 24/30 full-frame rate.

[JarrettH]

Yes, there is an ever so slight reduction in sharpness. Maybe disabling anti-ring could "counter" that.