Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 18th October 2013, 03:58   #20421  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 5,964
sry in germany you can get a 660 ti for 185

235 wow ...

in your case the 650 ti NON boost.

or think about an import
huhn is offline   Reply With Quote
Old 18th October 2013, 06:12   #20422  |  Link
6233638
Registered User
 
Join Date: Apr 2009
Posts: 1,019
Quote:
Originally Posted by madshi View Post
I've found a quite promising new tweak for the debanding algorithm. So all ya debanding geeks out there, here's a new test build:

http://madshi.net/madVRdeband6.rar

The new feature is called "angleBoost" and you can control it via Ctrl+Alt+F9/F10 (decrease/increase) and Ctrl+Alt+Shift+F9/F10 (off/on). This feature checks whether the surrounding pixels all have the same gradient angle. If they do, the other parameters (avgDif, maxDif etc) are all multiplied with the "angleBoost" factor. So a factor of 1.0 means no change. A factor of 2.0 means double parameters.

It seems that this new feature might be able to separate details from gradients, so I hope we'll get a nice debanding improvement without losing any image detail. On the content I've tried so far an angleBoost of 2.0 seems to work quite nicely, although that might be a tad too high. Let me know what you think...

P.S: The angleBoost feature does consume a bit of additional rendering power. But from my first tests it seems to be more than worth it.
I might not get a chance to do much testing until the weekend now, but I'll do what I can.

Can we get a build which lets us customize the keyboard shortcuts though? I find them increasingly difficult to use.

I'd much rather be using QA, WS, ED, RF etc.
6233638 is offline   Reply With Quote
Old 18th October 2013, 08:20   #20423  |  Link
AngelGraves13
Registered User
 
Join Date: Dec 2010
Posts: 239
Quote:
Originally Posted by madshi View Post
Are you using Windows mode, Overlay mode or Fullscreen Exclusive Mode? For some people, smooth motion only really reliably works in Fullscreen Exclusive Mode. So try whether that fixes the problem. If not, does the OSD report presentation glitches or dropped frames?


Yeah, weird...

-------------------------

I've found a quite promising new tweak for the debanding algorithm. So all ya debanding geeks out there, here's a new test build:

http://madshi.net/madVRdeband6.rar

The new feature is called "angleBoost" and you can control it via Ctrl+Alt+F9/F10 (decrease/increase) and Ctrl+Alt+Shift+F9/F10 (off/on). This feature checks whether the surrounding pixels all have the same gradient angle. If they do, the other parameters (avgDif, maxDif etc) are all multiplied with the "angleBoost" factor. So a factor of 1.0 means no change. A factor of 2.0 means double parameters.

It seems that this new feature might be able to separate details from gradients, so I hope we'll get a nice debanding improvement without losing any image detail. On the content I've tried so far an angleBoost of 2.0 seems to work quite nicely, although that might be a tad too high. Let me know what you think...

P.S: The angleBoost feature does consume a bit of additional rendering power. But from my first tests it seems to be more than worth it.
Setting view does not go away. If I enable it, it just floats forever on top of the picture.
AngelGraves13 is offline   Reply With Quote
Old 18th October 2013, 09:56   #20424  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,137
Quote:
Originally Posted by 6233638 View Post
I might not get a chance to do much testing until the weekend now, but I'll do what I can.

Can we get a build which lets us customize the keyboard shortcuts though? I find them increasingly difficult to use.

I'd much rather be using QA, WS, ED, RF etc.
Sorry, no easy way to customize the keyboard shortcuts. What is so hard about using them?

I've intentionally released this test build *before* the weekend, so that you guys have it before the weekend starts, so no part of the weekend is lost...

Quote:
Originally Posted by AngelGraves13 View Post
Setting view does not go away. If I enable it, it just floats forever on top of the picture.
That is intentional for the test builds. It stays on for 20 seconds. The purpose is that you have a lot of time to play with the parameters. If it went away after 3-4 seconds, like all other OSD messages, that would make tweaking the parameters more difficult. The OSD message will be cut down to 3-4 seconds when the next official build is released.
madshi is offline   Reply With Quote
Old 18th October 2013, 10:31   #20425  |  Link
6233638
Registered User
 
Join Date: Apr 2009
Posts: 1,019
Quote:
Originally Posted by madshi View Post
Sorry, no easy way to customize the keyboard shortcuts. What is so hard about using them?
Well I don't have a number pad or function keys on my keyboard for one thing. So Ctrl+Alt+Shift+F9 means I'm pressing five keys at once. (F9 becomes Fn+9)
I can touch-type, but I have difficulty doing Ctrl+Alt+Shift 1-9 without looking at the keyboard, instead of looking at the screen while making adjustments.

With AltGr instead of Ctrl+Alt, and something like
QWERT: +
ASDFG: −
ZXCVB: on/off

You're only ever pressing two keys, and shouldn't have to look at the keyboard.
6233638 is offline   Reply With Quote
Old 18th October 2013, 10:44   #20426  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,137
Well, there aren't so many letter keys left which are next to each other and not already in use by default madVR settings. Ok, I've modified F9/F10 to K/L now. But I don't have a replacement for the number keys.

http://madshi.net/madVRdeband7.rar

This build also has a bugfix in it, so please everybody who uses the debanding test build update to this one. The keys for the "angleBoost" are now Ctrl+Alt+K/L and Ctrl+Alt+Shift+K/L.
madshi is offline   Reply With Quote
Old 18th October 2013, 11:09   #20427  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,227
Angleboost is amazing.

Here's my offer for the low preset.

6233638, I have tested this vs your previous preference and have found these settings provide better debanding and much improved shadow detail retention.
It could probably still tweak a bit here and there like anything, but overall I'm quite impressed. A excellent find with this setting Madshi!

After some more testing I conclude Localcontrast is not required for great results.

Code:
		avgDif	maxDif	grad	penalty  localcontrast   angleboost
low:		0.6	2.4	1.0	1.2	 off             2.0
Quote:
Originally Posted by madshi View Post
This build also has a bugfix in it
What was fixed? does it affect picture quality?

Last edited by ryrynz; 18th October 2013 at 13:02.
ryrynz is offline   Reply With Quote
Old 18th October 2013, 11:15   #20428  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,137
Quote:
Originally Posted by ryrynz View Post
Angleboost is amazing.


FWIW, the AngleBoost feature isn't perfect. It misses some parts where debanding should be applied. So we should make sure that we don't lower the other parameters too much. The other parameters should still do useful debanding even without AngleBoost. Maybe your suggested settings already do, haven't checked. Just wanted to say...

Quote:
Originally Posted by ryrynz View Post
What was fixed? does it affect picture quality?
I had nonGradiantPenalty and localContrast swapped in the OSD. Meaning if the OSD claimed you had localContrast off, you actually had nonGradiantPenalty off and vice versa. I'm sorry about the confusion!
madshi is offline   Reply With Quote
Old 18th October 2013, 12:12   #20429  |  Link
ryrynz
Registered User
 
ryrynz's Avatar
 
Join Date: Mar 2009
Posts: 3,227
Quote:
Originally Posted by madshi View Post


FWIW, the AngleBoost feature isn't perfect. It misses some parts where debanding should be applied. So we should make sure that we don't lower the other parameters too much. The other parameters should still do useful debanding even without AngleBoost. Maybe your suggested settings already do, haven't checked. Just wanted to say...
Maybe not but it made it jump up to a whole new level, I will continue to tinker with it, I'm hoping madVR can have the low preset enabled by default.

Quote:
Originally Posted by madshi View Post
I had nonGradiantPenalty and localContrast swapped in the OSD. Meaning if the OSD claimed you had localContrast off, you actually had nonGradiantPenalty off and vice versa. I'm sorry about the confusion!
Ah that explains the lack of difference I saw with localcontrast disabled.. anyway did another test with build 7 and I'm on the fence regarding localcontrast, it does so little I'm not sure it's worth having.
I might enable if it was an available option and I had the GPU power for it, I'm not going to push for the option to be there though, have adjusted my preset accordingly.

Making a comparison vs my old f3kd settings shows my current low preset providing vastly better detail retention whilst maintaining about the same deband strength, awesome stuff.

Last edited by ryrynz; 18th October 2013 at 13:15.
ryrynz is offline   Reply With Quote
Old 18th October 2013, 13:26   #20430  |  Link
Ver Greeneyes
Registered User
 
Join Date: May 2012
Posts: 445
Quote:
Originally Posted by madshi View Post
FWIW, the AngleBoost feature isn't perfect. It misses some parts where debanding should be applied. So we should make sure that we don't lower the other parameters too much.
It might not matter much, but have you concidered changing AngleBoost from a binary threshold to a continuum? i.e. use the degree to which the angles match (from -100% to 100% say) to decide how much to boost or penalize the strength of the other settings?

(you could even apply a knee strength setting to the result, like in dynamic range compression, but that's probably getting too fancy for how much good it'll do)

Last edited by Ver Greeneyes; 18th October 2013 at 13:29.
Ver Greeneyes is offline   Reply With Quote
Old 18th October 2013, 13:52   #20431  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,137
So two suggestions:

(1) penalty vs. boost: I think a penalty for non-matching angles would make things too complicated. Sometimes the angles don't match, but still debanding is needed. So I think a pure boost is a better solution. This way we can set up the other thresholds to do a minimum of debanding in case the angles don't match, and we can rely on that this minimum amount of debanding is always applied.

(2) binary threshold vs continuum: I've actually thought about this, too. All the other thresholds are already applied with "FuzzyLogic" (continuum instead of binary threshold, using a simplified knee strength algorithm). The AngleBoost is currently a binary threshold. I could make the AngleBoost non-binary, too, but I'm not sure if I should do that. FWIW, there are 4 surrounding pixels I have to take into account (each with its own angle), that makes it different to find a continuum formula which covers all the possible situations. But I'll go experiment a little, maybe I can find a solution which works well enough...
madshi is offline   Reply With Quote
Old 18th October 2013, 15:53   #20432  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,137
Ok, here's the latest build:

http://madshi.net/madVRdeband8.rar

Changes:

(1) The AngleBoost is now of variable strength, depending on how much the angle differs (suggested by Ver Greeneyes).
(2) You can now define both the AngleBoost strength (Ctrl+Alt+H/J), and also the "MaxAngle" for with the boost is applied (Ctrl+Alt+K/L).
(3) You can still turn the AngleBoost completely on/off (Ctrl+Alt+Shift+H/J).
(4) You can activate a debug mode (Ctrl+Alt+Shift+K/L) which shows to which image areas the AngleBoost is applied. White image areas get the full boost. Black image areas don't get any boost. Gray areas get a reduced boost. That should help figuring out the optimal "MaxAngle".

The current default values are "AngleBoost = 2.0" and "MaxAngle = 0.2". Practically this means that if the angle of a gradient differs by up to 13.333%, all thresholds are multiplied by 2x. If the angle differs by 20%, all thresholds are unchanged. If the angle differs by a value between 13.333% and 20% the thresholds are multiplied by a value between 1.0 (20%) and 2.0 (13.333%). For example, an angle difference of 15% would result in a threshold boost of 1.75x.

My first tests indicate that for some gradients the "MaxAngle" could be set as low as 0.01. However, for other gradients, we need at least 0.10-0.15. Maybe even 0.20. Let me know what you think.
madshi is offline   Reply With Quote
Old 18th October 2013, 16:18   #20433  |  Link
Francois76l
Registered User
 
Join Date: Oct 2013
Location: France - Paris
Posts: 19
Smooth Motion

Hello Madshi!
First, thanks for your amazing work along the years!
I've one question concerning the smooth motion option under madVr v0.86.11.
On my computer (i7 3770k @4.6Ghz + 660GTX Ti + 8Go ram) The picture quality is bad with this option (@60Hz). There is no difference in the picture fluidity and sometimes I can see some frame doubling. It's really strange.

I'm using Windows 7 Pro N (special version without Windows Media Player and Media Center) Do you think my problem can be link?
Thanks again for your help

Quote:
Originally Posted by madshi View Post
Are you using Windows mode, Overlay mode or Fullscreen Exclusive Mode? For some people, smooth motion only really reliably works in Fullscreen Exclusive Mode. So try whether that fixes the problem. If not, does the OSD report presentation glitches or dropped frames?
Hello Madshi. Thanks for your answer.
I've no dropped frames and no glitches (ctrl+j) and I'm using Fullscreen Exclusive Mode. Sorry for my poor explanations in my first question.

I'm using MPC-BE + LAV Splitter + LAV Video decoder (8 bits YV12 output) + ffdshow with some avisynth scripts (4:4:4 AYUV output) + MadVr 0.86.11

On Madvr:
- Chroma upscaling Jinc 3taps + anti ringing
- Image downscaling Jinc 8taps + anti ringing
- Nothing in "Trade quality for performance"
- Smooth motion On...
- CPU queue size: 12 / GPU: 8

I've also remarked 1 thing. On my Benq W1070 if I output 16 bits colorspace (P016, P216 or Y416) my black are little grayed compared to a 8 bits output. am I crazy?

Thanks again for your explanations Madshi!
Francois76l is offline   Reply With Quote
Old 18th October 2013, 17:34   #20434  |  Link
Werewolfy
Registered User
 
Join Date: Feb 2013
Posts: 135
Quote:
Originally Posted by madshi View Post
Ok, here's the latest build:

http://madshi.net/madVRdeband8.rar

Changes:

(1) The AngleBoost is now of variable strength, depending on how much the angle differs (suggested by Ver Greeneyes).
(2) You can now define both the AngleBoost strength (Ctrl+Alt+H/J), and also the "MaxAngle" for with the boost is applied (Ctrl+Alt+K/L).
(3) You can still turn the AngleBoost completely on/off (Ctrl+Alt+Shift+H/J).
(4) You can activate a debug mode (Ctrl+Alt+Shift+K/L) which shows to which image areas the AngleBoost is applied. White image areas get the full boost. Black image areas don't get any boost. Gray areas get a reduced boost. That should help figuring out the optimal "MaxAngle".

The current default values are "AngleBoost = 2.0" and "MaxAngle = 0.2". Practically this means that if the angle of a gradient differs by up to 13.333%, all thresholds are multiplied by 2x. If the angle differs by 20%, all thresholds are unchanged. If the angle differs by a value between 13.333% and 20% the thresholds are multiplied by a value between 1.0 (20%) and 2.0 (13.333%). For example, an angle difference of 15% would result in a threshold boost of 1.75x.

My first tests indicate that for some gradients the "MaxAngle" could be set as low as 0.01. However, for other gradients, we need at least 0.10-0.15. Maybe even 0.20. Let me know what you think.
I did some tests with your latest build and AngleBoost seems to be a great idea! It allows a better debanding with less details blurred. A value of 0.20 for MaxAngle seems to be a good choice, I found one case where 0.15 is not enough and no case where 0.20 is too low.

Here are my settings for low :
avgDif 0.6, maxDif : 2.0, gradient 1.3, nonGradientPenalty : 1.2, localContrast ; off, angleBoost : 2.0, maxAngle : 0.20 .

1.0 for gradient is not enough sometimes like I saw in a earlier post and we can lower maxDif at 2.0. The debanding is better than before with my low settings (0.7, 2.4, 1.5, 1.2, off) and details are better preserved.

Great job madshi
Werewolfy is offline   Reply With Quote
Old 18th October 2013, 19:46   #20435  |  Link
mandarinka
Registered User
 
mandarinka's Avatar
 
Join Date: Jan 2007
Posts: 735
This might eventually become interesting for smooth video playback, in the future: http://www.pcper.com/news/Graphics-C...tor-Technology

Basically it makes the rendering on an LCD fully VFR. Sadly, it needs special logic in the monitor, might be nvidia-only feature, and what's worst, will cost extra (so it might end up in highend devices only).
mandarinka is offline   Reply With Quote
Old 18th October 2013, 21:17   #20436  |  Link
bacondither
Registered User
 
Join Date: Oct 2013
Location: Sweden
Posts: 125
The new angleBoost algorithm seems to work good some times and bad other times. Especially it seems to blur sharp dark lines alot, and it seems to detect dark grey flat colored boxes as gradients.

It seems to be effective at removing banding in heavy banded material at the expense of blurring sharp dark details.
I would prefer it off on a low deband setting and maby turn it on at medium or high.

I've concocted a test image with some dark boxes of different sizes and a banded gradient:
Test image

Contrast boosted (easier to spot differences) images with different settings on the previously mentioned test image:
No debanding

(My prefered settings "low") avgDif0.7, maxDif 2.4, gradient 1.5, nonGradientPenalty 1.2, localcontrast off, angleBoost off

avgDif0.7, maxDif 2.4, gradient 1.5, nonGradientPenalty 1.2, localcontrast off, angleBoost 2.0, maxAngle 0.20

avgDif0.6, maxDif 2.0, gradient 1.3, nonGradientPenalty 1.2, localcontrast off, angleBoost 2.0, maxAngle 0.20

avgDif0.6, maxDif 2.0, gradient 1.3, nonGradientPenalty 1.2, localcontrast off, angleBoost 2.0, maxAngle 0.01

angleBoost debug mode

/Addendum
I was looking for a medium setting and made a full screen gradient with <7-bit (<127 steps) to simulate bitdeph loss. And i found that the settings below was sufficient to smooth the stairstep gradient to a continuous smooth gradient.

My suggestion for medium debanding:
avgDif 1.1, maxDif 3.0, gradient 2.5, nonGradientPenalty 1.3, localContast off, angleBoost off

Last edited by bacondither; 18th October 2013 at 22:06.
bacondither is offline   Reply With Quote
Old 18th October 2013, 22:23   #20437  |  Link
Werewolfy
Registered User
 
Join Date: Feb 2013
Posts: 135
I haven't seen this issue... Does it do that even with lower values? 2.0 for angleBoost is maybe too much.

Can you send here your test video?

Last edited by Werewolfy; 19th October 2013 at 00:47.
Werewolfy is offline   Reply With Quote
Old 18th October 2013, 23:41   #20438  |  Link
iSunrise
Registered User
 
Join Date: Dec 2008
Posts: 497
Quote:
Originally Posted by mandarinka View Post
This might eventually become interesting for smooth video playback, in the future: http://www.pcper.com/news/Graphics-C...tor-Technology

Basically it makes the rendering on an LCD fully VFR. Sadly, it needs special logic in the monitor, might be nvidia-only feature, and what's worst, will cost extra (so it might end up in highend devices only).
Damn you´re fast. Also wanted to post it and ask madshi, what he thinks this could mean regarding madVR and video playback.

Since Nvidia hasn´t yet detailed how exactly G-Sync operates (they said it switches to 3D-Mode) it seems a bit early to tell. However, since madVR basically behaves like a game that uses a D3D-variant and supports fullscreen exklusive, this seems like a no-brainer at first.

Perfectly smooth playback with any input fps at (hopefully) sanely priced monitors (as long as the panel is fast enough) just seems too good to be true.
iSunrise is offline   Reply With Quote
Old 19th October 2013, 00:38   #20439  |  Link
e-t172
Registered User
 
Join Date: Jan 2008
Posts: 568
Yes, G-SYNC seems very exciting. What's more, that would probably mean that the application has full control over the display clock and is not constrained by the video clock anymore, which would remove audio/video clock drift issues and thus render ReClock completely useless!
e-t172 is offline   Reply With Quote
Old 19th October 2013, 00:52   #20440  |  Link
turbojet
Registered User
 
Join Date: May 2008
Posts: 1,840
It would be nice if nvidia worked with competitors on a standard. So we don't get 3 different technologies programs need to support which reduces the chances of supporting it. Then of course we'll probably get some things that only support one technology (paid off?). Comparable to cuvid, quicksync and opencl vs dxva.

Code:
		avgDif	maxDif	grad	penalty	contrast
low:		0.7	2.4	1.6	1.2	1.4
maximum:	1.9	3.7	4.3	off	off
Maximum is giving me really nice results without any noticeable banding in normal viewing. It's surprising how much improvement it gives to the not so great material (US HDTV) I watch, much more than f3kdb. Good work!
__________________
PC: FX-8320 GTS250 HTPC: G1610 GTX650
PotPlayer/MPC-BE LAVFilters MadVR-Bicubic75AR/Lanczos4AR/Lanczos4AR LumaSharpen -Strength0.9-Pattern3-Clamp0.1-OffsetBias2.0
turbojet is offline   Reply With Quote
Reply

Tags
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 12:26.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.