madVR Tool: MadmeasureHDR Optimizer (Measurements, Dynamic Clipping & Target Nits) - Page 28 - AVS Forum | Home Theater Discussions And Reviews
Forum Jump: 
 1015Likes
Reply
 
Thread Tools
post #811 of 1220 Old 02-17-2019, 03:52 AM
Newbie
 
Join Date: Feb 2019
Posts: 3
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 2 Post(s)
Liked: 0
Quote:
Originally Posted by Soulnight View Post
Please install the latest beta of madmeasurehdr and select the corresponding madVR folder in our tool also.
Also if you use a NAS, create a local network.
Quote:
Originally Posted by Jacob B View Post
I realize people are busy testing the flow of new builds, but I would appreciate advice on the above.
Thanks!
I'm running the latest version 3.6.2 and I've already configured the path to my madVR folder. Maybe I'm doing something else wrong? I choose the movie file and I click the green "Start!" button and that's when the error pops up
chinesekid is offline  
Sponsored Links
Advertisement
 
post #812 of 1220 Old 02-17-2019, 05:38 AM - Thread Starter
AVS Forum Special Member
 
Soulnight's Avatar
 
Join Date: Dec 2011
Location: Germany
Posts: 1,479
Mentioned: 235 Post(s)
Tagged: 0 Thread(s)
Quoted: 1132 Post(s)
Liked: 1863
Quote:
Originally Posted by chinesekid View Post
I'm running the latest version 3.6.2 and I've already configured the path to my madVR folder. Maybe I'm doing something else wrong? I choose the movie file and I click the green "Start!" button and that's when the error pops up
Did you read the first post of this thread? Did you install the latest madVR beta V38 or higher?
Soulnight is offline  
post #813 of 1220 Old 02-17-2019, 07:07 PM
Newbie
 
Join Date: Feb 2019
Posts: 3
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 2 Post(s)
Liked: 0
Quote:
Originally Posted by Soulnight View Post
Did you read the first post of this thread? Did you install the latest madVR beta V38 or higher?
Sorry I missed that part. I was able to install madVR beta V51 and give it a go. Now it's giving me a new error
Attached Thumbnails
Click image for larger version

Name:	Untitled.png
Views:	59
Size:	24.3 KB
ID:	2527264  
chinesekid is offline  
Sponsored Links
Advertisement
 
post #814 of 1220 Old 02-19-2019, 08:22 AM
AVS Forum Special Member
 
damelon's Avatar
 
Join Date: Sep 2007
Posts: 2,327
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 355
Have any of you measured a file before and received a MaxCLL/MaxFALL of 0 nits? One of my MKV files just processed with this result and it seemed odd.
damelon is offline  
post #815 of 1220 Old 02-19-2019, 11:20 AM
AVS Forum Special Member
 
sonichart's Avatar
 
Join Date: Jan 2002
Location: East Dundee, IL
Posts: 1,131
Mentioned: 24 Post(s)
Tagged: 0 Thread(s)
Quoted: 698 Post(s)
Liked: 583
Quote:
Originally Posted by damelon View Post
Have any of you measured a file before and received a MaxCLL/MaxFALL of 0 nits? One of my MKV files just processed with this result and it seemed odd.
I thought I saw that when I measured Solo. I will have to check when I get home.

JVC RS600 ¤ 130" Wide Seymour XD 2.35:1
Denon x4200 ¤ Onkyo M5010 ¤ iNuke 3000 ¤ 7.2.2
HTPC GTX1080 + MadVR is my master now ¤ Zidoo X8
sonichart is offline  
post #816 of 1220 Old 02-19-2019, 11:26 AM
AVS Forum Special Member
 
damelon's Avatar
 
Join Date: Sep 2007
Posts: 2,327
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 355
Quote:
Originally Posted by sonichart View Post
I thought I saw that when I measured Solo. I will have to check when I get home.
I'm doing a large batch process now and have seen it 5 different times. It isn't that there isn't any data. There is data in the measurements and luminance sections. I wonder if it is just some sort of divide by zero or math conversion output issue. I believe I saw it on A Quiet Place, Jack Reacher, Guardians Vol 2 as some examples.
damelon is offline  
post #817 of 1220 Old 02-19-2019, 11:57 AM
Advanced Member
 
jmonier's Avatar
 
Join Date: Jan 2003
Location: Torrance, CA
Posts: 945
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 226 Post(s)
Liked: 126
Quote:
Originally Posted by damelon View Post
I'm doing a large batch process now and have seen it 5 different times. It isn't that there isn't any data. There is data in the measurements and luminance sections. I wonder if it is just some sort of divide by zero or math conversion output issue. I believe I saw it on A Quiet Place, Jack Reacher, Guardians Vol 2 as some examples.
Quite a few HDR movies do not have MaxCLL or MaxFALL data. I've seen it on several that I have, for instance "Life of Pi". This is completely independent of any MadmeasureHDR operations.
damelon, Soulnight and Dexter Kane like this.
jmonier is online now  
post #818 of 1220 Old 02-19-2019, 01:21 PM
AVS Forum Special Member
 
SamuriHL's Avatar
 
Join Date: Jan 2005
Posts: 5,337
Mentioned: 12 Post(s)
Tagged: 0 Thread(s)
Quoted: 318 Post(s)
Liked: 410
Quote:
Originally Posted by sonichart View Post
I thought I saw that when I measured Solo. I will have to check when I get home.
Indeed.

Measuring video file "D:\MKV\Solo - A Star Wars Story Ultra HD.mkv" using D3D11 (native)...
Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.68 0.32, 0.15 0.06, 0.265 0.69, 0.3127 0.329
MaxCLL: 0, MaxFALL: 0 nits
SamuriHL is online now  
post #819 of 1220 Old 02-23-2019, 09:40 AM
Member
 
Lost_62's Avatar
 
Join Date: Apr 2018
Posts: 114
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 79 Post(s)
Liked: 5
Fast question , If I have a profile 3DLut for HDR and I insert it in Tone Map HDR Using External 3DLUT ; Tone Map HDR Using Pixel Shaders
it is usable as an option of work ? or an option selected excludes the other.
Lost_62 is offline  
post #820 of 1220 Old 02-26-2019, 07:05 AM
Senior Member
 
fingersdlp's Avatar
 
Join Date: Oct 2002
Location: Omaha NE
Posts: 466
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 184 Post(s)
Liked: 98
Arrival from 1:01:50 to 1:02:30 has several visible brightness adjustments - at least for me. This is exhibited by both the recent live algo and also from my tweaked measurement file playback for this title. Curious if this could be from the way the Fall algo treats this material and not just scene change detection at play? Hoping @Soulnight might review?

EDIT: Might just be a scene change issue. I will retest later so maybe wait if not that interesting.

Last edited by fingersdlp; 02-26-2019 at 07:21 AM.
fingersdlp is offline  
post #821 of 1220 Old 02-26-2019, 08:08 AM - Thread Starter
AVS Forum Special Member
 
Soulnight's Avatar
 
Join Date: Dec 2011
Location: Germany
Posts: 1,479
Mentioned: 235 Post(s)
Tagged: 0 Thread(s)
Quoted: 1132 Post(s)
Liked: 1863
Quote:
Originally Posted by fingersdlp View Post
Arrival from 1:01:50 to 1:02:30 has several visible brightness adjustments - at least for me. This is exhibited by both the recent live algo and also from my tweaked measurement file playback for this title. Curious if this could be from the way the Fall algo treats this material and not just scene change detection at play? Hoping @Soulnight might review?

EDIT: Might just be a scene change issue. I will retest later so maybe wait if not that interesting.
I am 99% sure that the Fall algo has nothing to do with it.

Probably a scene change issue.

2 evils possible:

Option 1:
the target nits gets resetted at scene change at a bad time.
Typically:
You can get a visible brightness jump between 2 people discussing with camera change but the viewer sees it as "one single scene".
- LIVE algo current implementation always reset at each scene cut and will definitely display a lot of the associated issues
- Our tool behaviour depends on the settings used. Default settings try to avoid this kind of unwanted reset.

Option 2:
Huge change in brightness and scene cut not detected.
- Our tool may try to smooth this out with the rolling avg which can result in pumping.
- Live algo will be either too dark or overblown if big scene is missed.

So the default settings in our tool try to avoid both bad options.

Can you share the settings you are using?
And also maybe share a video sample to look at the issue?

Last edited by Soulnight; 02-26-2019 at 08:27 AM.
Soulnight is offline  
post #822 of 1220 Old 02-26-2019, 12:39 PM
Senior Member
 
fingersdlp's Avatar
 
Join Date: Oct 2002
Location: Omaha NE
Posts: 466
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 184 Post(s)
Liked: 98
Quote:
Originally Posted by Soulnight View Post
I am 99% sure that the Fall algo has nothing to do with it.
I agree - looks like just a scene change issue - I will edit this later when I have access to the PC and can provide some more info. Thanks.
fingersdlp is offline  
post #823 of 1220 Old 02-27-2019, 05:28 AM
Senior Member
 
fingersdlp's Avatar
 
Join Date: Oct 2002
Location: Omaha NE
Posts: 466
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 184 Post(s)
Liked: 98
@Soulnight - So I tested the Arrival scenes again and the scenes match your option 1 evil - two people discussing. This movie seems to have more issues than any of my others I have watched - especially the last 30 to 40 minutes. As example at 1:02:21 ish there is a cut to one actor and it noticeably rolls darker. Then at 1:02:26 ish there is a cut back to the other actor and it noticeably rolls lighter. This is part of a conversation around the time of "I'm curious" dialog. The brightness adjustments are at a scene cut between the actors both times that I assume is missed. Here are the settings used in case you can point out a possible tweak to improve - thanks.

Selected target nits calculation method: FALL-Algo
Selected static target nits: 269
Real display peak nits: 90

Dynamic target nits: Yes
Minimal target nits: 90
Maximum Target Nits: 2500
Time for rolling avg in frames: 200
Dynamic Target Nits Tuning [50-100]: 125
Merge scenes [FALL change in %]: 100
Minimal chapter duration in frames: 100
Merge chapters [avgFALL change in %]: 50
No compression limit [nits]: 150
Fix for very small and bright spots [%]: 5
Number of identified chapters: 425
----------------------------------------------
Dynamic clipping
Dynamic range recovery strength in %: 100
fingersdlp is offline  
post #824 of 1220 Old 02-27-2019, 12:13 PM
Senior Member
 
Jacob B's Avatar
 
Join Date: Apr 2001
Posts: 464
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 138 Post(s)
Liked: 33
What madVR build is recommended to use with latest flo and Anna tool?
One of the latest betas? Or a public release?
Jacob B is offline  
post #825 of 1220 Old 02-27-2019, 01:00 PM - Thread Starter
AVS Forum Special Member
 
Soulnight's Avatar
 
Join Date: Dec 2011
Location: Germany
Posts: 1,479
Mentioned: 235 Post(s)
Tagged: 0 Thread(s)
Quoted: 1132 Post(s)
Liked: 1863
Quote:
Originally Posted by Jacob B View Post
What madVR build is recommended to use with latest flo and Anna tool?
One of the latest betas? Or a public release?
MadVR Beta V40.

Any newer beta "should" work without any issue either as long as the "measurement file" is not checked as "ignored" in madVR settings.
Soulnight is offline  
post #826 of 1220 Old 02-27-2019, 02:11 PM
Advanced Member
 
ddgdl's Avatar
 
Join Date: Mar 2007
Posts: 686
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 379 Post(s)
Liked: 360
Quote:
Originally Posted by Soulnight View Post
MadVR Beta V40.

Any newer beta "should" work without any issue either a slong as the "measurement file" is not checked as "ignored" in madVR settings.
I asked this in another thread but figured this is probably the better one to ask it in (though you may be biased!)---

I know madshi is working on real time dynamic mapping by looking ahead a few frames, which markmon and others have said will obviate the need for measurements. But won't pre-measuring the entire file always give the best results, at the very least by offloading some of the real-time processing work that would have to be done otherwise? Am I missing something?
ddgdl is offline  
post #827 of 1220 Old 02-27-2019, 02:12 PM
Senior Member
 
Jacob B's Avatar
 
Join Date: Apr 2001
Posts: 464
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 138 Post(s)
Liked: 33
Jacob B is offline  
post #828 of 1220 Old 02-27-2019, 02:15 PM
Senior Member
 
Jacob B's Avatar
 
Join Date: Apr 2001
Posts: 464
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 138 Post(s)
Liked: 33
Quote:
Originally Posted by Soulnight View Post
Quote:
Originally Posted by Jacob B View Post
What madVR build is recommended to use with latest flo and Anna tool?
One of the latest betas? Or a public release?
MadVR Beta V40.

Any newer beta "should" work without any issue either a slong as the "measurement file" is not checked as "ignored" in madVR settings.
[IMG class=inlineimg]/forum/images/smilies/wink.gif[/IMG]
Should dynamic clipping be ticked in madVR, or is that only used when NOT using the Measuring files, i.e. the live algo?
Jacob B is offline  
post #829 of 1220 Old 02-27-2019, 02:47 PM - Thread Starter
AVS Forum Special Member
 
Soulnight's Avatar
 
Join Date: Dec 2011
Location: Germany
Posts: 1,479
Mentioned: 235 Post(s)
Tagged: 0 Thread(s)
Quoted: 1132 Post(s)
Liked: 1863
Quote:
Originally Posted by ddgdl View Post
I asked this in another thread but figured this is probably the better one to ask it in (though you may be biased!)---

I know madshi is working on real time dynamic mapping by looking ahead a few frames, which markmon and others have said will obviate the need for measurements. But won't pre-measuring the entire file always give the best results, at the very least by offloading some of the real-time processing work that would have to be done otherwise? Am I missing something?
Well honestly, without being biased , it's pretty obvious that *in theory" you should be able to have much better results than ANY version of the LIVE algo IF you know all the frames in advance.

Now, having said that, it of course depends on how good in the LIVE algo and how good is the "Measurement file based" algo.
But, if both are given the same developement effort, "measurement file based" will always beat by quite a margin the LIVE algo.

So for the *maybe* biased part:
the current philosophy of the "Dynamic target" live algo is to use the "FALL algo" and then reset the target nits for each new detected scene.
This means that if 2 people are talking to each other in the same room, and the camera keeps switching every 2s between the two, the target nits will get reseted at each camera change. IF the FALL is very different between the 2 camera perspective, then you will observe large target nits change at each camera change.
--> This might be disturbing since while in the same "conversation" the brightness will change up and down

Ideally, you would like for such "conversation between 2 people" to be handled as one single scene, so that you don't have strange brightness jump between the same "chapter".
--> This is where the "measurement file" has a huge advantage: you can basically detect such situation by looking ahead.

-->In our tool working with the measuement file, we "try" to only reset the target nits only large "chapter" change (large FALL change). "Chapter merge" is here for that.

We also made an improvement in the V3.7.2 (not released to you guys yet ), where we basically handle "sandwich scene" to help with this kind of situation where the camera switch back and forth, but you actually want to keep the same target so that the brightness does not change too much.

Also while in a "SCENE", the live algo is able to change the target nits based on a predefined speed scaled to the current delta to the desired frame peak. But Live algo does not known the future.
With the measurement file, we currently use a centered rolling avg so that we can better prepare for the future with a smoth transition to the future required target nits.

So while I am very happy that the LIVE algo now included the dynamic target nits, and while the LIVE algo may please most people and avoid the 'hassle" of generating measurement file, the "measurement file" will still be beneficial to be "smarter" about the "when" do you reset the target nits so that the relative change between "friend scenes" is still respected.

Also, we should not forget that Madshi first purpose of the measurement file was to know in advance the frame peak so that you would never tone map to a peak smaller than the current frame peak which would result in indesired clipping. The live algo may lead to uncontrolled clipping because of the "fixed" moving speed. With the measurement file, it's always "perfect", because it can react in advance (it knows the future) and raise the tone mapping peak target progressively so that when it does reach the frame with the highest peak, it still does not clip.

And finally, you can probably do much more than what we are doing at the moment with the measurement file to make it even better.

Edit: and yes you are right at the very least you can unload your gpu and save some precious ms if you use the already pre-analysed and post-processed measurement file.
arcspin and Dexter Kane like this.

Last edited by Soulnight; 02-27-2019 at 03:04 PM.
Soulnight is offline  
post #830 of 1220 Old 02-27-2019, 02:55 PM - Thread Starter
AVS Forum Special Member
 
Soulnight's Avatar
 
Join Date: Dec 2011
Location: Germany
Posts: 1,479
Mentioned: 235 Post(s)
Tagged: 0 Thread(s)
Quoted: 1132 Post(s)
Liked: 1863
Quote:
Originally Posted by Jacob B View Post
Should dynamic clipping be ticked in madVR, or is that only used when NOT using the Measuring files, i.e. the live algo?
No, you can untick it. WE do it directly with the tool in the measurement file.
(I think it's not active anyway if measurement file are active, but would need confirmation).
Soulnight is offline  
post #831 of 1220 Old 02-27-2019, 04:01 PM
Advanced Member
 
ddgdl's Avatar
 
Join Date: Mar 2007
Posts: 686
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 379 Post(s)
Liked: 360
Quote:
Originally Posted by Soulnight View Post
Quote:
Originally Posted by ddgdl View Post
I asked this in another thread but figured this is probably the better one to ask it in (though you may be biased!)---

I know madshi is working on real time dynamic mapping by looking ahead a few frames, which markmon and others have said will obviate the need for measurements. But won't pre-measuring the entire file always give the best results, at the very least by offloading some of the real-time processing work that would have to be done otherwise? Am I missing something?
Well honestly, without being biased [IMG class=inlineimg]/forum/images/smilies/biggrin.gif[/IMG] , it's pretty obvious that *in theory" you should be able to have much better results than ANY version of the LIVE algo IF you know all the frames in advance.

Now, having said that, it of course depends on how good in the LIVE algo and how good is the "Measurement file based" algo.
But, if both are given the same developement effort, "measurement file based" will always beat by quite a margin the LIVE algo.

So for the *maybe* biased part:
the current philosophy of the "Dynamic target" live algo is to use the "FALL algo" and then reset the target nits for each new detected scene.
This means that if 2 people are talking to each other in the same room, and the camera keeps switching every 2s between the two, the target nits will get reseted at each camera change. IF the FALL is very different between the 2 camera perspective, then you will observe large target nits change at each camera change.
--> This might be disturbing since while in the same "conversation" the brightness will change up and down

Ideally, you would like for such "conversation between 2 people" to be handled as one single scene, so that you don't have strange brightness jump between the same "chapter".
--> This is where the "measurement file" has a huge advantage: you can basically detect such situation by looking ahead.

-->In our tool working with the measuement file, we "try" to only reset the target nits only large "chapter" change (large FALL change). "Chapter merge" is here for that.

We also made an improvement in the V3.7.2 (not released to you guys yet [IMG class=inlineimg]/forum/images/smilies/biggrin.gif[/IMG] ), where we basically handle "sandwich scene" to help with this kind of situation where the camera switch back and forth, but you actually want to keep the same target so that the brightness does not change too much.

Also while in a "SCENE", the live algo is able to change the target nits based on a predefined speed scaled to the current delta to the desired frame peak. But Live algo does not known the future.
With the measurement file, we currently use a centered rolling avg so that we can better prepare for the future with a smoth transition to the future required target nits. [IMG class=inlineimg]/forum/images/smilies/smile.gif[/IMG]

So while I am very happy that the LIVE algo now included the dynamic target nits, and while the LIVE algo may please most people and avoid the 'hassle" of generating measurement file, the "measurement file" will still be beneficial to be "smarter" about the "when" do you reset the target nits so that the relative change between "friend scenes" is still respected.

Also, we should not forget that Madshi first purpose of the measurement file was to know in advance the frame peak so that you would never tone map to a peak smaller than the current frame peak which would result in indesired clipping. The live algo may lead to uncontrolled clipping because of the "fixed" moving speed. With the measurement file, it's always "perfect", because it can react in advance (it knows the future) and raise the tone mapping peak target progressively so that when it does reach the frame with the highest peak, it still does not clip. [IMG class=inlineimg]/forum/images/smilies/cool.gif[/IMG]

And finally, you can probably do much more than what we are doing at the moment with the measurement file to make it even better. [IMG class=inlineimg]/forum/images/smilies/wink.gif[/IMG]

Edit: and yes you are right at the very least you can unload your gpu and save some precious ms if you use the already pre-analysed and post-processed measurement file.
Fantastic explanation. Thank you. I cannot see why I wouldn't pre-measure all of my UHD content. Looking forward to the next release!
arcspin likes this.
ddgdl is offline  
post #832 of 1220 Old 02-27-2019, 04:07 PM
Advanced Member
 
grendelrt's Avatar
 
Join Date: Jun 2004
Location: Richmond, VA
Posts: 973
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Quoted: 590 Post(s)
Liked: 318
Related question to the mapping, I was trying to get some quick measurements as I break in a new bulb to set up my tone mapping. I did a 100 IRE pattern to get peak nits, I used the built in hcfr pattern with a small square in the middle of a black screen, would this be a valid way of getting peak nits for inputting into the actual nits field? Or should I do a full white screen or something different?
grendelrt is offline  
post #833 of 1220 Old 02-28-2019, 12:57 AM
Senior Member
 
Jacob B's Avatar
 
Join Date: Apr 2001
Posts: 464
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 138 Post(s)
Liked: 33
Quote:
Originally Posted by Soulnight View Post
Quote:
Originally Posted by Jacob B View Post
Should dynamic clipping be ticked in madVR, or is that only used when NOT using the Measuring files, i.e. the live algo?
No, you can untick it. WE do it directly with the tool in the measurement file.
(I think it's not active anyway if measurement file are active, but would need confirmation).
Thanks!
Jacob B is offline  
post #834 of 1220 Old 02-28-2019, 01:06 PM
Member
 
sat4all's Avatar
 
Join Date: Apr 2013
Location: Casablanca, Morocco
Posts: 122
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 89 Post(s)
Liked: 41
Hi Soulnight,

Is the default settings good enough for high peak displays? Let's say that my real display peak nits is 740 what do you suggest for no compression limit and dynamic tuning settings.

Thanks

LG OLED65C8 / Denon AVR-X3200W / KEF E305+ONKYO SKH-410 / Synology DS2415+ / Logitech Harmony Companion / ZOTAC MAGNUS EN1060K (Kodi DSPlayer x64) / LightSpace&ColourSpace, DisplayCal, HCFR, Calman Home for LG / i1Display PRO OEM Rev.B, i1PRO2 OEM Rev.E / Ted's LightSpace CMS Calibration Disk.
sat4all is offline  
post #835 of 1220 Old 03-01-2019, 05:24 AM
Advanced Member
 
grendelrt's Avatar
 
Join Date: Jun 2004
Location: Richmond, VA
Posts: 973
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Quoted: 590 Post(s)
Liked: 318
Question for someone just starting out tuning this stuff. I am currently using a dynamic tuning value of 100 as a mid point and trying to get a starting point to tweak.

My question for you guys with lots of experience with tone mapping would be how much diminishing returns are there on the nits when using the mapping. I have 3 choices for my settings ,

High lamp with color filter 156 nits,98% p3 coverage
Low lamp no filter 136 nits, high 80s p3 coverage
Low lamp with filter 113 nits , 98% p3 coverage

I am doing low lamp with filter right now but trying to decide if the extra coverage is worth the loss in brightness or if the extra noise in high lamp would be worth the extra nits. I tried doing a/b testing but it's hard with how long the sync takes and this my first viewing of hdr so I have no reference point.

I am currently using no dynamic clipping and a no compression of 150 with a minimum real nits of 105 (bulb is new I expect it to drop quick from the 113).

Any advice would be appreciated , I am trying to watch a movie this weekend and would like some starter settings
grendelrt is offline  
post #836 of 1220 Old 03-04-2019, 03:16 PM
Senior Member
 
fingersdlp's Avatar
 
Join Date: Oct 2002
Location: Omaha NE
Posts: 466
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 184 Post(s)
Liked: 98
Quote:
Originally Posted by grendelrt View Post
... trying to decide if the extra coverage is worth the loss in brightness or if the extra noise in high lamp would be worth the extra nits. I tried doing a/b testing but it's hard with how long the sync takes and this my first viewing of hdr so I have no reference point.

I am currently using no dynamic clipping and a no compression of 150 with a minimum real nits of 105 (bulb is new I expect it to drop quick from the 113).

Any advice would be appreciated , I am trying to watch a movie this weekend and would like some starter settings
For me the thing that makes HDR tough for projectors is low nits. So I favor more nits over color coverage when keeping HDR and using a custom Arve curve. With tone mapping I still prefer it to look as "HDR like" as possible and that means I also favor more nits over color coverage to give me the highest dynamic range I can squeeze out of it. Personal tastes might differ however and I know some like to watch tone mapped on low lamp closer to their regular SDR experience and want the WCG. I guess I got used to the High Lamp for actual HDR and so I have kept that even now that I am tone mapping for my HDR content and watching in SDR BT2020 (but without the filter). I am sure someone will disagree but that's just what I am doing.
fingersdlp is offline  
post #837 of 1220 Old 03-04-2019, 03:32 PM
Advanced Member
 
grendelrt's Avatar
 
Join Date: Jun 2004
Location: Richmond, VA
Posts: 973
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
Quoted: 590 Post(s)
Liked: 318
Quote:
Originally Posted by fingersdlp View Post
For me the thing that makes HDR tough for projectors is low nits. So I favor more nits over color coverage when keeping HDR and using a custom Arve curve. With tone mapping I still prefer it to look as "HDR like" as possible and that means I also favor more nits over color coverage to give me the highest dynamic range I can squeeze out of it. Personal tastes might differ however and I know some like to watch tone mapped on low lamp closer to their regular SDR experience and want the WCG. I guess I got used to the High Lamp for actual HDR and so I have kept that even now that I am tone mapping for my HDR content and watching in SDR BT2020 (but without the filter). I am sure someone will disagree but that's just what I am doing.
Thanks, I ran the 113 nits this weekend and it looked great, but still trying to decide what to do. Trying to do comparisons is tough though, I also wonder how many movies take advantage of full P3 colorspace.
grendelrt is offline  
post #838 of 1220 Old 03-05-2019, 05:37 AM
Senior Member
 
fingersdlp's Avatar
 
Join Date: Oct 2002
Location: Omaha NE
Posts: 466
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 184 Post(s)
Liked: 98
I have one movie in my collection that the measurement does not complete. I have tried the measure with D3D11 as normal and also DXVA2 native to see if that might allow it to complete but same result. It takes the full time and appears to be processing up until it finishes with the incomplete file. The movie file itself seems fine - I can play it and navigate around no problem. Anyone else have a measurement issues like this with a specifc title? Any place to review for possible error messages or a reason? The title is "Keeping up with the Jonses".

Thanks
fingersdlp is offline  
post #839 of 1220 Old 03-05-2019, 05:52 AM
AVS Forum Special Member
 
Manni01's Avatar
 
Join Date: Sep 2008
Posts: 9,747
Mentioned: 384 Post(s)
Tagged: 0 Thread(s)
Quoted: 5925 Post(s)
Liked: 6507
Quote:
Originally Posted by fingersdlp View Post
I have one movie in my collection that the measurement does not complete. I have tried the measure with D3D11 as normal and also DXVA2 native to see if that might allow it to complete but same result. It takes the full time and appears to be processing up until it finishes with the incomplete file. The movie file itself seems fine - I can play it and navigate around no problem. Anyone else have a measurement issues like this with a specifc title? Any place to review for possible error messages or a reason? The title is "Keeping up with the Jonses".

Thanks
If you're muxing with makemkv, try remuxing that title with mkvtoolix. There is a bug in makemkv when the audio and video track are not the same length (audio longer than video, so black screen at the end of the file). Mkvtoolnix deals better with the situation than makemkv. Mike knows about the issue but it won't be solved any time soon apparently.

To see if this is the same issue, go to the end of the file. If it's audio on a black screen, and if you can't navigate that part of the file at the end, that's what it is.

I had this issue with a few titles, remuxed them with mkvtoolnix and measurements completed fine.

Otherwise redo your rip, it might be wrong for another reason.

Don't ever use DXVA native, it's the worst option for measurements, at least here, and it's not recommended for playback anyway.

D3D11 native is usually the fastest for measurements, then copyback. Use DXVA2 copyback if you have to, but not native.
fingersdlp likes this.

Batch Utility V4.02 May 16 2019 to automate measurements files for madVR with support for BD Folders
JVC Macro feature on Vertex/Vertex2/Integral2/Maestro/Diva
Manni01 is online now  
post #840 of 1220 Old 03-05-2019, 11:13 AM
AVS Forum Special Member
 
Manni01's Avatar
 
Join Date: Sep 2008
Posts: 9,747
Mentioned: 384 Post(s)
Tagged: 0 Thread(s)
Quoted: 5925 Post(s)
Liked: 6507
Quote:
Originally Posted by Soulnight View Post
We also made an improvement in the V3.7.2 (not released to you guys yet )
We've been waiting patiently...

Batch Utility V4.02 May 16 2019 to automate measurements files for madVR with support for BD Folders
JVC Macro feature on Vertex/Vertex2/Integral2/Maestro/Diva
Manni01 is online now  
Sponsored Links
Advertisement
 
Reply Home Theater Computers

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

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
Trackbacks are Off
Pingbacks are Off
Refbacks are Off