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 21st September 2018, 01:22   #52641  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 5,657
Quote:
Originally Posted by madshi View Post
The Nvidia API is buggy there.
bugged in term of not working at all or something like nonsense reports?

if it is not utterly broken and reports "something" i would like to test it on a couple of screen of cause only if you still have a version with it lying around.
huhn is offline   Reply With Quote
Old 21st September 2018, 02:25   #52642  |  Link
Chouonsoku
Registered User
 
Join Date: Sep 2007
Posts: 38
Quote:
Originally Posted by madshi View Post
Is there a specific reason why you're not simply using "convert HDR content to SDR by using pixel shader math"? The "process" option has the potential problem that although madVR already did all of the tone mapping work, the TV might double process (= damage) it.
It's like I said in my post, processing via HDR -> SDR means my TV stays in SDR mode which has a lower peak brightness than the HDR mode. It also means I have to change my SDR mode picture settings on the TV for the HDR content (Bt.2020) and then back again when I'm playing SDR content (Rec.709) instead of being able to have separate SDR and HDR picture modes like I do with the passthrough option. I could be understanding this wrong, but I had to change a lot of settings to make the HDR tonemapped to SDR image look right on playback compared to how I've had the settings for my SDR content.

What is the "send HDR metadata to display" box for in this mode, by the way? I kind of assumed it was meant to submit the "new" HDR metadata that madVR maybe generates from using it's tonemapping algorithm to the TV. A lot of this was just my assumption that this mode was to put the TV into HDR mode. I'll play with the SDR conversion method and putting Windows into HDR manually via display settings. My goal was essentially to replace LG's tonemapping method with the one in madVR for HDR display. I had not considered the TV might doing a second process like you describe.

Quote:
Originally Posted by Warner306 View Post
madshi could maybe improve this. I know there is a new Panasonic Blu-ray player that gets along well with this setting with many displays. I have seen several examples where tone mapping the image before the display results in an image with more highlight detail with any display that clips too much at the top.

The tone mapping was optimized for HDR -> SDR, so I don't know if it was tested that much with a PQ output. You are probably compressing reference white (100 nits) too much at 400 nits. It would likely work better if you could find a higher value that only compresses the top of the curve to better match the bottom of the PQ curve enforced by the LG. Your display must be brighter than 400 nits in HDR mode.
Increasing the nits doesn't fix the super strong red hue, but they have to be that low to avoid the intense black crush that also happens with the HDR process setting. It was also set to 150 / 400 to make it easier to see the red problem in the photos.

Last edited by Chouonsoku; 21st September 2018 at 02:42.
Chouonsoku is offline   Reply With Quote
Old 21st September 2018, 03:30   #52643  |  Link
magic144
Registered User
 
Join Date: May 2005
Posts: 386
Playing back 720p HD mkv, run into new issue since (including) madVR version 0.92.15 (WASN'T present with 0.92.14 and reverting still works).

When I engage vobsub (idx/sub) subtitles via XySubFilter in Zoom Player, video freezes though audio continues. I don't get any subs. In fact the freezing only occurs at the point when the next sub would have appeared. It's non recoverable - have to restart player to restart video.
VobSub filter still works.
Plain text (SRT) subs still work in either sub filter.

Using AMD RX460 with Adrenalin 18.9.2 (latest) driver. Output is direct HDMI to Samsung monitor, 1920x1080 resolution.

Sub filters previously installed (as pair) via ZP Install Centre - reported as 3.1.0.747 via that installer.
VSFilter.dll (VobSub) shows 3.0.0.306
XySubFilter.dll (XySubFilter) shows 3.1.0.747
LAV Decoders 0.72.0 (video using DXVA2 copy-back)
Zoom Player is MAX v14.4b1 (latest, ZP is a 32-bit app)

----

UPDATE: same issue occurs on different PC w/ same software setup, but with older AMD Radeon HD5670
(again, reverting to madVR 0.92.14 works)
UPDATE2 (2018-09-21): issue confirmed in BOTH full-screen and windowed playback
UPDATE3 (2018-09-23): issue confirmed using LAV in BOTH (none) and DXVA2 (copy-back) acceleration (or not) modes
UPDATE4 (2018-09-23): issue confirmed on laptop w/ same software setup, but uses Intel HD GPU

Last edited by magic144; 23rd September 2018 at 20:08. Reason: added extra info
magic144 is offline   Reply With Quote
Old 21st September 2018, 06:57   #52644  |  Link
mrmojo666
Registered User
 
Join Date: Jan 2017
Posts: 80
@madshi, i'm not complaining with you, neither finger pointing. i'm just wondering if maybe it's possible to fine tuning something madvr side to make HDR auto switch more reliable.
__________________
AMD Ry 1500x - 8GB - RX460 4GB
TV Philips 55pus6501+ Marantz 1608 avr
WIN10(1903) 4K/444RGB
Mediaportal - Mpc-hc
MADVR-D3D11/10bit

Last edited by mrmojo666; 21st September 2018 at 07:58.
mrmojo666 is offline   Reply With Quote
Old 21st September 2018, 09:08   #52645  |  Link
Sunset1982
Registered User
 
Join Date: Sep 2014
Posts: 277
AMD guys, better stay away from driver 18.9.2! Can't use D3D11 10bit mode in madvr with latest 18.9.2. Reverted back to 18.8.2 and it works again.
__________________
Intel i5 6600, 16 GB DDR4, AMD Vega RX56 8 GB, Windows 10 x64, Kodi DS Player 17.6, MadVR (x64), LAV Filters (x64), XySubfilter .746 (x64)
LG 4K OLED (65C8D), Denon X-4200 AVR, Dali Zensor 5.1 Set
Sunset1982 is offline   Reply With Quote
Old 21st September 2018, 09:23   #52646  |  Link
Klaus1189
Registered User
 
Join Date: Feb 2015
Location: Bavaria
Posts: 565
Quote:
Originally Posted by Sunset1982 View Post
AMD guys, better stay away from driver 18.9.2! Can't use D3D11 10bit mode in madvr with latest 18.9.2. Reverted back to 18.8.2 and it works again.
Working fine here.

EDIT: What doesn't work for you exactly?

Last edited by Klaus1189; 21st September 2018 at 09:27.
Klaus1189 is offline   Reply With Quote
Old 21st September 2018, 10:27   #52647  |  Link
Sunset1982
Registered User
 
Join Date: Sep 2014
Posts: 277
Quote:
Originally Posted by Klaus1189 View Post
Working fine here.

EDIT: What doesn't work for you exactly?

the 10bit windowed mode in D3D11... only works with 8bit with latest drivers
__________________
Intel i5 6600, 16 GB DDR4, AMD Vega RX56 8 GB, Windows 10 x64, Kodi DS Player 17.6, MadVR (x64), LAV Filters (x64), XySubfilter .746 (x64)
LG 4K OLED (65C8D), Denon X-4200 AVR, Dali Zensor 5.1 Set
Sunset1982 is offline   Reply With Quote
Old 21st September 2018, 11:35   #52648  |  Link
Crimson Wolf
Registered User
 
Join Date: Dec 2014
Posts: 42
@Sunset1982 Even with nvidia, windowed mode is 8bit "D3D11 windowed (8 bit)", but as soon as you full screen it, it turns into "D3D11 fullscreen windowed (10bit)". Is this not the expected behavior?
Crimson Wolf is offline   Reply With Quote
Old 21st September 2018, 11:51   #52649  |  Link
aufkrawall
Registered User
 
Join Date: Dec 2011
Posts: 1,705
For what it's worth: I still had the render queue not filling correctly issue with 0.92.16, it only worked in FSE. However, it seems to have disappeared after a Windows restart. Maybe you want to keep an eye out on this.

Edit: The CPU load with HDR pixel shader conversion is also a bit high, especially with highlight reconstruction.

Last edited by aufkrawall; 21st September 2018 at 11:57.
aufkrawall is offline   Reply With Quote
Old 21st September 2018, 13:19   #52650  |  Link
mrmojo666
Registered User
 
Join Date: Jan 2017
Posts: 80
Wooowoo!! I've started to try all possible combinations of amd driver setting. And finally i managed to have back hdr autoswitch with 18.9.2. i have to set desktop at 12 bit. We will see with future drivers updates if it keep working.

As usual madshi was right.

__________________
AMD Ry 1500x - 8GB - RX460 4GB
TV Philips 55pus6501+ Marantz 1608 avr
WIN10(1903) 4K/444RGB
Mediaportal - Mpc-hc
MADVR-D3D11/10bit

Last edited by mrmojo666; 21st September 2018 at 13:25.
mrmojo666 is offline   Reply With Quote
Old 21st September 2018, 13:34   #52651  |  Link
iakoboss7
Registered User
 
iakoboss7's Avatar
 
Join Date: Sep 2015
Posts: 13
Quote:
Originally Posted by iakoboss7 View Post
do you know how to fix it?

this is a first for me (didnt even happen with v0.92.15 )
Quote:
Originally Posted by iakoboss7 View Post
just installed v0.92.16 and for the first time ever in full screen i can see the windows taskbar. this has never ever happened before in the 3 years i use madvr with mpc-hc.

anyone facing the same problem?
ok after a restart it fixed itself!
iakoboss7 is offline   Reply With Quote
Old 21st September 2018, 14:05   #52652  |  Link
blu3wh0
Registered User
 
Join Date: Feb 2014
Posts: 38
I'm probably going to continue using HDR pass-through as that seems the only way to utilize the higher brightness levels of my LG B7. HDR to SDR looks very good now for tone-mapping, but the brightness in SDR holds it back. I also utilize the dynamic tone-mapping on the TV to bring it closer to how it would look like in Dolby Vision. Are there any plans to add dynamic tone-mapping (if even possible) for HDR pixel processing to HDR output? Also, I didn't notice it in the profile variables, can display bitdepth output be added as a parameter? I'm currently using display refresh rate to decide between 8/10 bit output from madVR.
blu3wh0 is offline   Reply With Quote
Old 21st September 2018, 15:32   #52653  |  Link
Warner306
Registered User
 
Join Date: Dec 2014
Posts: 1,072
Quote:
Originally Posted by Chouonsoku View Post
Increasing the nits doesn't fix the super strong red hue, but they have to be that low to avoid the intense black crush that also happens with the HDR process setting. It was also set to 150 / 400 to make it easier to see the red problem in the photos.
It sounds bugged if you are getting crushed blacks at higher target nits. It should be the same.

Part of the problem is that madVR may send a value to the display that is supposed to be shown at an exact nits and the display's tone mapping curve may be designed to show the same PQ value at a different brightness. I'm not sure how the Panasonic "HDR Optimizer" gets around this. It only seems to impact the top of curve in the screenshots I've seen. I would think this feature would only work well for displays that closely follow the PQ curve and roll-off.

Edit: I looked at a review of the Panansonic pre-tone mapping feature that also used an LG C7 and it was tone mapping the result to a preset of 1,000 nits. So it was actually above the brightness of the display when the reviewer was glowing about its effectiveness.

I don't know how sending a signal with an altered brightness response is tone mapped by a display expecting a standard brightness response from a standard PQ source.

Last edited by Warner306; 21st September 2018 at 18:45.
Warner306 is offline   Reply With Quote
Old 21st September 2018, 16:32   #52654  |  Link
mclingo
Registered User
 
Join Date: Aug 2016
Posts: 771
Quote:
Originally Posted by Sunset1982 View Post
AMD guys, better stay away from driver 18.9.2! Can't use D3D11 10bit mode in madvr with latest 18.9.2. Reverted back to 18.8.2 and it works again.
i've had all sorts of issues since the latest MADVR update, black screens HDMI loss mainly but also on occasion MADVR failing to load at all, I ended up going back to AMD 18.8.1 and MADVR v0.92.14
__________________
OLED EF950-YAMAHA RX-V685-Win101809-4K 444 RGB 60hz-AMD RX580 19.2.2
KODI DS - MAD/LAV 92.14/0.72.2 - FSE / 3D / DIRECT3D11 / 10bit
mclingo is offline   Reply With Quote
Old 22nd September 2018, 03:39   #52655  |  Link
Warner306
Registered User
 
Join Date: Dec 2014
Posts: 1,072
Quote:
Originally Posted by mclingo View Post
i've had all sorts of issues since the latest MADVR update, black screens HDMI loss mainly but also on occasion MADVR failing to load at all, I ended up going back to AMD 18.8.1 and MADVR v0.92.14
You are still protesting a color change that was fixed by setting madVR to BT.2020? How exactly will this get this issue fixed?

I can’t understand why you are interested in this hobby when your PC breaks every month or so. I just play stuff almost every day and watch it. I don’t know why you seem to have so many issues.

You would have to narrow down the exact driver version and all of the exact settings to reproduce the issue and madshi would to have somehow reproduce the problem.
Warner306 is offline   Reply With Quote
Old 22nd September 2018, 13:55   #52656  |  Link
Ver Greeneyes
Registered User
 
Join Date: May 2012
Posts: 445
Hmm, on the latest madVR if I uncheck "use Direct3D 11 for presentation" and switch to non-FSE fullscreen mode, my screen flickers black. With D3D11 enabled everything is fine. That's on Windows 10 r1803 with a GeForce GTX 1080 and driver version 399.24 (heard people were having issues with the new 411 series so I haven't updated yet). I don't think v0.92.14 had this issue but I haven't checked yet.
Ver Greeneyes is offline   Reply With Quote
Old 22nd September 2018, 18:15   #52657  |  Link
ashlar42
Registered User
 
Join Date: Jun 2007
Posts: 401
Quote:
Originally Posted by madshi View Post
madVR v0.92.15 released
Thanks madshi for your continued work on madVR. And thanks for reading 100 pages of comments. I can't imagine the nightmare it must have been.
ashlar42 is offline   Reply With Quote
Old 22nd September 2018, 19:02   #52658  |  Link
mclingo
Registered User
 
Join Date: Aug 2016
Posts: 771
Quote:
Originally Posted by Warner306 View Post
You are still protesting a color change that was fixed by setting madVR to BT.2020? How exactly will this get this issue fixed?

I can’t understand why you are interested in this hobby when your PC breaks every month or so. I just play stuff almost every day and watch it. I don’t know why you seem to have so many issues.

You would have to narrow down the exact driver version and all of the exact settings to reproduce the issue and madshi would to have somehow reproduce the problem.
EDIT - the colour sat issue which is fixed by calibrating for BT2020, no idea why this fixes it, that it does should tell whoever knows how MADVR and CALIBRATION works what is going on here, this is why its odd nobdy seems to be able to help with this.

watching movies is the hobby, how I get my machine stable isnt.

i've had some bad luck with hardware, i'm also pretty skint so everything I buy is used so that does lead to some extra issues.

However, if I just left my machine as is i'd have no issues as I have workarounds. Whenever a new driver or madvr release comes out I feel the need to test it to see if it cures either of my two issues which i've had for ages, the colour sat issue and the HDMI loss coming out of 3D movies.

You'd think simply rolling back would revert everything back to working again but this is rarely the case, I do usually manage to get back to working fairly quickly though.

I dont know what else I can give MADSHI to help with either issue to be honest, I've asked, perhaps if more people had the problem MADSHI could give it some time but it appears there is a small subset of people with similar hardware, setups and players.

I cant blame MADSHI for wanted to give both issues a low priority as there only seems to be me and maybe 1 or 2 other people with the colour sat issue, so few people play 3D MVC movies theses days this is an even smaller dwindling subset and so I doubt my black screen HDMI loss issue with ever be fixed.

Because i'm here a lot it probably seems like I have a lot of problems., I dont really, at the end of the day i have a fully working system and thoroughly enjoy using it on a daily basis.
__________________
OLED EF950-YAMAHA RX-V685-Win101809-4K 444 RGB 60hz-AMD RX580 19.2.2
KODI DS - MAD/LAV 92.14/0.72.2 - FSE / 3D / DIRECT3D11 / 10bit

Last edited by mclingo; 22nd September 2018 at 19:06.
mclingo is offline   Reply With Quote
Old 22nd September 2018, 20:17   #52659  |  Link
mrmarioman
Registered User
 
mrmarioman's Avatar
 
Join Date: Jul 2017
Posts: 36
Quote:
Originally Posted by j82k View Post
411.63 broke NV HDR for me. When starting an HDR video the TV flashes the HDR icon a few times but then returns to SDR mode. Went back to 399.24 and it's working again.
OS HDR still works with 411.63 though.

This is on Win10 1803, 1050Ti, LG Oled C8.

Anyone able to confirm the broken NV HDR with 411.63?
Same here with 411.63. The TV flashes the image in HDR for an instant, then goes back to SDR. But if I go full-screen the TV will go back to HDR mode. It seems that now it only works when the player is in full screen.
Another issue (but I think that's just me, my set up) is that the colors don't look right, they don't pop. That also happened before, but turning on and off HDR in madVR settings could fix it, now I can't figure it out
mrmarioman is offline   Reply With Quote
Old 22nd September 2018, 21:04   #52660  |  Link
mrmarioman
Registered User
 
mrmarioman's Avatar
 
Join Date: Jul 2017
Posts: 36
Okay, just tried to play an HDR video enabling HDR in Windows, and with 'let madvr decide' option, and for the first time it works flawlessly! Must be something about the new Nvidia drivers, I think.
mrmarioman 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 23:00.


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