You could do YCbCr manual calibrations for SDR with your OPPO and Ted's calibration disk. I would submit that your first priority should be to purchase a decent colorimeter such as the I1 Display Pro (I1D3), either Retail or OEM. Trust me, even with a good pattern generator, the I1 Pro and Pro 2 are S-L-O-W and don't read the dark end very well. With a colorimeter, you gain speed and the ability to read much better down low. You would use your Pro 2 to enhance the colorimeter's accuracy by profiling the I1D3 to it.

Thanks, but I would like to find something that Calman can drive so I can let it happen automatically.

Then you are pretty much stuck with the more expensive spread, if you insist on YCbCr.

All 2018 LG OLEDs don’t perform very well with YCC patterns. That’s why I and all the guys I know use 16-255 RGB 8 bit patterns. Probably it’s the same with 2019 series. An RPi PGenerator is supported by all the most famous softwares and it’s bit perfect with RGB output. You can also use your laptop hdmi.

Do you have an example for 24hz on netflix?

As pattern generators are sending a static image for a considerable amount of time (in the order of seconds), why do they need to support 24 or 60 Hz if it's so expensive?

PGenerator + HD Fury Device = HDR10 RGB-Video Patch Generation

For users who want to generate bit-perfect HDR10 patch generation for their HDR10 calibration, using PGenerator which is bit-perfect with RGB output combined with an HD Fury device (for metatadata/avi injection) can be used.

Using the HD Fury GUI, the user has to add to custom HDR10 Metadata (Tick always to send REC.2020 flag):

Custom Metadata (0.005 Black / 1000 nits Peak): 87:01:1a:74:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:e8:03:32:00:e8:03:90:01

or

Custom Metadata (0.005 Black / 4000 nits Peak): 87:01:1a:b0:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:a0:0f:32:00:e8:03:90:01

About AVI InfoFrame, usually users get the code for AVI from AVTopController panel of CalMAN but the problem with latest display models is that they require the complete header to able to provide the correct color output.

Since there no selection in CalMAN for AVTopController for the output resolution/frame rate the user will use (its not complete code with header also), for that reason you have to modify the AVI Infoframe according to the resolution you will use:

82:02:0D:AE:00:E8:64:10:00:00:00 for 1080p60 RGB (VIC 16 is the decimal code for 1080p60)

82:02:0D:AE:00:E8:64:20:00:00:00 for 1080p24 RGB (VIC 32 is the decimal code for 1080p24)

82:02:0D:AE:00:E8:64:5D:00:00:00 for 2160p24 RGB (VIC 93 is the decimal code for 2160p24)

82:02:0D:AE:00:E8:64:51:00:00:00 for 2160p60 RGB (VIC 97 is the decimal code for 2160p60)

If the user will use the 'short AVI code' without header which CalMAN generates, while the patterns will be HDR10, the gamut readings will be totally wrong with high under-saturation of colors.

1. What EDID do I use?
2. Where do I enter the custom metadata? I'm assuming: HDR / AVI > CUSTOM HDR INJECTION and tick 'Enable custom HDR'.
3. Where do I enter the AVI Infoframe code? I'm assuming: HDR / AVI > CUSTOM AVI and tick 'Enable custom AVI'.
4. HDR / AVI is also where I tick the 'Forced On' box for BT.2020 OUT?
5. Do I select 'SCALING MODE' 'UP'?
6. Do I still need to set Lightspace to output a limited RGB range?
7. I believe 1 through 5 will be the same when using the Linker with a AVFoundry VideoForge Classic and/ or CalMAN Home for Panasonic?

Hi Paul,

1: Not required to change EDID. So just leave this on 'FIXED EDID?'
2,3,4: Yes
5: You don't want any scalling, as PGenerator will send 2160p24 directly. I take it that I need to set up PGenerator to do this? Like I did to get it to send 1080p50?
6: Patchscale 16-235 @ LightSpace Options.
7: Yes, only RGB signal from any generation (not use YCbCr)

Ted, thank you, much appreciated as ever.

Paul

AUTOMIX.

You set the resolution you like from generator, not from Fury and then you paste the correct per resolution custom AVI.

There no need to send 1080p50 for HDR10, send 2160p24 from PGenerator or 1080p24 from VF.

AUTOMIX.

You set the resolution you like from generator, not from Fury and then you paste the correct per resolution custom AVI.

There no need to send 1080p50 for HDR10, send 2160p24 from PGenerator or 1080p24 from VF.

Thanks for all the tips and help. Ted. But, is the above a typo

PGenerator Update has been released @ 28 November 2019

For update process information see: PGenerator Update

Just finished the update. For a small box like the RPI, it was a long update! Took over 30 minutes. I was watching off and on. There were a lot of elements to the update. I would like to thank Riccardo Biasi for his excellent selfless work.

PGenerator + HD Fury Device = HDR10 RGB-Video Patch Generation

For users who want to generate bit-perfect HDR10 patch generation for their HDR10 calibration, using PGenerator which is bit-perfect with RGB output combined with an HD Fury device (for metatadata/avi injection) can be used.

Using the HD Fury GUI, the user has to add to custom HDR10 Metadata (Tick always to send REC.2020 flag):

Custom Metadata (0.005 Black / 1000 nits Peak): 87:01:1a:74:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:e8:03:32:00:e8:03:90:01

or

Custom Metadata (0.005 Black / 4000 nits Peak): 87:01:1a:b0:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:a0:0f:32:00:e8:03:90:01

About AVI InfoFrame, usually users get the code for AVI from AVTopController panel of CalMAN but the problem with latest display models is that they require the complete header to able to provide the correct color output.

Since there no selection in CalMAN for AVTopController for the output resolution/frame rate the user will use (its not complete code with header also), for that reason you have to modify the AVI Infoframe according to the resolution you will use:

82:02:0D:AE:00:E8:64:10:00:00:00 for 1080p60 RGB (VIC 16 is the decimal code for 1080p60)

82:02:0D:AE:00:E8:64:20:00:00:00 for 1080p24 RGB (VIC 32 is the decimal code for 1080p24)

82:02:0D:AE:00:E8:64:5D:00:00:00 for 2160p24 RGB (VIC 93 is the decimal code for 2160p24)

82:02:0D:AE:00:E8:64:51:00:00:00 for 2160p60 RGB (VIC 97 is the decimal code for 2160p60)

If the user will use the 'short AVI code' without header which CalMAN generates, while the patterns will be HDR10, the gamut readings will be totally wrong with high under-saturation of colors.

Ted,
As always very helpful. I did my SDR calibration of my sony xbr940d a while ago but have not done HDR 4k (kept putting it off!). I use calman with a DVDO AVlab TPG and have an HDFury Linker too. Will these codes work for me and are there step by step instructions somewhere? I know calman has an hdr 10 workflow, I mean more of getting the patterns working with what step in the workflow.

Thanks,
BJBBJB

I may try the laptop, but am always nervous about driver and Windows mucking things up. I may look into the RPi Generator. I do have an Oppo 203 so I read that Ted's Disc on the Oppo should be bit perfect for YCC.

Tested the firetv stick 4k with ted’s patterns and 1080p 8bit 24hz sdr output.

1-3 digital errors.

Ycbcr 4:4:4 8 bit was bit perfect.

Hi, for DVDO AVLab TPG, set the output to 2160p24 8bit.

From CalMAN select RGB-Video, 10% Windows.

Using the HD Fury GUI, add that custom HDR10 Metadata (Tick always to send REC.2020 flag):

87:01:1a:74:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:e8:03:32:00:e8:03:90:01 (P3 Primaries / 0.005 Black / 1000 nits Peak / 1000 MaxCLL / 400 MaxFALL)

About custom AVI InfoFrame:

82:02:0D:AE:00:E8:64:5D:00:00:00 (2160p24 RGB-Video)

Ted,

Thanks! To help remind me how to enter all of this, I re-located this document. I assume other than the input strings themselves the rest applies. Hopefully this helps someone.

https://kb.portrait.com/help/hdfury-integral-4k60

There is a pdf somewhere too.

It says updated this year. Hopefully works with Linker vs. just original.
BJBBJB

All the custom metadata you will insert it using HD Fury GUI, not CalMAN.

With CalMAN it was not wolking the Integral 1 only with specific version of CalMAN until 2017.

Integration is broken after a software update.

HD Linker of any other newer HD Fury was never supported from CalMAN.

The AVTOP codes which CalMAN is generating for custom AVI are incomplete, they are not asking you for what resolution you will use and they don't contain the full header, so the colors will be a lot of under-saturated if you use CalMAN codes.

The codes I provided for custom AVI are full and accurate per each resolution [IMG class=inlineimg]/forum/images/smilies/smile.gif[/IMG]