Posts: 95
Joined: Mar 2017
Reputation:
7
Yes you can with XDR. When I release it try it. It actually makes HDR better but this is only my opinion. I'll put it out there and let everyone criticize it. To users over at redfox they see the potential for such a program. This whole project is about unlocked controls for HDR TVs and to show HDR on projectors. Also elimates the HDMI 2.0 ....can use 1.4. My last test was fate furious. Looked wonderful and almost exact to UHD disk . Madvr crushes blacks on HDR.
Posts: 1,771
Joined: May 2015
Reputation:
73
wesk05
Posting Freak
Posts: 1,771
This may be good for someone who equates HDR with brightness.
Posts: 95
Joined: Mar 2017
Reputation:
7
I own UHD player and HDR TV and HDR card. It's hard convincing you guys that HDR is contrast and brightness. Either my TV is wrong or I'm right. In my 8 UHD test samples PC adjustments match UHD player dark and brightness. Anyway I'm heading back over to redfox. Good luck with HDR for the guys still having troubles getting it to show. Personally I've never cared for madvr from day 1. I'm sure there are many who love madvr. Some have HDR working perfect....others are only getting flat dull video. XDR fills that gap. Have a good day guys....
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
Appreciate your work. So far I am seeing reference to Windows players - does your code work on Linux?
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 95
Joined: Mar 2017
Reputation:
7
Linux I'm not familiar with. The code would have to be change to write to Linux registry if that's what Linux uses. I don't even think .net is supported with Linux. Miscosoft visual studio does offer templates to program for Linux as well as c++. I'm sure a Linux coder could take my program and convert .net commands to work.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
Fwiw, I get no crushed blacks using madVR or PowerDVD. The Movies & TV app leaves a little to be desired though. Judging by your video, I think your app fills a gap for non-HDR display users. It looks professional, straight forward and provides a ways to a means. I don't understand how a wider color gamut could be rendered on a limited display but at least an HDR title can be viewed without looking hazy grey. I'm not fond of the requirement to edit individual title settings into a .cal file but you have to do what you have to do. Not sure how that would go over with users unless they are enthusiasts. Perhaps one common player setting is 'close enough' and leave it at that, putting the player adjustments back to zeros at the end of playback? Not sure of the discrepancy between titles though? I still think it's a good contribution. Well done.
Posts: 95
Joined: Mar 2017
Reputation:
7
Thkyou. I have a uhd cal file that I use for uhd. Its a start file that can be tweaked. Ive got 10 bit 16bit float to pass to my hdr tv. Madvr has way to many peoblems. I made this for me because amd and madvr are horrible. No one else is making an efford to get hdr for amd users. Anyway 16 bit float show hdr brightness and shadow detail. I set my lav filters to no touch color and use 15-255. I can use0-250 as well. If i turn on bt2020 I leave tint at 0. Its looks identicle to uhd disk Im adding 10bit and lav settings to hdrcal so a user has complete control over everytging. The program is done. Im holding out till I add thise items. Maybe this looks weird to guys watching it on my demo video. Do this on hdr tv you will see real hdr once you try it. No point in trying to justify this . You guys can try it and then for the critics they will be surprised hdr does not revolve around madvr. You do know mircosoft apis use custom presenter for hdr! Lol
Posts: 2,510
Joined: Dec 2012
Reputation:
216
Hi Gereral1. This post isn't only for you and open for corrections by anyone.
I see you've released it. Your video looks appetizing. Ok, I'm using madVR passthrough as my renderer. So, the display makes the settings changes when HDR mode kicks in. I don't know, and don't have the knowledge to confirm if there are settings going on behind the scenes I don't know about? It seems to me those display settings (in HDR mode) always look the same, like it's just one generic default setting no matter what title is played. I look at my display settings during playback and they never change, title to title. I assume each title has custom settings and its metadata was applied accordingly telling my display to use those custom settings for that unique title. So, passing through avoids any software changes and hands the metadata to the display level untouched and lets the display calculate what to do. So, my common sense tells me I end up with one common setting for everything which defeats the entire purpose of custom presented titles via metadata. I have a decent 10bit HDR display. Either it simply doesn't do anything with metadata and just kicks up settings like contrast, backlight, and anything else 'calibrated' into memory when HDR mode enables, or I'm misunderstanding what HDR really is? I like the idea of having more control at the software level because their are many more settings that can be custom presented between titles vs my display settings.
I have a custom playercorefactory I need to retain. I see your app creates a new one or modifies an existing one. What happens to my original playercorefactory in the event I try XDR? I don't want to manually rename it or manually flip anything back and forth. In other words, can I use my existing playercorefactory at the same time so I can compare madVR with XDR during the same Kodi session, back to back video comparison?
Also, when creating a .cal, I noticed you said BT 709 required +12 to the right on HUE and Saturation. Does this mean BT 2020 would require 0 or -12 to the left? My display is 10bit. I assume I get a wider gamut using 10 vs 8 on this 10bit display. Or, will 8bit render the same gamut every bit as well?
Again, well done on the software. I just want to do some real world comparisons and see with my own eyes if I gain anything software tuning vs display tuning. I don't rule out HDR mode may not be all that and software may enhance beyond what HDR mode itself is doing. I'll let my eyes judge. Either it's the same, better, or worse. I like that this app can also enhance other formats and is not limited to HDR.
Fwiw, I understand anything I've written here could be waaaaay off. I'm no expert. I welcome any other discussion to educate myself and maybe others lurking not necessarily just related to XDR. This the 4k/HDR thread.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
2017-08-07, 20:10
(This post was last modified: 2017-08-07, 20:25 by brazen1.)
Maybe you misunderstood me. I haven't tried XDR yet. Yes, my display is set at BT2020 (HDR is enabled for that HDMI port). You answered one of my questions, BT2020 10bit would be set to 0 in a .cal. Great. Gives me a head start creating one. I really don't need to google playercorefactory. I've written many including the latest for 3 players two of which call .bats uniquely for 3D interactions as well as HDR directives and GPU commands relayed to O/S global settings. I just wanted to know if the existing one would work simultaneously with the one your app creates once mine is renamed and set aside. I had hoped it would integrate with an existing. Evidently it won't but maybe I can play with it. I understand your app does not trigger HDR mode, that adjustments are made at software level in the player. I thought I would make a .cal for a title and then compare playback with madVR. MadVR produces HDR SDR conversions using it's 3D LUT method. MadVR also simply passes through also. Passthrough is the method I'm currently using with Nvidia and a 10 year old PC. I just wanted to visually test the difference using madVR passthrough in HDR mode and XDR in SDR mode but without my playercorefactory to flip between the two in Kodi, it would be difficult since only XDR would be present.
On second thought, one could simply set options in MPC to use separate players, natively start HDR playback using madVR passthrough and pause it. Then custom adjust MPC to his hearts content on a 2nd instance of another MPC player and play it natively side by side with each other. These would be in windowed mode though and it wouldn't be fair to madVR since it would only pass 8bit windowed. Hmmmm? This wouldn't allow HDR mode to kick in using passthrough either. Maybe starting MPC, adjusting it as if I was setting up a .cal, leaving it open and starting another MPC player with madVR passthrough in FSE to allow HDR mode to enable, watch it and memorize details, and then close it to begin playback of the already adjusted 2nd instance of MPC and compare...... Need to think about it some.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
2017-08-07, 20:45
(This post was last modified: 2017-08-07, 20:53 by brazen1.)
So, to be clear, if I all I need to do is add XDR as a 4th player to my existing playercorefactory, making sure it points to XDRFE.exe (once it gets put in the directory via your app), all 4 players will show in 'play using' including XDR? If so great. Comparisons are only a couple button clicks with no hassle. The player setting is going to change when XDR is used and revert to default when it's closed to allow madVR subsequent playback use default settings. Now I understand. TIA.
MPC HC and MPC BE at the same time from the desktop for testing one title is also a good idea. Then one can retain a simulated .cal setting without affecting the other.....
