madVR - high quality video renderer (GPU assisted)

[70MM]

I am using ordered dither on madvr...
Ive just noticed that dither is set to Auto on my Lumagen Pro, should it be turned off?

[nussman]

I am using ordered dither on madvr...
Ive just noticed that dither is set to Auto on my Lumagen Pro, should it be turned off?
No ... why you think it should be turned off?
Not sure what this setting does but if its needed for internal Lumagen processing turning it off is wrong for sure.

[70MM]

I just thought maybe it was wrong to be using dithering twice, once in madvr and a second time in the Lumagen...

[Asmodian]

No, anytime processing is done in a higher bit depth dithering should be used when converting (back) to the output bit depth.

It would be better to avoid the second processing step if possible, the Lumagen will mess up madVR's dithering (causing some loss in precision), but it is still better to dither after processing than not. Not dithering simply rounds (or clips!) after processing, which results in the loss of even more precision and madVR's dithering is still damaged because it is the processing itself that damaged it.

Two rights do not make a wrong. ;)

[70MM]

Thank you for that information Asmodian. I too thought it would be wrong to have the dithering set to ON in the Lumagen and also be doing it in madvr. Ive been running it "ON" in the Lumagen for all this time and never knew until yesterday when i opened that menu. I turned it off, then today the other guy here said I should have it on, so it went back on....easy to get trapped In here at times...

So I will leave dithering set to OFF in the Lumagen and just use dithering in madvr only, correct?

[huhn]

no you leave it on.

the lumagan it self is questionable if you want the madVR image untouched.

[Asmodian]

So I will leave dithering set to OFF in the Lumagen and just use dithering in madvr only, correct?

Ack! What in my statement made you think that?

I messed up badly if that is what you came away with. Sorry. :(

[ryrynz]

It would be better to avoid the second processing step if possible, the Lumagen will mess up madVR's dithering

An opening with a line like that did the recommendation no favors :D

[70MM]

Ack! What in my statement made you think that?

I messed up badly if that is what you came away with. Sorry. :(

I read this...
It would be better to avoid the second processing step if possible, the Lumagen will mess up madVR's dithering (causing some loss in precision)

I will turn the dithering ON again in the Lumagen in conjunction with madvrs dithering, also ON.

[nevcairiel]

I read this...
It would be better to avoid the second processing step if possible, the Lumagen will mess up madVR's dithering (causing some loss in precision)

What he really meant is to get rid of the Lumagen entirely. :)

If you do any processing, it should apply dithering in the end. But still better to not process at all, then you also don't need any dithering. :)

[70MM]

Well I wont be getting rid of the Lumagen at all. His post didnt look like remove the Lumagen Pro to me.... Oh well case closed!

[madshi]

00 ff ff ff ff ff ff 00 10 ac 8b 40 00 00 00 00
2e 16 01 04 a5 43 1c 78 3e ee 95 a3 54 4c 99 26
0f 50 54 25 4b 00 81 00 b3 00 71 4f 81 80 d1 c0
01 01 01 01 01 01 7e 48 00 e0 a0 38 1f 40 40 40
3a 00 80 0e 21 00 00 1a 74 55 00 a0 a0 38 25 40
30 20 3a 00 80 0e 21 00 00 1a 00 00 00 fc 00 44
45 4c 4c 20 55 32 39 31 33 57 4d 0a 00 00 00 10
00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 ce

02 03 1d 40 50 90 05 04 03 02 07 16 01 06 11 12
15 13 14 1f 20 23 09 1f 07 83 01 00 00 02 3a 80
18 71 38 2d 40 58 2c 25 00 e0 0e 11 00 00 1e 01
1d 80 18 71 1c 16 20 58 2c 25 00 e0 87 10 00 00
9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 40 b4 10
00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 b4
78 00 00 00 18 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0
FWIW, I've analyzed this EDID and it very clearly claims that your display's native resolution is 1920x1080. It also lists 2560x1080 as a supported mode, but the "native" resolution is marked as 1920x1080. So it seems the EDID is faulty.

Hi guys. I was wondering which option is better, using TV at 60hz and smooth motion on, or make it go to 23/24hz with smooth motion off?
I kinda like smooth motion on because there is no flashing on screen because there is no refresh rate change.
Also I really don't know if my tv can actually handle 24p content, is a Samsung Eh6030, maybe 120hz because of 3D and accept various refresh rates.
My brother's TV can change to 24hz too but is not a 120hz tv so I think is a waste making it change to 24hz everytime.
So what do you guys think about this?
Native 23Hz/24Hz should provide better quality, but only if your TV is able to properly handle it. Not all TVs that accept 23Hz/24Hz input handle it properly.

So there are 2 questions to answer:

1) Does your TV handle 23hz/24hz properly? Only your eyes can judge that. Use a video with smooth camera pans to find out.
2) If your TV can't handle 23hz/24hz then there's no question and smooth motion is your best option. Otherwise it's your personal judgement whether smooth motion is an acceptable compromise or not. We can't really decide that for you.

HEYYYY there we go! I got it to freeze again and maybe this'll shed a little light on the subject. Can someone with a 1060 try this and see what they get for results? With D3D11 Native mode enabled, watch a 3D movie for a couple minutes. Stop playback and then try to watch a 2D movie. It's now frozen for me. The average and max stats do seem to be changing in the OSD, but, the queues are full and no video is playing. That's...weird right?

Ok, I think I got this one figured out finally. If I exit out of JRiver MC23, go to display properties and toggle 3d off, then back on, I'm able to play the 2D movie again. So I have a feeling something's not getting reset on playback of a 3D movie.
That sounds bad. So even just restarting MC23 doesn't help at all? You have to toggle 3D off -> on to make it work again? Sounds like a GPU driver bug to me. But why do you want to play a 2D movie with 3D mode toggled on? Have you tried letting madVR auto enable/disable 3D for you, depending on whether the movie is 2D or 3D?

Active Decoder says: avcodec
madVR OSD says: P016, 16bit 4:2:0.
It seems, even these days there is no GPU assisted decoding method for main12 HEVC sources. After reading the specs of my card I was pretty sure it could be done at least via CUVID or DXVA. I was wrong, or just not having enough info.
I don't know the limitations of the hardware decoders. That's something that you might want to discuss with nevcairiel in the LAV thread.

I was playing around with the hdr to sdr conversion. Why is the default display's peak nits set to 400?
I read sdr content is usually intentionally limited to 100 nits for compatibililty with older devices. I understand that newer devices allow for more nits but that's not exactly sdr anymore. So when conversion to sdr is needed wouldn't 100 nits (less than madVR even allows to be set) be the most sensible default?
Well, if you want to simulate how a Blu-Ray looks then maybe choosing a value nearer to 100 nits might make more sense. However, today's flat panel TVs are exceedingly bright. So converting HDR to SDR with a nits target of 400 nits should actually produce better looking results overall. In the end, it's only a default value and you can override if you don't like it, of course.

The goal of my HDR -> SDR conversion is not to get as near to SDR Blu-Ray as possible, but to provide the best possible image quality.

Hi Madshi, would it be possible to add something like a 'lock-buttom' for a custom mode once a perfect setting was found ? I am asking because last weekend I spent hours trying to find a setting for a refresh rate but with each new measurement it got worse, e.g. dropped frames down to minutes until I remembered that I had already found a p.s. for that frequency.
But unfortunately that remark was changed to 'optimization available' after playing another file not long enough or with interruptions or whatever ...
So after, say, a driver update it can get unlocked - tested - and locked again.
Makes sense, I'll think about it.

Ok Madshi I got it!

I've deleted every custom resolutions and started from scratch, made the new custom mode (1080p23) on madvr again but this time I followed the Asmodian advice (letting madvr automatically change the resolution every time a new video is open) it worked!!
To be honest, I'm still not sure why it didn't work before. But I'm glad you got it working now.

I am getting a few random freezes/crashes with D3D11 DXVA.
Might be fixed in the next build. If not, please let me know.

@madshi, this is the Ctrl+J OSD when playing 3D MVC while the windows desktop resolution is on 4k

https://i.imgur.com/UwuOEVHr.jpg
Hmmmm... The screenshot resolution is 1456x820, but the OSD seems to suggest that madVR thought the display mode was 3840x2160. What was the actual display mode? Was it 3840x2160 or 1920x1080? Can you create a debug log for this situation (please zip it, upload it somewhere else and then link to it here)?

https://arxiv.org/abs/1708.01692
http://www.sniklaus.com/publications/adaconv
http://www.sniklaus.com/publications/sepconv
Sounds very interesting, this video explains it better:
http://web.cecs.pdx.edu/~fliu/project/adaconv/demo.mp4

Madshi is it possible to implement this interpolate method in MadVR?
Holy crap that is amazing, absolutely add this to madVR at whatever cost for the paid version.
Quality looks really good, but speed is too slow. 0.9 seconds for one 1080p frame on a Titan X? That means we need a GPU that is about 21.5x faster than a Titan X to make this algo suitable for realtime playback of 1080p24 movies. Doing so would produce 1080p48, not even 1080p60. Ok, for 24fps SD content (720x480 DVD) we'd only need a GPU that is about 3.5x faster than the Titan X. So maybe 2 years from now this algo could be run in real time for NTSC DVDs (but only after IVTC!).

Maybe these algos could be dumbed down a bit. A certain quality hit would be quite acceptable if that would buy us a big speed improvement. However, we'd need at least a 50x speed improvement to make this viable for 1080p playback. For 3D playback we'd need a 100x speed improvement, for 4K 200x. And that's just for 24p -> 48p, we wouldn't even reach true 60p yet.

I got a new 100Hz G-Sync monitor connected to a GTX 1080 which I have configured to switch to 50,60,85 Hz. However, when it's playing a 60fps video in fullscreen (non-exclusive) on MPC-BE, the queues are all starved (https://i.imgur.com/fjUU2mR.jpg) and I get a couple drop/repeat frame each second. This doesn't happen in window mode or if there's an overlaying element like MPC-BE's seek bar or right-click menu is shown, but as soon as those are dismissed the queues are down again.

Any idea what's going on and how I can fix this?
For some reason the decoder queue seems to be struggling, too, which seems kinda weird if it runs smoothly in windowed mode. Also, rendering times seem very high, how are they in windowed mode?

Are you using the "device\display modes\hack Direct3D..." option in madVR? If so, does disabling that one help? Alternatively, you could also try to reduce the number of pre-presented frames and/or the size of the GPU queue, just in case you're running into VRAM trouble.

I used an older version and there i had always a TAB for HDR settings in MADVR. But now i donwloaded the newest madvr on your website and have activate it an deleted the older one.

But now i see no HDR Tab and options for HDR anymore.
How can this be? :scared:
That sounds pretty weird. The HDR tab should always be there! Can you make a screenshot?

finally, now i have a 1050 TI 4gb. to have a picture with many dettegi on the 576i to 1050p What madVR filters should I use?
For 576i movie content try forced film mode. For image upscaling try NGU Anti-Alias High, or alternatively NGU Standard or Sharp High. For chroma you could try NGU Anti-Alias Medium, if your GPU is fast enough for that. For image upscaling is much more important.

Can somebody point me to the right link if this has been answered. I'm having problems searching this:

1. It seems I can't get madvr to generate optimized setting for custom mode. I have played numerous videos already

2. Sometimes I get Black Screen. Hitting pause then unpause so far solves this. is there a way to prevent this?
1. So madVR doesn't offer to optimize the modes? Did you create the custom modes in the madVR settings dialog? Or did you create them with the Nvidia/AMD/Intel custom mode tool?

2. Not enough information for me to say anything.

After some more attempts (a couple of days trying, what a nightmare..) I got one that worked this morning (85%), only 1 frame repeat after 6 hours, so I'm really happy right now because it was all luck, like hitting the jackpot lol. I'm going to treasure this values like gold.
Glad to hear that! Will have to do some more tests with my JVC X35, maybe I can figure out why JVC projectors seem to be picky with custom resolutions, and how I can maybe create more custom modes that the JVCs will like.

LAV Filters 0.70.2-74 Nightly 64-bit D3D11 is very good in performance, but there is big motion blur that I never had before...
Sounds weird. Are you sure that you compared the exact same video frame? Sometimes when there's motion, some video frames are very blurry already in the original video file. I'm not sure how D3D11 DXVA decoding could blur the video. Doesn't sound likely, from a technical point of view.

Whenever I set a profile group, MadVR crashes if I open a video file.
I sent a bug report here:
http://frd.li/695682d5f1f1b243cef85800862eb8f8
This will likely be fixed in the next build.

Is there a reason you prefer NNEDI3 for SD videos? I believe NGU Anti-Alias Very High should look better than NNEDI3-256 in most situations. Although if you look at only one video/image, there's always a chance that one algo might look better than another. The important thing is to test with various different videos.

[70MM]

As we all seem to use RGB with madvr, there is something I have been confused about...
Lumagen tells us that they process in 422 and to always use 422 out of the Lumagen regardless of what you input.
So I have always used RGB from madvr into the Lumagen Pro and output 422 from the Lumagen.

Yet I feel that RGB from madvr > Lumagen > RGB would be more correct.
Are there others here using a Lumagen and how do they feel about it, even though "they" always tell us we should use 422 out.
Thoughts please on the subject....
I think madshi commented about this once....

[madshi]

Well, this is really a question you should ask Lumagen. *Why* are they recommending 422 over RGB output? If the reason is that they internally process everything in 422, then it may make sense. But I don't know the exact processing pipeline in the Lumagen. If you tell it to output RGB, how will it internally convert 422 to RGB? Maybe the Lumagen's 422 -> RGB conversion isn't optimal?

Generally, IMHO a high quality external video processor should be doing its internal processing in 12bit+, either in 444 or RGB. IMHO 422 as a processing format is disappointing. E.g. if you run your Xbox, PS3 or HTPC through the Lumagen, a 422 processing pipeline means that you automatically lose half the chroma resolution with every game, your browser, DSLR photos etc.

[nussman]

I think what lumagen says makes sense for video processing, because RGB 4:4:4 input is not "supported" by many displays (especially TV's).

Anyway this is not the personal support thread for @70MM and everything about Lumagen is really off topic here. Feel free to start a new thread and we can talk about it. :cool:

[Cruzader]

Hmmmm... The screenshot resolution is 1456x820, but the OSD seems to suggest that madVR thought the display mode was 3840x2160. What was the actual display mode? Was it 3840x2160 or 1920x1080? Can you create a debug log for this situation (please zip it, upload it somewhere else and then link to it here)?

The ss might have been auto resized by imgurl.
The actual display mode was 3840x2160. I've attached the log file here

http://s000.tinyupload.com/index.php?file_id=88259651262117668096

[madshi]

The ss might have been auto resized by imgurl.
The actual display mode was 3840x2160. I've attached the log file here

http://s000.tinyupload.com/index.php?file_id=88259651262117668096
Some interesting extracts from the log:

00000338.635 Render needed framerate: 23
00000338.643 Render current display mode, width: 3840, height: 2160, rate: 30, interlaced: -
00000338.646 Render DisplayModeCount: 0
00000338.647 Render IsStereoContent: +, IsStereoPresentation: +
00000338.648 Render we're doing frame packed stereo presentation, so we use 1080p23 display mode
00000338.650 Render matching display mode, width: 1920, height: 1080, rate: 23, interlaced: -
00000343.536 Render started madHcCtrl helper process to restore display mode (3840x2160 30Hz) -> +
00000882.167 Render ChangeDisplaySettingsEx() -> +
00000885.027 Render resulting display mode, width: 1920, height: 1080, rate: 23, interlaced: -
[...]
00004790.218 Creator WM_SIZE: 3840, 2160
00004790.223 Creator CQueue::WindowSizeChanged(width: 3840, height: 2160);
00004790.486 Reset Window: 00210504; WindowRect: 0, 0, 3840, 2160; ClientRect: 0, 0, 3840, 2160; ClassName: madVR
00004790.491 Reset ParentWindow: 000D04CE; WindowRect: 0, 0, 1920, 1080; ClientRect: 0, 0, 1920, 1080; ClassName: Kodi
[...]
00004798.376 Render display mode: 1920x1080, 23 Hz, progressive, 16
So it seems madVR switches the display mode to 1920x1080p23, because you're playing 3D content and most displays don't support 3D with a 2160p display mode. So far, so good. However, after the mode change, Kodi's main window has a size of 1920x1080, but madVR's rendering window has a size of 3840x2160. So basically only the top left quarter of the madVR rendering window is actually visible.

It's Kodi's responsibility to resize the madVR rendering window properly. So it seems to be a Kodi bug to me.

[SamuriHL]

That sounds bad. So even just restarting MC23 doesn't help at all? You have to toggle 3D off -> on to make it work again? Sounds like a GPU driver bug to me. But why do you want to play a 2D movie with 3D mode toggled on? Have you tried letting madVR auto enable/disable 3D for you, depending on whether the movie is 2D or 3D?


Restarting MC23 did not help, no. I do have that option set in madVR, however, I think I went the opposite way with it. Meaning turning off 3D when playing a 2D movie. I'll try it with that setting turned off in windows and see if it makes any difference. I'll play around with it more and see if I can give you more info.

[SamuriHL]

madshi, you were right. Turning off 3d in the display properties solves the issue. I can play 3D and 2D MKV's no problem and switch between them without issue. This problem only happens when the 3D option in Windows display properties is turned on. Thanks!

[fluidz]

Hi guys, i'm getting slight pauses in playback that last for approx 1-2 seconds, it happens once every few minutes.

Madvr 0.91.11 , Jriver Media Player 21, Windows 10, 1080ti - 385.41

This has only started to happen recently but I can't put my finger on whats causing it.

I'm using a 3dlut for calibration.

https://image.ibb.co/e9C23a/freezes.png

[Sunset1982]

madshi, playback of my video files sometimes start paused and i have to resume it by hitting "space". It only happens sometimes... Any idea what error this could be?

[Dorohedoro]

Hi guys, i'm getting slight pauses in playback that last for approx 1-2 seconds, it happens once every few minutes.

Madvr 0.91.11 , Jriver Media Player 21, Windows 10, 1080ti - 385.41

This has only started to happen recently but I can't put my finger on whats causing it.



Your rendering time is too high and you are losing frames because of that, lower a little bit your settings and aim for 20ms~25ms... 40ms is too high.

[ForceX]

For some reason the decoder queue seems to be struggling, too, which seems kinda weird if it runs smoothly in windowed mode. Also, rendering times seem very high, how are they in windowed mode?

Are you using the "device\display modes\hack Direct3D..." option in madVR? If so, does disabling that one help? Alternatively, you could also try to reduce the number of pre-presented frames and/or the size of the GPU queue, just in case you're running into VRAM trouble.

I did have Hack D3D option enabled but disabling didn't help since I'm running 60fps content to begin with. I have disabled that and tried it with shorter queues, but it wasn't the issue since the GTX 1080 has 8GB of RAM. Also, decoder queue shouldn't be struggling since the gpu can easily handle 4k60fps content.

Fullscreen with overlay element: http://i.imgur.com/TFeLoSb.jpg
Fullscreen: http://i.imgur.com/uoPS6ga.jpg

The rendering time behaves weirdly in fullscreen with max render time (5s) sometimes jumping to 100 ms, but in a window it always stays near average render time.

[YxP]

You have your player at adaptive or high performance power state in nvidia settings?

[Asmodian]

I read this...
It would be better to avoid the second processing step if possible, the Lumagen will mess up madVR's dithering (causing some loss in precision)

I will turn the dithering ON again in the Lumagen in conjunction with madvrs dithering, also ON.

Sorry, nevcairiel was correct. You have to finish that sentence: ", but it is still better to dither after processing than not." ;)

What does the Lumagen Pro do that is beneficial?

Lumagen tells us that they process in 422 and to always use 422 out of the Lumagen regardless of what you input.

Ouch. :(

I assume this image shows 4:2:2 then? http://madshi.net/madVR/ChromaRes.png
At least you don't need to worry about madVR's chroma scaling options very much. :p

Edit: A Lumagen is good for people who are not using madVR but once you are using madVR a Lumagen only damages the video signal. madVR uses your GPU to do everything a Lumagen does but at higher precision and full resolution. When going for maximum quality 4:2:2 processing is completely unacceptable, down sampling the chroma to half the horizontal resolution for processing will lose a lot of quality. :(

[chros]

I have calibrated my Tv display for gamma bt1886. (HCFR)
How should I configure madvr? Pure power curve 2.20 or 2.40 or BT.709/601 curve?
Hi Attila!

0. Here's the dedicated thread (https://forum.doom9.org/showthread.php?t=172783&page=10) for calibration. And here's a small explanation (https://forum.doom9.org/showthread.php?t=171787) by Asmodian wht the different options mean (but it won't give you much of a help with your question).

1. I'm not sure, but I think you have to go for "BT.709/601 curve" and one of the values (preferably 2.20) since there's no better option.
But are you sure (http://www.avsforum.com/forum/139-display-calibration/1471169-madvr-argyllcms-139.html#post40108362) that that's the best mode (bt1886) for your display and you? :)

2. But: what you did is the "old" way to do calibration. The better (final :) ) one is profiling: creating 3dlut with DisplayCal that can be used by madvr.
Feel free to ask more in the above mentioned calibration thread.

[Asmodian]

I have calibrated my Tv display for gamma bt1886. (HCFR)
How should I configure madvr? Pure power curve 2.20 or 2.40 or BT.709/601 curve?

BT.1886 is pure power 2.4 if black = 0 nits, so if you have a pretty low black level use pure power 2.4. Never use the BT.709/601 curve unless you are trying to see shadow details on a bad display (and then you would set it in color & gamma, not calibration).

Note that these options don't do anything unless you start messing with gamma in "color & gamma", you are simply telling madVR the starting point in case you want to make adjustments.

And do check out DisplayCal, it isn't too hard to create a good 3DLUT for madVR now. :)

(Sorry, Cunningham's Law in effect again :p)

[Siso]

I'm wondering if image doubling is worth for 1080p files-> http://imgbox.com/XMGeHv9q

As for 720p it is ok -> http://imgbox.com/DATSnfxQ

So for 1080p files, I get bicubic 150 AR as the final step for luma?

[ForceX]

You have your player at adaptive or high performance power state in nvidia settings?

I have it at Prefer maximum performance.

After getting frustrated with MPC-BE, I dusted out PotPlayer (blasphemy. I know) to give it a try and to my utter rage, it works fine. I now feel like an idiot for wasting so much time tinkering madVR on MPC-BE.

[Asmodian]

Doubling for 1080p -> 1440p has always been questionable. I do like doubling for 1.5x or more but for 1.33x simply using Jinc upscaling often looks almost identical for a lot less power. Bicubic 150 AR is downscaling it again, you can change it with the "<-- downscaling algo" option under "if any (more) scaling needs to be done:". SSIM 1D100 AR might look a bit better to you, or Bicubic60, but IMO nothing significantly beats Jinc for that upscale.

Do you not have the power to go up to NGU AA high? You have some room left in your rendering times. ;)

[Siso]

Doubling for 1080p -> 1440p has always been questionable. I do like doubling for 1.5x or more but for 1.33x simply using Jinc upscaling often looks almost identical for a lot less power. Bicubic 150 AR is downscaling it again, you can change it with the "<-- downscaling algo" option under "if any (more) scaling needs to be done:". SSIM 1D100 AR might look a bit better to you, or Bicubic60, but IMO nothing significantly beats Jinc for that upscale.

Do you not have the power to go up to NGU AA high? You have some room left in your rendering times. ;)

For downscaling algo, it was left on "let madvr decide". I put SSIM 1D100 AR to see how it is.

What do you mean by "nothing beats Jinc for that upscale"?

[Asmodian]

I meant that for small upscaling ratios Jinc and NGUAA+SSIM look so similar that the improvement from spending all that GPU power is very small (Jinc is the best algorithm in madVR that can directly upscale to any size, not just 2x). 1.33x is on the line between worth it and not, where it is hard to decide. :)

[Siso]

I meant that for small upscaling ratios Jinc and NGUAA+SSIM look so similar that the improvement from spending all that GPU power is very small (Jinc is the best algorithm in madVR that can directly upscale to any size, not just 2x). 1.33x is on the line between worth it and not, where it is hard to decide. :)

I see, good point! How about instead of Jinc for chroma, to put NG AA low?

[Shawns1234]

All, first time posting. I have kept up with this thread over the years and I have had an issue for some time now.

I have Windows 10 with CU. An AMD 480, madvr and Lab Filters are the latest available. I use a 4k Vizio m70. I am now using D3D11 in LAV now and it has been so much better, but I still have an issue where my PC locks up if I use NGU or any "doubling" algorithm. I can use xbr and cubic for chroma. The only option I can use for the other is cubic. Anything else, along with many other sharpening settings, and my PC locks up immediately after going full screen. I have tried every combo of settings, but this happens on my 480 and my 460 video card. If I use EVR, I do not have this issue. This has been going on for at least 6 months now. Any ideas?

[HillieSan]

I have no issues of this kind with my AMD RX 480. Perhaps you should check your power supply unit (PSU) if it provides enough power (Watts). The RX will consume lots of power when using NGU.

[Oguignant]

Hi. I have problems with the latest version (0.92.2) . When I want to watch a HDR movie in full screen exclusive mode, the Tv HDR mode is disabled. I already tried to make changes to the configuration, but I can not fix it. With the previous version (0.92.1) works perfect. Any ideas?

Thks!!!

[JayeDog]

I will tell you my sharpening options tonight , I'm not in my house right now. Ffdshow is an old filter that will give you some problems (none for me so far) specially if you want to use hdr (I'm not using it yet).

Under the ffdshow options you will find some denoise filters, I really like denoise 3d because it will help you get rid of that ugly grain of some old movies (I dont don't like grain) without losing to much fine details. Until Madshi add some denoise options in madvr, ffdshow raw is a good option for me.

Hi, do you mind posting your denoise settings in ffdshoew raw?

[Asmodian]

I see, good point! How about instead of Jinc for chroma, to put NG AA low?

You mean instead of Bicubic60AR? Your screen shot is using Bicubic60AR for chroma doubling.

NGU AA low is a good choice but any differences will be very minor, it would be better to put more power into luma, if you can.

[x7007]

I have a weird issue with 0.92.2 . when first entering the first movie at least after windows restart, the movie doesn't use the full upload queue , render queue and present queue. it only happen when entering D3D11 Full Screen 10bit . with D3D11 windowed 8 bit it works fine. not sure if it's the Lav Filters 0.70.2-74-git D3D11 issue.
after exiting and renetering it works fine. when entering the 2nd time to the same movie the Rendering time also reduced to 15-14 ms instead 26-24ms. I checked GPUZ and it shows full utilization of the core and mem .

EDIT: It also randomly happens while watching a movie , Decoder queue becomes 22 instead 24/24 . upload queue 5-8/8 render queue 3-8/8 and present queue is 0-4/4.
Do we must use Maximum performance on nvidia now for potplayer or MPC ? instead optimal power or adaptive ?

EDIT : It was something with the Cpu queue size , when it was 24 it happened , when I lowered it in real time to 16 it fixed itself .

hmm I didn't see this must rule "The rule is that the CPU Queue size must be bigger or equal to the GPU Queue size." that's why it's 16 and 8 ..


Potplayer is using Optimal power on the nvidia.
https://imgur.com/LzKlJay

[huhn]

rendertiems down matter much because modern GPU are changing the clock as they pleases so on low load the rendertimes can be really high.

optimal power settings can make problems when using madVR for me it is making major problem on my PCs adaptive is working fine for me.

some fluctuation in the queue are pretty meaningless as long as you are not dropping or repeating a frames for that reason.

you are using d3d11 which is not released yet and you ask question like: Do we must use Maximum performance on nvidia now for potplayer or MPC ? instead optimal power or adaptive ?

so the first thing is to find out why. so in this case you should disable d3d11 decoding and check if it happens again.

[Asmodian]

Potplayer is using Optimal power on the nvidia.
https://imgur.com/LzKlJay

Adaptive is much more reliable for madVR.

[x7007]

rendertiems down matter much because modern GPU are changing the clock as they pleases so on low load the rendertimes can be really high.

optimal power settings can make problems when using madVR for me it is making major problem on my PCs adaptive is working fine for me.

some fluctuation in the queue are pretty meaningless as long as you are not dropping or repeating a frames for that reason.

you are using d3d11 which is not released yet and you ask question like:

so the first thing is to find out why. so in this case you should disable d3d11 decoding and check if it happens again.

yes, it also happened with DXVA copy back. that's why I went back to D3D11 because it was not the issue.


So I'll use Adaptive then . if optimal is an issue. also an issue I was currently having is when have a movie on pause for a long time more than 1 hr or so after TV is turned off . when I turned the TV back on and try to unpause , the video is freezed while the audio keep going correctly. but when this happened it's somehow fixed when I change the Cpu queue , that's is what I think , it takes a long time till the video synced back with the audio , but again I'm not sure what exactly fixed it, and it takes time for it to happened till I can test again. the Gpu and Mem clock are all max when the video is played, the recording time is correctly the same as normal, but the all render queue , upload queue , prerenderqueue are messed up




Another question I wanted to ask : is Is there a need to use the Madvr reduce ringing artifacts ? because this thing takes 15 ms on rendering time.

[nsnhd]

I meant that for small upscaling ratios Jinc and NGUAA+SSIM look so similar that the improvement from spending all that GPU power is very small (Jinc is the best algorithm in madVR that can directly upscale to any size, not just 2x). 1.33x is on the line between worth it and not, where it is hard to decide. :)

For Luma Upscaling, my iGPU can afford up to Jinc without AR or Lanczos/Spline 4-tap with AR. So, is Anti-Ringing important at all because I haven't noticed its effect so far ?

[huhn]

Another question I wanted to ask : is Is there a need to use the Madvr reduce ringing artifacts ? because this thing takes 15 ms on rendering time.

you don't need it. it is there to remove source ringing if the source doesn't have ringing it not needed anyway.

[Dorohedoro]

Hi, do you mind posting your denoise settings in ffdshoew raw?

Sure, I will post my entire settings soon, but you will have to wait a bit because my ups died last night and I'm afraid to use my htpc/projector without it.

[Siso]

You mean instead of Bicubic60AR? Your screen shot is using Bicubic60AR for chroma doubling.

NGU AA low is a good choice but any differences will be very minor, it would be better to put more power into luma, if you can.

Madvr selects it automatic...if I use super-xbr, there isn't any bicubic60 selection.

[Asmodian]

Super-xbr works on RGB so it effectively does both luma and chroma at the same time. :)

If you set chroma manually you can get it to use NGU too, but it is better to spend the power budget on luma. Only start manually setting chroma if you cannot turn up luma anymore.

For Luma Upscaling, my iGPU can afford up to Jinc without AR or Lanczos/Spline 4-tap with AR. So, is Anti-Ringing important at all because I haven't noticed its effect so far ?

AR is very important for Lanczos/Spline 4-tap, it is less important but still good for Lanczos/Spline 3-tap or Jinc. AR is not important enough for Jinc that I would use Lanczos/Spline over Jinc just so I could use AR.

[Siso]

Super-xbr works on RGB so it effectively does both luma and chroma at the same time. :)

If you set chroma manually you can get it to use NGU too, but it is better to spend the power budget on luma. Only start manually setting chroma if you cannot turn up luma anymore.


If I choose "high" instead of medium in luma doubling, I can then choose chroma - normal, high, very high. If I set "high", I got ~29ms rendering time. Not sure if it is worth the load on the card...I'm confused :D

[Asmodian]

Only you can decide if it is worth it. :)

[Siso]

Only you can decide if it is worth it. :)

That's true, so the only way to eliminate bicubic60 for chroma is to pump up the settings to ~29 ms rendering time...The other option for me is to keep NGU AA medium for chroma, and to use super-xbr 100 for luma doubling.