madVR - high quality video renderer (GPU assisted)

[huhn]

so you fix a dropped repeated frame by still seeing the drop repeated and a blurred frame? to minimise blur you use the highest available refresh rate. 1 frame per input frame is blended that means with 60 HZ you have a blended frame on for ~16 ms but for 120 hz for ~8 ms with other words the higher the refreshrate the lower the blurred frames are on the screen.

sorry but you tried to use it a 24 HZ which should be utterly illegal or with other words only be used to prove that it should not be used like that.

SVP is a frame interpolation algorithm not only has it little to nothing todo with SM it's also in capable of fixing frame repeates/drops because it is just integar based not using the audio clock as reverence and it'S also pretty impossible to motion interpolate a fraction of a ms.

it can't even do 24 to 60 it doing 120 and just throws half the frames away including the originals that's not part of a bad implementation it's just as good as it get's

[flossy_cake]

Well the best solution is to slightly nudge the monitor refresh to sync with audio clock and minimise "1 drop every..." and this is what I'm using, but sadly not reliable across all systems.

120hz & 144hz are divisible by 24 so no gain for SM at removing judder.

For hiding a dropped frame every 10 minutes, it seems that SM would still blend for 9.999 minutes leading up to the drop @ 10 mins, so I'm not sure how higher refresh rates would help minimise SM blur.

I do agree that higher refresh rates should help hide the dropped frame as in the case of 120hz the drop should be a 8ms stutter instead of 16ms stutter for 60hz. But 8ms is still going to be noticeable, and most HDTVs in the wild are 60hz max.

SVP's motion vectors would be better at interpolating between the skipped frame, but I'm not sure it could be configured that way.

[huhn]

wow that's disappointing.

i never talked about how 120 hz shortes dropped frames which are less notable (but need far more because they are only correcting 8 ms if madVR would even work like that which i never tested because why would i)


For hiding a dropped frame every 10 minutes, it seems that SM would still blend for 9.999 minutes leading up to the drop @ 10 mins, so I'm not sure how higher refresh rates would help minimise blur.
it will never reach the dropped or repeated frame because the audio and video are always in perfect sync at all times it does not drift madVR only calculates the numbers for you that's all.
the deviations is correct all the time with no pause.

For hiding a dropped frame every 10 minutes, it seems that SM would still blend for 9.999 minutes leading up to the drop @ 10 mins, so I'm not sure how higher refresh rates would help minimise SM blur.
that's how
1 frame per input frame is blended that means with 60 HZ you have a blended frame on for ~16 ms but for 120 hz for ~8 ms with other words the higher the refreshrate the lower the blurred frames are on the screen.

let me do some math here even through you are most likely going to ignore it like other the other things i have listed:
if you use SM at 24 with a 24p source you will get blended frames with the length of 42 ms every 42 ms
or in short you get garbage on the screen.
makes total sense very simple math.
if you play 24p at 60p you will get 16 ms of blended frames every ~3 frames with means you don't get garbage on the screen. ~1/3 of all displayed frames are blended the rest is original
and now we comes to 120 with 120 hz you get 8 ms of blended frames every 6 frames about 1/6 of all displayed frames are blended for barely any time at all.
I do agree that higher refresh rates should help hide the dropped frame as in the case of 120hz the drop should be a 8ms stutter instead of 16ms stutter for 60hz. But 8ms is still going to be noticeable, and most HDTVs are 60hz max.
the blended frame duration is 8 ms not the dropped repeate frame time...

SVP's motion vectors would be better at interpolating between the skipped frame, but I'm not sure it could be configured that way.
no why would it be it makes zero sense the interval is still interrupted by 42 ms with a drop there are now 42 ms missing and with a repeat 42 are repeated interpolation or not doesn't change that.
i talked about that before.
SVP is a frame interpolation algorithm not only has it little to nothing todo with SM it's also in capable of fixing frame repeates/drops because it is just integar based not using the audio clock as reverence and it'S also pretty impossible to motion interpolate a fraction of a ms.

it can't even do 24 to 60 it doing 120 and just throws half the frames away including the originals that's not part of a bad implementation it's just as good as it get's

[e-t172]

If you want to experiment with various ways of doing frame blending, try out the time interpolation (https://github.com/mpv-player/mpv/wiki/Interpolation) options in mpv (--interpolation, --tscale, etc.), which has lots and lots of various algorithms to try (including one that is similar to madVR Smooth Motion). For me it was a great way to convince myself that the approach madVR uses is probably the best one - other approaches tend to come with very obvious, very obnoxious motion blur.

[flossy_cake]

120 with 120 hz you get 8 ms of blended frames every 6 frames about 1/6 of all displayed frames are blended for barely any time at all.

Not if SM weights the blending by how close it is to the next/previous video frame, which is the premise I was writing under.

Going by the link in e-t172's post, it seems that is NOT how SM works -- it only blends 50% with next/prev frame, and no other amount of blending is used other than 50%.

Why do I believe this? I took a dozen screenshots of SM frames (24@60hz) and they all have the same amount of 50% blending like this:

https://i2.lensdump.com/i/rb4Up5.png

I am not sure why there would be any blended frames with 24@120hz as 120 is evenly divisible by 24.

However my 120hz mode is tuned to 59.94x2 so 23.976 goes evenly, maybe that's why.

[huhn]

i recommend you to read up some math stuff.

it needs 1000 of frames to move the blending around it is not 50/50 a dozen doesn't mean anything and if you don't have a clock deviation it will not move at all.

if you get a frame drop every 40 min that with 24p that's 54600 frames to get it deviate by ~42 ms

seriously just throw 25 at 24 no no no throw 60 at 24 and tell me that it is only blending 50 %
i can't wait for your explanation with "dozen" of screenshoots.

[flossy_cake]

Going by the link in e-t172's post, it seems that is NOT how SM works -- it only blends 50% with next/prev frame, and no other amount of blending is used other than 50%.

This screenshot of 30.000fps video displayed at 59.94hz appears to indicate otherwise -- note the grey is darker on the left side than right side -- not a 50% blend.

https://i3.lensdump.com/i/rb7nFq.png
https://www.youtube.com/watch?v=-Ht8EIAOrj8



if you get a frame drop every 40 min that with 24p that's 54600 frames to get it deviate by ~42 ms

That's what I thought too, but then I did a test with 23.976@23.8hz to induce a frame drop every 5 seconds and it was blending 4/5ths of the time. I was expecting it to blend only for a short amount of time.



seriously just throw 25 at 24

I tried 24@50hz and it spends majority of time blending too. So SM is definitely weighting it, I just don't understand how the weights work cause with 24@60hz we DON'T get weighting like this:

Refresh# 60hz interval 24fps frame# 24fps interval Blend weight Blend formula
1 0ms 1 0ms 0% (0-0)/41.6
2 16.7ms 1 0ms 40% (16.7-0)/41.6
3 33.3ms 1 0ms 80% (33.3-0)/41.6
4 50.0ms 2 41.6ms 20% (50.0-41.6)/41.6
5 66.6ms 2 41.6ms 60% (66.6-41.6)/41.6
6 83.3ms 3 83.3ms 0% (83.3-83.3)/41.6
7 100.0ms 3 83.3ms 40% (100.0-83.3)/41.6
8 116.6ms 3 83.3ms 80% (116.6-83.3)/41.6
9 133.3ms 4 125.0ms 20% (133.3-125.0)/41.6
10 150.0ms 4 125.0ms 60% (150.0-125.0)/41.6
11 166.6ms 5 166.6ms 0% (166.6-166.6)/41.6

Maybe Madshi wrote an exception to the rule for 24@60 since limiting it to 50% weighting in this mode reduces the total amount of blending by quite a lot. Or maybe his algorithm just naturally determines the best way to minimise total blending.

[huhn]

yes he wrote that it fixes deviation by simulating a unlimited frame rate screen.

but more important do these files even have audio?

it's "simply" (not easy to programm) vsync time changed by audio clock (42 ms treated as 43 ms)
now you take the 43 ms and look what is displayed at it for example frame 1 for 8 ms and frame 2 for 35 so you blend in linear light 8/43 frame one and 35/43 and present it(not in linear light).

[flossy_cake]

but more important do these files even have audio?

The pendulum one I didn't bother remuxing an audio track because I'm not using it to minimise drops, only to induce drops so I can try to understand how SM algorithm works in different scenarios.


now you take the 43 ms and look what is displayed at it for example frame 1 for 8 ms and frame 2 for 35 so you blend in linear light 8/43 frame one and 35/43 and present it(not in linear light).

Yes but I'm not sure that is how SM works @120hz because 24 goes evenly 5:5 into 120hz & I took screenshots and couldn't find any blended frames.

[flossy_cake]

You don't want to use smooth motion when the source frame rate almost equals the display's refresh rate

This is consistent with what I'm observing, so SM is not good at minimising "1 frame drop every n minutes" but in theory I think it could be if its algorithm was tweaked a little.


but it is great when the display's refresh rate is much higher


This is consistent with huhns comments, but it's not quite correct because 24@120 doesn't appear to have any blended frames given the 5:5 cadence. So cadence needs to be unsmooth, then yes higher refresh will give better results.

But higher refresh will give better results anyway even with SM off, since the rendered frame will "land" closer to a refresh cycle as there are more refreshes available. An easy way to think about this is a hypothetical 1000hz display (refresh every 1ms) in which max stutter will be 1ms regardless of the video fps since the longest wait till next refresh cycle is only 1ms, and a 1ms stutter is probably invisible.

[huhn]

This is consistent with what I'm observing, so SM is not good at minimising "1 frame drop every n minutes" but in theory I think it could be if its algorithm was tweaked a little.
yeah just blend 2 frames together when it comes up so we get a drop and a repeat at the same time terrible idea.

at 120 HZ you have the except same issue as 24 and SM fixes it the fact that you are unable to find the blended frames should tell you volumes...


This is consistent with huhns comments, but it's not quite correct because 24@120 doesn't appear to have any blended frames given the 5:5 cadence. So cadence needs to be unsmooth, then yes higher refresh will give better results.

yes i'm incorrect because you can't find a repeated/drop frame with a screenshoot?

small tip there are blended frames and another tip there is something called video capture. it's very powerful.

But higher refresh will give better results anyway even with SM off, since the rendered frame will "land" closer to a refresh cycle as there are more refreshes available. An easy way to think about this is a hypothetical 1000hz display (refresh every 1ms) in which max stutter will be 1ms regardless of the video fps since the longest wait till next refresh cycle is only 1ms, and a 1ms stutter is probably invisible.

25 at 120 look absolutely horrendous without SM because you make that way to simple.

[Asmodian]

This is consistent with what I'm observing, so SM is not good at minimising "1 frame drop every n minutes" but in theory I think it could be if its algorithm was tweaked a little.

That isn't quite right. It is great for fixing "1 frame drop every n minutes" but not when the frame rate is equal or close to the source frame rate.

So for 24 FPS content on a 120 Hz display smooth motion is ideal, totally fixing any timing issues and eliminating dropped or repeated frames with very little downside.

[Filmgeek47]

Has anyone run into the issue of the custom display modes tab vanishing? Trying to change my pixel clock to eliminate a frame drop every 50 minutes, and despite my display being the active one I still don’t get that tab.

[Balling]

That isn't quite right. It is great for fixing "1 frame drop every n minutes" but not when the frame rate is equal or close to the source frame rate.

So for 24 FPS content on a 120 Hz display smooth motion is ideal, totally fixing any timing issues and eliminating dropped or repeated frames with very little downside.

You do not need to remove repeated frames in 24 --> 120 (or /1.001), because every frame will be just repeated 5 times and it will be perfect.

[huhn]

you have followed the topic at least a little have you?
because no that's not how the world works.

[flossy_cake]

yes i'm incorrect because you can't find a repeated/drop frame with a screenshoot?

small tip there are blended frames and another tip there is something called video capture. it's very powerful.

Is this with 23.976 @ 120.00hz or 119.88hz?

That isn't quite right. It is great for fixing "1 frame drop every n minutes" but not when the frame rate is equal or close to the source frame rate.

You're right & and I was mistakenly writing within the context of tuning my 23.976hz mode for 23.976 content. At 60hz obviously SM is visibly blending with 23.976 content regardless of "1 frame drop every..." value.

[huhn]

Is this with 23.976 @ 120.00hz or 119.88hz?

the only thing that matter is if it is active or not the refreshrate it self is irrelevant it's relative to the audio clock don't forget this part.

it is blending with the audio clock as reference not the video clock else it would be useless for this.

[flossy_cake]

it is blending with the audio clock as reference not the video clock else it would be useless for this.

Yes but 23.976 @ 120.000hz is 1 drop every ̶8̶ ̶s̶e̶c̶ 41.6 sec vs minutes/hours for 119.880hz which might affect how much blending SM does. I need to do more tests though with video capture like you said.

[flossy_cake]

Went back and screenshotted both my 119.880 and 120.000 modes with 23.976 scrolling credits with SM set to always on and there are blended frames in both, so yeah not sure why I missed it the first time.

[flossy_cake]

not sure why I missed it the first time.

Seems to be a Windows/GPU bug -- if I restart Windows after changing the display mode then I get no blends on 119.88 and blends on 120.00.

Might be that bug with the desktop compositor being stuck at the previous refresh rate: https://forum.doom9.org/showpost.php?p=1955143&postcount=62103

Will need to do video capture to be sure.

[flossy_cake]

Did video capture with OBS of 119.88hz and 120.00hz with Windows restart in between and observe both have blended frames with 23.976 scrolling credits. Approx 1 every 2-3 frames blended. 120.00 seems to have slightly less blending.

[Bo.]

Guys, which subtitle renderer is preferred at the moment? I used XySubFilter (+MPC-BE + madVR), but it hasn't been updated in almost 4 years. I think maybe something more modern appeared during this time.

[Siso]

Guys, which subtitle renderer is preferred at the moment? I used XySubFilter (+MPC-BE + madVR), but it hasn't been updated in almost 4 years. I think maybe something more modern appeared during this time.

You can always use mpc-be's internal subtitle renderer.

[flossy_cake]

This is a wrong way to use CRU. You need to add VIC, not DTD. DTD timings are quite complex, compared to just normal VIC that are just mandatery supporting /1.001 multiplier.

I checked VIC timings here (https://web.archive.org/web/20171130183104/https://standards.cta.tech/kwspub/published_docs/CTA-861-G_FINAL_revised_2017.pdf) on page 26 and the 1080p24.000 mode (VIC 32, 72) is the same as what CRU chooses for "Automatic HDTV".

To derive the 23.976 mode it says we just adjust the refresh rate or pixel clock which can be done in CRU:

3. A Video Timing with a vertical frequency that is an integer multiple of 6.00 Hz (i.e., 24.00, 30.00, 48.00, 60.00, 120.00 or 240.00 Hz) is
considered to be the same as a Video Timing with the equivalent detailed timing information but where the vertical frequency is adjusted by
a factor of 1000/1001 (i.e., 24/1.001, 30/1.001, 60/1.001, 120/1.001 or 240/1.001). That is, they are considered two versions of the same
Video Timing but with slightly different pixel clock frequencies.

However CRU's "Automatic HDTV" timings for 2160p24.000 are different than CTA/CEA spec (no idea why).

btw this calculator (https://tomverbeure.github.io/video_timings_calculator) has column "CEA-861" which is same as CTA's VIC timings. But putting in decimal places for vertical refresh rate doesn't update the timing parameters correctly.

[scollaco]

Just wanted to report that using a RTX 3090 with an Intel Core i9-12900F on windows 11, all refresh rates are playing perfectly in madVR including 23.976 for 3840x2160. No custom resolutions needed at all to be made by me. I tested 2160p at 23.976, 24, 25 for various movie and tv show sources that I have. Frame drops reported come back as no drops/repeats for 2-3 days approx. As a side, all settings in madVR can be pushed to the max on this card and tonemapping can also use "are you nuts?!" for highlight recovery and "insane" for shadow recovery if you so wish and even with all of that, the card only gets to ~31ms rendering for 4K HDR at 23.976. I didn't test any 2160p 60hz movie/show material as I don't watch or have any of those. I imagine at 2160p 60hz, settings on the card will need to be dialed down a slight bit to be able to play without drops/repeats.

[Filmgeek47]

So I’ve googled the heck out of this issue and can’t find a solution. Tried disconnecting my AVR and even tried another display and PC and I still can’t get the custom modes tab to appear in MadVR. Is this just broken now?

[x7007]

it still has the chroma subsample position issue.

4:2:0 can be done at most refresh rates and resolution it's simply not supported by any end device.

if the bandwidth and frame rate falls into HDMI 1.4 range than 4:2:0 is usually (if not always) not available because HDMI 1.4 doesn't know what that is and devices like to keep such a signal HDMI 1.4 complain because that's much better supported.

Do you have enabled both of them? please try to disable and restart Explorer. also check windows 11 newest update it might fixed something

https://i.imgur.com/Y9jRLWU.png

[huhn]

the post is about the situation with HDMI and how it works and how it worked in the past and some general issue with signal difference and file types.

[flossy_cake]

Do you have enabled both of them? please try to disable and restart Explorer. also check windows 11 newest update it might fixed something

https://i.imgur.com/Y9jRLWU.png

If you are trying to smooth out chroma artefacts I seem to find "bilateral old" chroma upscaling works the best.

These are from the Family Guy DVD which has some chroma alignment issue baked into the video.

Nearest neighbour
https://i3.lensdump.com/i/rwT4AZ.png

Bicubic 60
https://i.lensdump.com/i/rwTKQP.png

NGU anti alias very high quality
https://i1.lensdump.com/i/rwTpnm.png

Bilateral old
https://i2.lensdump.com/i/rwT75i.png

NGU vs bilateral (animation)
https://i3.lensdump.com/i/rwTHTo.png

[chros]

Try out NGU Sharp instead of NGU AA.

[jkauff]

So I’ve googled the heck out of this issue and can’t find a solution. Tried disconnecting my AVR and even tried another display and PC and I still can’t get the custom modes tab to appear in MadVR. Is this just broken now?

You didn't mention what version of madVR you're using. Have you tried running "uninstall.bat" (as Administrator), then "install.bat" (also As Administrator)? As a last resort, set a Restore Point, then run "restore default settings.bat" to wipe out your settings and start fresh.

[flossy_cake]

Try out NGU Sharp instead of NGU AA.

Worse than nearest neighbour!

https://i2.lensdump.com/i/rwJrqv.png

Precisely this appearance of chroma artefact is why I was forced to abandon my Panasonic OLED some years ago -- I was constantly seeing these chroma artefacts on free to air television, it was unbearable. You would have an orange logo on a blue background and it always had those awful jagged spikey steps along curved edges just like in the above image. I suspect NGU requires a high quality source.

[huhn]

can you share a sample so i can proof that the file is broken(not to show how great NGU sharp as a chroma scaler is because it isn't just to show that they really failed here).

btw. bilateral is able to fix chroma channel mismatches to some degree because that's how it works but even it still fails utterly.
but bilateral also completely falls apart if no luma is there to guide it so what ever.

[Filmgeek47]

You didn't mention what version of madVR you're using. Have you tried running "uninstall.bat" (as Administrator), then "install.bat" (also As Administrator)? As a last resort, set a Restore Point, then run "restore default settings.bat" to wipe out your settings and start fresh.

I’ve tried it with multiple versions (I’m running the last non-time limited beta on my main system but I also had the same behavior on another PC with a fresh install of the release version).

[flossy_cake]

can you share a sample so i can proof that the file is broken

https://drive.google.com/file/d/12ToXaCimSozYjyVjiE_G5TDUlaVQZqUP/view?usp=sharing



btw. bilateral is able to fix chroma channel mismatches to some degree because that's how it works but even it still fails utterly.
but bilateral also completely falls apart if no luma is there to guide it so what ever.

What would you recommend instead? I'm after something that I don't have to tweak per file.

[x7007]

.
please try to disable what I post with the screenshot and tell me if it fixes your issue with 10bit. it works fine for me with those 2 off so one of them causes the 8bit fullscreen

maybe the windows 11 update now released yesterday fixed the issue totally need to check again with the enabled

[huhn]

the HDR bug is ranges it also effect computer games which are literally broken on win 11.

i don't have the AMD card connected to an HDR display anymore there is no point.
http://bugs.madshi.net/view.php?id=674
not like i'm alone.

flossy_cake
the file is utterly broken.
my guess the deint was done wrongly.
https://abload.de/img/chroma0pk9t.png
you should not judge a chroma scaler on this file.

NGU AA and super XBR are the high contender for good chroma scaler NGU sharp does good on sharp Chroma which is super rare.

[chros]

the file is utterly broken. my guess the deint was done wrongly.


Worse than nearest neighbour!

Now it makes sense. Try out with a progressive 1080p source, if you are interested.

[Grinchy]

Is there a big difference between luma NGU Medium and High?


Just replaced my 1050 Ti with an RTX 3070 (Asus), but I get really bad Coil Whine with NGU High. With Medium it's almost gone :-(

Someone knows a GPU without Coilwhine @ High?

[huhn]

yes there is but it's not much.

coil whine is random.

[flossy_cake]

Now it makes sense. Try out with a progressive 1080p source, if you are interested.

Kind of beside the point...

If you are trying to smooth out chroma artefacts I seem to find "bilateral old" chroma upscaling works the best.


When FOX was originally editing together the episodes they were using Adobe Premiere 6 for Mac which had various problems to do with splicing and changing the speed of clips which caused it to do nasty deinterlacing, so that includes when they Freeze-frame an entire frame or a portion of the frame...

...While the DVDs chroma location cannot technically be incorrect, it technically is. The DVDs use Chroma-location of 2 (top-left) or 1 (center) depending on the season. The problem here is that is not what the ITU e.t.c recommends for MPEG-2. Players like VLC, MPV, MPC e.t.c use a static chroma location to playback based on the codec instead of reading it from the metadata...

...S01E05's chroma position is incorrect, It's chroma is 1 pixel too far to the left. Originally I thought this to be a Chroma location value mistake, but it isn't, the chroma is simply encoded 1 pixel too far to the left.

The version on streaming services doesn't have these issues but is censored.

[huhn]

the sample has artifacts like it been scaled while still been interlaced. that's where these sharp edges come from.
and the chroma subsample position is not the only issue with the chroma location because it is not to the left it is shift to it is the bottos and i'm pretty sure it could be more then one pixel.

the blue bleeds out of the sign same for the red it bleeds into the blue both have a black boarder around them which supposable has a different chroma as can be seen in my Cb screenshoot.

the job of an chroma scaler is not to fix a totally messed up encode.

[flossy_cake]

the job of an chroma scaler is not to fix a totally messed up encode.

Yes & this was always about...

trying to smooth out chroma artefacts

for a source...

which has some chroma alignment issue baked into the video.

So I wasn't trying to say that there is anything wrong with NGU or others. Only that bilateral old seems to be the best at smoothing out video which has chroma artefacts in it.

I will probably switch to using NGU or XBR as my default and then tag my Family Guy folder with [profile=bilateralold].

But I watch a lot of old shows and I'm already having to use different sharpness profiles for different seasons so it's not much extra effort to set the chroma as well.

I'm just really glad that MadVR has this tagging ability otherwise it would be so annoying to have to keep manually adjusting settings all the time. Just set it and forget it :)

[x7007]

the HDR bug is ranges it also effect computer games which are literally broken on win 11.

i don't have the AMD card connected to an HDR display anymore there is no point.
http://bugs.madshi.net/view.php?id=674
not like i'm alone.

flossy_cake
the file is utterly broken.
my guess the deint was done wrongly.
https://abload.de/img/chroma0pk9t.png
you should not judge a chroma scaler on this file.

NGU AA and super XBR are the high contender for good chroma scaler NGU sharp does good on sharp Chroma which is super rare.

I dunno, 10bit and HDR works fine for me using AMD HDR.. I have no idea which issues you have exactly, can you show me?

When I disabled the 2 options from artefact removal 10bit works all the time. I still need to check if one of them causing it, I'm using the 1.58b version so I don't have the identification duplicates.
Also, HDR is engaging all the time properly using Let Madvr decide or Passthrough.

When I enable Exclusive mode it works at start and when it stops working in 10bit then it stop going into exclusive mode. something weird

Try to use the 2 separate device for presentation and DXVA enabled. seems to fix something

Opening Chrome seems to mess it up instantly.

[LenniePaz]

How do you totally uninstall MadVR so I can start from scratch? I’ve used the uninstall bat, ran as Administrator, deleted MadVR folder, but when I re-install the original MadVR, all my settings are still there.


Sent from my iPhone using Tapatalk

[x7007]

How do you totally uninstall MadVR so I can start from scratch? I’ve used the uninstall bat, ran as Administrator, deleted MadVR folder, but when I re-install the original MadVR, all my settings are still there.


Sent from my iPhone using Tapatalk

use the restoretodefault.bat

[jkauff]

How do you totally uninstall MadVR so I can start from scratch? I’ve used the uninstall bat, ran as Administrator, deleted MadVR folder, but when I re-install the original MadVR, all my settings are still there.
Run "regedit", search the registry for the key "madshi", then delete the key.

[flossy_cake]

Just had a really weird bug where Ctrl+J was reporting my refresh rate completely wrong -- 23.979hz instead of 23.976hz. And yet, playing a 23.976fps file still showing 1 repeat every 8 hours or so, which is impossible if it really was 23.979hz.

But then on other files Ctrl+J reported the correct 23.976hz.

But then vsynctester.com was reporting the bugged 23.979hz (and also 59.950hz for my tuned 59.940hz mode!)

So weird. I'm guessing the Windows system clock or event timer must have gotten into a bugged state or something? Rebooting brought it back to normal.

[huhn]

there is a reason i told you to not take this number to serious.

[LenniePaz]

I just totally wiped MadVR, and started from scratch. When I watch a video my Epson says the input signal is RGB-Video. When I use my Shield Pro to watch a video, the Epson says the input signal is Component. Which is correct, or are they both?


Sent from my iPhone using Tapatalk