madVR - high quality video renderer (GPU assisted)

[oddball]

Can someone tell me why I can no longer use MadVR in Windows 10 unless I enable DX11? Or rather why it gives a blank screen on default settings. Locks up solid if I try to use Windows overlay and locks up/corrupts when switching between multiple displays??? FSE only works with DX11 too but I tend to have to disable delayed playback.

I asked about this earlier and got NO response whatsoever!

I have tried rolling back MadVR, rolling back AMD drivers to Win10 defaults. Various flavors of MPC-HC and setttings. It's only MadVR causing the crashes and not being able to use it like I used to up until the last few weeks. It's got me beat.

[huhn]

do you have a crash report?

[ryrynz]

I have tried rolling back MadVR, rolling back AMD drivers to Win10 defaults. Various flavors of MPC-HC and setttings. It's only MadVR causing the crashes and not being able to use it like I used to up until the last few weeks. It's got me beat.

You think madVR is fault but haven't reset the madVR settings??
There's a lot of options and you done nothing really other than roll back your drivers. Have you run a SFC? Or tried a system restore?
Doesn't sound like it's going to be madVR's problem at all.

[neno]

hi~madshi and everyone:
1) I find the issue of 0.90.18 "image doubling activated if the window is smaller than the video" also happened when I play a DVD resolution video. The scale shows "0,0,720,480 -> 0,0,852,480", but the image also unnecessarily doubled "image > super-xbr < Bicubic150 AR".

2) About downscaling, is SSIM 2D 100 the optimal choice ignoring performance? (I'm using Bicubic150 AR now.)

3) I updated from 0.90.10 to 0.90.18, under the same setting, rendering time increases for a few ms. Maybe the reason is:
* downscaling anti-ringing filter is now much more aggressive;
* added Hyllian's super-xbr anti-ringing (for image doubling);
* reworked super-xbr chroma upscaling anti-ringing algorithms;
Anyone have the same experience of rendering time with me?

4) I tick the "delay playback start until render queue is full" all the time, but find the queue is not filled when playback start several versions ago(the stutter in playback-start also disappeared compared to very old versions). I don't mind it for the queue will fill quickly until I updated to 0.90.18. Maybe for some reason above, the rendering time comes to a threshold, and the queue struggles and can not fill for 1 or even 2 minutes, during which the dropped frame increases.
Does anyone also have this "queue is not filled when playback start" problem or is it a known issue? I have tested on WIN10/XP, D3D11/D3D9, FSE/WINDOWED mode, the problem is the same.

Thanks!

[Uoppi]

neno,

2) I only use SSIM 2D for UHD -> 1080p downscales. For downscales after doubling/quadrupling, I use SSIM 1D. 2D is more resource hungry/better but I remember madshi saying there's not much (if any?) visible benefit in using 2D for smaller downscales. Anyway, 1D seems to be a little less taxing than Bicubic 150, which is an added bonus.

3) On one of the previous pages madshi confirmed that some (can't remember which) features are more resource hungry now. Also updating to the latest Nvidia drivers cut off a few ms with the previous build for me. There's no escaping regular tweaking...

4) Maybe the queue is struggling to fill up because of increased resource requirements? Has happened to me after madVR updates. Try lowering or disabling some features.

[Ver Greeneyes]

1) I find the issue of 0.90.18 "image doubling activated if the window is smaller than the video" also happened when I play a DVD resolution video. The scale shows "0,0,720,480 -> 0,0,852,480", but the image also unnecessarily doubled "image > super-xbr < Bicubic150 AR".This is a known issue, should be fixed in the next build. As a workaround, you could create a profile for image doubling that activates if ((scalingFactor.x < 1.0) && (scalingFactor.y < 1.0)) and explicitly disables image doubling.

[madshi]

madshi, is there a way to ignore wrong ST.2086 metadata and use peak white was selected by user?
The official test video from Sony has completely useless metadata and madVR simply shows all white picture (0.5 nit peak white)
I don't want to add options for broken files. However, I've PM'ed nevcairiel about the issue to check if we can maybe auto detect files with broken HDR metadata and handle them differently.

Too bad, your deringing filter seems to work wonders in general. :)
Especially with super-xbr, the difference in the cartoon example without SuperRes is enormous.
Try the next build, maybe it has improved slightly?

What a remarkable addition this deringing is. Ringing is my number one annoyance, much more so than mild banding or aliasing. Whatever leftovers you guys are talking about, they definitely are not as bad as ringing itself :P Great work!
:D

While we are at it, I will share some thoughts:

1. 3D DCP video is a frame sequential 48fps stream with alternate left eye and right eye frames for 24 fps content. If LAV video decoder just flags and sends the stereo frames in the same way as it does for MVC content, no special handling of 3D would be required in madVR (I believe).

2. Currently, the black bar detection algorithm doesn’t work for RGB content (and also YUV content, IIRC), so it wouldn’t work for XYZ as well without extra work on your side. However, you can use the “Y” of XYZ for black bar detection as you do for YCbCr content because “Y” in XYZ and YCbCr are very similar as both have lightness information.
One step at a time.

Another positive vote for the new deringing. Very impressive results I must say! I only had limited time to check it out, but, I tried it on some Family Guy episodes and I'm quite impressed. Nicely done!
Glad you like it!

Yeah I'm using it on Naruto Shippuden ATM, and I'm happy with the results. Dehalo Alpha was one filter I used a little quite some years back, in the end I think it destroyed the image too much so I stopped using it.
:)

I'm trying to find your post, but I can't remember where I read it unfortunately.

Anyway, you said (if I remember correctly) something about adding a feature which added/rendered black bars into the video. This could be a misinterpretation, but me and several others noticed it and discussed it after the fact.

Is that a possible, viable feature to implement?
For which purpose?

OMG, is this for real? The difference is unbelievable!

All the details still intact, while it only removes the ringing COMPLETELY.

Wow, I am speechless. This one feature alone is probably the best proof that madVR is so much better than anything else out in the market for video playback rendering by far.

Great work madshi!
:D

Guys Ive just checked with my installer and he says we are installing madvr correctly in conjunction with JRiver. He said the madVR install he did was using the Program Files/madVR folder, not the one in the user folder so he updated the folder under users and will see how it goes....
JRiver MC uses the madVR version in the user folder. Ideally you should upgrade both versions. In theory you don't need 2 installations. You could remove the one from the Program Files folder. madVR would only work with JRiver MC then, though, and not in any other media player.

Can I ask for further improvements in the 6:4 film mode used for p60 video? I don't know if you use it all that often which is why it's in the state it's in or if it's extremely hard to detect the pattern accurately, but it's not very polished from my use of it. It's probably the least polished feature I've found in madVR, by far. It sometimes takes several seconds to detect a pattern change resulting in the slow-mo playback look, it sometimes seems to displays frames out of order, or it flashes a random frame it shouldn't after a pattern change. It feels like an experimental / alpha feature. The 3:2 mode for i60 content works much, much, much, much better.
Samples are always welcome. I can't promise when I'll find time for this, but if I get samples, at least it gets on my (long) to do list.

It seems mixed upscaling (target 1024x768) is broken again... First pic is latest madVR (no settings changed), second pic is madVR v0.90.17
Try again with the next build. If it's still broken, please let me know.

Not only that, it's the only correct way - a linear 16-bit ramp with the goal to not alter the input in any way has to start at 0 and end at 65535, not 65280, so the CalibrationTester is simply wrong :-)
At least it seems more logical that way. However, and here comes the weird part: If you read the BT.709, BT.2020 etc specs, they explicitly say that limited range 8bit video has peak white at 235, while limited range 10bit video has peak white at 940. Using this logic, it could be 65280 instead of 65535.

In any case, when analyzing those 16bit ramps, madVR understands both types of LUTs to be "linear". But when creating a linear 16bit ramp, madVR uses 257.

From what I remember, in some OSs and with some GPU drivers, 256 was used and sometimes 257.

Turns out it seems to work stunningly well with SuperRes LL@2 + AB@100 so please don't remove AB from SR anytime soon, still playing around but I certainly like what I see in combination with vanilla 100% LL SSIM2D & vanilla sxbr(whose main problem was amplifying existing ringing as I understand it).

Outrageous results really, hats off http://forum-images.hardware.fr/images/perso/mlc.gif
Glad it works well for you!

I know we already talk about this but in would like to ask you to rethink about and if its possible implement on madvr
The resolution of my tv is 1366x768 (Windows says that native is 1360x768 but in tv datasheets says 1366x768, i use the two resolutions depending on the movie fps)
That implies aways upscaling or downscaling the movies
I almost watch 720p content and on this movie resolution madvr don't allow me to use upscaling refinements only image refinements because is small scaling factor near the movies native resolution
I like to use some sharpen because its not a big screen and the sharpen plus enhance details give me for depht
But seens that using some of the sharpen algos and upscaling after produces a little distortion on image, more bloated, and ant bloating filter poduces some extra blur and great loss of depht
I really like sharpen edge but seens that to get more depht with ab before scaling i have to use bigger strenghts but ant bloat sometimes produces some strange distortions and much blur when use before scalling
Adaptive sharpen plus ab is great but is unusable in this scenario because using both give me more distortion and dont reduces the oil paint apparence../
In some past version (can t remember the version that this has changed) madvr allowed to use upscalling refinements on such smallers scaling factors even 1919 to 1920 on my other laptop that is full hd and the effect was pretty good much less artificial... And for last this limitation don t let me use super resolution wich produces good natural sharpen results even with this small scalling factor... Same for supersampling that don t allow using upscalling refinements with this resolution, but in the past if i checked aways when upscaling is required the refinements were used... I don t really have much interest in supersampling but really want to use upscaling refinements when scaling 720 to 768 especialy the antibloat
Im on my phone now but this weekend i can make some screenshots examples of
Ant bloat loss of quality if used pre resizing, i made some tests scaling on avysinth... To see the effect after scalling...
Can you allow use upscalling refinements to smal scaling factors?
It's difficult to make this configurable. Some users may share your opinion, others might not. If I added an option for this, it would be hard to understand for most users what the option means exactly.

Maybe you could activate supersampling (see image doubling section)? If you do that, upscaling refinement should work as expected. Of course this solution costs quite a bit of extra performance.

Thanks. Madshi posted comparison picture and the one for Dark Halo Removal was VERY blurry.
I think the VERY blurry image you mean was not from madVR, but from the AviSynth script DeHalo_alpha.

Your dering algorithm is very promising, it derings very well when maintaining details. It's way above DeHalo and other deringing filters I've seen so far. But sometimes it adds some artefacts as you can see here :

http://postimg.org/image/efe86s6f5/full/

Also note that the color of the door is slighlty different and the lines on the bottom of the wall just next to the door are narrower.

Here I found it too agressive on 2 spots :

http://postimg.org/image/durdyqd8h/

Could you improve a little bit the situation? Personnaly, I would prefer to have a lower deringing strength with fewer artefacts and better details preservation.
It's not that easy. Edges are either detected as being ringing or not. If they are detected as being ringing then I try to remove them. Different "strengths" don't really make too much sense here. Well, ok, there are some thresholds I'm using. But if I allow you to lower those, you'll get less ringing removed and maybe fewer artifacts in some places, but then you'll get more ringing left in the image, and some other artifacts instead. I don't think it would really improve the situation much.

But please try the next build, it has some (smallish) improvements. Maybe it works better for you? It's not perfect, though. And it probably never will.

Does anti-ringing do anything for compression artifacts:

"The signal is bandwidth-limited, discarding too much information for high frequencies."
Anti-ringing or Deringing?

madshi, is there a way to resize the MadVR settings window or collapse all the profiiles upon opening the window?

I've finally managed to set up a number of profiles for different resolutions under both processing and scaling algorithms, but it's a pain having to scoll to find each one.
Not at this point. Cosmetical issues are not a priority at this stage of development.

I think processing image enchancements is before scaling, and scaling algorithims upscaling refinement is after.. so it is possible to sharpen edges (random example) twice if you toggle it in both image enchancements and upscaling refinement panels as they can be set independently. The checkbox is not either/or exclusive.
The image enhancements controls are meant to be used if you play a source which is too soft, regardless of whether you upscale or downscale it.

The upscaling refinement controls are meant to repair softness that most upscaling algorithms introduce.

So these 2 sets of options really have a different purpose, and it may make sense to use both at the same time.

That said, this is all a work in progress. I absolutely plan to make the whole settings mess less complicated at some time in the future.

Possible bug, "disable calibration controls for this display" still allows use of the enable gamma processing function so it is unclear what the difference would be between disable and "already calibrated".
Hmmmm... Yes, I suppose enabling gamma processing probably doesn't make much sense if "disable calibration controls" is set. On the other hand, I don't consider it a crucial problem. Things like this should be fixed before version 1.0. But atm other things are more important.

Perhaps this is not the first time being discussed but I am curious as to whether I am doing something wrong.

I have downloaded a video with hdr, this one in particular: http://demo-uhd3d.com/fiche.php?cat=uhd&id=144

When I use enhanced video renderer it looks fine but when I use madvr it looks wrong: http://imgur.com/XPLQ320

Is there a setting I must change or is this a bug or compatibility issue?
As you already found out, the metadata in that file is broken. But I'll see if I can find a workaround to play this file with decent quality.

Can someone tell me why I can no longer use MadVR in Windows 10 unless I enable DX11?
Issues like this are hard to diagnose from afar. Try reinstalling/updating DirectX. Newer OSs sometimes don't ship with full DX9 support. But the key question is: If this used to work, what has changed to break this? It's almost impossible for me to say with the limited information I have.

[madshi]

madVR v0.90.19 released

http://madshi.net/madVR.zip

* fixed: image doubling was sometimes activated although it shouldn't
* deringing strength was slightly increased
* deringing artifacts were slightly reduced
* deringing now adds some grain to deringed image areas
light house:
no deringing (http://madVR.com/doom9/dering/lightHouseOrg.png) - - | - - madVR v0.90.18 (http://madVR.com/doom9/dering/lightHouse9018.png) - - | - - madVR v0.90.19 (http://madVR.com/doom9/dering/lightHouse9019.png)

[aufkrawall]

Try the next build, maybe it has improved slightly?

Unfortunately not. I haven't directly compared it yet, but maybe the old deringing filter even looked better with this particular cartoon even without SuperRes than the new one (which probably is better with filmed content?).
Maybe the grain around the dark lines makes the image look a bit dirty, will do screenshot comparison soon.

[QBhd]

madshi,

Just did a quick test, seems the issue I reported is fixed. It's game 7 for my Raptors and I will be back to watching my shows afterwards and will report any issues, if there are some... But it looks A-Ok after the quick test.

QB

[Asmodian]

Hmmmm... Yes, I suppose enabling gamma processing probably doesn't make much sense if "disable calibration controls" is set. On the other hand, I don't consider it a crucial problem. Things like this should be fixed before version 1.0. But atm other things are more important.

Does madVR assume the display is BT.709 with pure power 2.2 gamma if "disable calibration controls" is set?

[DragonQ]

Is there any way of altering default settings for displays? I want to set MadVR to output 16-235 levels but every time I turn my AVR on and off it's detected as a new display and defaults to 0-255. :(

[CarlosCaco]

It's difficult to make this configurable. Some users may share your opinion, others might not. If I added an option for this, it would be hard to understand for most users what the option means exactly.

Maybe you could activate supersampling (see image doubling section)? If you do that, upscaling refinement should work as expected. Of course this solution costs quite a bit of extra performance.



I was not asking for a new way option, only to be able to choose in such a small upscaling factor if i use a pre resizer or a pos resize filter same behavior as with bigger upsscaling factors... BTW madvr in some past version allowed that... but i respect your point... with all options avaliable can be hard and confusing to understand the behavior without reading and "studing" madvr functionality....
until v0.18 upscalling refinements was not active when set supersampling and upscaling 720 to 1360x768 neither if i set aways if upscaling is needed, i double checked in v0.18, i will try on v0.19 and report... but i already know that my hardware plus settings can ´t handle supersampling, i will tweak the settings and report
IMHOt is not the best way, this can be more confusing for some people, like happened to me, people can think that upscaling refinements activate with all upscaling factors... i waste sometime increasing the upscaling refinements strenght until understand that i was not seeing difference in image results because they not are activated...
but even with this the quality of my movies is spetacular and i only have to thank you madshi, sorry bother you with such as specific situation...

[Warner306]

My question was about the nature of the new deringing algorithm. What percentage of sources are likely to have these artifacts and how good of a general use filter is this? Also, does deringing help with ringing created by compression of a source, where too much information is lost around high frequencies edges?

[ryrynz]

* deringing now adds some grain to deringed image areas[/code]
light house:
no deringing (http://madVR.com/doom9/dering/lightHouseOrg.png) - - | - - madVR v0.90.18 (http://madVR.com/doom9/dering/lightHouse9018.png) - - | - - madVR v0.90.19 (http://madVR.com/doom9/dering/lightHouse9019.png)

Oh wow, that's far better than I thought you'd achieve with adding some grain although I suspect your other changes made a difference here too, but it's absolutely spectacular! Amazing work madshi, am suitably impressed.
An absolute must for most anime without a doubt, can't wait to do a quick comparison when I get home.

[madshi]

Unfortunately not. I haven't directly compared it yet, but maybe the old deringing filter even looked better with this particular cartoon even without SuperRes than the new one (which probably is better with filmed content?).
Maybe the grain around the dark lines makes the image look a bit dirty, will do screenshot comparison soon.
Ok, I'll wait for screenshots.

Does madVR assume the display is BT.709 with pure power 2.2 gamma if "disable calibration controls" is set?
I think so, but I'm not sure right now.

Is there any way of altering default settings for displays? I want to set MadVR to output 16-235 levels but every time I turn my AVR on and off it's detected as a new display and defaults to 0-255. :(
Unfortunately no.

It's a new display every time? Does your AVR use a random serial number or how does that happen? Maybe it's just 2-5 different detected displays instead of an infinite number?

I was not asking for a new option, only to be able to choose [...]
How can you choose if there is no new option?

What percentage of sources are likely to have these artifacts
I don't know. Probably most sources have very minor ringing artifacts, which might not bother 99.9% of all users. Some sources probably have more obvious artifacts than others.

how good of a general use filter is this?
I don't know. You tell me!

Also, does deringing help with ringing created by compression of a source, where too much information is lost around high frequencies edges?
I've already explained before which kinds of artifacts this filter is supposed to fix, and how and why these artifacts occur.

Maybe the filter also fixes some compression artifacts as a side effect, I don't know, but that's not what it was designed to do.

Oh wow, that's far better than I thought you'd achieve with adding some grain, absolutely spectacular! Amazing work madshi.
FWIW, the added grain is only a part of the overall quality improvement. I've also done some other tweaks to the deringing algo.

[CarlosCaco]

Ok, I'll wait for screenshots.



How can you choose if there is no new option?




the same way we choose with all other bigger upscaling factors
if we want to sharpen the source we use image enhacements
if we want apply the sharpen after upscaling use upscalling refinements
if we want use in both use in both

this give the option to user decide what is best, as i said ATM madvr dont allow me to use upscalling refinements if the scalling factor is small... such as 720p to 1360x768, only allow me to use image enhacements
but don´t want to bother you with a situation that only me is asking...
these resolutions will sooner be end... almost everyone is using at least fullhd tv projectors and monitors... and seens that in general theres no such a smaller diference between the movies and the display, only bigger upscalling factors..

[Nevilne]

use profiles

[huhn]

use profiles

and how should a profile trigger it?

[Nevilne]

in his specific case, something like


processing>image enhancements

if (scalingFactor.x>1) or (scalingFactor.y>1) "sharpen"
else "normal"

[CarlosCaco]

in his specific case, something like


processing>image enhancements

if (scalingFactor.x>1) or (scalingFactor.y>1) "sharpen"
else "normal"

profiles don´t solve this... i just want to use upscalling refinements when upscalling hd to hd+ but as madshi said sometime ago madvr internaly don ´t active upscalling refinements for such a small scalling factor...
even if set to use upscalling refinements... the same with supersampling madvr doubles the image downscalle but don´t apply upscalling refinements, a least until v.18, i wil tes .19
but serious maybe this subjetic is extending too much, i don ´t want to bother madshi and other users with my specific situation

[bcec]

Just when I thought madVR can't get any better, and that it is already amazing as it is... this deringing thing is frigging fantastic! Ringing in the original bluray source is my number 1 annoyance. I am even annoyed by ones caused by very mild DNR+EE that is present in newer titles like Force Awakens. This thing is doing wonders! A big THANK YOU!

[70MM]

If using Exclusive Mode, do you also have Full screen Window mode turned on?

[Asmodian]

If using Exclusive Mode, do you also have Full screen Window mode turned on?

Exclusive and Windowed modes are mutually exclusive. That is what "windowed" means in this context, i.e. "not exclusive".

Or do you meant something else?

[70MM]

Exclusive and Windowed modes are mutually exclusive. That is what "windowed" means in this context, i.e. "not exclusive".

Or do you meant something else?

So you never have both turned on at the same time, correct?

[70MM]

Is there anyway to stop the small couple of jumps I get at the start of each movie?
There are no frame drops after a few secs..

[Asmodian]

I think so, but I'm not sure right now.

Thanks, This might actually be the preferred behavior too.

Now that madVR handles HDR files, and there is even some wide gamut content, users might be very confused if an "HDR" BT.2020 or DCI P3 gamut file looked really washed out by default. You sort of need a default target gamut.

Having "unset" actually default to "Normal PC mode" makes sense to me but I suppose you could also remove that option and simply default a new display to "this display is already calibrated" set to BT.709 with pure power 2.20. Something to worry about for v1.0. ;)

I haven't mentioned it yet but "reduce ringing artifacts" is great.. like all these new options it is hard for me to offer useful feedback for but it is a Good Thing. The updated version is better still.
Thanks a lot. :thanks:

So you never have both turned on at the same time, correct?
Correct.

Is there anyway to stop the small couple of jumps I get at the start of each movie?
There are no frame drops after a few secs..
The option "delay playback start until render queue is full" is your best bet. Try increasing queue sizes if needed.

[70MM]

Correct.


The option "delay playback start until render queue is full" is your best bet. Try increasing queue sizes if needed.

When I try to use Exclusive mode by itself the image starts to break up and stutter.

When I playback in just Window Mode its stable, why is this?

[70MM]

The option "delay playback start until render queue is full" is your best bet. Try increasing queue sizes if needed.

I have "delay playback start until render queue is full" turned on yet I still get the few dropped frames at the start of everything for a couple of secs.

When increasing queue size, which cue do I increase, the render one?
What numbers might some people here increase this to?
I have all mine set at 8...

[Asmodian]

I have "delay playback start until render queue is full" turned on yet I still get the few dropped frames at the start of everything for a couple of secs.

When increasing queue size, which cue do I increase, the render one?
What numbers might some people here increase this to?
I have all mine set at 8...

There are so many things it might be it is hard to offer specific suggestions. Try increasing and decreasing all the queues within their full range (well, over 24 GPU queue is getting crazy). You can use GPU-Z (https://www.techpowerup.com/gpuz/) or similar to watch your video memory to make sure you aren't running out with very large queue sizes.

Try lower queues too, all the way down to the minimums. Try changing the "how many video frames shall be presented in advance" numbers too. Usually the CPU queue size is less important, as long as it is big enough and usually stays full.

[70MM]

Is there a way for a 3rd party control system to control any of the MADVR functions via IP? I have currently been using Eventghost but I would like to eliminate the middleman and control it directly if possible.

[mzso]

madVR v0.90.19 released

* deringing now adds some grain to deringed image areas[/code]

??? What's the point of this? Adding grain is just more noise isn't it?

[Patrik G]

problem with the Sony HDR camp Demo

well i had this problem before also with the picture turned all white but it would go away if i flipped between fullscreen and window mode
but now the blown out details are there all the time

any setting you can get it to work properly or is the problem with the Nvidia Graphics cards ?
latest madvr and latest lav build
http://privat.bahnhof.se/wb192876/Sony%20HDR.jpg

[burfadel]

??? What's the point of this? Adding grain is just more noise isn't it?

Grain is noise, but applying the right type of this type of noise can subjectively improve the picture. The key thing is to use a grain fine enough, grain that changes with each frame, and of the right strength. You only want a very slight amount!

I actually use Janwillem's Semi-randow greyscale noise shader with my own noise amount (it's configurable in the shader text file). I think it's great! You don't want colour noise, only luma. One of the things that is obvious with a very light amount of added noise is that the picture seems to be sharper without aliasing or other sharpen artifacts, and also the picture is less flat.

[Werewolfy]

It's not that easy. Edges are either detected as being ringing or not. If they are detected as being ringing then I try to remove them. Different "strengths" don't really make too much sense here. Well, ok, there are some thresholds I'm using. But if I allow you to lower those, you'll get less ringing removed and maybe fewer artifacts in some places, but then you'll get more ringing left in the image, and some other artifacts instead. I don't think it would really improve the situation much.

I understand your point but maybe it would makes sense to do a test build with different tresholds to play with? Maybe we will find a better compromise, maybe we won't.


But please try the next build, it has some (smallish) improvements. Maybe it works better for you? It's not perfect, though. And it probably never will.

I just tried it and I found more artefacts. Look at the teeth of the characters. It's maybe the only thing that keeps me to use it all the time with compressed videos.

Deringing 90.18 vs 90.19 (http://screenshotcomparison.com/comparison/173052)
Deringing off vs on (http://screenshotcomparison.com/comparison/173053)

Here's the original picture but I don't know if it will help because on my side, deringing doesn't seem to work on juste one picture.

http://postimg.org/image/5t877ur9t/

[nevcairiel]

problem with the Sony HDR camp Demo


That file is broken.

[SamuriHL]

Glad you like it!


Very much so! Watched some content this weekend with it. It's quite impressive indeed!!


JRiver MC uses the madVR version in the user folder. Ideally you should upgrade both versions. In theory you don't need 2 installations. You could remove the one from the Program Files folder. madVR would only work with JRiver MC then, though, and not in any other media player.


The way I do it is to run the install bat from the jRiver MC folder and then it's exposed to other players from that location, as well. It's been working for me.

[Patrik G]

That file is broken.

nope
next suggestion
am i the only one with this issue ? lol

everyone with a nvidia graphics card and Win10 should have this issue.

[huhn]

and everyone has the same problem because this file is broken.

[aufkrawall]

As expected, unfortunately deringing in .19 looks quite dirty with cartoons.

.18:
http://abload.de/thumb/18enk21.png (http://abload.de/image.php?img=18enk21.png)


.19:
http://abload.de/thumb/1923j7l.png (http://abload.de/image.php?img=1923j7l.png)

[Patrik G]

and everyone has the same problem because this file is broken.

ok i get it
didnt know the file was broken for all
thought it was a bad download so i downloaded it again and its the same.

lets hope for a new demo then.

whats broken with the sony hdr demo btw?

[huhn]

ok i get it
didnt know the file was broken for all
thought it was a bad download so i downloaded it again and its the same.

lets hope for a new demo then.

whats broken with the sony hdr demo btw?

i don't remember the exact number but the max brightness was something like 0.5 nits just as a reference SDR is 100 and HDR is usually about 1000.

[Patrik G]

i don't remember the exact number but the max brightness was something like 0.5 nits just as a reference SDR is 100 and HDR is usually about 1000.

yes i noticed it
it says 1 nit for hdr brightness with this demo so something is wrong
the other hdr demos reports 1000 nits

[ang3l]

@madshi

madvr 0.90.19 + mpc-hc (nightly) crash at start with last AMD crimson 16.5.2 hotfix

http://pastebin.com/XCWq7Akt

[Uoppi]

What numbers might some people here increase this to?
I have all mine set at 8...

Just do some testing and raise/lower the values to whatever works.

After some thorough testing a few months ago, my optimal settings for example turned out to be 6/20/20. Less or more than 6 didn't work properly and increasing past 20 didn't bring any added benefit (while 18 on the other hand was a tad too low). Now I never get unexpected drops after the playback has started.

[djfred93]

Just for knowing, ringing is this, right ?

http://imgur.com/zC5U2kK

[CarlosCaco]

It's difficult to make this configurable. Some users may share your opinion, others might not. If I added an option for this, it would be hard to understand for most users what the option means exactly.

Maybe you could activate supersampling (see image doubling section)? If you do that, upscaling refinement should work as expected. Of course this solution costs quite a bit of extra performance.


Hey madshi, as you suggest i tried again supersampling on v.19 and madvr still don´t activate upscalling refinements on my resolution movie = 720p, screen =1360x768
double checked on aways 2x supersampling and aways when upscaling is needed,
the image doubles, downscale but not apply the refinements
no image changes and no render times changes even if check all the refinements on high
remember you said one time that supersampling only actives upscaling refinements if screen resolution was the same as movie resolution... still not activating on my situation...
i trie restore default settings uninstal, and copy the new version and begin from 0 but still the same behave
by the time i have to use with only image enhacements with no supersampling, its preety good but has some distortions with ab enabled... thanks for your atention and again sorry for bother you and the others with this situation

[har3inger]

Just for knowing, ringing is this, right ?

http://imgur.com/zC5U2kK

Yes, that is compression ringing (artefact from low video bitrate). However, the dering filter is more targeted towards downscale ringing, which are thin halos right beside lines, not ripples a fair ways away. The filter may not remove the ringing in this image very well/at all.

[James Freeman]

Actually ringing is an artifact of sharpening of downscaled images.

For upscaling (chroma or luma) I don't think more than Bilinear is needed for accurate results.
Anyone disagree and why?

[burfadel]

@madshi

madvr 0.90.19 + mpc-hc (nightly) crash at start with last AMD crimson 16.5.2 hotfix

http://pastebin.com/XCWq7Akt

Works fine here (Windows 10 Insider). What OS and card do you have?