Quantcast

Dolby Vision, including HDR10 conversion w/ DTM on Projectors? Yes!

kitschcamp

Active Member
I’ve done a fairly quick measurement on my screen and projector, and used the new calculation tool, so it won’t be perfect on all Sony 760/885s, but it does tame the red push significantly on mine.

Code:
eb:01:46:D0:00:45:03:90:92:3E:13:97
Red .6304, .3166
Green .2835, .6196
Blue .1670, .0901

Measurements done with Lightspace and an i1 OEM.
 

raz77

Well-known Member
Yes, just paste it in. Don’t worry about trailing zeros. It’s the Integral 2 you can’t change it on.

Looking very good, using the 350 nit setting with Dominic chans colour profile LLDV_A1F for JVC projector. There is no need for me to change to a NX7 or get a Lumagen. This just gets better, getting allot more life out of an amazing projector.
 

Dca78

Standard Member
I’ve done a fairly quick measurement on my screen and projector, and used the new calculation tool, so it won’t be perfect on all Sony 760/885s, but it does tame the red push significantly on mine.

Code:
eb:01:46:D0:00:45:03:90:92:3E:13:97
Red .6304, .3166
Green .2835, .6196
Blue .1670, .0901

Measurements done with Lightspace and an i1 OEM.
THANKS!!!

Is it possible for you to measure the difference between source with and without the red tint. To be able to compute a more generic code?

Your code for target nits is 90.. seems to be different from the default target 900 nits ( 80 @bmandra). Which value did you use for target nits?
 

raz77

Well-known Member
Just tried 500 nit string, not sure which I prefer, possibly the 500. Colours and detail very good
 

raz77

Well-known Member
Just watching edge of tomorrow Blu-ray via Sony x800m2 Dolby vision, wow, best it has ever looked.
 

kitschcamp

Active Member
Is it possible for you to measure the difference between source with and without the red tint.
I’ll see what I can do - his nibs takes the dog out for a walk shortly, so I’ll try then.
Your code for target nits is 90.. seems to be different from the default target 900 nits ( 80 @bmandra). Which value did you use for target nits?
I thought I’d left it on the default, but I’ll check in an hour or so.
 

bmandra

Member
One thing that was pointed out on the other forum is that until/spreadsheet isn’t enforcing range limits for values.

Here are the limits for each value:

Nits: 0 - 1650
Rx: 0.625 - 0.746
Ry: 0.250 - 0.371
Gx: 0.000 - 0.496
Gy: 0.500 - 0.996
Bx: 0.125 - 0.152
By: 0.031 - 0.059

I uploaded an updated version of the until over there, if anyone wants to grab it and post it here feel free. The limits are only enforced in the app and not the spreadsheet, so use spreadsheet and previous version with caution as incorrect values for Bx or By can corrupt the values for Rx and Ry.
 

HarperVision

Active Member
I’ve done a fairly quick measurement on my screen and projector, and used the new calculation tool, so it won’t be perfect on all Sony 760/885s, but it does tame the red push significantly on mine.

Code:
eb:01:46:D0:00:45:03:90:92:3E:13:97
Red .6304, .3166
Green .2835, .6196
Blue .1670, .0901

Measurements done with Lightspace and an i1 OEM.
Yes this seems to corroborate what I said awhile ago regarding the red tint being caused by a mismatch of peak greyscale lumens vs peak color lumens.


Dang I haven’t been able to test these new DV strings. My sister and niece have come to visit and all my spare time is being spent with them, of course. Priorities after all! 😊

Keep it coming, this is great!
 

kitschcamp

Active Member
I thought I’d left it on the default, but I’ll check in an hour or so.
That string was generated with 1000 nits, I’ve just corrected it to 900 nits.

Code:
eb:01:46:d0:00:45:03:80:92:3e:13:97
Just waiting for my i1 to warm up to try and get the other readings for you.
 

Dca78

Standard Member
That string was generated with 1000 nits, I’ve just corrected it to 900 nits.

Code:
eb:01:46:d0:00:45:03:80:92:3e:13:97
Pay attention to your blue value

your values
Red .6304, .3166
Green .2835, .6196
Blue .1670, .0901

limit reported by @bmandra

Nits: 0 - 1650
Rx: 0.625 - 0.746
Ry: 0.250 - 0.371
Gx: 0.000 - 0.496
Gy: 0.500 - 0.996
Bx: 0.125 - 0.152
By: 0.031 - 0.059
 

bmandra

Member
Pay attention to your blue value

your values
Red .6304, .3166
Green .2835, .6196
Blue .1670, .0901

limit reported by @bmandra

Nits: 0 - 1650
Rx: 0.625 - 0.746
Ry: 0.250 - 0.371
Gx: 0.000 - 0.496
Gy: 0.500 - 0.996
Bx: 0.125 - 0.152
By: 0.031 - 0.059
Make sure you’re calculating correctly... By will never be decoded higher than 0.059, however when creating the string if the value for Bx or By exceeds the limits it will change the values for Rx and Ry when using either the spreadsheet or first version of app.
 

kitschcamp

Active Member
Readings in DV mode. NB: Not taken at same time as ones used to calculate string, but taken together just now, so the sensor and projector are not in exactly the same condition as the time the string was calculated but are self-consistent.

Original A1 based string
Red .6216, .3128
Green .2879, .6503
Blue .1516, .0720

New string
Red .6324, .3125
Green .2880, .6552
Blue .1653, .0788
 

kitschcamp

Active Member
Make sure you’re calculating correctly... By will never be decoded higher than 0.059, however when creating the string if the value for Bx or By exceeds the limits it will change the values for Rx and Ry when using either the spreadsheet or first version of app.
Ok, so should I put false limits in, or has the string been calculated “correctly”? I used the app from this thread. Those are the values my i1 and Lightspace reported :/
 

Dca78

Standard Member
Readings in DV mode. NB: Not taken at same time as ones used to calculate string, but taken together just now, so the sensor and projector are not in exactly the same condition as the time the string was calculated but are self-consistent.

Original A1 based string
Red .6216, .3128
Green .2879, .6503
Blue .1516, .0720

New string
Red .6324, .3125
Green .2880, .6552
Blue .1653, .0788
Big thanks for your measurements
 

kitschcamp

Active Member
Ok, I’ve recoded it for the limits and have got a new string. Haven’t taken any measurements yet, just going to sit down and watch a few things and see what it looks like. The Blu-Ray UFO looks a lot better than the original string, and Prince of Darkness UHD just looks heavily tanned rather than severely sunburnt. The latter film is a real oddball. It is by far the most red-pushed film I’ve ever seen on UHD whether in HDR10 or Dolby Vision (including on my LG OLED which supports Dolby Vision). It looks about the same for reds in HDR10, OLED DV and Sony corrected DV.

Code:
eb:01:46:d0:00:45:03:80:92:3e:0f:8f
 

TimHuey

Active Member
Yes this seems to corroborate what I said awhile ago regarding the red tint being caused by a mismatch of peak greyscale lumens vs peak color lumens.


Dang I haven’t been able to test these new DV strings. My sister and niece have come to visit and all my spare time is being spent with them, of course. Priorities after all! 😊

Keep it coming, this is great!
Hurry up and get back, your missing all the fun.
 

raz77

Well-known Member
Ok, I’ve recoded it for the limits and have got a new string. Haven’t taken any measurements yet, just going to sit down and watch a few things and see what it looks like. The Blu-Ray UFO looks a lot better than the original string, and Prince of Darkness UHD just looks heavily tanned rather than severely sunburnt. The latter film is a real oddball. It is by far the most red-pushed film I’ve ever seen on UHD whether in HDR10 or Dolby Vision (including on my LG OLED which supports Dolby Vision). It looks about the same for reds in HDR10, OLED DV and Sony corrected DV.

Code:
eb:01:46:d0:00:45:03:80:92:3e:0f:8f

Hi what projector have you tried this on? At the moment I am using this thread on the JVC x7900 with good results.

eb:01:46:d0:00:45:03:60:86:60:76:8f

Loving the work you guys are doing with the new strings and keep us all updated with new ones to try.
 

bmandra

Member
Hi what projector have you tried this on? At the moment I am using this thread on the JVC x7900 with good results.

eb:01:46:d0:00:45:03:60:86:60:76:8f

Loving the work you guys are doing with the new strings and keep us all updated with new ones to try.
At this point I don’t think there will be many new strings to try.

If you’re using a JVC projector just use the default string with the A1 color profile Dominic created. Then just tweak max nits to your liking.

If you are using another projector, use the utility to create a custom string that matches the primaries of your calibration and tweak the max nits to your liking.
 

kitschcamp

Active Member
Hi what projector have you tried this on?
My string is for the Sony 760/885. It's based on my calibrated projector.
 

Dca78

Standard Member
My string is for the Sony 760/885. It's based on my calibrated projector.
Finally I revert back to the original A1 LLDV (with 900 nits).
Applying your code have actually generated the red tint image ;-). Now I know I don’t have this problem with my current settings.
Keep the default 900 nits is still the best result on my installation.
I will have soon the possibility to get my primaries of calibration and will see if I can still improve.
So finally, it is not so complex to configure the vertex 2 to make it work and my 760. But Dave told us, it requires time !
 

pj

Well-known Member
Could I please check that this is dv working correctly please (it all seemed too easy so far!) it looks great and it's showing dv on screen and on the vertex/atv4k/Sony x800m2
Tv through sky looks to be normal too I have got to have done something wrong somewhere 😂 thanks I did it thru the ios bluetooth app and denon 7200 and epson 9300 projector do I need to do it through the windows app to change the tx info to Sony a1? Even if it appears to ge working whilst showing epson edid and dv
So
DA4D7E9E-382B-4A09-AB16-D5DA25BC7994.jpeg
27C73006-1A73-4EEE-B096-788B877D45F9.jpeg

99E5878D-04B1-4A66-8597-1211D39CDCE3.jpeg

E34F2319-3D1C-487D-AEAC-283D8D431354.jpeg
 

bmandra

Member
Could I please check that this is dv working correctly please (it all seemed too easy so far!) it looks great and it's showing dv on screen and on the vertex/atv4k/Sony x800m2
Tv through sky looks to be normal too I have got to have done something wrong somewhere 😂 thanks I did it thru the ios bluetooth app and denon 7200 and epson 9300 projector do I need to do it through the windows app to change the tx info to Sony a1? Even if it appears to ge working whilst showing epson edid and dv
So View attachment 1259269View attachment 1259267
View attachment 1259270
View attachment 1259272
Looks like it’s all correct to me.
 

pj

Well-known Member
I just spotted that the projector is saying it's receiving SDR if I manually change it from auto HDR to manual it looks even better 👍👍
Should the tx on the vertex display be saying it's the Sony A1? I've set it in the custom edid section but it still gives the tx details as my epson edid? Thanks again 👍👍
 

bmandra

Member
I just spotted that the projector is saying it's receiving SDR if I manually change it from auto HDR to manual it looks even better 👍👍
Should the tx on the vertex display be saying it's the Sony A1? I've set it in the custom edid section but it still gives the tx details as my epson edid? Thanks again 👍👍

The Tx should always be what’s physically connected.
 

Trending threads

Latest News

Micro LED TV alternative to modular design on the way?
  • By Andy Bassett
  • Published
Musical Fidelity announces M8xi integrated amp
  • By Andy Bassett
  • Published
Sky announces price rises for UK
  • By Andy Bassett
  • Published
LG Display OLED panel production below forecasts
  • By Andy Bassett
  • Published
Panasonic launches SC-HTB600 and SC-HTB400 soundbars
  • By Andy Bassett
  • Published
Top Bottom