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 25th January 2019, 18:19   #54461  |  Link
madjock
Registered User
 
Join Date: May 2018
Posts: 259
Quote:
Originally Posted by Warner306 View Post
With most HDR displays, it is not advisable to change the brightness or contrast controls because you can offset the display's tone mapping, which is based on the default settings for both.
Thats the part I struggle with, I have lots of presets and Movie is usually a favorite, but unsure what is right or wrong. I turn off all processing and motion options, but when I tried any HDR calibration items, especially black and white I could not achieve anything near the finesse of adjusting for clipping on an SDR display.
madjock is offline   Reply With Quote
Old 25th January 2019, 19:53   #54462  |  Link
hannes69
Registered User
 
Join Date: Nov 2012
Posts: 99
Quote:
Originally Posted by Warner306 View Post
Coil whine is defect of the fan, so NGU can exasperate it, but not cause it..
No.
My passive GPU has coil whine as well. That has nothing to do with a fan.
Additionally the coil whine seems to be triggered by the kind of electric load caused by NGU, it doesnīt depend on the strength of the load but on the 'sort' of load.
Nothing to do against it - beside of some nasty (and maybe not working) decoupling tricks with glue, plastic spray etc.
Coil whine is part of NGU (on the hardware side)
Madshi should implement a totally new scaler that is better in all regards than all other recent scalers and of course coil-whine-proof
hannes69 is offline   Reply With Quote
Old 25th January 2019, 20:28   #54463  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,403
It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 25th January 2019, 20:41   #54464  |  Link
tp4tissue
Registered User
 
tp4tissue's Avatar
 
Join Date: May 2013
Posts: 706
Quote:
Originally Posted by Asmodian View Post
It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.

It isn't always the choke, the Core itself is susceptible to piezoelectric effects given the right frequency of operation.

Capacitors also, but usually only big ones.
__________________
Ghetto | 2500k 5Ghz
tp4tissue is offline   Reply With Quote
Old 25th January 2019, 21:02   #54465  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,403
Woah! I have never head of that, the core resonating at audible frequencies enough to make noise!?! It seems like that would be really bad. Do GPUs have capacitors big enough to make noise?

It wouldn't be coil whine either, the coils in that description are the chokes.

Anyway my point still stands, this is not NGU's fault, it is simply a common defect in the hardware that can be triggered by NGU or any other GPU load.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 25th January 2019, 21:33   #54466  |  Link
tp4tissue
Registered User
 
tp4tissue's Avatar
 
Join Date: May 2013
Posts: 706
Quote:
Originally Posted by iSeries View Post
385.28 probably works easiest if you are using a custom resolution. With later drivers (not sure when it started), madVR could only create 8bit custom resolutions, which means needing CRU to create it. I found 416.35 to work great if not using a custom resolution (or if creating an 8bit custom res with madVR, or creating a 12bit custom res with CRU). I believe the latest driver will only kick into HDR if madVR sends 10bit, regardless of whether the GPU driver is set to 12bit or 8bit.

You should look and carefully compare 12bit vs 8bit. Many TVs will show colour banding with 12bit input which isn't there when given 8bit.

Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..
__________________
Ghetto | 2500k 5Ghz

Last edited by tp4tissue; 25th January 2019 at 21:36.
tp4tissue is offline   Reply With Quote
Old 25th January 2019, 21:38   #54467  |  Link
hannes69
Registered User
 
Join Date: Nov 2012
Posts: 99
Quote:
Originally Posted by Asmodian View Post
Anyway my point still stands, this is not NGU's fault, it is simply a common defect in the hardware that can be triggered by NGU or any other GPU load.
Yes, you can read in the net here and there about coil whine in PSUs and GPU boards, sometimes more often with certain manufacturers and models, so to speak a kind of hardware defect.
But many people in this thread here reported independantly about coil whine in combination with NGU. And many confirmed that the whine only can be triggered by NGU. So you have coil whine by using NGU with e.g. 85% GPU load and you have no coil whine when using any other scaler with 85% GPU load.
So NGU seems to trigger a kind of 'load distribution' or whatever you call it that triggers coil whine.
A perfect coil should not produce any noise of course. But we donīt live in a perfect world
My GPU NEVER makes any noise (independant of load) with the exception of NGU (-> coil whine).
Interesting physical phenomena
Of course I donīt blame NGU or madshi. The coil should be mute in all possible situations, but NGU seems to be a strong trigger for unknown reasons.

Last edited by hannes69; 25th January 2019 at 21:40.
hannes69 is offline   Reply With Quote
Old 25th January 2019, 22:23   #54468  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,403
madVR is a very spiky load. After the buffers are full it renders one frame as fast as possible then idles until the next frame needs to be rendered. NGU simply needs more work done by the GPU so these odd peaks last longer. I think this is why NGU seems to trigger coil whine in a way that many GPU bound applications do not.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 26th January 2019, 00:14   #54469  |  Link
Warner306
Registered User
 
Join Date: Dec 2014
Posts: 1,127
Quote:
Originally Posted by Asmodian View Post
It isn't the fan it is the chokes or coils in the power delivery circuits, hence "coil whine".

The power circuits are contently turning off and on because they use PWM to control power output. Anytime this on/off cycle matches a resonate frequency or harmonic of the coils they can vibrate audibly. Almost any load can cause coil whine if you have coils that can vibrate audibly. The GPU core and memory also use different power circuits so it isn't surprising to have memory load (power draw) cause whine if it is one of those coils that is resonating.

Coil whine is not "part of NGU". NGU is simply a somewhat heavy, but not 100%, load on the card. I do not have any coil whine with NGU (or anything else) because the power circuitry on my card, or my previous one, does not resonate at any audible frequencies under any loads I have run so far. Don't blame NGU, blame whoever made your GPU for selecting chokes that can whine.
That is informative. I've never experienced coil whine, either. I did have an idea of what it sounds like, but the GPU has always managed to arrive in working order. I would have hoped this would be less common in new GPUs by this point.
Warner306 is offline   Reply With Quote
Old 26th January 2019, 00:18   #54470  |  Link
Warner306
Registered User
 
Join Date: Dec 2014
Posts: 1,127
Quote:
Originally Posted by tp4tissue View Post
Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..
Come on man, you are bordering on spamming this thread with random stuff.

There is one gradient test in the madVR guide in my signature that can be of some help, but you might have to find some blue skies in UHD Blu-rays to prove or disprove banding.
Warner306 is offline   Reply With Quote
Old 26th January 2019, 00:55   #54471  |  Link
actarusfleed
Registered User
 
Join Date: Jun 2009
Posts: 71
code do not work

Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...



if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"

Surely I've missed something ....

Any help?
thank you
actarusfleed is offline   Reply With Quote
Old 26th January 2019, 01:09   #54472  |  Link
Alexkral
Registered User
 
Join Date: Oct 2018
Posts: 319
Quote:
Originally Posted by huhn View Post
just frame match and let the TV do it.

doing 5/1 instead of 5/2 interpolation is massively better anyway even through i would use neither.
That's unusable because of the input lag, and yes 5/1 is kind of what I'm doing.
Alexkral is offline   Reply With Quote
Old 26th January 2019, 01:46   #54473  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,403
Quote:
Originally Posted by actarusfleed View Post
if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"
I think these greater than signs should be less than or equal to signs.

However, I would also rewrite it simpler:
Code:
If (deintFps < 26) and ((srcWidth <= 1920) and (srcHeight <= 1080)) "1080p24"
else if ((srcWidth <= 1920) and (srcHeight <= 1080)) "1080p60"
else if (deintFps < 26) "2160p24"
else "2160p60"
Remember, if an If statement validates it doesn't continue to the next statement so you only need to account for content in the next rule that doesn't match an earlier one.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 26th January 2019, 05:59   #54474  |  Link
austonrush
Registered User
 
Join Date: Oct 2015
Posts: 33
Quote:
Originally Posted by actarusfleed View Post
Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...

if (deintFps <= 25) and (srcWidth > 1920) "2160p24"
else if (deintFps <= 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p24"
else if (deintFps > 25) and (srcWidth > 1920) "2160p60"
else if (deintFps > 25) and ((srcWidth <= 1920) and (srcHeight > 1080)) "1080p60"

Surely I've missed something ....

Any help?
thank you
I run 9 profiles for my scaling algorithms and below is my profile rules. I only run 4 processing profiles based on sd, hd, fullhd and 4k.

This allows me to max out and also micro adjust for 24fps versus 60fps on each resolution type.

if ((srcHeight <= 540) and (deintFps < 25)) "SD 24fps"
else if ((srcHeight <= 540) or (fileName = "*.avi")) "SD 60fps"
else if ((filename = "*3D*") and (srcHeight <= 720)) "HD 3D"
else if ((srcheight <= 720) or (fileName = "*720p*")) and (deintFps < 30) "HD 24fps"
else if ((srcheight <= 720) or (fileName = "*720p*")) "HD 60fps"
else if ((filename = "*3D*") and (srcheight <= 1080)) "FullHD 3D"
else if ((srcheight <= 1080) or (fileName = "*1080p*")) and(deintFps < 25) "FullHD 24fps"
else if ((srcheight <= 1080) or (fileName = "*1080p*")) "FullHD 60fps"
else if ((srcheight <= 2160) or (fileName = "*2160p*")) and(deintFps < 61) "4k"

If anyone knows a better way to activate a 3d playback profile other than with the filename please let me know!?

Last edited by austonrush; 26th January 2019 at 06:21.
austonrush is offline   Reply With Quote
Old 26th January 2019, 14:04   #54475  |  Link
madjock
Registered User
 
Join Date: May 2018
Posts: 259
Quote:
Originally Posted by actarusfleed View Post
Hi, I've tried to do the same thing on two different PCs...
I've installed only MPC-HC and last official build of Madvr.
I set a code to change automatically profiles but do not works ...

Any help?
thank you
I am confused, are you saying your profile has not changed the refresh rate ?, as it is a 23.976 file running at 60, you need to setup the refresh rate for that.
madjock is offline   Reply With Quote
Old 26th January 2019, 14:45   #54476  |  Link
mclingo
Registered User
 
Join Date: Aug 2016
Posts: 1,348
Quote:
Originally Posted by tp4tissue View Post
Is there a 10bit 8bit gradient test pattern confirmed to distinguish noticeably in Madvr..
https://forum.doom9.org/showthread.php?t=172128
__________________
LG OLED EF950-YAM RX-V685-RYZEN 3600 - 16GBRAM - WIN10 RX 5700 - https://www.videohelp.com/software/madVR/old-versions
mclingo is offline   Reply With Quote
Old 26th January 2019, 19:15   #54477  |  Link
brazen1
Registered User
 
Join Date: Oct 2017
Posts: 331
I'm hoping you folks can help me edit my profile(s). I like the idea of more madVR control based on FPS @austonrush exampled a couple posts up. (Side note - is FPS the same as Hz and refresh rate in this regard?) 2160p 23/24FPS allows more aggressive settings in Scaling vs 2160p 60FPS for example. Since I don't use a profile separating the two, I use less aggressive settings to meet the demands of 2160p 60FPS but desire to use higher settings for 2160p 23/24 FPS. I'd like this to automate based on a profile. I'd prefer not to add something in a file name to trigger and use metadata instead if possible (as I presently am) but will only if necessary. I'm only interested in separating 2160p 23/24 FPS and 2160p 60 FPS for SCALING at this time but would welcome others. Here are my present profiles:

DISPLAY profile for calibration tab based on BT.2020 vs BT.709

if (HDR) "BT.2020"
else "BT.709"

PROPERTIES profile based on 10-bit vs 8-bit native bitdepth setting (both currently set to 8bit and really not in use at this time but may be in the future)

If (deintFps <= 30) "10-bit"
else "8-bit"

PROCESSING profile based on 2160p, 1080p, 720p, and SD resolutions

if (srcWidth > 1920) "2160p"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"


SCALING profile based on 2160p,1080p, 720p, and SD resolutions

if (srcWidth > 1920) "2160p"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"


RENDERING profile based on 3D, 2160p, 1080p, 720p, and SD resolutions

if (3D) "3D"
else if (srcWidth <= 720) and (srcHeight <= 576)"SD"
else if (srcWidth <= 1280) and (srcHeight <= 720)"720p"
else if (srcWidth <= 1920) and (srcHeight <= 1080)"1080p"
else if (srcWidth <= 3840) and (srcHeight <= 2160)"2160p"


*EDIT*
Maybe this will help others? I edited my '2160p' profile to '2160p 24fps' and used more aggressive settings.
I added another profile '2160p 60fps' and retained the old calmer settings.
I edited the SCALING rules to this: If someone knows of something more elegant...

if (srcWidth > 1920) and (deintFps < 25) "2160p 24fps"
else if (srcWidth <= 1920) and (srcHeight > 1080) "2160p 24fps"
else if (srcheight <= 2160) and (deintFps > 59) "2160p 60fps"

else if (srcWidth > 1280) and (srcWidth <= 1920) "1080p"
else if (srcWidth <= 1280) and ((srcHeight > 720) and (srcHeight <= 1080)) "1080p"

else if (srcWidth > 960) and (srcWidth <= 1280) "720p"
else if (srcWidth <= 960) and ((srcHeight > 540) and (srcHeight <= 720)) "720p"

else if (srcWidth <= 960) and (srcHeight <= 540) "SD"

Now I can control 2160p 60fps and 24fps separately.
__________________
HOW TO-Kodi 2D-3D-UHD (4k) HDR Guide Internal & External Players
W11 Pro 23H2 GTX960-4GB RGB 4:4:4 @Matched Refresh Rates 8,10,12bit
KODI 21 MPC-HC/BE 82" Q90R Denon S720W

Last edited by brazen1; 26th January 2019 at 21:29.
brazen1 is offline   Reply With Quote
Old 28th January 2019, 04:16   #54478  |  Link
Oguignant
Registered User
 
Oguignant's Avatar
 
Join Date: Nov 2016
Posts: 181
hello, what is the latest version of nvidia drivers that work with madvr + hdr
__________________
"To infinity, and beyond!"
Oguignant is offline   Reply With Quote
Old 28th January 2019, 06:16   #54479  |  Link
Klaus1189
Registered User
 
Join Date: Feb 2015
Location: Bavaria
Posts: 1,666
Quote:
Originally Posted by Oguignant View Post
hello, what is the latest version of nvidia drivers that work with madvr + hdr
https://forum.doom9.org/showthread.php?t=176013
Klaus1189 is offline   Reply With Quote
Old 28th January 2019, 07:14   #54480  |  Link
giulianoprs
Registered User
 
Join Date: Mar 2018
Posts: 39
Little curiosity, in devices / properties I set in the automatic "BIT", according to you is wrong? my tv is a plasma panasonic g20 is 8 bit.
When I look at the OS with a fullHD movie it tells me:
D3D11 fullscreen windowed (10BIT)
h264, 8 bit, 4: 2: 0 -> NV12, 8 bit, 4: 2: 0
do you think it's right or wrong?
giulianoprs 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 03:07.


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