New Lumagen Radiance Pro Series - Page 157 - AVS Forum | Home Theater Discussions And Reviews
Forum Jump: 
 3576Likes
Reply
 
Thread Tools
post #4681 of 5233 Old 06-02-2019, 05:09 AM
Senior Member
 
Join Date: Nov 2016
Posts: 204
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 115 Post(s)
Liked: 29
Quote:
Originally Posted by Eventidal View Post
I love this feature.... If you don´t then simply set the dimming to limited or off.
Not same low light effect. With Limited blacks are a bit washed and with off blacks are gray.
stefanop is offline  
Sponsored Links
Advertisement
 
post #4682 of 5233 Old 06-03-2019, 01:11 AM
Senior Member
 
jabz's Avatar
 
Join Date: Apr 2004
Location: New Zealand
Posts: 291
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 164 Post(s)
Liked: 70
Ever since I updated to Beta 112818 and then 011119 (Dynamic HDR tone mapping), I am having instances of video blanking/dropping out. It was pretty stable on my previous firmware which was 100317.

With 100317 I had my Oppo 203 connected to the Bd/DVD input of the Onkyo RZ3100, and the output connected to the input of the Lumagen Pro (18GHz input card). I have 1, 18GHz output card which is connected via fibre optic HDMI to my Sony VW520ES. This setup worked fine until I updated to 112818 I started getting video dropouts.

So as a test I took the Onkyo AV receiver out of the video path, and connected the Oppo Main HDMI out direct to the Lumagen 18GHz input, and the Oppo 2nd (audio) HDMI out to the AV receiver. This cleared up the issue and it worked fine.
However I also have an LG OLED and needed the Oppo to work with it too, and to maintain Dolby Vision, so I used a HD Fury Vertex in splitter mode to split the Oppo Main HDMI OUT. So from the Vertex HDMI 0 Output to the Lumagen Input, and HDMI 1 Output to the AV Receiver Bd/DVD input.

This is still causing video blanking/video dropouts.

So has anyone else experienced the same, and what did you do to fix it?
Have the most recent Firmware updates fixed it?
I may try a 9Ghz output port to the Projector, seeing as it doesn't need 18GHz, to check if the issue is isolated to the 18GHz output?

Note Direct input from the Oppo to Lumagen is ok, however need the Oppo to output to my Projector and also the LG OLED, so can't leave it in this config. What are others doing here?

Sony VPL-VW520 | Elitescreens TT 135" 2.35:1 | Elitescreens TT 120" 16x9 | Prismasonic HD-6000F | Onkyo TX-RZ3100 | Oppo UDP-203 | PS4 PRO | ATV4K | LG OLED 65 C7 | Klipsch Reference RP-280 | Klipsch Reference RP-280C | Klipsch Reference RP-250S | Klipsch Reference RP-150M | Klipsch Reference R-115SW | Klipsch Reference R-140SA
jabz is offline  
post #4683 of 5233 Old 06-03-2019, 09:19 AM
Advanced Member
 
uderman's Avatar
 
Join Date: Apr 2008
Location: MA
Posts: 516
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 122 Post(s)
Liked: 58
Is there any room left on the fpga for 8K upscaling? I think 8K TVs will be very common in 2 years.

Wanted:
HD-VMD Discs
Muse/Hi-Vision Discs - Mint/Complete Only!
uderman is offline  
Sponsored Links
Advertisement
 
post #4684 of 5233 Old 06-03-2019, 09:43 AM
Advanced Member
 
sjschaff's Avatar
 
Join Date: Apr 2004
Location: Alameda, CA
Posts: 573
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 112 Post(s)
Liked: 44
Anyone out there with an Nvidia Shield TV, who is attempting to play source files that are HDR, through the Lumagen?



When I try to do so, I find that the advanced HDMI settings in the Nvidia, though they present an option for YUV 422 12-bit Rec. 709, never let me "keep" this setting. It reverts back to YUV 422 8-bit Rec. 709. Using OK button on the Lumagen remote shows that the source colorspace and Lumagen are different. Input shows RGB-HDR709 and output 422-SDR2020. By the way, this is for using CMS1 for all HDR source. Also, not using Auto-Convert for either CMS0 or CMS1.



The only way I can get this option in the Nvidia to "stick" is to alter the Lumagen Pro's input setting for the Nvidia. The specific setting is Video Limit. Changing from 9ghz or 9ghz Max to 1080p has the Lumagen working with the Nvidia to allow a set of options, which includes the color space I tried to pick. When I now pick the YUV 422 12-bit Rec. 709 the Nvidia suddenly asks if I want to keep it. I say yes, and now find that when I return to the advanced HDMI settings the "current" setting has been updated to reflect the change. Lumagen OK button now shows for input 422-HDR2020 and output 422-SDR2020 while playing HDR source. So, this all seems to suggest some sort of limitation or disagreement in the Nvidia with the Lumagen or configuration problem on my part in either/both devices.



By the way, I have enabled colorimetry in the Nvidia via the developer options, as described in prior posts for Nvidia Shield for colorspace switching.


Also, if anyone is using the 18 ghz cards in the Lumagen along with the Shield does this combination allow for 422 12-bit Rec 709 to work on the Nvidia?




giomania likes this.

JVC RS500 - Stewart Firehawk - Lumagen Radiance Pro - Anthem D2V - Revel Salon speakers - SV Sound SB13 Ultra sub - Tivo/Nvidia Shield TV/Panasonic UB900


sjschaff is offline  
post #4685 of 5233 Old 06-03-2019, 10:31 AM
AVS Forum Club Gold
 
Carbon Ft Print's Avatar
 
Join Date: Nov 2009
Location: FL
Posts: 608
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 362 Post(s)
Liked: 302
Quote:
Originally Posted by jabz View Post
What are others doing here?
Same config as yours ... no drop outs ... took 5 wks to figure this out. For this to work, Dolby Vision is "Forced" manually via Vertex when watching Dolby Vision 4k movies via LG OLED ... (the JVC projector is off when watching DV movies). When watching "non Dolby Vision" HDR movies, Dolby Vision is not forced via Vertex.

Video drop outs can be caused by: remedy found:

1. Bad cables: HDfury 18Ghz 6 ft, Tributaries 18GHz 6ft, RUIPRO 18GHz 10M optic cable.
2. Device settings: see below for OPPO and Vertex setup.
3. Device power up sequence: see below.
4. Sink (display) devices are asleep and need to be awaken for proper handshaking: Sink Hot plug disconnect/reconnect and/or reset Vertex ... else, power off/on sink device.
5. Source devices are asleep and need to be awaken for proper handshaking: eject disk and re-insert disc and/or reset Vertex... else, power off/on source device.
6. AVR/Pre-Pro is asleep and is blocking handshaking btwn sink and source devices and need to be awaken: switch to another input then back ... else power off/on AVR/Pre-Pro.
7. "Forced Dolby Vision" by Vertex/OPPO: let Vertex do the manual "Force Dolby Vision" ... this works faster than having to eject the disc then forcing Dolby Vision via OPPO.

Device Settings (Use Vertex App (not OPPO) to "Force Dolby Vision" when using LG OLED in Dolby Vision mode):

OPPO: Set all video settings to (4k) Auto. This automatically forces 2160p/24 444 12bit BT2020 for HDR disc movies. For Dolby Vision disc movies, this forces 1080p/60, RGB, 8 bit tunneling of Dolby Vision. See Dolby Vision Tunneling below. LPro does 24p to 60p conversion.
Vertex: Automix, Mix Audio=max/max, Mix Video= nothing checked (except to "Forced DV" only when LG OLED is doing Dolby Vision and JVC is not on), no scaling.

First power up sequence (First step is needed to erase past history of EDID/HDCP handshakes ... for subsequent power up sequences, just do steps 2 and 3):

1. Turn off all devices. Then, pull power cords from AC power source for ALL devices in video/audio handshaking path. Wait 10 seconds. Plugin all devices ... DO NOT power up devices at this point ... i.e. leave all devices Standby mode. Wait 2 minutes for all handshaking to finish ... yes, devices talk to each other in standby mode.
2. Then power up Vertex and Audio Processor.
3. Then power up all other devices.

Dolby Vision Tunneling:

Dolby Vision HDR RGB Tunneling (copied from another source ... don't remember who):
The method Dolby Vision HDR (DV) uses to transport the signal over HDMI is referred to as “RGB Tunneling”. The 12-bit ICtCp or ITP colorspace DV signal + Metadata is encapsulated inside the regular RGB 8-bit video signal. The DV “tunneling” carries 12-bit YCbCr 4:2:2 data in an RGB 4:4:4 8-bit transport. This is possible because both signal formats have the same 8.9 Gbps data rate requirements.
https://www.dolby.com/us/en/technolo...hite-paper.pdf

Config:

OPPO Main V/A(Out1) ---> Vertex(IN 0)

Vertex(Out 0) --->> LumagenPro(In 1)
Vertex(Out 1) ---> RMC-1(In 1)

Lumagen(Out 2 18 Gbps) --->---> JVC600 (In 1)

RMC-1 (Out 1 18 Gbps) ---> LG C8 OLED
RMC-1 (Out 2 18GHz) --->---> JVC 600 (In 2) ... used to compare LPro vs. Custom Curves on JVC

Cable Notes:
---> = HDfury 18GHz 6ft Cable
--->> = Tributaries 18GHz 6ft Cable
--->---> = RUIPRO 10M 18GHz Fiber Cable

Last edited by Carbon Ft Print; 06-04-2019 at 10:07 AM.
Carbon Ft Print is offline  
post #4686 of 5233 Old 06-03-2019, 11:05 AM
AVS Forum Special Member
 
mikela's Avatar
 
Join Date: Nov 2002
Location: Los Angeles
Posts: 1,038
Mentioned: 46 Post(s)
Tagged: 0 Thread(s)
Quoted: 401 Post(s)
Liked: 611
mikela is online now  
post #4687 of 5233 Old 06-03-2019, 02:39 PM
AVS Forum Special Member
 
turls's Avatar
 
Join Date: Feb 2000
Location: Central IL
Posts: 4,982
Mentioned: 8 Post(s)
Tagged: 0 Thread(s)
Quoted: 509 Post(s)
Liked: 225
Quote:
Originally Posted by uderman View Post
Is there any room left on the fpga for 8K upscaling? I think 8K TVs will be very common in 2 years.
Hopefully, we'll see what is left after the current todo list is done. PiP well over 3 years waiting at this point...

If 8K is in the conversation before that is done, that's a little over the top IMO...

Matt
turls is offline  
post #4688 of 5233 Old 06-03-2019, 04:14 PM
AVS Forum Special Member
 
audioguy's Avatar
 
Join Date: Jun 2001
Location: Not far from Atlanta - but far enough!
Posts: 9,256
Mentioned: 92 Post(s)
Tagged: 0 Thread(s)
Quoted: 4716 Post(s)
Liked: 3500
Got a chance to do some A/B-ing with the latest DTM firmware. LOVE it. Great upgrade to my video chain.

I have a few folks who might be prospective Lumagen clients and would like to give them a demo comparing with and without DTM engaged.

Can anyone recommend a movie and scene that makes the comparison obvious even to the untrained eye, so that I don't have to search through a gazillion movies to find a few good examples.

Thanks
giomania and Craig Peer like this.
audioguy is online now  
post #4689 of 5233 Old 06-03-2019, 04:53 PM
.NET Solution Architect
 
SoulOfUniverse's Avatar
 
Join Date: Mar 2014
Location: Chigwell, Essex, UK
Posts: 844
Mentioned: 10 Post(s)
Tagged: 0 Thread(s)
Quoted: 591 Post(s)
Liked: 484
Quote:
Originally Posted by audioguy View Post
Got a chance to do some A/B-ing with the latest DTM firmware. LOVE it. Great upgrade to my video chain.



I have a few folks who might be prospective Lumagen clients and would like to give them a demo comparing with and without DTM engaged.



Can anyone recommend a movie and scene that makes the comparison obvious even to the untrained eye, so that I don't have to search through a gazillion movies to find a few good examples.



Thanks
I tried Dynasties it's the series about life and animals on earth, also planet earth II I believe the best examples to demo DTM

Sent from my GM1913 using Tapatalk

Video: Synology 416Play 24TB / OPPO UDP-203 / Zidoo X9S -> Lumagen Radiance Pro 4444 -> SONY VPL-VW760ES -> Elite Screen 135'' 16:9 1.1 Max White;
Audio: DENON X3500H -> Dali Zensor 7.1 Dolby Atmos (7, 1, E12F, Vokal, Dolby Alteco C1)
SoulOfUniverse is offline  
post #4690 of 5233 Old 06-03-2019, 04:58 PM
AVS Forum Special Member
 
audioguy's Avatar
 
Join Date: Jun 2001
Location: Not far from Atlanta - but far enough!
Posts: 9,256
Mentioned: 92 Post(s)
Tagged: 0 Thread(s)
Quoted: 4716 Post(s)
Liked: 3500
Quote:
Originally Posted by SoulOfUniverse View Post
I tried Dynasties it's the series about life and animals on earth, also planet earth II I believe the best examples to demo DTM
I don't have those but do have a couple of movies that might be great examples. "IMAX: Journey to Space" and "A Beautiful Planet". I will try those next time I am in the theater.

Thanks
audioguy is online now  
post #4691 of 5233 Old 06-03-2019, 05:56 PM
Member
 
Htnut2000's Avatar
 
Join Date: May 2004
Location: Australia
Posts: 131
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 41 Post(s)
Liked: 85
Quote:
Originally Posted by jabz View Post
Ever since I updated to Beta 112818 and then 011119 (Dynamic HDR tone mapping), I am having instances of video blanking/dropping out. It was pretty stable on my previous firmware which was 100317.
I have been having similar issues but cant pinpoint exactly which version started this. It seems to me that the recent firmware is more sensitive to cables.

I have talked to Jim and he believes it is an HDMI cable issue.

I have ordered Tributary 2m cables and a Ruipro 20m cable to replace my existing cables and hope that that solves the problem.

HDMI is such a pain!
giomania and mikela like this.
Htnut2000 is offline  
post #4692 of 5233 Old 06-03-2019, 06:19 PM
AVS Forum Special Member
 
audioguy's Avatar
 
Join Date: Jun 2001
Location: Not far from Atlanta - but far enough!
Posts: 9,256
Mentioned: 92 Post(s)
Tagged: 0 Thread(s)
Quoted: 4716 Post(s)
Liked: 3500
Just remember: HDMI means Highly Demonic Media Interface
Mark_H, GerryWaz and mikela like this.
audioguy is online now  
post #4693 of 5233 Old 06-03-2019, 06:20 PM
Senior Member
 
Join Date: Feb 2016
Posts: 394
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 183 Post(s)
Liked: 76
Quote:
Originally Posted by Htnut2000 View Post
I have been having similar issues but cant pinpoint exactly which version started this. It seems to me that the recent firmware is more sensitive to cables.



I have talked to Jim and he believes it is an HDMI cable issue.



I have ordered Tributary 2m cables and a Ruipro 20m cable to replace my existing cables and hope that that solves the problem.



HDMI is such a pain!


It’s true when I changed All my hdmi it work like I was laying about the issue i report every thing then works fine at the highest level 18gbps




Sent from my iPhone using Tapatalk
A7mad78 is online now  
post #4694 of 5233 Old 06-03-2019, 06:35 PM
AVS Forum Special Member
 
SJHT's Avatar
 
Join Date: May 2002
Location: SF Bay Area
Posts: 3,491
Mentioned: 11 Post(s)
Tagged: 0 Thread(s)
Quoted: 1046 Post(s)
Liked: 695
I remember watching the Solo SW 4K HDR movie prior to IM and now DTM. It was so dark, we almost put on the Blu-ray version from K vs. playing the 4K HDR version. Now, much easier to watch with these improvements. SJ
Mike_WI likes this.
SJHT is offline  
post #4695 of 5233 Old 06-03-2019, 10:02 PM
Senior Member
 
KarlKlammer's Avatar
 
Join Date: Apr 2010
Location: Germany
Posts: 306
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Quoted: 256 Post(s)
Liked: 247
DTM does a really good job with titles mastered at 1000 nits. But the more titles I watch that are mastered at >=4000 nits the more issues I notice.

How do you set the parameters for The MEG for example to prevent the picture from looking overexposed and flat and highlights from being totally clipped?
It's the same issue I noticed with the scene from Magnificent Seven I posted some time ago. Display Max Light set to 1800 improves the picture at the cost of general brightness in darker scenes and 1000 nits titles being unwatchable.

I downgraded to Beta 011119. And at least the higlights looked a little bit better than with the current Beta.

I hope this will be addressed with the upcoming version.

Projection: JVC DLA-NX9
VP/Calibration: Lumagen Radiance Pro, LightSpace CMS, x-rite i1 Pro 2, x-rite i1 Display 3

Last edited by KarlKlammer; 06-04-2019 at 12:36 AM.
KarlKlammer is offline  
post #4696 of 5233 Old 06-03-2019, 10:51 PM
AVS Forum Addicted Member
 
Craig Peer's Avatar
 
Join Date: Aug 2003
Location: Sacramento, CA
Posts: 15,913
Mentioned: 110 Post(s)
Tagged: 0 Thread(s)
Quoted: 6705 Post(s)
Liked: 7830
Quote:
Originally Posted by audioguy View Post
I don't have those but do have a couple of movies that might be great examples. "IMAX: Journey to Space" and "A Beautiful Planet". I will try those next time I am in the theater.



Thanks


Overlord, Guardians of the Galaxy II are two that come to mind.


Sent from my iPhone using Tapatalk
Craig Peer is offline  
post #4697 of 5233 Old 06-03-2019, 11:51 PM
aka jfinnie
 
Join Date: Aug 2015
Location: Norwich, UK
Posts: 3,013
Mentioned: 49 Post(s)
Tagged: 0 Thread(s)
Quoted: 2433 Post(s)
Liked: 1566
Quote:
Originally Posted by uderman View Post
Is there any room left on the fpga for 8K upscaling? I think 8K TVs will be very common in 2 years.
Which Lumagen Pro are you thinking of? I'm sure the 424x architecture only has a maximum of 18gbps simultaneous IO bandwidth which I think falls short for any of the 8K formats, so I don't think there is any possibility of those units going much above 4K.

I believe there is some chance the 444x could have input / output cards spanning two slots (4 ports) that could support 8K in and out.
bobof is offline  
post #4698 of 5233 Old 06-04-2019, 12:46 AM
Senior Member
 
jabz's Avatar
 
Join Date: Apr 2004
Location: New Zealand
Posts: 291
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 164 Post(s)
Liked: 70
Quote:
Originally Posted by Carbon Ft Print View Post
Same config as yours ... no drop outs ... took 5 wks to figure this out.
Awesome thanks for the detailed write up will try this out.
One note however the cables I'm using are as follows:

Monoprice SlimRun Fiber Optic AV HDR Cable 20m
Monoprice Certified Premium High Speed HDMI cable - 1.8m

Do I really need to change cables?

Sony VPL-VW520 | Elitescreens TT 135" 2.35:1 | Elitescreens TT 120" 16x9 | Prismasonic HD-6000F | Onkyo TX-RZ3100 | Oppo UDP-203 | PS4 PRO | ATV4K | LG OLED 65 C7 | Klipsch Reference RP-280 | Klipsch Reference RP-280C | Klipsch Reference RP-250S | Klipsch Reference RP-150M | Klipsch Reference R-115SW | Klipsch Reference R-140SA
jabz is offline  
post #4699 of 5233 Old 06-04-2019, 05:49 AM
AVS Forum Special Member
 
audioguy's Avatar
 
Join Date: Jun 2001
Location: Not far from Atlanta - but far enough!
Posts: 9,256
Mentioned: 92 Post(s)
Tagged: 0 Thread(s)
Quoted: 4716 Post(s)
Liked: 3500
My opinion, but 8K really does seem to be one of those "we can so we should" technologies. The arguments on both sides of the benefits (or lack) of 8K vs 4K are almost as vitriolic as political discussions. In my own experience (~13 feet from a 10 foot wide screen), the differences between properly shot 1080P and 4K PALE in comparison to the advantages of HDR vs SDR.

While I am probably in the small minority, 8K is of zero interest to me. But it will eventually be here and when it is, either the Lumagen will need to upgraded to handle it or there will need to be Lumagen Radiance Pro II. But I won't need to worry about that.
llang269 likes this.

Last edited by audioguy; 06-05-2019 at 04:48 AM.
audioguy is online now  
post #4700 of 5233 Old 06-04-2019, 07:02 AM
AVS Forum Special Member
 
Tom Bley's Avatar
 
Join Date: Jan 2001
Location: IL. USA
Posts: 3,405
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Quoted: 912 Post(s)
Liked: 869
Quote:
Originally Posted by audioguy View Post
In my own experience (~13 feet from a 10" wide screen), the differences between properly shot 1080P and 4K PALE in comparison to the advantages of HDR vs SDR.
You could probably get away with 480p with that distance and screen size.
Craig Peer likes this.
Tom Bley is online now  
post #4701 of 5233 Old 06-04-2019, 09:14 AM
QuadMersed in bass!
 
giomania's Avatar
 
Join Date: Nov 2001
Location: Chicago, Illinois
Posts: 3,867
Mentioned: 13 Post(s)
Tagged: 0 Thread(s)
Quoted: 620 Post(s)
Liked: 426
Quote:
Originally Posted by sjschaff View Post
Anyone out there with an Nvidia Shield TV, who is attempting to play source files that are HDR, through the Lumagen?



When I try to do so, I find that the advanced HDMI settings in the Nvidia, though they present an option for YUV 422 12-bit Rec. 709, never let me "keep" this setting. It reverts back to YUV 422 8-bit Rec. 709. Using OK button on the Lumagen remote shows that the source colorspace and Lumagen are different. Input shows RGB-HDR709 and output 422-SDR2020. By the way, this is for using CMS1 for all HDR source. Also, not using Auto-Convert for either CMS0 or CMS1.



The only way I can get this option in the Nvidia to "stick" is to alter the Lumagen Pro's input setting for the Nvidia. The specific setting is Video Limit. Changing from 9ghz or 9ghz Max to 1080p has the Lumagen working with the Nvidia to allow a set of options, which includes the color space I tried to pick. When I now pick the YUV 422 12-bit Rec. 709 the Nvidia suddenly asks if I want to keep it. I say yes, and now find that when I return to the advanced HDMI settings the "current" setting has been updated to reflect the change. Lumagen OK button now shows for input 422-HDR2020 and output 422-SDR2020 while playing HDR source. So, this all seems to suggest some sort of limitation or disagreement in the Nvidia with the Lumagen or configuration problem on my part in either/both devices.



By the way, I have enabled colorimetry in the Nvidia via the developer options, as described in prior posts for Nvidia Shield for colorspace switching.


Also, if anyone is using the 18 ghz cards in the Lumagen along with the Shield does this combination allow for 422 12-bit Rec 709 to work on the Nvidia?



I have a shield and 18 GHz input and output cards, so I can provide some feedback. However, I am confused why you are attempting to use YUV 422 12-bit Rec. 709 for HDR files (which I assume are 4K HDR). Did you mean to type "SDR files" instead of "HDR files"?

Mark
giomania is online now  
post #4702 of 5233 Old 06-04-2019, 09:27 AM
QuadMersed in bass!
 
giomania's Avatar
 
Join Date: Nov 2001
Location: Chicago, Illinois
Posts: 3,867
Mentioned: 13 Post(s)
Tagged: 0 Thread(s)
Quoted: 620 Post(s)
Liked: 426
Quote:
Originally Posted by audioguy View Post
Got a chance to do some A/B-ing with the latest DTM firmware. LOVE it. Great upgrade to my video chain.

I have a few folks who might be prospective Lumagen clients and would like to give them a demo comparing with and without DTM engaged.

Can anyone recommend a movie and scene that makes the comparison obvious even to the untrained eye, so that I don't have to search through a gazillion movies to find a few good examples.

Thanks
Maybe these scenes for setting up would be of use? Please forgive the formatting issues.

1) Mad Max Fury Road™ (2015) Max Mon = 4000, MaxCLL = 9919
▪ Examples of bright (specular) highlights in an overall low-APL scene.
• Chapter 03 / 0:28:37 Sand Storm: Fireball in the upper left; lightning in the upper right.
▪ Examples of extremely bright (specular) highlights.
• Chapter 03 / 0:28:29 Sand Storm: Car exploding in the air.
• Chapter 03 / 0:28:37 Sand Storm: Fireball in the upper left; lightning in the upper right.
• Chapter 03 / 0:38:13 Muzzle flash; a couple pixels in the 4400 Nit range.
• Chapter 11 / 1:46.59 Sunset in the desert.

2) The Martian™ (2015) Max Mon = 1100, MaxCLL = 0
▪ Examples of bright (specular) highlights in an overall low-APL scene.
• Chapter 02 / 0:33:35 Storm approaching.
• Chapter 21 / 1:19:08 Large setting sun with character sitting on a rock.
• Chapter 24 / 1:37:35 Sun peeking around dark mountains.

3) The Magnificent 7™ (2016) Max Mon = ????, MaxCLL = ????
▪ Examples of bright (specular) highlights in an overall low-APL scene.
• Chapter 3 / 0:12:01 Horseback rider cresting hill with sun in the background.
• MaxCLL = 1113, MaxY = 1752
• Chapter 03 / 0:16:00 Dimly lit bar with bright windows & doorway in the background.

4) Blade Runner 2049 (2018) Max Mon = ????, MaxCLL = 480
▪ A very dark movie with a MaxCLL = 480 Nits (Disc metadata incorrectly reports 182 Nits)
giomania is online now  
post #4703 of 5233 Old 06-04-2019, 09:28 AM
Advanced Member
 
sjschaff's Avatar
 
Join Date: Apr 2004
Location: Alameda, CA
Posts: 573
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 112 Post(s)
Liked: 44
Quote:
Originally Posted by giomania View Post
I have a shield and 18 GHz input and output cards, so I can provide some feedback. However, I am confused why you are attempting to use YUV 422 12-bit Rec. 709 for HDR files (which I assume are 4K HDR). Did you mean to type "SDR files" instead of "HDR files"?

Mark
I only have 9ghz cards in my Lumagen Pro. Kris Deering came by a few months ago to calibrate my Lumagen Pro to JVC RS500 setup. I will caution that we did not work on the Nvidia source at all. Just used UHD discs on my Panasonic 900 and previous JVC settings performed by another calibrator.

The reason for the particular setting is that I received this information from Kris. The recommendations came from a friend of his, as settings to use for the Nvidia Shield.

Here are the full details I received:

In the NVidia Shield Settings Menu:
1) Set the default GUI resolution: Go to - Settings > Display and Sound > Resolution > Set to 4K 59.940 Hz.
2) Set the default color space and resolution: Go to - Settings > Display and Sound > Advanced Settings > HDMI Settings > Choose 3840x2160 59.940 Hz YUV 422 12-bit Rec 709.
3) Next enable developers options: Go to - Settings > About > Build > Click seven times on build to become a developer (you will see a toast which will say you are now a developer).
4) Set color space switching: Go to - Settings > Developer Options > Colorimetry (set toggle to ON) > restart the NVidia Shield for changes to take effect. Colorimetry is under “HDMI” and is pretty far down the menu, there are a lot of options before it.
5) Restart the NVidia Shield.

In The Kodi Settings Menu:
1) Set Kodi to “Expert” mode: Go to - Settings > System > Click on the gear icon at the bottom of the list until it shows “Expert.”
2) Set Kodi to resolution switching: Go to - Settings > System > Display > Whitelist and then enable ALL of the resolutions displayed. Click “OK.”

Your experience and thoughts on this are appreciated. I can obviously also provide any other Lumagen settings or Nvidia as well, beyond what you see above. My communication with JRP suggests that the Lumagen is configurable to handle most anything and that it may well be a fault with the Nvidia at possibly a hardware level in complying with spec.
giomania likes this.

JVC RS500 - Stewart Firehawk - Lumagen Radiance Pro - Anthem D2V - Revel Salon speakers - SV Sound SB13 Ultra sub - Tivo/Nvidia Shield TV/Panasonic UB900



Last edited by sjschaff; 06-04-2019 at 09:32 AM.
sjschaff is offline  
post #4704 of 5233 Old 06-04-2019, 10:00 AM
AVS Forum Club Gold
 
Carbon Ft Print's Avatar
 
Join Date: Nov 2009
Location: FL
Posts: 608
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 362 Post(s)
Liked: 302
Quote:
Originally Posted by jabz View Post
Awesome thanks for the detailed write up will try this out.
One note however the cables I'm using are as follows:

Monoprice SlimRun Fiber Optic AV HDR Cable 20m
Monoprice Certified Premium High Speed HDMI cable - 1.8m

Do I really need to change cables?
A year or so ago, @jrp recommends Tributaries for 6-10ft lengths and RUIPRO for longer lengths. @jrp recommendation at that time had to do with how the cable handled the sharpness of the digitized waveforms associated with the Lumagen Pro (very fast rise times) ... and these cables handled them the best. Not sure if @jrp recommendation applied to both LPro's input and output, but I applied it to both input and output.

People on this thread have also had good luck with monoprice and blue jeans cables ... don't have those cables.
Carbon Ft Print is offline  
post #4705 of 5233 Old 06-04-2019, 02:12 PM
AVS Forum Special Member
 
Wookii's Avatar
 
Join Date: Aug 2008
Posts: 3,449
Mentioned: 57 Post(s)
Tagged: 0 Thread(s)
Quoted: 2893 Post(s)
Liked: 2095
Quote:
Originally Posted by KarlKlammer View Post
DTM does a really good job with titles mastered at 1000 nits. But the more titles I watch that are mastered at >=4000 nits the more issues I notice.

How do you set the parameters for The MEG for example to prevent the picture from looking overexposed and flat and highlights from being totally clipped?
It's the same issue I noticed with the scene from Magnificent Seven I posted some time ago. Display Max Light set to 1800 improves the picture at the cost of general brightness in darker scenes and 1000 nits titles being unwatchable.

I downgraded to Beta 011119. And at least the higlights looked a little bit better than with the current Beta.

I hope this will be addressed with the upcoming version.
Karl, for what it’s worth I don’t have any clipping issues in that Magnificent 7 scene with DTM on. I am a couple of FW behind at 021219:



Do you have time stamps for The Meg and we can compare those too? Thanks
Attached Thumbnails
Click image for larger version

Name:	980549A6-AA56-4253-856B-BA192C0CBDA4.jpg
Views:	139
Size:	82.5 KB
ID:	2575912  
KarlKlammer likes this.
Wookii is offline  
post #4706 of 5233 Old 06-04-2019, 02:44 PM
Senior Member
 
KarlKlammer's Avatar
 
Join Date: Apr 2010
Location: Germany
Posts: 306
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Quoted: 256 Post(s)
Liked: 247
Quote:
Originally Posted by Wookii View Post
Karl, for what it’s worth I don’t have any clipping issues in that Magnificent 7 scene with DTM on. I am a couple of FW behind at 021219:
Do you have time stamps for The Meg and we can compare those too? Thanks

Thanks for the screenshot. This looks OK to me. Which value did you set for Display Max Light?
If I remember it correctly, this is how it looked with 011119. But I have to check it again this weekend to be sure.



With The MEG, I have four examples:


00:18-00:20 -> Clipping
01:13 -> Clipping in red background
05:23 -> overexposed (too bright)
05:56 -> overexposed (too bright)



I have seen these issues in two different installations with different settings (my own and at a friend).



I attached four screenshots from VLC. They are just for illustration and not actually projected. I try to get some projected screenshots this weekend.
Attached Thumbnails
Click image for larger version

Name:	MEG_0_18.JPG
Views:	46
Size:	126.4 KB
ID:	2575922   Click image for larger version

Name:	MEG_01_13.JPG
Views:	44
Size:	49.9 KB
ID:	2575924   Click image for larger version

Name:	MEG_05_23.JPG
Views:	44
Size:	171.2 KB
ID:	2575926   Click image for larger version

Name:	MEG_05_56.JPG
Views:	40
Size:	138.8 KB
ID:	2575928  

Projection: JVC DLA-NX9
VP/Calibration: Lumagen Radiance Pro, LightSpace CMS, x-rite i1 Pro 2, x-rite i1 Display 3
KarlKlammer is offline  
post #4707 of 5233 Old 06-04-2019, 03:02 PM
AVS Forum Special Member
 
Wookii's Avatar
 
Join Date: Aug 2008
Posts: 3,449
Mentioned: 57 Post(s)
Tagged: 0 Thread(s)
Quoted: 2893 Post(s)
Liked: 2095
Quote:
Originally Posted by KarlKlammer View Post
Thanks for the screenshot. This looks OK to me. Which value did you set for Display Max Light?
If I remember it correctly, this is how it looked with 011119. But I have to check it again this weekend to be sure.



With The MEG, I have four examples:


00:18-00:20 -> Clipping
01:13 -> Clipping in red background
05:23 -> overexposed (too bright)
05:56 -> overexposed (too bright)



I have seen these issues in two different installations with different settings (my own and at a friend).



I attached four screenshots from VLC. They are just for illustration and not actually projected. I try to get some projected screenshots this weekend.
I have DML on 600, approx 150nits measured peak.

I will try and check those Meg shots tomorrow evening. When you say those screen shots are from VLC - do you mean they are grabbed from the source file?
Wookii is offline  
post #4708 of 5233 Old 06-04-2019, 03:12 PM
Senior Member
 
KarlKlammer's Avatar
 
Join Date: Apr 2010
Location: Germany
Posts: 306
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Quoted: 256 Post(s)
Liked: 247
Quote:
Originally Posted by Wookii View Post
I have DML on 600, approx 150nits measured peak.

I will try and check those Meg shots tomorrow evening. When you say those screen shots are from VLC - do you mean they are grabbed from the source file?

Yes, they are just grabbed from the source.
I have about 120 nits measured peak and used to set my DML to 700.
In the other installation I saw, DML was set to 300 (with 70 nits peak). The other settings were left to standard. That was even worse.

Projection: JVC DLA-NX9
VP/Calibration: Lumagen Radiance Pro, LightSpace CMS, x-rite i1 Pro 2, x-rite i1 Display 3

Last edited by KarlKlammer; 06-04-2019 at 03:16 PM.
KarlKlammer is offline  
post #4709 of 5233 Old 06-04-2019, 03:22 PM
Advanced Member
 
Lasalle's Avatar
 
Join Date: Aug 2005
Location: Sarasota, FL
Posts: 906
Mentioned: 19 Post(s)
Tagged: 0 Thread(s)
Quoted: 564 Post(s)
Liked: 419
Quote:
Originally Posted by Htnut2000 View Post
I have been having similar issues but cant pinpoint exactly which version started this. It seems to me that the recent firmware is more sensitive to cables.

I have talked to Jim and he believes it is an HDMI cable issue.

I have ordered Tributary 2m cables and a Ruipro 20m cable to replace my existing cables and hope that that solves the problem.

HDMI is such a pain!
I have several 2M Tributaries and a 25m Ruipro, they work flawlessly and I never have a handshake issue with them.
Lasalle is online now  
post #4710 of 5233 Old 06-04-2019, 05:23 PM
Advanced Member
 
uderman's Avatar
 
Join Date: Apr 2008
Location: MA
Posts: 516
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 122 Post(s)
Liked: 58
Quote:
Originally Posted by bobof View Post
Quote:
Originally Posted by uderman View Post
Is there any room left on the fpga for 8K upscaling? I think 8K TVs will be very common in 2 years.
Which Lumagen Pro are you thinking of? I'm sure the 424x architecture only has a maximum of 18gbps simultaneous IO bandwidth which I think falls short for any of the 8K formats, so I don't think there is any possibility of those units going much above 4K.

I believe there is some chance the 444x could have input / output cards spanning two slots (4 ports) that could support 8K in and out.
I don’t think 8K input will be necessary for a long time but 8K output. There are some 8K tvs already and in two years I believe all high end models will be 8K with hdmi 2.1.

Wanted:
HD-VMD Discs
Muse/Hi-Vision Discs - Mint/Complete Only!
uderman is offline  
Sponsored Links
Advertisement
 
Reply Video Processors

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