HDR workflow question - where to find master display data?

Hi
i am trying to learn HDR workflow with UM4.6k. I know how to grade and output HDR in resolve (more or less) but i have many problems with uploading files to youtube. I grade on oled panasonic EZ1000, i know it is not ideal solution but offline files looks great in HDR, TV recognizes hdr without any problem. So i render files (rec2020, st2084) to DHxHR HQX 12bit, i can play those files via resolve and decklink straight to TV ad it looks awesome in HDR. To upload to YT i use hybrid, i render h265 mkv and put medadata into them.
Files than looks very nice on tv when i play them offline from disk. But on YT colors are ugly, highlights are clipped and looks wrong in general in HDR and SDR after YT internal conversion. I think, that it is because i dont know what shoud i put into Master display (i attached screenshot from hybrid). Could anybody could tell me where to find master display data for panasonic EZ1000? Is this can couse the problem? Thanks

You need to put what you graded your footage to which is your output color space in Resolve. Most likely it's P3 or Rec.2020 (or maybe just Rec.709)
Values looks strange, but they are just multiplied by constant value.

SMPTE ST 2086 mastering display color volume SEI info, specified as a string which is parsed when the stream header SEI are emitted. The string format is “G(%hu,%hu)B(%hu,%hu)R(%hu,%hu)WP(%hu,%hu)L(%u,%u)” where %hu are unsigned 16bit integers and %u are unsigned 32bit integers. The SEI includes X,Y display primaries for RGB channels and white point (WP) in units of 0.00002 and max,min luminance (L) values in units of 0.0001 candela per meter square. Applicable for HDR content.

Example for a P3D65 1000-nits monitor, where G(x=0.265, y=0.690), B(x=0.150, y=0.060), R(x=0.680, y=0.320), WP(x=0.3127, y=0.3290), L(max=1000, min=0.0001):

G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)

For Rec.2020:
G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)

Don't use full range (pc), better to stick with limited as in case some app/hardware doesn't read this *** it will use limited by default.